Strategic Capacity Letter #6: Not Every Problem Needs a Diagnostic
Sometimes you need to stop fixing the whole system and look at the problem in front of you.
There is a tendency in the operational consulting world to look at every problem as evidence of something larger.
A question comes back to the founder. A handoff doesn't go as expected. A team encounters a situation that falls just outside its normal responsibilities. A workflow that usually works suddenly doesn't. And the response becomes: Something is broken.
So we examine the system. We redefine responsibilities. We revisit boundaries. We create new processes. We test them. We look for signals. We adjust them again. Sometimes that's exactly what is needed. And sometimes it isn't. Sometimes something happened because something happened.
The Difference Matters
A team recently encountered a situation that was well outside its normal authority. The team discussed the problem, considered its options, and decided the appropriate person to consult was the founder. That doesn't automatically indicate a failure in the system. In fact, it may indicate that the system worked exactly as it should.
The team recognized that the decision was beyond its authority and escalated it to the person who had the authority to make it. The founder made the decision. Everyone moved on.
Now, if the same type of question keeps coming back, that's worth examining. But even then, the first question shouldn't necessarily be “What's broken?” It might be: “What did you need that you didn't have?”
Perhaps the team needed more information. Perhaps the founder hadn't explained how they wanted similar situations handled. Perhaps the boundary was unclear. Or perhaps the team simply encountered a situation that genuinely belonged to the founder.
Those are very different problems.
Judgment Is Part of the System
Good operations don't eliminate judgment. They make room for it. A useful process can tell someone what to do in the situations you already understand. A good cheat sheet can answer the common questions. Clear responsibilities can prevent unnecessary handoffs.
But no business can document every possible situation in advance. At some point, someone has to look at what's happening and decide: Is this mine to handle, or does this need to go somewhere else? That decision is part of operating a business.
And the founder has a role in that judgment, too. If a team brings something to you that is only slightly outside its normal boundaries, don't automatically assume the team needs more authority. Ask what they thought they should have done. You may discover that they simply didn't have enough information to make the decision.
That's useful information. Give them the missing information. Clarify the boundary. Make the decision. Move on.
Not Everything Needs to Become a Project
This is one reason I don't believe every operational problem calls for a comprehensive review. Sometimes you need to understand the entire operation before you can know what needs to change. That's what a Diagnostic is for. But sometimes you already know where the problem is. You don't need to stop the business and examine every workflow, communication pathway, and responsibility.
You need someone experienced to look at this problem with you. What happened? Why did it happen? Was the response reasonable? Is something actually missing? And what should happen next time? Sometimes that's enough.
The Goal Isn't a Perfect System
There is no operating system so perfectly designed that nobody will ever have a question, encounter an exception, or need to involve the founder. Nor should there be. The goal is not to build a business where every possible decision has been anticipated.
The goal is to build a business where most things can move without the founder, and the things that genuinely require the founder reach the founder without unnecessary drama. That's a much more useful definition of operational capacity.
Sometimes the smartest operational decision is not to redesign anything. It's to answer the question, make the adjustment, and get back to work.
Not every problem needs a diagnostic. Sometimes it just needs a conversation.
About the Strategic Capacity Letters
These letters explore the repeating operational patterns that surface as founder-led businesses grow. Drawing on more than three decades of experience working inside businesses, they examine the structural problems that can quietly limit capacity, create friction, and make growth harder than it needs to be.
The letters are written by Anne Albright, who works with solo practices and founder-led teams to identify and fix the operational problems that slow growth.
