Broken operations rarely send up a flare. There's no outage, no single dramatic failure you can point to — just a slow, ambient tax on everything the business does. Work still ships, customers still get served, but it costs more effort than it should, depends on the same few heroes, and gets a little more fragile every quarter. The danger of broken operations is precisely that they look survivable. Here's how to spot the signs before they harden into a ceiling on your growth.
Broken operations don't look broken — they look busy
The most common disguise for bad operations is a team that seems impressively hardworking. Everyone's slammed, everyone's responsive, everyone's putting out fires with admirable energy. It reads as a healthy hustle. But constant firefighting isn't a sign of a committed team — it's a sign of a system that manufactures fires. As I've written before, good operations are invisible; you only notice them when they're absent. So the busyness itself is the first clue. If heroics are routine, the process is doing something wrong.
The signs to watch for
Individually, any one of these is normal. Several of them together mean your operations need work:
The same things fall through the cracks
A follow-up missed, an order slipped, a handoff dropped — and not once, but as a recurring pattern. When mistakes repeat, it's not a people problem; it's a process that has no reliable catch.
Only one person knows how
Key work lives entirely in someone's head. When they're on leave, everything stalls. That's not depth of expertise — it's a single point of failure wearing a friendly face.
Simple questions take days to answer
"How many customers did we onboard last month?" shouldn't require an archaeology dig. If basic numbers are hard to get, you're flying without instruments.
Nobody's sure who owns what
Tasks fall between roles because ownership is fuzzy. Two people assume the other has it; nobody does. Every gap is an argument waiting to happen.
Growth makes everything worse, not better
More customers or more staff should create leverage. If instead each increment adds chaos — longer queues, more errors, more meetings — your operations don't scale, and that's the clearest sign of all.
Why it happens
Almost no one designs broken operations. They accrete. In the early days you do everything manually and informally, and it works fine because the team is small and everyone can see everything. Then you grow. The informal habits that worked at five people quietly fail at fifteen, but nobody notices the exact moment they stop working — the cracks just widen. Broken operations are rarely a decision; they're the residue of decisions never revisited. What got you here genuinely won't get you there, and the transition is invisible until something snaps.
How to fix it
The fix isn't a big-bang reorganisation or an expensive new tool. It's a handful of unglamorous disciplines applied to your most painful process first:
Make the work visible
You can't fix what you can't see. Write down how a core process actually runs today — not the idealised version — end to end. The gaps usually announce themselves the moment it's on paper.
Give every step an owner
One name against each part of the process. Not a committee, not "the team" — a person accountable for it running. Ambiguity is where work goes to die.
Instrument the essentials
Pick the few numbers that tell you whether the process is healthy, and make them easy to see. You don't need a dashboard for everything — you need the vital signs at a glance.
Automate the parts that have earned it
Once a process is stable and repeatable, automate the mechanical, high-frequency steps — but only those. Automating a broken process just makes it fail faster, so fix the flow first, then decide what to automate.
Start with the single process that causes the most pain, fix it properly, then move to the next. Operations improve the way they broke — one quiet decision at a time, just in the right direction now.
Broken operations don't look broken — they look busy. Watch for repeated dropped balls, single points of failure, slow answers to simple questions, fuzzy ownership, and growth that adds chaos instead of leverage. Fix it by making one painful process visible, giving each step an owner, instrumenting the essentials, and automating only what's already stable.
Read next
Feeling the friction as you grow?
I help founders and teams turn firefighting into calm, repeatable operations — the processes, ownership and reporting that let a team scale without breaking — see how I work.
Book a Call