Upstream Leadership:

What's actually running the business.

No one wants to hear they're the problem, but getting the diagnosis right is what makes a lasting fix possible. Let's get into it:

Your growing business began — and still runs — on your DNA. That's true of every founder-led business and it's why you've had the successes you've had.

But here is the problem I've seen and fixed for more than a decade of this work:

Your preferences live almost entirely inside your head.

Not written down, not fully-formed, not really explained.

(This was how you moved so quickly when the business was smaller. You met the demand of the moment. Then you moved on. And it worked.)

But now those habits that helped you move fast early on have hardened into bottlenecks.

It's a three-part problem:

They're invisible. "Done well" lives in your head and nowhere else. You've never articulated it, let alone documented it. Your team can't see the standard, so they can't hit it on their own — they can only guess and hope, or check with you and wait.

They're arbitrary. When you make a call, you don't explain it and you don't defend it. It's right because it's yours. Which means the next call could be different for the same reason — because that one's yours too.

They're ever-shifting. You're an idea volcano. You change your mind, in small ways and big ways, all the time. Last month's priority is this month's old news, and the thing that displaced it was something you saw, read, or thought about over the weekend.

Now stop and ask yourself this question:

How are they supposed to build against that?

The only people who succeed inside this setup are the ones with constant access to you — the ones who can ping you all day with their million questions and catch your changes in real time.

Which, by the way, is the very thing you're complaining about.

Everything routing through you, every decision waiting on you, every plan needing your sign-off. That isn't your team failing to step up. That's the only way the system works.

Your team is being asked to perform clairvoyance, against a standard
that isn’t written, can’t be explained, and won’t sit still.

Execution problems are leadership problems in disguise. When the work comes back wrong, when the senior hire underperforms, when the deadline slips — the reflex is to say someone didn't execute.

The truth is your team is being asked to perform clairvoyance, against a standard that isn't written, can't be explained, and won't sit still.

That isn't a performance problem on the team side. That's a lack of clarity on your side.

Why the four common fixes don't take.

Here's what the industry tells you to do about it.

Read the books. Install a system. Hire help. Train the team to lead.

Sound familiar? The founders who end up on my discovery calls have tried combinations of these, all with — let's just say — partial success.

Let's sift through each one and find out why.

A book.

Clockwork. Buy Back Your Time. Traction. The E-Myth. You've probably read more than one.

Three problems with reading your way out.

First, reading feels like action. You finish the book energized, you've highlighted half of it, you can summarize the framework at the next leadership meeting — and the felt sense of having done something about it quietly substitutes for actually doing something about it.

Second, books describe the pattern. They can't see the specific story you tell yourself about why your situation is different, or why this week is the exception, or why the framework applies to everyone but you.

That's the narration that keeps the dysfunction in place, and a book can't catch it because a book can't see you.

And third — even when the book lands, even when the insight is real, the leap from I understand this to I'm executing differently on Monday is enormous, and most readers can't make that leap alone.

The book got you to the edge of the pool. It can't get you to swim.

A system.

A methodology. A piece of software. A documentation push. Maybe EOS, maybe a project management tool, maybe an SOP project that lasted a few weeks.

A system installed on top of unclear standards inherits the unclarity. It doesn't generate clarity — it carries clarity, once you've supplied it. And you didn't supply it.

That's why you bought the system!

The tool routes the same confusion through a prettier interface. The methodology gives your team new lingo...for the things they're still guessing about.

Hire help.

A VA, an EA, an ops coordinator, a fractional specialist. Someone whose job is to absorb the load and just handle things.

They take orders and fight fires. And the fires keep starting because the cause — the unclear, unexplained, ever-shifting standards in your head — never gets touched.

So they fight today's fire, and tomorrow's, and next week's, and the more competent they are the more fires they can put out, which feels like progress. (It isn't.)

And the longer they stay, the better they get at absorbing the mess around them — which means you stop seeing the confusion around them at all. They handle it. You forget it's there. And the day they leave, you find out exactly how much of the business was running on their pattern-matching, and the fires you'd forgotten about all come back at once.

Train the team.

There's a whole category of program built on this premise: the problem is that your team isn't leading, so let's make them better leaders.

Coach the managers. Build their judgment. Give them frameworks. Once they can carry their own weight, the founder doesn't have to carry it for them.

Sounds great. Doesn't work, for one reason: You can't train a team to lead well against a standard they can't see, that won't get explained, and that will change next month.

The better-trained they get, the more capable they become — at exactly the thing they were always doing, which is reading your mind, catching your changes, and asking before they decide.

You're not training leaders, you're training mind-readers. That isn't a performance investment. It's a clairvoyance investment. And it works exactly as well as that sounds.

You can't downstream your way out of an upstream problem.

Four answers, but the same failure.

A book can't catch the story you tell yourself about why it shouldn't apply to you right now. A system can't generate clarity it wasn't given. More help can't fix a problem it constantly inherits. A trained team can't lead well against a standard they can't see.

Every one of these operates downstream of where the actual problem lives.

They're real tools. They do work — for an already-clear founder. But they fail when things are unclear, because they were designed to operate inside clarity, not produce it.

You can't downstream your way out of an upstream problem.

Where the fix actually goes.

Here's where the fix needs to go: With you. The same place the problem is.

