Ask an owner what needs fixing and you rarely get one answer. You get a list. Nothing is written down. The new hire is taking too long to get useful. Decisions are scattered across text threads. Nobody knows who owns what. And there’s no clean way to see how the month is actually going.
All five are true. That’s what makes the list so discouraging — and so misleading.
Because those five problems are not equal. One of them is holding the business back more than the other four combined. Fix that one and the others get quieter on their own. Fix any of the others first and you will work hard, spend money, and feel almost no difference.
The five places work gets stuck
In every operation I’ve audited, the same five gaps show up. Different industries, same five:
- Knowledge capture. Is what the business knows written down, findable, and current — or does it live in people’s heads?
- Onboarding and training. Can a new hire get productive from the system, or only by shadowing someone?
- Communication and decisions. Is there one place where decisions land, or do they scatter across texts, calls, and memory?
- Rhythm and accountability. Are there operating cadences with clear owners, or does everything route through you?
- Data and visibility. Can you see how the business is actually doing without building a spreadsheet from scratch?
Score each one honestly, one through five, and you get a picture of the business. What you do not get is a plan. A list of five weak scores tells you everything is bad. It doesn’t tell you where to start, and starting in the wrong place is how most improvement efforts quietly die.
Why fixing everything at once fails
You have a finite number of hours that aren’t already committed. Realistically it’s a few a week, and they compete with the actual business. Spread those hours across five fronts and each one gets a push too small to hold. In three months you have five half-built things, none of which anyone uses, and a well-earned belief that this stuff doesn’t work.
There’s a second failure mode that’s harder to see, because it looks like success. You pick a gap, you fix it properly, and nothing happens.
Say you build a genuinely good training system. Clear, well organized, actually finished. But the reason new hires were slow was never the training — it was that the answers they needed after week one lived in one person’s head, and that person is in meetings all day. You improved training. The bottleneck never moved. The business feels exactly the same, and now you’re tired.
Improving something that isn’t the constraint doesn’t make the business better. It makes one number better while the business stays where it was.
The 20% test
Here’s the question that sorts it out. Take one gap and ask:
If this gap alone were fixed, and the other four stayed exactly as bad as they are today, what would actually change?
Sit with the second half of that sentence. Not “what if we improved everything.” What if you fixed this one thing and deliberately ignored the rest?
If the honest answer is a real, describable change — I stop getting called on my day off, or we could take on another crew without hiring an admin, or I’d know by Wednesday whether the month is working — that’s your constraint.
If the honest answer is “not much, because we’d still be stuck on [something else]” — then you’ve just named the real constraint. It’s whatever appeared in that sentence after the word because.
Run it on all five. Usually one comes back obviously louder than the rest. That’s the one that gets your next three months.
An example of how it goes
Picture a small service company — plumbing, HVAC, electrical, it doesn’t matter. The owner’s list: no documentation, slow onboarding, decisions scattered across texts, no weekly rhythm, no visibility into job profitability.
Run the test on visibility first, because that’s the one that feels most urgent. If we had a live profitability dashboard and nothing else changed, what happens? Honest answer: we’d finally see which jobs lose money — but we’d still bid the next one the same way, because how we bid lives in the owner’s head and nowhere else.
That “because” is the whole answer. The constraint isn’t visibility. It’s knowledge capture. The dashboard would have been a real improvement that changed nothing, and it would have cost a month.
Now run it on knowledge capture. If how we bid, scope, and close jobs were written down and current, and nothing else changed? Two other people could bid without the owner. Onboarding gets shorter for free, because there’s finally something to onboard into. And the profitability numbers become worth collecting, because now someone can act on them.
One gap. Three problems quieter. That’s what a constraint looks like when you find the right one.
What to do this week
You don’t need anyone’s help to start this, so start it:
- Write down the five gaps and score each one to five. Take ten minutes, not an afternoon. Your first instinct is usually right.
- Run the 20% test on your two worst scores. Write the answers as full sentences. The word because is doing the work — watch for what follows it.
- Name one constraint and write it on something you’ll see. One. Not a top three. A top three is just the original list wearing a nicer outfit.
- Give it your next three months and deliberately let the other four sit. That last part is the hard one, and it’s the part that works.
The discipline isn’t in finding problems. You already have the list — every owner does. The discipline is being willing to leave four real problems alone long enough to actually finish the fifth.
That’s also what a good audit is for. Not a longer list of what’s broken. A shorter one: the single gap worth your attention, what it’s costing while it stands, and what to do about it first.