Most problems brought to me are not the real problem.

​

The visible thing, slow execution, the team that's underperforming, the strategy that won't translate, the hire that didn't work, is almost always a symptom. The real cause sits one layer underneath, in how decisions actually get made and authority actually flows. Not how it's supposed to. How it does.

What follows is five patterns I see consistently in scaling companies.
Each one looks like one thing on the surface and is something else underneath.
The point isn't to give you a fix. It's to give you a clearer name for what you may already be sensing.

​

​

​

1. Symbolic authority

You hired a senior leader to take ownership of a function. The title is real. The salary is real.
Six months in, the same decisions are still routing through you. Not because they're underperforming.
Not because you're holding on. Because the authority you handed them is symbolic.

The decision rights, the budget gates, the cross-functional veto power, none of it actually moved with the title.
The team feels this before anyone names it. They escalate around the new hire because they can read where the real authority sits. The new hire feels capped within months. Either they leave, or they accept reduced scope and the cost of the role becomes invisible.

This is not a hiring problem.
It's a governance gap that a hire cannot close, and that another hire will reproduce.

​

​

​

2. Strategic translation drift

Ask three of your leaders, separately, what the company's top three priorities are this quarter.
 

You won't get contradictory answers. You'll get three different coherent answers. Each one is a reasonable reading of what they've heard you say. The variance lives in the gap between what you intended and what arrived.

This is not a communication problem. It's a structural one.

There's no mechanism that converts strategic intent into a single shared version of priorities, owned by a specific person, refreshed at a specific cadence. So each leader reconstructs the strategy from fragments, the all-hands, the 1:1, the email, the offhand remark in last week's meeting. Each team then executes against a slightly different version. Resources allocated to work that doesn't compound. Decisions made downstream that contradict each other six weeks later. The strategy you can articulate clearly in your office is being delivered as three strategies in the work.

The visible problem is alignment.
The actual cause is that strategic translation has no owner.

​

​

​​​

3. Decision routing

Every founder I've worked with has, at some point, said some version of this: "I need to step back. The team needs to make more decisions without me." Then they delegate harder. Push more responsibility down. Take a vacation to force the system to function without them. It works for two weeks. Then the same decisions are routing through them again. The conventional reading is that the founder hasn't really let go.

That diagnosis is wrong in a specific way. You can delegate every task you currently hold and still find the same pattern in 90 days. Because what's routing through you is not tasks. It's decisions. And decisions route to the only place in the company where the authority to make them is genuinely clear.

If your name is the only place in the org where decision rights have no ambiguity, every consequential decision will end at your desk regardless of how the boxes on the org chart are drawn. The org chart is a description.
Decision routing is the reality.

The visible problem is delegation.
The actual cause is that decision authority has only one unambiguous owner, and it's you.

​

​

​​​

4. Pattern repetition

The same execution problems keep returning. Different teams, different quarters, different shapes.
New hires fix it for a quarter. Reorganizations fix it for two. Process documents fix it briefly.
Off-sites reset the energy. Then the pattern comes back.
This is the most useful diagnostic signal a founder has, and the most often misread.
 

What it usually gets attributed to: people, culture, communication, execution discipline. New initiatives launched to address each one. What it actually means: there is a structural cause you have not located, and every operational fix is treating a symptom of it. The pattern returns because nothing you've tried has reached the cause.

It's not bad luck. It's not the team. It's a structural fingerprint. Patterns that repeat across hires, quarters, and reorganizations are the cause sending you a signal. The fix is not another initiative. It is finding what is producing the pattern and changing that.

The visible problem is recurring failure.
The actual cause is unaddressed structure.

​

​

​​​

5. Sequence inversion

Operations are too manual. Costs are climbing. The team is overloaded.
The obvious answer is to automate, to scale, to build infrastructure.
You're often right that automation and scale are needed. You're often wrong about when.
 

Automating unstructured work multiplies the unstructured work. If each engagement, project, or delivery is being reinvented every time, scaling those instances faster doesn't produce efficiency. It produces a faster version of the original mess, now harder to fix because it's baked into systems. The sequence that works is the inverse of the obvious one. Structure the work first, define the architecture of how delivery actually happens, who owns what, what the repeatable spine looks like. Automate on top of structured work. Scale once the structure holds.
 

Most companies skip step one because it feels slower. It is slower for the first quarter.
It is significantly faster after that, and structurally sound, in a way that the reverse sequence never produces.

The visible problem is operational cost.
The actual cause is that the work itself isn't structured enough to be automated yet.

​

​

​​​

What these five have in common

Each pattern has the same shape:

A visible problem that's real. A conventional diagnosis that's plausible.
An actual cause that sits one layer underneath. The conventional fix targets the visible problem and produces temporary relief. The pattern returns because the cause was never reached. The reason these are hard to see from the inside is structural, not personal. You're operating inside the system that's producing them.

The thing you're using to perceive the problem is the thing that's generating it.
That's not a flaw of intelligence. It's a property of position.

​

If this read produced recognition, the next layer of the diagnosis is relevant to your situation.