Years ago, at a major global studio, I received a joke trophy for submitting the most pipeline tickets in a year.
Everyone laughed. I laughed, too. I was the squeaky wheel.
Looking back, that trophy captured something I did not fully understand at the time: sometimes the person creating the most visible friction is also the person mapping the system’s hidden costs.
Those tickets were not complaints about personal preferences. Many were deep investigations into motion blur consistency, DCC mismatches, quaternion conventions, rendering handoffs, publishing logic, and the small operational failures that quietly consume artist time.
By addressing those bottlenecks instead of endlessly hacking around them, we helped artists spend more time on the work itself and less time fighting the system.
I know what a healthy system feels like.
One of the production experiences I remain most proud of was working on DUNE. Not because it was easy. It was not. The work was complex, technical, artistic, and large-scale. But what made that experience memorable was something quieter: the system around the work supported the artists.
The hardest problems were mostly the right problems: creative judgment, simulation quality, technical execution, and shot delivery. We were not spending half the day fighting the operating system around the work.
Across VFX, animation, and games, we often normalize waste: waiting on preventable tool failures, reconstructing decisions from private conversations, tracking complex work in disconnected spreadsheets, performing manual version archaeology, and asking artists to compensate for workflow gaps that should have been designed out of the system.
Over time, I have become more interested in the difference between studios that deliver because the system works, and studios that deliver because talented people quietly compensate for the system.
Both can ship. Both can hit deadlines. Both can appear healthy from the outside.
But one builds capability while the other consumes it.
A studio’s real capability is not measured only by whether the show shipped. It is measured by how much invisible human compensation was required to ship it.
Finding Language for Production Scars
For years, I understood these issues through production experience: lost artist time, repeated handoff failures, unclear ownership, avoidable rework, undocumented decisions, and burnout.
My recent MIT Sloan coursework did not replace my production experience. It helped me translate it.
It gave me better language for patterns I had already seen across production floors: hidden rework, weak feedback loops, local workarounds, unclear decision rights, and the difference between shipping a project and strengthening the system that shipped it.
Nelson Repenning and John Sterman’s work on process improvement and capability traps describes a dynamic many production leaders will recognize: under pressure, organizations often reward firefighting and heroic recovery while underinvesting in the improvements that would prevent the same problems from recurring.
In creative production, that trap often hides inside success.
The show shipped.
The external markers of success were there.
The dashboard turned green.
But the dashboard may not show the hidden rework, private workarounds, unclear handoffs, repeated decision loops, or senior-level compensation required to get there.
Pipeline is only one part of it. The larger issue is the studio operating system: workflow design, communication loops, decision rights, production visibility, tooling adoption, training, and the way feedback from the floor is handled.
The goal is not to force every studio into one “correct” way of working. Every company has different clients, budgets, tools, culture, and constraints. The goal is to create a serious feedback loop where the people closest to the work can help leadership see what the dashboard cannot: where time is leaking, where decisions are unclear, where tools are shaping behavior, and where talented people are quietly compensating for the system.
Not every complaint is correct. Not every studio can redesign a workflow overnight. Constraints are real: budget, schedule, client needs, legacy tools, staffing, and production pressure all matter. But those constraints are exactly why the feedback loop matters. Without it, teams keep paying the same hidden cost over and over.
Across the industry, I have seen this friction show up in four recurring patterns.
1. The Inverted Workflow
In a healthy system, the people closest to the work help define the workflow. Engineering, pipeline, production, and artists collaborate around how the work actually needs to move.
In an inverted workflow, tool limitations or implementation convenience begin to dictate the creative process. Artists become testers of a system they did not help design.
This can show up as rigid publishing rules, missing iteration paths, hardcoded review steps, or workflows where a small creative adjustment requires a technical ticket instead of an artist’s decision.
Leadership should notice when “the tool requires it” becomes the default answer. That is often the moment when workflow has stopped serving production and started shaping it.
2. The Black Box Production
Another common pattern is production visibility without production intelligence.
A studio may have powerful tracking software, but if the real truth lives in scattered spreadsheets, private conversations, undocumented calls, or individual memory, supervisors cannot plan with confidence.
This often appears when shot status, bidding assumptions, client notes, and schedule changes all move through different channels. The system may contain data, but the team still does not have a shared operational truth.
Upstream handoffs become unclear. Client decisions become hard to trace. Approved work becomes difficult to distinguish from assumed work. The team spends energy reconstructing reality instead of moving the show forward.
3. Decision Rights Drift
Creative change is part of production. But if ownership is unclear - who can approve, who can push back, who protects scope, who translates creative ambition into schedule and budget impact - teams absorb change without understanding its cost.
This often appears when creative notes, production approvals, and scope decisions move through different people without a shared decision model. Everyone is trying to be helpful, but no one is clearly accountable for the tradeoff.
The result is not always visible conflict. Sometimes it is quiet overextension: extra versions, unclear priorities, repeated rework, and teams absorbing change that was never properly evaluated.
4. The Heroic Compensation Loop
The most dangerous pattern is when senior people compensate so effectively that leadership never sees the cost.
Leads absorb ambiguity. Supervisors patch gaps. Artists wait, retry, rebuild, and stay late. Production keeps moving because experienced people quietly create workarounds around the system.
That competence can become invisible. The show ships, the dashboard turns green, and the organization learns the wrong lesson: that the system worked, rather than that people protected it from failing.
The absence of visible failure is not the same thing as operational health.
The Leadership Pivot
I have had to evolve in how I communicate this kind of feedback.
Earlier in my career, I sometimes believed that being technically right was enough. It is not. Delivery matters. Timing matters. Emotional temperature matters. A valid signal can be lost if it arrives as frustration rather than clarity.
But the opposite mistake is just as dangerous: dismissing repeated operational feedback because it is uncomfortable, badly timed, or coming from someone who has become tired of saying the same thing.
In many cases, that frustration is not the problem. It is evidence that the problem has been allowed to persist too long.
Before dismissing repeated friction from the floor, leaders should ask:
- What cost is this person seeing that our dashboard does not capture?
- Where are artists compensating for unclear workflows, missing ownership, weak tooling, or undocumented decisions?
- What workarounds have become normal simply because the team is good at surviving them?
- Are we measuring only delivery, or are we measuring the human compensation required to deliver?
Then do one practical thing: bring the right people into the same room and map the friction together. Not as a complaint session. As operational diagnosis.
Senior friction is often a measurement system. If leaders learn how to read it, they can protect quality, margins, and people before the show turns into a rescue mission.
Great shots are not made by talent alone. They are made by talented people working inside systems that let them do their best work.