diagnosis
Stop treating symptoms like causes
Why smart teams keep fixing the visible pain and missing the decision that is actually creating it.
The mistake most teams make
When a business starts to feel heavy, the first instinct is usually to grab the loudest symptom. Leads are poor, so the team rewrites the funnel. Delivery is slow, so the team adds another project board. Clients are confused, so the team writes more copy. Each move feels sensible in isolation. Together they create a pile of activity that still leaves the root problem untouched.
This happens because symptoms are easier to see than causes. A symptom is where pain shows up. A cause is the decision, condition, or pattern that keeps producing that pain. Symptoms are visible on the surface. Causes tend to sit one layer earlier, inside the way the business defines work, assigns ownership, or makes trade-offs.
Once you see the difference, a lot of wasted motion becomes obvious. A team can have a demand problem that is really an offer problem. It can have a delivery problem that is really a kickoff problem. It can have a team problem that is really a decision problem. None of those get fixed well if you start at the surface.
Why symptom-fixing feels productive
Symptom-fixing gives fast emotional relief. It makes the team feel active. It also creates a story that is easy to explain to other people. "We hired support." "We redesigned the process." "We changed the tooling." Those are visible actions. They look like progress because they can be listed, announced, and tracked.
The problem is that visible action is not the same as useful action. If the business has not worked out what is actually producing the drag, every fix is partly a guess. Some guesses help for a while. Some make the next round of friction harder to read because they change the surface without changing the source.
- A noisy symptom can hide a quieter upstream decision.
- A quick fix can make the real cause harder to spot later.
- More activity often lowers confidence because nothing truly settles.
A better way to look at the problem
Instead of asking, "What hurts most right now?" start with a different question: "Where does this problem begin?" That question shifts the work from reaction to diagnosis. It forces the team to look at timing, evidence, and sequence rather than urgency alone.
In practice, this means looking for the first point where the business stops being clear. That might be the offer. It might be the way work is sold. It might be the way ownership gets handed over. It might be the fact that nobody can tell the difference between urgent work and important work. Whatever it is, the first break matters more than the final pain.
Once the first break is visible, the next move usually gets smaller. That is one of the best signs you are finally looking at the real problem. Good diagnosis tends to reduce the amount of work, not increase it.
What founders and operators can do this week
Start by listing three recurring frustrations from the last month. Keep them concrete. Do not say "delivery is bad." Say "projects slip in week one because the owner is not clear." Then ask what has to be true before that symptom can appear. Keep walking backward until you reach a decision, condition, or missing standard that feels earlier than the pain.
If you do this honestly, you will usually find that the business has fewer true problems than it first appeared to have. That is good news. It means the work can become narrower, more defensible, and less expensive.
- Write down the symptom in plain language.
- Ask what had to go wrong before that symptom appeared.
- Stop when you reach a point where one decision could change the outcome.
Next step
Ready to find yours? Start the diagnostic — £300 →
Start the diagnostic — £300 →