Everyone downstream of you (your team, your hires, your systems, your tools) can only juggle whatever you hand them.

If what you hand them is unarticulated, unexplained and ever-shifting, they spend their week grappling with it, applying it and then asking about it.

That isn't their individual failure. That's the unclear system producing its predictable results.

So the move is upstream — to the layer where standards get articulated, where context for the work gets set, where decisions come with reasoning behind them.

You stop being the person who does everything.
You become the person who makes everything possible.

This is Upstream Leadership. And it has a specific job: create a clear, coherent, durable, documented context for work to get done.

Clear answers invisibility. The standards that have been living in your head come out of it — articulated, written down, available to the people who need them to perform against them.

Coherent answers arbitrariness. Decisions don't land as decrees. The context comes with them — why this, why now, what changed, what's staying put. The team learns the reasoning behind the call, not just the call, which means they can apply that reasoning themselves the next time something similar comes up.

Durable answers ever-shifting. Priorities hold for as long as they're set to hold. When something does change, the change is itself communicated, dated, and named — not absorbed silently into a new normal that nobody marked the start of.

Documented is what makes the other three real. Clarity, coherence, and durability that live only in your head are no different from the preferences they were supposed to replace. They have to be written down to be transferable, and they have to be transferable to be anything other than another version of the same problem.

Your value doesn't disappear when you make this move. It shifts upstream. You stop being the person who does everything. You become the person who makes everything possible.

The four practices that put the fix in place.

So what does this actually look like in practice.

Upstream Leadership is made up of four main practices. Each one is a way you produce a specific ingredient the team can use — instead of expecting them to absorb it from proximity to you.

Choose the work wisely. Set durable priorities that hold against the next shiny thing, the next client request, the next idea that walked in over the weekend. This is where durability lives. Most founders don't have a priority problem in the sense of not knowing what matters. They have a priority problem in the sense of letting it quietly get displaced — by fires, by new ideas, by whatever walked in over the weekend.

Articulate your standards. Write down what done well looks like — for projects, for roles, for deliverables — so the standard exists outside your head and your team can perform against it. Articulating clearly and then rarely overriding yourself is what turns standards from preference into structure. This is where clarity lives, and where the documentation mechanism does its real work.

Follow through steadily. Track the metrics that will surface drift early. Defend the priorities you set. Change your mind on purpose when changing your mind is warranted — using a process you and the team can both see — not because something caught your eye on a Tuesday. This is where coherence lives. The team learns to trust that changes are real changes, not whimsy.

Distribute authority alongside work. When you hand someone a task, hand them the decisions that go with it. Distribute approval, not just execution. Review on a cadence that builds the team's judgment instead of replacing it. This is the practice that turns documented context into team capability — the practice that finally gets you out of the daily decision stream.

And a bonus: Watch what happens to the accountability conversation when these four are in place.

Most of what gets called an accountability problem — work that comes back wrong, deadlines that slip — isn't accountability at all. You can't hold someone accountable to a standard they were never given, that wasn't explained when it was set, and that quietly changed three weeks ago.

Create transparent expectations that are built on mutual agreement and most of what you'd been calling accountability problems will just dissolve.

Most of what gets called an accountability problem isn't accountability at all.

Upstream Leadership Tradecraft is nameable, learnable, and repeatable. There's more underneath each practice: what the specific moves look like, how they sequence, what the common failure modes are. That lives here.

What changes when this works.

Here's what life looks like when these ingredients are in place.

Your priorities survive contact with your own attention span.

The thing you committed to in January is still the thing in April. When something does displace it, the displacement is a named event with reasoning behind it, not a quiet drift nobody marked.

The standard left your head.

You stop being the only person who knows what done well looks like.

New hires get productive against the standard in weeks instead of months.

You stop rewriting your team's work — not because you've disciplined yourself out of it, but because the work is meeting the standard the first time more often than not.

Your team starts anticipating what you'll decide before you decide it (which inspires them to produce better work).

Not because they're psychic. Because they've watched you reason in public — through documented changes of mind, through explained priorities, through standards held steadily — long enough that the reasoning has become learnable.

Your priorities survive contact with your own attention span.

The "quick question" interruptions drop sharply.

The team isn't routing every judgment call through you because they have the standard, the priority, and the authority to decide. You can think for an hour without someone needing something.

You stop being the answer to every question.

The team handles the answerable ones. You handle the genuinely hard ones — strategic bets, real exceptions, the calls only you can make.

Senior people stay.

They stay because their judgment matters now. The capable hires who used to leave after eighteen months because they were managed like assistants are operating like the senior people you hired them to be.

You can step away for a few days and the business holds.

Not because of heroics on the team's part. Because the context they need to operate is on the page where they can reach it, regardless of where you are.

You get the white space back.

The hours that used to disappear into approvals and "quick questions" and rewriting come back to you.

You can think for long stretches. You can write the thing you've been meaning to write.

You can take a real look at the next bet you're considering, instead of glancing at it sideways between meetings. The generative part of your job — the part you started this business to do — has room to operate again.

Now you know.

Now you know why nothing you tried worked. The effort was real. It was just aimed downstream: at the team, at the systems, at the books, at the hires. The fix was upstream the whole time.

Now you know what it looks like. You know where it goes. You know what it produces.

Get to work.