#015: The Rules No One Questions: The Hidden Cost of Extra Processing
A few years ago, I visited a studio working with a well-known retailer. Their production workflow was complex partly because of a set of rules governing how outfits could be styled on set.
These rules dictated which brands could be paired and which combinations were off-limits. Stylists had to work within these constraints, with the system automatically flagging any violations.
At first glance, it seemed logical—ensuring brand consistency and avoiding conflicts. But something about it felt… outdated. So, I asked a simple question: Do these rules still apply?
No one in the studio knew.
These rules had been in place for years, built into the system, embedded in their processes. After a quick conversation with the retailer, the answer became clear:
The rules were obsolete. The client no longer required them, yet they had been shaping the studio’s production for years.
This isn’t an isolated case. In fact, it’s one of the most common types of waste I see in studios.
And it often goes unnoticed.
The Hidden Cost of Extra Processing
Since starting Content Insider, I’ve written about two major types of studio waste: complexity and rejections.
Today, we need to discuss the third: extra processing—anything that doesn’t add value to the final result.
(Imagine a customer is paying for every single step in your workflow. Would they be willing to cover the cost of this? If not, it’s probably extra processing.)
Extra processing happens when studios follow outdated workflows, apply unnecessary steps, or enforce rules that no longer serve a purpose.
And just like that studio's styling restrictions, these inefficiencies aren’t questioned until someone actively challenges them.
Where does extra processing come from?
- Legacy Decisions. Rules and workflows created years ago that no one remembers the reason for.
- Over-Engineering. Workflow steps designed for extreme precision that add no value in most cases.
- One-Size-Fits-All Processes. Treating every job, asset, product, or scenario the same instead of adapting workflows to what’s actually needed.