Sitemap
Chad Knight

Chad Knight

3D Workflow Strategy | Former Head of 3D Footwear Design @Nike | CEO, Super Digital

Footwear’s 3D Tower of Babel: Why Your Teams Keep Rebuilding the Same Shoe

6 min readNov 24, 2025

--

Press enter or click to view image in full size

By Chad Knight

If your teams are constantly rebuilding the same 3D model, the problem is not workflow. It is the collision of three fractured 3D paradigms.

Three industries invented and advanced 3D technology in isolation for far too long. Inevitably they created a Tower of Babel.

Entertainment built polygons for screens. Engineering built surfaces for manufacturing. Medical built voxels for imaging and simulation.

For forty years these paradigms never needed to talk to each other. In most companies they are still barely aware of one another.

Then footwear came along and needed to merge all three at once inside an already complex product pipeline.

Footwear needs a 3D Legend to decipher this twisted landscape.

The Hidden Translation Problem

Your design team says “3D model.” Your engineering team says “3D model.” Your innovation team says “3D model.” Your sales team says “3D model.” Your marketing team says “3D model.”

They believe they are speaking the same language. But they are not.

When entertainment invented 3D for movies, they optimized for how things look on screens. When engineering invented 3D for manufacturing, they optimized for how things get made in factories. When medical invented 3D for diagnostics, they optimized for simulating physical reality.

Each industry developed its own vocabulary, file formats, and fundamental assumptions about what “3D” means. A “mesh” in entertainment has nothing to do with a “mesh” in engineering. “Resolution” means pixel density to your designers and manufacturing tolerance to your engineers. “Accuracy” is not even the same concept between teams.

This is your Tower of Babel. Everyone is speaking “3D,” but they are speaking three different languages that happen to use the same words.

All of this is before you even touch the confusion piled on by buzzwords like parametric, generative, and computational, which most teams use as loose synonyms even though they describe very different ways of creating geometry.

Why Footwear Gets Hit Hardest

A game studio only needs entertainment 3D. They never manufacture anything.

A mold shop only needs engineering 3D. They do not render for consumers.

A sports lab only needs medical 3D. They scan, they do not design.

But a single shoe requires:

  • Entertainment 3D for marketing renders, e-com, and virtual try on
  • Engineering 3D for lasts, molds, and manufacturing
  • Medical 3D for material testing, foot scanning and fit analysis

In footwear, that medical logic shows up every time you capture a foot with a scanner or simulate the pressure distribution in an airbag. You are applying clinical imaging thinking to consumer bodies, then trying to connect that data to creative design and engineering geometry.

No other industry faces this collision of all three paradigms at the same time. You are trying to connect technologies that were never meant to connect, built by industries that never needed to communicate.

Your hiring pool comes from those single paradigm industries. Your designer came from gaming or film and only knows polygons. Your engineer came from automotive or aerospace and only knows surfaces. Your innovation lead came from medical or research and only knows voxels. Job postings for 3D experts are not filled with illogical info and reqs

Nobody on your team has worked across all three because no other industry requires it.

What This Costs You

Here is what happens on every single product.

Design creates a beautiful 3D model in Cinema 4D or Blender. It is made of polygons, perfect for rendering and useless for manufacturing.

Engineering cannot use it. Product communication gets compressed into 2D. They rebuild the entire shoe from scratch in Rhino or SolidWorks using surfaces, perfect for manufacturing and useless for marketing renders.

Get Chad Knight’s stories in your inbox

Join Medium for free to get updates from this writer.

Manufacturing gets the engineering file but needs different tolerances and details. They rebuild critical components again.

Meanwhile, innovation has foot scan data that does not integrate with either design or engineering systems. Marketing needs renders but cannot use engineering files. E commerce needs lightweight models that require another rebuild.

Three teams. Same shoe. Zero compatibility.

The expensive part is not the software licenses. It is the human hours spent rebuilding the same geometry three times because nobody realized you are dealing with three fundamentally incompatible types of 3D.

