I've sat in a lot of agency ops reviews where the conclusion was "we need a better system." A new brief template. A new approval workflow. A new project management tool. Most of the time, that's not the problem.
The problem is the system already exists - and nobody's following it.
The brief gets signed off verbally because the client's "in a rush." Feedback is supposed to come back in one consolidated round but arrives in five scattered Slack messages over a week. None of that is a design flaw. It's a discipline issue.
Why this happens
Creative agencies are relationship businesses. Pushing back on a client you like - "we need that in writing before we start" - feels awkward. Holding a team accountable to a workflow feels like it clashes with a culture that prizes flexibility and instinct over rigidity.
So people keep taking the easy option instead of following the process, until it stops being a rule and just becomes something everyone agrees to ignore.
Why more process makes it worse
Add a new tool or template, and you haven't fixed the enforcement problem - you've just given people something new to skip.
Agencies that cycle through project management software every 18 months usually have this exact issue. I've seen it play out almost identically each time: the team migrates from Asana to Monday to ClickUp, everyone gets a fresh onboarding session, and for two or three weeks the new tool actually gets used properly. Then a big client asks for a "quick turnaround," someone skips the sign-off step to save time, nothing bad happens immediately, and that becomes the new normal. Six months later, someone's back in a vendor demo for tool number four.
The workflow gaps look identical each time, just with a different piece of software behind them. The tool was never the constraint. The follow-through was.
This pattern shows up everywhere ops gets treated as a technology question instead of a behavioural one. A new tool arrives with real optimism, gets set up, even gets used well for the first few weeks. Then old habits creep back in, because nothing about switching software changed who was willing to hold the line when someone tried to skip a step.
Why it has to be the founder
The Ops Lead can design a good process, document it, train the team on it, chase people about it. But only the founder can make it non-negotiable. When leadership skips it for a big client, everyone reads that as permission to do the same.
At my last agency, we ran a consistent way of working across five internal studios - no exceptions by client size or studio reputation. It worked not because the system was clever, but because I had backing from the very top: the chairman supported it publicly and held people to it when it got tested. That's what made consistency possible across five local cultures. Without it, the process would have eroded studio by studio, the way it always does when enforcement is left to someone without the authority to make it stick.
What that backing actually looked like in practice
- When an account director tried to skip sign-off for a "VIP" client, the chairman backed the process publicly in that conversation - not just in a private aside afterward.
- Exceptions were made visible and explained, so the team didn't have to guess whether the rule still applied.
- The Ops Lead was empowered to escalate to the chairman directly, rather than having to build a business case every time someone tested the line.
If you're an Ops Lead reading this without that kind of backing yet, the first job isn't a new template. It's a direct conversation with your founder about what happens the first time someone important tries to skip a step.
A simple 3-part enforcement framework
1. Name the one thing.
Don't try to enforce everything at once. Pick the single process costing you the most right now - usually sign-off, scope change, or resourcing - and ignore the rest for 30 days.
2. Make the cost visible, not moral.
Don't frame it as "we should be more disciplined." Show the number: hours of rework last quarter from verbal sign-offs, margin lost to unbilled scope creep, overtime paid because nobody flagged a resourcing clash early. People change behaviour for numbers faster than for principles.
3. Hold the line once, publicly, where it's uncomfortable.
The first real test is always with a client or team member everyone expects to be the exception. That's the moment that sets the norm - not the policy doc.
The temptation I resist
When I'm brought into an agency, the easy move is to recommend a new process or system. It sounds like proper consulting. It's also more work for me - which is exactly why it's tempting.
But I'd rather be straight with people. I listen to their specific issues first. I look at how they're working now and what tools they're using. Most of the time, the process and system itself is fine. It would work if people used it. So if what they've got is already good enough, I tell them that. They just need to enforce it properly.
That usually means less work for me. But there's real satisfaction in handing someone a quick fix they can run with themselves, rather than selling them something they don't need.