Across a full season, redundant rebuilds can easily consume forty to sixty percent of 3D labor hours on a given product line. That is wasted budget masquerading as normal process.

Why Your Platform Strategy Will Not Fix This

Every quarter, another vendor promises to solve your “3D problem” with a unified platform.

They cannot.

That vendor comes from one of those three industries. Their geometry kernel is built for a single paradigm, and the math under it does not support the other primitives.

An entertainment based platform will never give you manufacturing grade precision. An engineering platform will never give you production ready marketing renders. A medical platform will never give you flexible creative design.

When they promise “complete 3D workflows,” they mean complete for their paradigm. They are not lying. They genuinely do not see that the other paradigms exist as different mathematics, not just different file formats.

The consultants you hire to evaluate these platforms carry the same blind spot. They grew up in one industry. They judge everything through that lens. They keep recommending solutions that work perfectly for one third of your needs and quietly ignore the other two thirds.

The Integration Points That Break

The breakdowns happen at predictable boundaries.

  • Design to engineering
    “Convert the model for manufacturing” means completely rebuilding it, because polygons and surfaces are mathematically incompatible. Data loss, manual rebuild, and schedule risk all show up here.
  • Engineering to marketing
    “Send the file for renders” means rebuilding again. Manufacturing surfaces are built for tolerances and tooling, not for quad edge flow, UVs, and Sub D. Engineering ships an ideal digital twin. Marketing needs a virtual twin that looks perfect when it shows real imperfections. The gap between those two purposes is where the extra work lives.
  • Scanning to design
    “Use the foot scan data” means manual interpretation, because voxel data does not translate to either polygons or surfaces. The cost is fit risk and untested assumptions about how the shoe meets the body.

Every time someone says “just convert the file,” they are acknowledging without understanding that conversion means destruction and rebuilding, not translation.

Here is a concrete example.

A designer sculpts a knit upper in Blender for a hero campaign. To tool that upper, an engineer rebuilds it as NURBS surfaces in Rhino so that molds can be cut. To compare that upper to real feet, an innovation team samples both the molded shape and foot scans into voxels for analysis. Three geometry paradigms, three rebuilds, one shoe.

What Actually Works

Stop trying to force one platform to do everything. That is like forcing everyone to speak Latin. It looks universal on paper and fails in practice.

Start by mapping where paradigm boundaries naturally exist in your workflow. Design will always use polygons. Engineering will always use surfaces. Scanning will always produce voxels. These are not technology choices, they are mathematical requirements.

The solution is not eliminating boundaries, it is managing them. Know where translations must happen. Build buffers for rebuild time. Put specialists in place who understand both sides of each boundary.

Most important, get leadership that can see all three paradigms at once. When executives understand that “3D” means three different things, they stop expecting seamless integration and start planning for managed translations.

Where This Goes Next

I spent twenty years navigating all three paradigms at Nike, Vans, and DC Shoes. I watched this pattern burn millions in redundant work while executives kept buying “solutions” from vendors who could only see one-third of the problem.

The companies that win do not have better platforms. They have leadership that understands “3D” is three incompatible languages that require deliberate translation.

Your first step is not new software. It is diagnosis — mapping where paradigm boundaries create expensive rebuilds in your specific pipeline.

I help footwear executives see these boundaries clearly and design workflows that acknowledge geometric reality instead of fighting it. We test solutions with your actual data, not vendor demos.

If your teams are rebuilding the same shoe three times, you are not alone. But you are wasting forty to sixty percent of your 3D labor on a problem that is hiding in plain sight.

Ready to stop the rebuilds? Let’s map where your geometry breaks.

Chad Knight
Former Head of 3D Design, Nike
CEO, Super Digital LLC

--

--

Chad Knight
Chad Knight

Written by Chad Knight

3D Workflow Strategy | Former Head of 3D Footwear Design @Nike | CEO, Super Digital