You’re on vacation for the week.

While you’re offline, a real decision shows up: chase a new customer segment or go deeper with the one you have.

Nobody wants to bug you, so the team meets.

Marketing pushes expansion. Sales wants whatever closes fastest. Product argues for focus.

Everyone says the same words—opportunity, risk, priority. 90 minutes later, they punt: “Let’s wait until they’re back.”

When you get back, you see at the top of your inbox:

“When You’re Back — Need Your Steer On A Decision”

Everyone in that room is sharp, motivated, and stuck for the same reason: judgment lives in one person’s head, and that person isn’t here.

The question is whether it has to.

Everyone says judgment matters. Few can show where it comes from.

Ask a leadership team what they want more of and you’ll hear it fast: “better judgment.”

Then ask what judgment is made of.

Most people can’t point to it. They point to the person.

They talk about judgment like it’s a trait—something you either have or don’t.

“We need better judgment on this team.” Full stop. Because if it’s a trait, there’s nothing to build.

So decisions get pulled toward the person with the reputation. The rest of the org waits for the call.

Or they hide behind scripts.

“Talk to customers.”

“Get everyone on the same page.”

Useful moves, but not the call itself. Scripts tell you what to do. They do not tell you what matters.

Results get confused with reasoning.

“They have great judgment because it worked out.”

At the outcome level, luck looks exactly the same.

And when they feel stuck, they turn up the volume.

• More experiments.

• More meetings.

• More decks.

Activity goes up; signal doesn’t.

Every bad hire starts with a good feeling.

A leader interviews a candidate and says, “I’ve got a good feeling about this one.”

Ask what drove that feeling and you get hand-waving.

• Which moments mattered?

• What was weighted heavily, and what barely counted?

• What would have disqualified them on the spot?

Months later, the hire doesn’t work out. The postmortem lands on “we need to tighten the process.”

So the company adds steps. Or the leader personally vets every candidate.

Either way, the thing that failed never gets named. The reasoning stays hidden.

Judgment is invisible because people treat it as a personality trait.

Judgment begins with context in a domain.

When people say someone “has good judgment,” they usually mean: in this situation, in this kind of work, they notice the right things and choose well.

You can usually spot three kinds of domains.

1) Implicit everyday domain

These are the domains you use without naming them.

“Good judge of character” is a classic example.

A good judge of character has a working model for how people behave in groups—and what “ethical” looks like when nobody’s watching.

The signals aren’t mysterious:

Do they do what they say?

Are they consistent across time and pressure?

Do their actions match their words?

You’ve been using domain judgment your whole life. You just didn’t label it.

2) Named professional domain

Now you name the work: sales, product, hiring, finance.

But naming it isn’t enough. You still have to narrow it.

“I want to get better at sales” is too broad. Sales to whom?

B2C real estate and B2B enterprise software don’t run on the same cues. Different buyers, different risks, different clocks.

Once you specify the domain, the signals get sharper:

Do you have the customer’s attention?

Is trust building?

Do you understand the problem the way they do?

And sometimes the miss isn’t inside sales at all.

You can close well and still sell to the wrong customer. Leads pour in, churn stays high. Or you close plenty of deals but leave money on the table each time.

The sale can work while the business doesn’t.

3) System domain

At this level, the domain isn’t just a job label. It’s a system with parts.

Your business model is a domain. So is your hiring engine. So is your onboarding flow.

Tool like the Lean Canvas — nine boxes on a one-page business model — draws the boundary: what belongs, what doesn’t, and what questions you have to answer.

Once you see that, familiar tools look different. They’re not answers. They’re domain definitions.

I’ll use the Lean Canvas as the running example, because it makes the idea visible.

A domain tells you which signals matter—and which don’t.

Every domain produces more data than you can use. The Lean Canvas makes that visible: nine boxes, but at any given moment only some of them change the next move.

Signals depend on the outcome you need. Start there and work backward.

If you skip that step, you end up tracking whatever feels urgent: the loud metric, the latest comment, the thing that spikes your anxiety.

The same domain can surface different signals depending on the result you need.

In the “judge of character” domain, charisma and first impressions feel useful.

They’re often noise.

If the outcome is “Can I trust this person to do what they say in a group?”, the signals that matter are the ones that hold after the charm wears off.

Sales works the same way. If the outcome is retention, the signal isn’t “how many people said yes.” It’s what they do after they pay.

Twenty yeses can be the wrong answer

A team runs twenty customer interviews.

They keep hearing: “I’d use this.”

They come back with “demand validated.”

They ship.

Customers even buy.

Then usage stays flat. Retention is weak.

They treated purchase intent as the signal. But the outcome they needed was ongoing use.

The signal that mattered was behavior: did people come back, did it become part of their week, did it keep solving a real job.

Get the signal wrong and you’ll optimize the wrong outcome.

Seeing the right signal is the first half. The second half is knowing what to do when you see it.

Scripts make decisions. Models make judgment transferable.

A script is a repeatable move.

On the Lean Canvas, every box has one: talk to customers about a problem, define a segment, list what they use today, set a price, decide what you won’t build.

Run those steps and you raise your floor. You don’t start from zero every time.

But scripts have a ceiling. They tell you what to do next until they don’t. A model shows you how the system works, so you can reroute.

If you treat the canvas like a checklist, you’ll fill every box and feel productive. It can still be dead. A living canvas has pull. What you learn in one box changes what you write in the others.

You don’t have to start at “Problem.” Start where you actually know something. If you’ve lived the pain up close, start with the problem. If you know the market, start with what people already buy. If you have a distribution edge, start with the channel you already own. Different entry points, same canvas.

The skill is tracing what one box implies about the other boxes.

One script, five boxes

The “Existing Alternatives” domain starts with a simple script: research what’s already out there. If you stop there, you get a list of competitors and a few bullets.

A model sees further.

Existing alternatives point to the customer: who is using these today.

They point to the problem: what these options fail to solve.

They point to early adopters: who complains, hacks around, or switches first.

They point to revenue: what people already pay, and what “normal” prices feel like.

One research move, five boxes changed.

That’s the jump from scripts in isolation to a working model.

Say you want to write a book about strategy.

Start in existing alternatives. Pull the top-selling strategy books. Then go straight to the one- and two-star reviews.

Those reviews are signals. They tell you what readers wanted and didn’t get, which gives you problems to solve. They tell you who the reader is, because the complaints come from a specific kind of person in a specific situation. They point to your promise: the gap you can own.

The only change in the canvas was the entry point.

To build this for yourself, start with the box you know best and draw the lines outward. Write down why you started there. Not the cleaned-up reason you’ll use later. The real reason that was true in the moment. That “why behind the why” is what disappears first—and it’s the part someone else would need to learn how you think.

Then keep it alive. Fill the canvas. Let reality push back—customers do not respond the way you expected, or a channel you were counting on starts to fade. Update it. Return every month and ask: what shifted, what held, what broke? The model stays useful because you keep running it.

The canvas is the tool. The skill is making your reasoning visible. Capture the thinking, not just the boxes. Name the signals you trusted. Name the ones you ignored.

Judgment feels like instinct because the steps happen fast. Slow them down enough to see them, and other people can learn them.

You’ve built the model step by step.

The fastest way to test it is to work backward from something real.

Your last big decision is the fastest place to start.

Start with the last outcome you drove—something you’d defend under pressure.

Then work backward.

• What model were you using when you made the call? How did the pieces connect?

• What scripts did you run—what repeatable moves did you rely on?

• What signals were those scripts responding to? What did you watch, and what did you ignore?

• What domain were you operating in? Name it as specifically as you can.

If you can answer all four, your reasoning is visible. It’s no longer trapped in your head.

If you can’t name the signals, or you can’t explain how the pieces connected—that’s where your judgment is still instinct. That’s where the design work starts.

If someone can walk backward from an outcome through trade-offs and constraints, they have something they can explain and repeat.

If all they can say is “it worked out,” they don’t.

And transfer runs both ways.

When someone on your team has a visible model—domain clear, signals named, scripts running, connections mapped—they can bring that structure back to you.

They can say: here’s what I’m seeing, here’s why I trust it, and here’s what it means for us.

You’re building a room that can think back.

With that, your thinking stays in the room, even when you’re not.

P.S. Two pieces this builds on: Decision Architecture Manifesto (the bigger frame) and The Context Pyramid (the structure).

Why your best thinking stays buried

You’re in the shower and it hits you.

Not a small thought. A real one. The kind that finally connects two things you’ve been circling for weeks.

By the time you’re toweling off, half of it is gone. So you grab your phone, record ninety seconds, and move on.

A few days later, you hit play.

A version of you is talking fast, mid-thought, referencing something you no longer remember. The note is a fragment of a fragment. What felt clear now sounds like someone trying to describe a dream.

This isn’t an idea problem. It’s a survival problem.

Your best thinking shows up in places that can’t hold it: showers, walks, the three minutes between meetings, the drive home when something someone said finally clicks. You catch it in a voice note or a half sentence in your phone and tell yourself you’ll come back.

But capture alone doesn’t give you anything you can return to. A voice note is a breadcrumb. The context that made it make sense stays behind: your mood, the conversation you just left, the connection your brain was making. None of that travels.

So you end up with a pile of recordings and notes that still might matter, but feel expensive to dig up. Replay. Rebuild the situation. Guess what you meant. Most of them just sit there.

And then there’s the journal. Your deepest thinking often lives there, not in clean paragraphs, but in the layout of ideas across a page. It has the same problem: the distance between the notebook on your desk and something you can ship to other people feels huge.

Raw material is everywhere. A way to turn it into something usable, while it’s still warm, is missing.

There’s a short window right after an idea shows up where it still has heat.

You still remember what sparked it. You can still explain the leap you just made. You can still name what it connects to.

Five minutes later, that clarity starts to drain. You’re left with the headline, not the reason it mattered.

Most people respond the same way: capture the fragment and move on. Voice note. Quick text. A line in Notes that says “REVISIT” with no other context.

It feels responsible. It’s also how the pile grows.

Because the failure isn’t the lack of capture. The failure is what happens next—nothing. No friction. No check for what’s missing. No way to come back without rebuilding the moment from scratch.

That’s what the next three mistakes have in common.

Three mistakes that keep the idea pile full

Mistake 1: Scheduling ideation

Blocking ninety minutes on Tuesday to “generate ideas” sounds responsible.

It also pushes your brain into a mode that rarely makes the good stuff. Your best ideas didn’t arrive in a calendar block. They arrived during loose, associative moments. When you force them on a schedule, you mostly get safe, obvious output.

Mistake 2: Half capturing

You record the thought, give it just enough shape to feel saved, and promise yourself you’ll test it later.

But later usually means you, alone, staring at your own idea. The feeling that it’s strong becomes a substitute for proof. Capture without testing is organized forgetting.

Mistake 3: Testing by yourself

Even when you do test, you often test alone.

You run the idea through the same lens that produced it. The blind spots in that lens are the ones that survive into the published piece.

The ideation flywheel: turn insights into workable ideas

Here’s a loop that makes your thinking compound instead of evaporate:

Capture. Test. Model.

Capture, while the context is alive

The raw material comes from three places:

• Spontaneous thought. The shower moment. The click between meetings. The drive-home connection.

• Conversation you’re already in. Meetings and calls, recorded, transcribed, and searchable.

• Deliberate reflection. Journaling and paper thinking, where you finally see the real answer after sitting with a question.

Each source gives you fragments. The loop turns fragments into something you can build on.

Test, while the thought is still fresh

Most people skip this step because it feels like extra work.

It isn’t. It’s five minutes that saves your idea.

The goal is not to “make it better.” The goal is to drag the real point out of the fog while you can still see it.

Here’s a script you can run in five minutes.

Step 1: Pin the claim (30 seconds)

Write one sentence:

“I think ____ because ____.”

If you can’t finish that sentence, you don’t have an idea yet. You have a vibe.

Step 2: Name the trigger (30 seconds)

Answer:

“What exactly set this off?”

A line from a meeting. A graph. A mistake you keep seeing. A weird example that stuck.

This is the context you lose first.

Step 3: Stress it (2 minutes)

Ask three questions:

• “What would make this false?”

• “What’s the obvious objection?”

• “Where am I smuggling in an assumption?”

Write the answers in plain language. No defending. Just list the weak spots.

Step 4: Force one example (1 minute)

Answer:

“What happened in real life that proves this?”

If you can’t name one concrete moment, it’s still too abstract to survive.

Step 5: Find the edge (1 minute)

Answer:

“What’s my angle that isn’t already everywhere?”

Not “it’s important.” Not “it matters.”

The angle is a specific claim, tied to your work, your experience, your pattern recognition.

That’s the checkpoint.

When you come back tomorrow, you don’t need to reconstruct anything. You pick up from:

• the one-sentence claim

• the trigger

• the objections

• the example

• your angle

That’s enough to write.

A tool can help here, but only if you use it like a sparring partner.

You’re not asking it to produce a finished draft. You’re asking it to push back fast.

Paste your one-sentence claim and say:

“Argue against this. Give me the strongest objection. Then tell me what evidence would change your mind.”

Or:

“Ask me ten questions until this stops being fuzzy.”

Or:

“Assume I’m wrong. What am I missing?”

The point is simple: you want friction while the idea is still alive.

Model, into something you can reuse

After testing, shape the idea into a form someone else can receive: a brief, a post, a framework, a protocol.

Not polished. Just legible.

Two examples

A shower thought becomes an argument

Raw fragment

“Batman = career.”

That’s what a voice note would have captured.

Five-minute test

Claim:

“I think career resilience looks like Batman because he builds power without backup.”

Trigger:

“I keep watching careers get reset by things people don’t control: new leaders, reshuffles, priorities changing overnight.”

Stress:

• Objection: “Batman is a billionaire with gadgets. That’s the opposite of ‘from zero.’”

• Assumption: “I’m assuming resilience comes from skills, not from position or network.”

• What would make it false: “If the real driver is access—money, connections—then the Batman frame collapses.”

Example:

“A project you owned gets shelved. A new leader arrives. The old plan is dead. You still need to land on your feet.”

Edge:

“It’s not about ‘saving up.’ It’s about building a core set of capabilities you can carry into any room: thinking clearly, planning, learning fast, staying useful when the map changes.”

Modeled output

Batman isn’t interesting here because he wins fights.

He’s interesting because nobody is coming.

No powers. No rescue. No promised path.

So he builds what he can control: skill, judgment, preparation, range.

That’s the part that transfers to work.

Career resets happen. Leaders change. Work gets shelved. Teams get rearranged.

If your value is tied to one role, one boss, one system, a reset wipes you.

If your value is tied to what you can do anywhere—how you think, how you learn, how you build—you survive the reset.

A meeting becomes a teachable protocol

Raw fragment

“I spoke for four minutes in a thirty-minute call. They said it changed everything. Why?”

Five-minute test

Claim:

“I think the value came from how I redirected their attention, not from how much I talked.”

Trigger:

“They wanted to be seen as ‘more strategic,’ but every sentence they said was about tasks, not choices.”

Stress:

• Objection: “Maybe they just needed validation.”

• Assumption: “I’m assuming ‘strategy’ is mainly about framing decisions.”

• What would make it false: “If they changed because of specific advice I gave, not because of a pattern I used.”

Example:

“They described ten problems. I ignored nine and asked one question that forced them to pick a lever.”

Edge:

“The move wasn’t advice. It was a repeatable sequence: detect the real goal, name the tradeoff, force a choice, tie it to how the org measures value.”

Modeled output

Here’s why four minutes can carry a thirty-minute call.

Most of the work isn’t talking. It’s listening for the lever.

A simple sequence:

1. Ask for the real goal in one sentence.

2. Name the tradeoff they’re avoiding.

3. Force a choice: “If you can only do one, which one wins?”

4. Tie that choice to how their org rewards people.

That’s not charisma. It’s a pattern.

Once you see the pattern, you can teach it. Once you can teach it, it stops living only inside your intuition.

Your first rotation: from fragment to workable idea

Pick one idea you already have.

Not the perfect one. The one that still nags at you when you scroll past it.

Open a voice note from your pile or a page from your notebook.

Then run the five-minute test once.

Write the one-sentence claim. Name the trigger. List the strongest objection. Force one real example. Find your angle.

At the end, you should have a checkpoint you can read tomorrow without cringing.

Do that once and you’ll feel the difference.

Not “I have content.”

“I know what I’m saying.”

That’s the whole point. The framework doesn’t write for you.

It keeps your thinking from dying on the way to the page.

This is part two of the Flywheel thinking series. Click here to read part one — The Insight Flywheel

Your organization makes hundreds of decisions a week.

Most of them happen in meetings. And most of those meetings weren’t designed to decide anything.

The machinery that runs those meetings was built for a different problem.

“More output” meant hiring. And hiring isn’t a knob you turn.

You run interviews for weeks. You finally get someone to sign. Then you wait. Best case, you get real yield six weeks in.

More often it’s three to four months before the person is doing work that changes results. And that’s if the first 90 days go well.

So we built guardrails around execution. Pre-meetings, approvals, roadmaps, committees — anything to keep a bad call from turning into a costly quarter.

Now AI makes execution cheap.

But the old machinery is still running, protecting a cost that’s mostly gone. So teams use AI to move faster inside the same loop, and the loop keeps aiming at the same problems.

Cheap execution changes what you can try. Being wrong costs days, not months.

The question isn’t how to protect execution anymore.

It’s which problems you couldn’t afford to chase—until now.

Most companies are treating this shift like a tool rollout. That’s why they plateau.

The Productivity Ceiling

Earlier this month, the Wall Street Journal ran a piece that landed in boardrooms across the country and got filed under the wrong diagnosis.

Consulting firms were being hired to teach employees how to use AI with real budgets. Leadership teams read it as a familiar story: adoption lag, change-management drag, normal deployment pain. Close the gap, usage rises, returns show up.

That reading nailed the symptom. It missed the cause.

The adoption problem wasn’t that employees couldn’t use the tools. It was that no one had changed what the tools were being used toward. The meetings stayed the same. The decisions stayed the same.

The execution got faster. Direction didn’t.

Every org chart, every meeting cadence, every weekly sync and quarterly offsite was designed to do one thing.

Coordinate human execution.

Status checks. Handoffs. Follow-through. The messy middle between “we decided to do this” and “this is done.”

Work about work.

That was the correct design for a long time. Humans executing in parallel are inconsistent, territorial, and slow.

Every process, every governance structure, every standing meeting answers a version of the same question: how do we get humans to do this thing reliably, at scale, across time?

AI just made the design spec obsolete.

The Messy Middle Just Became AI’s Job

An agentic system handles execution coordination at a different order of magnitude.

What needed a weekly sync, agents handle continuously. What needed a daily standup, agents track and surface as it happens. What needed a monthly review, agents aggregate and flag in real time.

Status chasing, handoffs, follow-through, anomaly detection, progress tracking, document synthesis, action item routing: these are now machine jobs. AI does them in the minutes between your conversations, rather than requiring your hours to do them at all.

Teams that use AI to do work about work faster get a bump. Teams that remove work about work from the human calendar get something else: time back for work no agent can do.

If AI can coordinate what your team currently meets to coordinate, every hour spent in those meetings is an hour not spent on the part that still needs judgment. You’re paying attention for work that’s already cheap.

Forget “How do we run better meetings?”

If AI handles coordination, what are meetings for?

Your New Job: Decide What’s True

When you pull execution coordination out of the agenda, one category of work remains: judgement.

Judgment #1: Staying in sync with Your Customer

Your business moves as your customer moves. AI doesn’t change that reality, but AI executes against a snapshot. The meeting is where you verify the snapshot is still accurate.

• Is what we know about the customer still true?

• Is the problem we’re solving still the problem they have?

• Are the agents executing toward the right destination, or executing precisely toward the wrong one?

This is not strategic planning. It’s calibration. The weather service doesn’t redesign its forecasting architecture every week. It updates the inputs.

Judgment #2: Writing Specs AI Can Run

The quality of that execution is bounded by the quality of the context they carry.

The meeting is where you ask:

• Do the agents have what they need to keep firing?

• What changed this week that they don’t know?

• What decision got made in one conversation that hasn’t been encoded into the execution cycle?

Judgment #3: Find the Next Problem

This is the one that determines whether an organization compounds or flatlines. The execution engine is running against today’s problem set.

New problems, emerging customer signals, opportunities that don’t fit the current model — none of this gets surfaced by agents. It gets surfaced in human conversation.

The meeting is where you ask: what are we not going after yet that we should be?

Three jobs. One governing logic.

The meeting keeps the execution engine calibrated to reality.

Agents handle the rest: status updates, progress reviews, escalation chains, resource debates. The meeting is for what agents cannot do: maintain the sync between what’s happening in the world and what the execution layer is running toward.

The Context Engine

Same company. Same leadership team. Same agenda item: a market expansion decision. Sales has surfaced a new segment. The question: pursue now or wait.

Meeting A.

Sixty minutes. The deck runs forty. Three slides on market size, two on competitive landscape, one on projected revenue. The team debates timeline.

A resource conflict surfaces: engineering is committed through Q3. Someone proposes a task force. The meeting ends with a follow-up and an action item to “gather more data.”

The AI writes four bullet points. Accurate. A clean record of an inconclusive conversation.

Two weeks later, the follow-up runs fifty minutes. The same resource conflict. The data is gathered.

No decision.

Meeting B.

Same sixty minutes. But forty-eight hours before the meeting, three questions go out:

• What do we know about this segment’s core problem?

• What would we need to believe to expand now rather than wait?

• What dependency has to move first?

People show up having opinions.

In the first fifteen minutes, the real constraint appears: not the engineering timeline, but an unresolved question about whether the segment’s buying motion fits the current sales model. Nobody had named it. It sat under the resource debate the whole time.

Once named, the decision takes twelve minutes.

The AI receives a decision, a rationale, and three context updates to encode for the agents running the expansion work. The execution cycle starts that day.

The difference isn’t discipline or facilitation. It’s context design.

Before a meeting fires, ask:

What does the decision-maker need to believe, and what do they need to know, for this conversation to produce calibration instead of recirculation?

If you can’t answer that before the invite goes out, the meeting isn’t ready.

Every Meeting Is Either Building or Burning

Meetings have two legitimate outputs:

1. Build the context that makes a decision possible.

2. Produce the decision.

If a meeting does neither, it’s a pure loss—because the machine still runs, just on old assumptions.

So be honest about the product.

A coordination meeting produces assignments: who’s doing what, by when, with which resources. If agents can generate that automatically, human time spent producing it is pure waste.

A decision meeting produces a commitment: what we’re doing, why, what we’re not doing, and what changes downstream.

A context-building meeting produces the inputs that make that commitment possible: what’s true, what changed, what we believe, what we need to learn, and what must be settled to decide.

If the meeting builds context or produces a decision, the time was spent. If it does neither, the pipe just helps you execute faster on yesterday's context.

There is no neutral meeting.

Every hour spent in a room where the real question stays buried is an hour where the system gets no update. The execution layer keeps running on yesterday’s picture of the world.

Compounding works both ways.

Meetings that build context leave behind a sharper map: what’s true about the customer, the market, and the constraints. The next decision starts half-made.

Meetings that avoid both context and decision leave behind a log. And logs don’t move the business.

Most organizations have spent years optimizing how they meet. Almost none have designed how they decide.

Decision Architecture—The Design of Organizational Judgment

The companies that keep gaining from AI over the next three years won’t be separated by model choice or agent stack complexity.

They’ll be separated by judgment.

Decision architecture is the design of organizational judgment: how a company decides what’s true, what matters, what to do next, and what to ignore.

This work has always existed. It just didn’t have enough space. When execution was slow and expensive, judgment got squeezed between coordination, approvals, and the drag of getting humans to move together.

Agents change the economics. Execution gets cheap. The constraint moves upstream.

When a machine can carry work forward nonstop, the quality of the business depends on the quality of the calls that aim it. Agents don’t fix judgment. They amplify it. Clean judgment turns into compounding. Sloppy judgment turns into fast, consistent mistakes.

Decision architecture is the system that keeps judgment usable at scale.

It determines who decides what, what good context looks like before a call gets made, and how a decision changes what the execution layer does tomorrow.

Strategy still lives upstream. But this is the daily work of keeping a powerful execution layer pointed at the right problems, with current inputs, under clear ownership.

Returns are capped by what your organization can decide, and how quickly it can update what it believes.

P.S. Fast decisions aren't fast. They're the last five minutes of slow work most leaders never see. The Context Pyramid maps the levels behind every decision that actually moves.

Read it here - The 5 Level of Slow Work Behind Fast Decisions

Thursday, 1 p.m.

Someone is explaining why the decision made on Monday doesn’t work in the field.

You made that call on Monday because you had the full picture. Market position. The deal on the table. It took you three seconds because you’d been carrying that context for six months. The decision felt clean.

But there was a constraint your team doesn’t know about yet.

By Thursday, that missing detail matters. A weird case shows up, the kind that only breaks things when the constraint exists. Someone follows the script. The script is missing a page. So you’re back in the same room.

Now you replay the week. Where did it drop?

Maybe it was Slack. Maybe it was a decision you made at 9 a.m. and unknowingly remade at 3 p.m.

This isn’t a communication issue or a speed issue. The people in this meeting can do the work.

The judgment that lived in your head on Monday never made it into the room by Thursday.

The meeting keeps coming back because your judgment didn’t travel.

The decision made it into the room. The six months behind it didn’t.

That gap is context debt: the judgment you’re carrying that never made it to the team. Every fast call that stays in your head adds to it.

Holding context in your head feels like speed. You see the situation, spot the pattern, decide. Three seconds because of six months.

That speed is real—and it’s locked to you.

Each quick decision leaves a deposit.

One undocumented call is fixable. You can patch it later.

A team that knows the script but not the thinking behind it can still get by. They’ll follow steps, copy past wins, and hope the next case looks like the last one.

But when one person’s head holds every non-obvious call in the company, the deposits don’t get cleared. They stack.

Thursday at 1 p.m. is what it looks like when that limit hits the field. The company moves at the pace you can personally carry. When you’re not in the room, the room guesses.

You can see this problem in five levels. Each level fails in a different way, and each one caps the company at a different size.

The Context Pyramid

• Domain: You've named the container. You know what terrain you're reading, specifically enough to distinguish a signal from noise. Each domain builds its own pyramid.

• Signals: You can say what you’re noticing—what you watch for, and what it tends to mean. You stop the meeting on one detail everyone else skimmed past.

• Scripts: You have a repeatable play you can point to when this case shows up. A teammate can run it without you—and knows when to pause.

• Models: ou can build the structure that resolves competing scripts—which one leads, which one limits, and when those roles swap. The play breaks and you can name what you're protecting, what you're giving up, and what would flip the call.

• Transfer: You can take someone else’s thinking apart and rebuild it with them until decisions stop routing back through you. Next week, they handle the new version without you—and can explain why.

These levels aren’t a ranking. They measure how far your thinking can travel.

It starts in fog. Someone asks what to do next and there’s nothing to point to. No read. No signal. No play. You’re guessing.

Then you get a couple calls right. You start to trust the feel. A read in your body, with nothing you can hand to someone else. Fog and intuition aren’t levels. They’re conditions inside whatever domain you’re reading.

After a few wins, it starts to look like speed.

But it’s speed with a catch. When you’re in the room, things move. When you’re not, they stall. Your team starts running on stop-and-go.

Keeping things moving takes a different kind of effort: putting your thinking into something other people can carry.

So it’s in the room even when you’re not.

Level 1: Domain

The pyramid doesn’t start when you get your first clear read. It starts when you decide what you’re reading.

Domain is the container. It sets the walls of the pyramid. Each domain has its own signals, its own scripts, its own form of judgment.

Fog and intuition live inside domains. They’re conditions, not levels. You can carry fog in a domain after twenty years, or have a sharp read in one you entered six months ago. Where you start on the pyramid isn’t determined by time inside the domain. It’s determined by how clearly you’ve named what you’re building in.

That’s the first act of slow work: getting the container right.

Sales is often too broad to generate a signal. “I want to get better at sales” is a direction: it tells you where you’re headed, not what to look at when you get there. The narrowing question is: what about sales? “B2B enterprise CRM sales” is a domain. Bounded enough to tell you what signals to watch for, which scripts have been tested, what breaks when a play meets the wrong case.

The step up from Domain isn’t more experience. It’s deciding what domain that experience belongs to. Specifically enough to start naming what you notice.

Level 2: Signals

Now you can name what you notice. You can point to the tell, not just the outcome. You catch shifts early and can make small moves before you’re locked in.

Signals help you stay light on your feet. They don’t justify a big bet on their own. If you treat a signal like a full story, you’ll commit too early and pay for it.

Signals don’t travel far on their own. The step up is to write them down in plain language: what you watch for, what it usually means, and what you do when you see it.

Level 3: Scripts

This is the first level where other people can run the move without you.

A script is a repeatable play with steps, inputs, and a default decision path.

Sometimes it’s written. Sometimes everyone “knows it” but it still lives in one person’s head.

Scripts are valuable because they keep work moving when you’re not present. They also create a new problem: they work until they don’t.

The edge case is the test. The script hits something it wasn’t built for. The failure mode is running it anyway, because it’s the only thing available.

The step up is to mark the boundary: when the play applies, when it doesn’t, and what triggers escalation.

Level 4: Models

Scripts compress what you know inside one domain, and models are what you build when domains collide.

A sales script says: close faster. Ops says: don’t overpromise. Marketing says: make the claim bigger. Each one works in its own lane. Put them in the same meeting and you get three answers to one question.

A model is the structure that resolves that clash. It explains which script leads, which one limits it, and when those roles swap.

You don’t build one model. You build a set. One for pricing, where sales and finance pull against each other. One for hiring, where speed fights culture. One for product calls, where customer signal runs into engineering capacity. Each model is a field-tested way to settle a specific kind of conflict.

That’s why models are hard to hire for. You can hear someone’s scripts in an interview. Ask what they’d do and you get their playbook. Models only show up under pressure, in new situations where multiple domains demand different things at once. The rare person you’re trying to find is the rainmaker: someone who has built enough of these models that the resolution happens as reflex, not math.

It’s also why senior people can’t always explain their calls. The conflict and resolution can happen faster than words. The mind gets the output, not the steps.

When you’re in the room, decisions move because the model is present. When you’re not, work stalls, detours, or returns in a Thursday meeting. The answer traveled; the model didn’t.

The step up is to make the model portable. Share more than the call: name the scripts in conflict, say which one won, and why. State the constraint that broke the tie, and the condition that would have flipped it. That’s what someone else needs to build their own models—and handle the next version without you.

Level 5: Transfer

Transfer is when the logic stops running through you.

Not “I told them what to do.” “They can think through the next one without me.”

This is the slowest work, and it pays the furthest forward.Each person you help build Models doesn't just carry the answer into the next room. They carry the reasoning. The scripts. The constraint set. The call they can make without you because they’ve seen you make it enough to know why.

When someone makes a mistake, can you see where the thinking broke? The missed constraint. The wrong assumption. The tradeoff they never weighed. Then can you rebuild that part with them? Not the answer. The logic underneath it. So the next decision changes.

Correcting the answer fixes today. Rebuilding the reasoning fixes the pattern.

But Transfer isn’t the top of a single pyramid. It’s the bridge to what’s next.

When judgment becomes portable, it does two things at once: it confirms you’ve built something real in this domain, and it tells you where to build next. You don’t transfer into thin air. The question that opens after Transfer is always: what domain does this judgment need to enter?

Lateral transfer moves at the same altitude: same complexity level, different terrain. The judgment you built with first-time homebuyers about emotionally-driven financial decisions moves to first-time investors. The frame holds. The signals are different.

Vertical transfer elevates in the same domain: from transactional pattern recognition to market cycle reading.

Either way, you’re not done. You’re at the start of a new container.

The step up from Transfer isn’t more time in the current domain. It’s naming the next one specifically enough to start building in it.

Climbing the pyramid is a practice you repeat.

It grows the way fluency grows.

You notice something you usually carry in silence, you name it, you give it a shape, and you do it again next week.

The first limit is willingness.

To combat that, keep a short set of questions in play long enough to get honest answers:

• What do I keep turning over in my head?

• What do I keep explaining to people who should already know it?

• What shows up across different rooms, different quarters, different people?

• What do I assume everyone sees that clearly disappears when I leave?

Those are your raw material. The judgment you’re already carrying. The parts of the job other people can’t reach yet.

The hard part is that your most valuable judgment often goes dark.

After you’ve made the same read a hundred times, it stops feeling like judgment. It feels like obvious. The pattern fires before you name it. The call lands before you track the logic. That’s why it feels fast. The faster it feels, the deeper it’s buried. What looks like instinct is often compressed experience that never got words.

The “obvious-to-you” layer is the hidden layer. Pulling it into the open is the first job.

Skip it, and the breakage shows up higher up the pyramid.

Scripts without the thinking behind them are brittle. They run clean until the edge case shows up, then they snap. The person running the play can’t adapt it, because they don’t know what it was built to protect.

Judgment that never gets rebuilt through Transfer stays trapped with you. Problems get solved when you’re present. The loop returns when you leave. Thursday ends when the logic travels without you.

Each level becomes the footing for the next. You climb in order.

In practice, the slow work shows up as small moments:

• A call you make, plus the reasoning that led to it.

• A play you write down instead of carrying for another quarter.

• A decision you walk someone through instead of dropping the verdict.

• A pattern you name out loud so someone else can start watching for it.

These moments don’t feel like building. They feel like stopping in a day that already feels packed. Most of them add fifteen minutes you think you don’t have.

That’s the constraint: stopping long enough to give your thinking a form, instead of spending it again.

If you stay in motion, you keep spending context. Calls route back to you. Decisions wait for you. You move fast and you become the pinch point.

If you pause at the right moments, judgment starts traveling. The room keeps moving when you’re gone.

The slow work is what makes everything else move.

You can start tomorrow with a tool you already have.

Not because it does the thinking for you. Because it keeps the question on the table when you’d normally move on.

You’ve felt this before. You’re walking someone through a decision, and halfway through you hear yourself say something you didn’t know you knew. You didn’t plan it. The act of explaining pulled it out.

Use the tool the same way. Treat it like a room where you’re the one doing the explaining—and the explaining is the work.

Start a sentence. Let it press you to finish it. Say the half-formed version. Let it reflect it back with the holes showing. Try again. That back-and-forth is the practice.

Use it as a mirror. Bring rough thinking. Ask it to hold the other end while you shape it into something you could hand to someone else.

How to Practice the Context levels

You can read the pyramid and nod along.

Or you can practice it tomorrow.

Pick a real decision you made this week and push it up one level. Use an AI chat as a practice partner. Not to think for you—just to keep asking until your reasoning is out in the open.

Open a new chat. Choose one decision. Start at the level your last Thursday meeting points to. Then run the prompt for that level.

Each level of the pyramid has a different kind of practice:

Domain

Name what you're building in. Specifically enough that you know what signals belong inside it, and what you're not trying to read.

Domain Prompt:

Signals

Take a recent signal and say what it means, not just what happened. “Revenue dipped” is a fact. The signal is what that fact points to for this quarter, this team, this customer. Let the tool ask the follow-up you usually skip.

Signals Prompt:

You are a thinking partner who helps turn observations into meaning. Your job is not to interpret for someone. It's to hold the question open until the interpretation surfaces from the inside.

PROMPT QUESTIONS
"Think of something you've noticed recently — a shift, a pattern, a moment that felt significant but you haven't fully processed.
Describe what you observed. Just the facts. What happened?"
After they respond:
"Now say what it means. Not what happened — what it points to. For this situation, this team, this quarter. What does that observation tell you?"

RESPONSE LOGIC
If they produce both the observation and a clean interpretation — specific, directional, actionable:
Say: "That's not just a signal — that's the beginning of a script. You're past Level 2. Take it to Level 3."
If they have the observation but the interpretation is vague, general, or restates the fact:
Reflect what they gave back and say: "That's what happened. Now say what it means. Finish this:
'When I see ___, it usually means ___, so the move is ___.' "

Press to complete all three parts. If the middle part won't come — the meaning behind the observation — that's where thinking is still sitting at the surface. Press there specifically.
If the third part won't come — the move:

Say: "The observation is clear. The meaning is clear. The move is what turns a signal into something someone else can use. What do you do when you see this?"
When all three parts hold, reflect the complete signal back in one sentence — observation, meaning, move.
That's the output — a signal with enough shape to become a script.

Don't advance until all three parts hold without prompting.

Scripts

Walk through a play you run often. Lay out the steps. Then ask why each step exists. The “why” is usually where the judgment is hiding. A play travels better when the thinking behind it travels with it.

Scripts Prompt:

You are a thinking partner who helps turn repeatable moves into transferable plays. Your job is not to evaluate the play. It's to find where the thinking behind it is still hidden — and press until it surfaces.

PROMPT QUESTIONS
"Think of a move you run regularly — something you do the same way because it works. Walk through it. What are the steps?"
After they respond:
"Now for each step — why does that step exist? What is it protecting against, or setting up?"
After they respond:
"Where does this play break? What's the case it wasn't built for — and what happens when someone runs it anyway?"

RESPONSE LOGIC
If they can walk through the steps, explain the reasoning behind each one, and name the edge case clearly:
Say: "That's not just a script — that's a play with judgment built in. You're past Level 3. Take it to Level 4."

If they can walk through the steps but the reasoning behind them is thin or assumed:
Reflect the steps back and say: "The play is clear. The thinking behind it isn't traveling yet. For each step, finish this:
'This step exists because ___. Without it, ___.' "

Press through every step. The step where that sentence won't complete — that's where the judgment is hiding.
If they can explain the reasoning but can't name the edge case:

Say: "Every script has a boundary — the case it wasn't built for. Describe the situation where someone runs this play and it breaks. What's different about that case?"
If the edge case still won't come, press here:
'This play assumes ___. When that assumption is wrong, the play ___.' "
When steps, reasoning, and edge case all hold:

Reflect the complete play back in this form —
"The play: [steps]
The thinking behind it: [why each step exists]
Where it applies: [the condition]
Where it breaks: [the edge case]
What triggers a different call: [the escalation]"

That's the output — a script with enough structure to become part of a playbook.

Don't advance until all three layers hold without prompting.

Models

Tell the story of a recent call. What did you notice? What did you weigh? What did you rule out? What did you decide? Keep going until the logic holds together without you patching it mid-sentence. If you’re still patching it, the reasoning is still stuck in your head.

Read more

It’s 11pm and you’re looking at a slide deck that explains why the quarter missed.

Not reading it — you wrote most of it. You’re looking at the space between the slides. The section that says “people” when you were expecting “pipeline.” The chart showing the team executing harder into territory that wasn’t working six months ago and isn’t working now.

The deck has an answer. The answer is wrong.

You already know what you’ll do. Change the person running sales. Bring in a consultant to audit the process. Schedule an offsite, get everyone realigned. These are the moves that are supposed to work. Some of them will work, briefly. The quarter after the change will look better. Then it will flatten again.

Here’s what almost never happens: you stop before acting and ask which element is the constraint.

Not “what’s wrong.”
Not “what should we change.”

Which element in the system broke first?

Until you can name the element, you’re fixing symptoms downstream without getting to the source. Adding process to a prioritization problem. Retraining people around a positioning failure. Moving faster in a direction that was already off.

The cash register isn't ringing. You redesign the store.

The Discipline That Makes You Rigid

Picture the moment the strategy becomes official.

The moment the leadership team nods, the deck gets filed, and the initiative list gets turned into a roadmap.

In that moment, something happens that no one names: the model freezes.

You've hired against them. Budgeted against them. Aligned the team to them. The cost of being wrong compounds from that moment — invisibly, because every week of execution makes the model harder to change.

That’s waterfall. Big planning before building. Review before action. It feels like discipline.

It’s also a trap.

Waterfall pushes uncertainty to the start, then takes away your ability to respond once you’re moving.

You’re investing in research, but research captures stated problems, not where people are headed. Customers can tell you what annoys them. They can’t map the future they’re trying to reach. Research gives you the surface. The thing they’re reaching for shows up only when you build, ship, and watch what they do. Instead, you compress the unknown into one bet, then you lock execution.

So you drive by the rearview mirror.

The measurement problem makes it worse. Planning cycles run on lagging averages: quarterly revenue, survey scores, aggregate churn. That data tells you what happened. It can’t tell you what’s about to happen. Strategy is a bet on what comes next.

By the time the lagging data tells you the bet is wrong, the plan is already six months into execution. You've hired for the bet. Allocated budget for the bet. Aligned the team to the bet. The cost of adjustment climbs with every week you're in motion.

The rigor that felt like discipline becomes the reason you snap.

You don’t see it because the model isn’t a diagram on a wall. It’s the cadence you inherited: the annual offsite that anchors the year, the business review rhythm every team has built around. It doesn’t feel like a choice. It feels like “how we work.”

You call it conviction. It’s a blind spot with a louder voice.

Courage Is a Data Problem

It’s 2am. You’ve been turning the same question over for an hour.

You know what you want to do. The logic holds. But there’s a gap between what the data supports and what you’re about to commit to, and it feels heavy. People who look decisive in moments like this have always seemed like a different species—less bothered by that gap, more willing to move without the certainty you can’t quite get.

You’ve probably called that difference courage.

That frame doesn’t help.

At 2am, the uncertainty is real. You don’t have enough signal to feel steady. When the signal is thin, every action feels like it carries more of you with it. The “courage” you think you need scales with the gap: the farther the jump from what you can see to what you’re signing up for, the braver the move looks. It’s not personality. It’s what happens when you try to decide with blurry numbers.

So the fix isn’t to pump yourself up. It’s to see more clearly.

Quarterly reports are averages. They sand down the edges, flatten the weird stuff, and leave you with a clean story after the fact.

What closes the gap is behavior in motion: what a specific set of customers is doing right now, not what the “average segment” did last quarter. Early patterns that show up before the outcome. Outliers that point somewhere new.

This isn’t a stats argument. It’s a direction problem. The customers at the edge are often the first to move. When you average them away, you lose the clue you needed.

The best early-stage teams didn’t solve this by being braver. They solved it by shortening the loop.

Early-stage teams don’t carry more courage than ones at enterprise. They start with less certainty and change course more often. They learn faster, so the distance between what they know and what they’re betting on stays small. The bet stays close to the signal. The need to “be brave” shrinks.

Not more conviction. Just a shorter learning loop.”

The Harder Discipline

Thursday at 3pm, an early-stage team finishes a customer call with an unexpected signal — not a complaint, not a feature request, but a different framing of the problem. By 5pm, they’ve changed the sales story. By Monday, they’re checking whether it changed anything.

Another team hears the same thing. It lands in a survey. It gets rolled into a quarterly pull. It gets summarized in a deck. It becomes an action item, handed to a workstream, reviewed at the next cycle. By the time it reaches a decision, the early-stage team has already tried two versions and knows which one moved.

The difference isn’t headcount. It’s thestructure of the loop.

Teams running the loop aren't better at strategy because they're smarter. They’re running a system you can actually run. They take a working view of reality, act on it, watch what happens, update, and act again.

Starting with less certainty is what keeps your ability to change. Moving before feeling certain isn’t reckless. You’re keeping ability to respond to what you learn. Waiting for certainty has already hardened the bet. Every week of waiting raises the price of changing course.

And planning events get mistaken for discipline.

The annual offsite. The business review. These are events. They feel strict because they’re structured, because they demand prep, because they pull the exec team into the same room. But an event isn’t a loop. The loop is the discipline.

Not the planning meeting. Not the strategy doc. Not the frozen list of priorities. The loop: run, learn, adjust, run again—often enough that you don’t need to wait for the next event to change.

Rigor lives inside the loop, not in how much you do before you start.

The hard part is knowing what to keep fixed and what to change.

It’s easy to treat flexibility like a mood: stay open, respond to what you learn. True, but vague. It doesn’t tell you what must not move.

Keep the “what” fixed. Your positioning: the change you own for the customer, the job they’re trying to get done, why your approach belongs there. Your priorities turn that into choices. The closer you get to the real problem—beneath the stated one—the more precise your positioning becomes. That precision isn’t optional.

Change the “how.” Process is the how. The how is where you move.

On Thursday, the team didn’t switch problems. They changed how they talked about the problem. Same what. New how. That’s the loop working.

The default is to get this backwards. Stay fuzzy on the what—positioning stays loose, the change you claim stays unnamed—and they clamp down on the how. The process becomes sacred. The playbook can’t move. Fuzzy what, fixed how. That’s waterfall in miniature: executing a process for a bet you can’t say out loud.

A plan is easy. It’s static. You can finish it, present it, approve it, file it.

A learning loop stays in motion. It asks for a different kind of leadership: hold the what steady enough to execute, keep the how loose enough to learn.

At the same time.

That tension is the work. Lock both what and how and you get a plan that can’t change. Stay vague on both and you get a team that can’t act. This only works when the what stays firm and the how stays open.

One question drives everything from here:

Which part is slipping?

The Flywheel Diagnoses Where Strategy Fractured

Here’s what it looks like when positioning breaks.

Sales explains the product one way to one buyer and a different way to the next. Product ships features that serve three conflicting stories. Marketing writes copy that could fit any competitor. The leadership team agrees in the room, then splinters the moment everyone walks out.

Everyone is busy. Nothing compounds.

The reflex is to fix execution: tighten the process, retrain the team, rewrite the messaging. Those are visible moves, so they feel like progress. But they’re downstream. The break is upstream.

You probably don’t need a brand-new strategy. You need to know what snapped.

The Strategy Flywheel is a diagnostic for locating where it broke.

Five elements, each resting on the one above it:

Positioning → Prioritization → Process → Performance → People

The flywheel runs in order. Positioning is the customer change you own. Prioritization is what deserves focus given that change Process is how you deliver the change, on purpose, repeatedly. Performance is how you tell if the change is sticking. People shows who has to act, and whether they can say the why without a script.

Clarity flows from the top. When positioning is clear, priorities stop fighting each other. When priorities are narrow, process can be designed around them. When process is coherent, measures start to mean something. When measures mean something, teams can move without constant executive rescue.

Break the chain anywhere and you’ll see symptoms below it.

This is why the reflex to “fix people” so often fails. The symptoms look like a people problem—slow execution, mixed messages, constant re-explaining. But the cause is usually higher up: fuzzy positioning or scattered priorities showing up at the bottom.

Positioning is the most misread element.

It’s often seen as a messaging problem. The language is off. The pitch needs work. The brand voice isn’t landing. So messaging gets fixed, and six months later the same misalignment reappears.

Because positioning isn’t a messaging problem. It’s a territory problem.

Territory means: what customer change you own, who it’s for, and why you—not anyone else—gets to claim it. That decision sets the boundaries for what you build, what you say, and what you measure.

If you polish the words without choosing the territory, you end up with a clean surface on top of a crooked frame.

Hold the Frame

A team is three weeks into Q2 when the head of sales notices a pattern — not a trend, just three accounts responding differently to the same pitch. She brings it to the Monday sync. By Wednesday, the team has changed what they’re testing. The next planning event is eleven weeks away.

That’s the loop running.

You saw the other version two sections back: the same signal arriving via satisfaction survey, quarterly data pull, QBR deck, action item, workstream, next planning cycle. By the time it reaches a decision, that team has run the experiment twice and knows whether it worked.

That gap is learning velocity — how fast the model improves because it’s in motion.

Your role in that loop isn’t to generate the strategy. It’s to hold the frame — steady enough for execution, loose enough for learning — so the cycle can run without waiting for the next event to authorize adjustment.

The team who gets this right becomes a different kind of bottleneck — not depending on the leader for answers, but the one holding the tension that keeps the model alive.

The plan doesn’t compound. The rhythm does.

Which element in your Flywheel is the constraint?

For the forward view — how to build the Flywheel from Positioning through People — start here: The Strategy Flywheel: How Strategic Clarity Compounds Into Momentum

If you want to think more clearly than 99% of people, you need to think on paper.

Not type. Write.

Think about last year. The books you finished, the podcasts that felt like insight, the newsletters you actually read. How much of it do you use? Not remember — use. How many of your decisions are running on something from that consumption? How much of your thinking actually changed?

For most people who answer honestly, the number is close to zero.

That’s not an indictment of your effort. You showed up. You consumed seriously. You did what you were supposed to do. But there’s a question that matters more than “did you remember it?” Did it change how you think?

Look at the beliefs you’re operating from right now. The mental models underneath your decisions. The assumptions you haven’t examined in a while. How much of that is from the content you consumed last year, and how much is the same thinking you arrived with?

Information went in. Thinking didn’t change.

That’s not a memory problem. That’s a processing problem.

Information Doesn’t Become Wisdom on Its Own

Here’s what actually happens with information.

There’s a progression:

Information → Knowledge → Understanding → Intelligence → Wisdom.

Information is raw input. It enters, competes for space in working memory, and begins fading almost immediately. Most people stop here. They consume information and call it learning.

Knowledge is when information connects to something you already understand. That connection doesn’t happen on its own. It requires effort. Organization, comparison, context-setting. You have to do something with what you received. When that work happens, you can describe the idea. Explain it to someone else. The transition from information to knowledge is active.

Understanding goes deeper. It’s when you can explain not just what, but why. When you can predict: if this, then that. Understanding comes from application. From using the knowledge somewhere and watching what happens. Most people never reach this level because they never test the idea. They read it, store it, move on.

Intelligence is transfer. Taking what you understand in one context and applying it somewhere it doesn’t obviously belong. Seeing the pattern underneath the examples. This is where synthesis lives. Where two unrelated things connect and reveal something neither contained alone.

Wisdom is when the insight changes how you navigate reality. Not just what you think. How you decide. What you notice. What you do differently when it matters. Wisdom is integration. The level where knowledge stops being something you carry and starts being how you see.

Most people stop at information. Some reach knowledge. Very few reach wisdom. Not because they can’t. Because they never had a system that moves them through the progression.

Wisdom isn’t reserved for people who’ve lived long enough. It’s achievable now. Through application. Through the processing that most people skip.

The shower insight is the clearest evidence of this.

You’re standing under the water. A problem you’ve been carrying for three days suddenly cracks open. You see it completely. The connection is obvious. The path forward is clear. You feel genuinely brilliant.

Then you turn off the water.

By the time you’re dry, it’s gone. Not faded — gone. You try to reconstruct it. The outline is there but the clarity isn’t. The specific texture of the breakthrough, the way everything fit together in that moment. That’s not coming back.

That wasn’t a memory failure. That was a hardware limit.

Working memory holds about four things at once. Not seven, as we used to think. In 2001, Nelson Cowan’s research revised Miller’s “magical number 7” to closer to four chunks. In the shower, with no competing demands, your brain’s four slots were all pointed at the same problem. The insight assembled itself. The moment you stepped out and started processing other things — what’s for breakfast, where’s my phone, what do I need today — those slots got replaced.

Writing changes that equation. When you externalize a thought onto paper, you free a slot. The page holds it so your brain doesn’t have to. Which means your brain can process deeper.

Drawing fires visual, motor, and semantic processing simultaneously. Three encoding pathways at once. Writing fires two. Typing fires one. More pathways means deeper encoding — which is why the hand on paper does something the keyboard can’t.

Not because digital is bad. Because analog demands more from your brain, and that demand is what produces encoding.

This is also why AI-generated frameworks feel hollow. The framework looks right. The structure is sound. But nothing encoded. The thinking that would have happened working through it stayed with the tool, not with you.

Thinking Compounds. Here’s the System.

This isn’t a three-step process. It’s three flywheels that feed each other. Each one operates at a different level.

A flywheel stores rotational energy. You put energy in to get it turning. Once it’s moving, it takes less energy to keep going. Each rotation compounds.

Flywheel Thinking runs three of them.

The Insight Flywheel operates at the level of self. It surfaces what’s already in you. The thinking buried under the noise of everything you’re consuming, managing, reacting to. The raw material is your own experience, your own contradictions, your own unresolved questions. The practice excavates it. That’s this piece.

The Ideation Flywheel operates at the level of connection. It catches what surfaces between sessions — the insight that sparks while you’re driving, the question that shows up in a conversation, the half-formed idea that arrives before you’re fully awake. This flywheel connects your analog depth to the world outside the notebook. That’s Part 2.

The Implementation Flywheel operates at the level of audience. It takes what you’ve excavated and connected and turns it into thinking others can use — strategy briefs, content, product thinking, decisions. Anything that requires taking what’s in your head and getting it into a form that creates value. That’s Part 3.

Each flywheel’s output becomes the next one’s input. The analog practice produces raw material. The voice ideation flywheel processes it into connectable ideas. The digital deployment flywheel publishes it into the world. The system feeds itself. The thinking compounds.

You’ll start this to think more clearly.

That’s the first thing that happens, and it’s real. But you’ll keep doing it because it reveals something else. Who you actually are as a communicator. Your natural tendencies start appearing on the page. Whether you reach for frameworks first or stories first. Whether you think in questions or declarations. Whether you excavate through argument or through example.

Each flywheel has its own internal momentum.

Together, they compound into something AI can’t replicate: your original thinking, your unique voice, and the people who need to hear both.

Friction Is the Feature. The Ideation Flywheel Stays Analog.

The first flywheel should stay analog.

Not because I’m against digital tools. I use them heavily in the second and third flywheels. But the insight stage has a property that digital shortcuts: friction.

When your hand moves across paper, your brain encodes differently. The slowness forces a kind of attention that typing doesn’t demand. You can’t move faster than you can think. You can’t cut and paste your way around an unresolved idea. You can’t format something before you’ve understood it.

There’s a second thing the slowness produces. You become deliberate about words. When you can’t outrun your thinking, you have to choose. You can’t produce volume and sort it later. The hand on paper forces the question before the pen moves: is this what I actually mean? Typing lets you skip that question. Analog doesn’t.

That friction is what most people are trying to eliminate. Faster, smoother, less resistance.

But friction is the feature. Not the obstacle.

Here’s what happens when you skip the insight stage and go straight to implementation. You open a document, you type fast, you produce something that looks organized. But the thinking is thin. You organized before you understood. You produced output before you encoded input. The structure is there. The depth isn’t.

There’s a phrase I keep coming back to: if writing feels hard, it’s working. Not because difficulty is a virtue, but because difficulty means your brain stopped skating the surface and started tunneling. The resistance you feel when you’re writing by hand about a genuinely unresolved problem. That’s not a signal to slow down. That’s encoding happening.

The insight flywheel isn’t anti-technology. It’s pro-depth. AI belongs in the second and third flywheels, where your thinking has already been processed. Deploy AI at the first flywheel, before you’ve excavated, and you’re asking someone to help you build before you’ve laid the foundation. The construction will be fast. The structure won’t hold.

That shows up in the content itself.

Without the insight flywheel, you end up publishing concepts. Structurally sound, logically coherent concepts. The same ones thousands of other people are publishing.

What stops a scroll isn’t a concept. It’s specificity. Your specific failure. Your specific lesson. The thing that only exists because you were in that situation, with those stakes, at that moment. Nobody else has that. Because nobody else lived it.

That specificity lives in the notebook — in the unresolved questions, the contradictions, the half-formed observations you haven’t examined yet. Skip the flywheel, and your content is built on borrowed ground. You have ideas. You don’t have a perspective.

The slowness isn’t a bug. It’s the mechanism.

10 Minutes a Morning. The Rest of the Day Thinks Differently.

The practice works because of what it’s actually doing.

You’re not just capturing thoughts. You’re locating yourself.

When you sit down with the notebook, the primary question isn’t “what do I know?” It’s: where am I in my thinking right now? What do I believe versus what do I assume? What have I worked through in this territory, and what am I still in the middle of?

The journal doesn’t create answers. It reveals where you are in the progression toward them. You can’t build on a foundation you haven’t located.

This is different from what most people use journaling for. Most journaling is capture. Record what happened, record what you feel, preserve the memory. That has value. But it’s not the same as locating.

Locating means: where am I in this, specifically? On this question, this problem, this decision — where am I in my own understanding of it? The journal answers that. It shows you where you are relative to where you thought you were. Sometimes you’re further along than you realized. Sometimes you’re further back. Either way, now you know. And knowing where you are is the first turn of any flywheel. Nothing moves until position is established.

Daniel Priestley calls this Pause, Reflect, Document — P-R-D. I haven’t found a better name for it.

Here’s how to run it.

The setup: Morning, before anything else. Before email. Before your phone. Before you’ve started reacting to anyone else’s agenda. Paper and pen. Ten minutes minimum.

A dedicated notebook. Not a general scratch pad. Not your work journal. One notebook. One practice. Nothing else goes in it.

A format that doesn’t impose structure — dot-grid or blank — keeps the page open to what wants to emerge, including sketches, arrows, diagrams. Some ideas have shapes that words can’t carry.

The investment is a pen and a notebook. The insight flywheel is accessible by design.

The prompt: Write about whatever is unresolved. Not structured, not pretty. Not a recap of yesterday. What’s unresolved. What’s sitting in the background of your thinking, taking up space you don’t always notice.

Pause is the hardest part. Most people skip straight to Document — they pick up the pen and try to write before they’ve stopped. Pausing means sitting for thirty seconds before the pen touches the page. It means asking: what actually occupies my thinking right now? Not what should — what does?

Reflect is where the work happens. You’re not journaling for therapy, and you’re not writing a strategy memo. You’re thinking out loud on paper. Externalizing the loops that are running in the background. The contradiction you noticed but haven’t resolved. The decision you’ve been deferring. The question that keeps surfacing.

Remember the shower insight? The one that was perfectly clear and then gone? This is how you catch it before it disappears. The analog session is the capture that happens before the shower ends. Before the insight gets replaced by the next demand on your working memory.

Document is the output — not a polished summary, but a record of where you are in your thinking today. It becomes the input for tomorrow. And that’s where the flywheel starts turning.

Here’s what will happen if you do this consistently.

First, something will clarify that was fuzzy. Not because you thought harder. Because you externalized it. The act of writing about an unresolved problem surfaces resolution that wasn’t available when it was just running in your head. You’ll write three sentences and suddenly know what you think.

Second, you’ll contradict yourself. You’ll write something, and four sentences later, write something that doesn’t match it. It’s synthesis waiting to happen. The contradiction means there’s a layer underneath that you haven’t reached yet.

Third, one insight will surprise you. Priestley uses the phrase “mountain of value.” The buried wealth of thinking, experience, and connection that exists in you, unexcavated. At some point in the first few weeks of this practice, something will surface from that mountain. An idea you didn’t know you had. A connection between two things that didn’t seem related. That moment is the flywheel catching.

Day one feels forced. You’re asking a part of your brain to do something it hasn’t been trained for. Write anyway. It doesn’t have to be good. Good isn’t the point.

By the end of the first week, patterns start showing up. The same themes reappear. The same questions resurface. That repetition isn’t a failure of the practice. It’s signal. The things that keep coming back are the things that actually need attention.

By the end of the first month, revelations happen. Something you wrote two weeks ago connects to something you wrote yesterday. You didn’t see the connection in the moment; the journal held both pieces until you were ready to put them together.

By month three, connections appear that would have been invisible before. You’re not starting from zero each morning. You’re starting from a progressively higher floor.

Your natural tendencies start appearing on the page. Some people, when they write freely, reach for frameworks first. Structure arrives before story. Others reach for story first. The example surfaces before the principle. Some think in questions. Some think in declarations.

But they’re all yours. And the notebook is where you discover which one you are.

You’re not deciding your voice. You’re discovering it was already there.

Voice is how you communicate. Point of view is what you see.

Ideas follow logic — pattern recognition, connecting concept A to concept B, extrapolating from what you’ve read. Anyone with strategic thinking can generate ideas. That’s real. It’s also replicable.

Point of view follows experience. Your specific wins. Your hard-fought losses. The lesson that only exists because you were in that situation with those stakes. Nobody else has that combination. It can’t be borrowed. It can only be excavated.

The notebook is where point of view gets developed — not decided, excavated. The same way voice doesn’t get invented, it gets surfaced. Both were already in you. The practice finds them.

The journal starts the excavation.

The Foundation Is Set. Now the System Starts.

You have a system for surfacing insights that have been hiding. Not through consumption. Through compression.

The insight flywheel creates raw material. Your own thinking, externalized and encoded. Not someone else’s framework applied to your situation. Your experience, your contradictions, your questions, processed into a form that compounds.

There’s no AI prompt here. That’s deliberate. The insight flywheel’s value is in the friction. Protecting that friction is part of using this correctly. The moment you hand this stage to a tool, you shortcut the encoding that makes everything downstream worth doing.

Start tomorrow. Before anything else. Ten minutes. Whatever notebook you have, dedicated only to this. Write about whatever is unresolved. No structure required.

The friction is the feature. Protect it.

But that’s only the first flywheel.

You’ve built the foundation. The depth, the raw material, the self-location that makes original thinking possible. The question that comes next is what happens between sessions. The insight that sparks while you’re driving. The question that shows up in a conversation. The idea that arrives on a Tuesday morning when you’re not near your notebook.

That’s where the second flywheel turns.

The Voice Ideation Flywheel doesn’t work without what you’ve built here. The depth you created is the fuel. Part 2 shows you how to catch what surfaces between sessions and turn it into something you can use.

The hardest part isn't the morning session. It's the idea that shows up at 2pm when you're not near your notebook.

Reply and tell me how you're catching those — or whether you're losing them.

You’re executing well. Building real things. Moving. And something still isn’t resolving the way it should. The effort is real. The gap between effort and outcome keeps widening.

That gap is almost never an execution problem.

When I started writing the Rented series, I was exploring one idea: the difference between owning something and renting it.

• Rented identity.

• Rented problems.

• Rented positioning.

The pattern kept showing up — leaders and companies building on foundations they didn’t own, competing inside categories someone else defined, executing brilliantly inside races they could never win.

The more I followed that thread, the further it went.

Positioning isn’t just a marketing problem. It’s the surface layer of something deeper — a question about where you operate and who sets the terms.

At its highest altitude, positioning is category ownership.

The leaders who've solved positioning aren't better at articulating what they do. They've stopped competing for position and started defining the space itself.

That’s where the thread led.

This publication is being renamed.

Prime Positioning is becoming The Breakaway.

Same Substack. No migration required. You’re already here.

The Rented series stays. Those concepts are the foundation — understanding what it means to own versus rent is prerequisite thinking for everything that follows.

The thesis behind The Breakaway:

Technology commoditizes the peloton. It amplifies the breakaway.

When AI accelerates execution for everyone, executing harder inside the existing race produces diminishing returns.

The advantage shifts to leaders who’ve stopped competing for position inside someone else’s category and started owning their own. Every new technology wave benefits them. It compresses everyone still in the peloton.

Joe Rogan didn’t go looking for a platform deal. Spotify came to him. YouTube came back to him. That’s not luck — that’s what category ownership produces. Platform optionality. The platforms needed him more than he needed any of them.

And it applies across every industry and every stage.

The Breakaway isn’t about better positioning tactics.

It’s about what game you’re actually playing, and whether it’s one you can win. That question gets more specific from here, not broader.

The writing stays peer-to-peer. I’m not teaching you to make the break. I’m writing from inside it, about what the view looks like from here.

If you’ve been reading the Rented series and something kept resonating — a sense that the problem runs deeper than positioning tactics, that there’s a frame you’ve been trying to articulate but haven’t found language for yet — that’s what The Breakaway is about.

You’ve found the room.

— Michael

The Breakaway · thebreakaway.com

A colleague pinged me on a Tuesday afternoon.

She was deciding whether to restructure her team — a real decision, with real stakes, two weeks of back-and-forth and no clear answer. She trusted my read on these things. So she asked.

I opened AI. Typed in the context. Ninety seconds later I had something clean: four considerations, a recommended path, even the framing she should use with her manager. It was good. Structured. It even used a couple of phrases I probably would have chosen myself.

I read it. Sent it.

Three days later she came back. “I tried your framing. My manager pushed back and I didn’t know what to say.”

I didn’t know what to say either. Because I hadn’t actually thought it through. I’d outsourced the thinking, packaged the output, and called it advice. The answer was clean. The conviction behind it was zero.

She didn’t get bad advice. She got borrowed advice. And there’s no way to defend borrowed thinking when someone starts pulling on it.

The Shift You Don’t Notice

When AI gives you bad output, you know immediately. You push back. You catch it. You stay in charge.

This is about what happens when the output is good.

When it’s coherent and settled and sounds like someone already figured it out — your brain does something convenient. It stops working. Not because you’re lazy. Because the output fills the gap before your own thinking has a chance to show up.

The drift is slow. It starts with “help me write this email.” Then “help me think through this.” Somewhere along the way it becomes “just tell me what I should do here.” You don’t notice the slide because the outputs keep being useful.

And then someone pushes back. And you’re empty.

You’ve had a version of this. Maybe not with a colleague. Maybe in a meeting, answering a question with a response that felt borrowed. Maybe publishing something that sounded like you but came from somewhere else.

The tool didn’t fail you. You stepped back too far. And the longer you keep stepping back, the harder it gets to find where you left off.

Three Stages. One Rule.

I spent the better part of last year working out how to stay the author of my own ideas without dropping tools that genuinely make me sharper. What I landed on is three stages.

Play. Pattern. Production.

Most people skip the first two. That’s the problem.

Play

Play is where you use AI to widen the field.

The default move is to ask for the answer. What should I do? What’s the right call? How should I think about this? That’s handing over the wheel before you’ve decided where you’re going.

Play looks different. You ask for terrain instead. “Give me five different ways to think about this.” “What’s the strongest argument on each side?” “Where do smart people usually get this wrong?” You’re not looking for a conclusion — you’re building more ground for your own thinking to push against.

One rule: no conclusions. Not yet. You’re generating raw material — and what you build from it is entirely your job.

Pattern

After a Play session, close the tab.

Not forever. Just long enough to notice what’s still in your head. Which ideas keep coming back. Which argument bothered you. Which answer felt close but slightly wrong — and you can’t explain why yet.

That dissonance is your thinking trying to show up.

Good AI output sounds settled. Sounds like someone already figured this out. And if you move straight from Play to Production without stopping, you end up saying what the AI said, with your name on it.

Pattern is where you find your actual position. Three sentences. Messy is fine. You’re not trying to be articulate — you’re trying to be honest. What do I keep returning to? What am I resisting? Where does my gut disagree with the logic?

Write it down. Then open the tab.

Production

Now you bring the argument. Now AI comes back in.

This is where most people start. That’s the mistake.

Production only works when you already know what you’re trying to say. You arrive with a real position. Rough around the edges is fine. Then you use AI to organize it, sharpen it, fill the gaps.

The question shifts completely: “Help me say this more clearly.”

One produces owned thinking. The other produces borrowed thinking with your name on it. The difference shows up the moment someone pushes back — because you either built the argument or you accepted one.

Before You Open the Next Tab

Play to think wider.

Pattern to find yourself in the material.

Production to say what you actually think.

Before your next AI session, try this first: write three sentences of your raw take. Don’t make them good. Don’t worry about being right. Just make them yours. Then open the tab.

You’ll notice it immediately. When you already have a position, the output hits differently. You’re not looking for an answer anymore. You’re stress-testing one.

Before you open the next tab, make sure you have something worth testing — not something worth accepting.

What’s something you actually think — that you haven’t let AI clean up yet?

Reply and tell me. I’m genuinely curious.

P.S. This is what I’ve been working through — how thinking without architecture defaults to borrowed conclusions. Not just with AI. Everywhere decisions get made. More on that soon.

Everyone has an opinion about AI.

Enthusiasts say it will create abundance.
Skeptics say it will destroy jobs.

Money is talking — nearly half a trillion dollars’ worth.

In 2025 alone, Amazon, Meta, Alphabet, Microsoft, and Oracle committed $399 billion to AI infrastructure. Projections push that past $600 billion.

Deutsche Bank estimates spending on AI data centers will reach $4 trillion through 2030.

That’s ten times the inflation-adjusted cost of the Apollo program.

And it’s already showing up outside tech budgets. U.S. GDP grew 4.3% in Q3, but the story gets narrow fast: private fixed investment is rising largely because of AI-related spending.

Adoption is already widespread. 72% of companies use AI in at least one business area. ChatGPT crossed 800 million weekly active users.

And the message has gone mainstream. Here’s Marc Benioff in The Wall Street Journal, selling “agentic enterprise” as the new default.

Pull AI-related spend out of the investment numbers, and Deutsche Bank says the U.S. economy would be close to recession.

The debate about whether AI will matter is happening inside an economy that’s already been built around the assumption that it will.

The strategic question is what your operating model looks like while all of it is happening.

Every major economic transition rewards clarity.

The leaders who do well can name what they’re building and what “done” looks like.

The ones who stall try to control the middle—choreographing every step, managing every variable, sitting through meetings that exist because nobody agreed on the destination.

A model like this existed long before business frameworks:

The farmer.

For most of human history, farming was the work. Then industry displaced it. Farmers adapted, scaled, mechanized, or left the field. But the mindset that kept them alive didn’t vanish. It’s built for uneven ground:

• Pests.

• Soil shifts.

• Weather turns.

• Market swings.

Farmers don’t survive by mastering every variable. They survive by reducing the chaos to one question:

Does this serve what I’m growing?

That filter turns noise into action. Forecasts become planting calls. Soil data becomes crop choices. Pest knowledge becomes protection. The farmer wins by setting conditions and judging everything by the harvest.

The Farmer’s Almanac captured the same logic.

It didn’t try to explain the world in full. It compressed patterns into choices you could make, organized around the harvest.

And the work followed a practical order. Learn what the weeds tell you. Then understand the pests. Then improve the soil. Then think across seasons. Each layer matters only if it helps what’s growing.

Handle the inputs. Define the harvest.

Everything in the middle is the system—conditions, constraints, timing.

When the inputs are right and 'done' is clear, hail doesn't send you back to the beginning. It sends you to the almanac. You check what the crop needs now, adjust, and keep moving. Every surprise still runs through the same filter:

Does this serve the harvest?

That’s the mindset worth bringing back.
A way of running work that holds up when the transition won’t sit still.

Specialization broke the loop.

We over-specialized the process and lost the harvest.

It happened slowly. As economies moved from agricultural to industrial, value moved from land to institutions. Work moved indoors. Scale demanded division. Division demanded specialization.

The farmer’s integrated loop got split into roles. Meteorology became a career. Geology became a department. Botany became an identity. What used to serve the harvest became the job—and the job drifted from the outcome.

The loop broke.

The textbook replaced the almanac. The almanac organized knowledge around one question: what does the harvest need? The textbook organized knowledge around a different one: what does this discipline contain? For a century, that model won because industrial scale needed it.

That shift changed what competence meant.

When value sits in land and harvest, you need people who can hold the whole loop. When value moves to institutions and scale, you need people who go deep in a bounded slice. The industrial age made “depth” the standard, measured by credentials and throughput.

Now look at how most organizations actually run. Not on shared models—on meetings. Context gets rebuilt, used once, and then expires. Next meeting, you rebuild it again. That’s the patchwork.

That’s also why language models land so hard. They beat specialists at processing the slices. They don’t replace the job of building the model that connects the slices—working backward from “done,” then forward to test what you thought was true.

If your value is “I process information in a bounded domain,” you’re in a race with something that improves faster than you do.

The farmer competed on judgment. Value lived in the decisions that linked inputs to harvest. Processing any single input was the cheapest part of the loop.

Nobody set out to become a process operator. Institutions trained it in. Incentives locked it in. Reviews measured it. Promotions rewarded it. And over time, specialization started to look like the point.

That bias is still baked into org charts, hiring, and how leaders spend their day.

The industrial age didn’t just produce specialists.
It produced people who forgot what they were specializing for.

Most leaders live in the middle.

Look at your calendar and count the decisions your team is waiting on.

Now count the ones that truly require your judgment—the kind that depends on context only you hold.

That number is smaller than your week suggests.

Most of what fills a leader’s schedule is the middle: the handoffs, the check-ins, the approvals, the updates. Not because the work is hard, but because “done” was never made clear enough for the system to run without you.

You can see it in your meetings:

• Check-ins because the endpoint stayed fuzzy.

• Sync meetings because shared direction drifted.

• Reviews because the model lived in one person’s head.

• Status updates because the work can’t report its own state.

Each one is a workaround. Each one is a step you’re maintaining.

And the standard advice is to make the workarounds quicker. Shorter meetings. Fewer touchpoints. Batch approvals. Push updates async. You get better at pushing traffic through the middle.

But you’re still pushing traffic.

A big chunk of what you call “process” is just payment for missing clarity.

People start work without a shared definition of success, so the middle expands to carry what the start didn’t provide.

Farmers don’t escape uncertainty. They live in it. The difference is that the target is shared and the signals are visible. When the leaves yellow, when the soil stays dry, when pests show up, the work changes. Decisions get checked against the harvest, not against whoever holds the most context.

Most teams run the opposite way. The system can’t move on its own, so everything routes through you. You’re not leading. You’re load-bearing.

That’s the dangerous middle: a week spent managing traffic in a system that never agreed on the destination. It looks like productivity. It’s just motion.

Clarity doesn’t cut steps. It changes which steps deserve to exist.

AI can rebuild the loop—if you start with “done.”

Don’t make the steps faster. Remove the ones that exist only because nobody agreed on “done.”

Most people meet AI as a faster version of their current week: write the email, summarize the doc, draft the report, prep the slide. Same workflow, less time.

That’s just polishing the middle with a better engine.

The farmer used information differently. Weather wasn’t “more data.” It was a decision input. The value wasn’t the forecast—it was knowing what mattered for the harvest.

AI is useful for the same reason. Not because it makes the middle quicker, but because it lets you rebuild the loop.

Start with the outcome. What has to be true for this to be done?

Work backward from that answer. You’ll see two piles immediately: decisions that require your judgment, and steps that follow a pattern.

Turn the outcome into a small set of conditions.
Turn those conditions into signals.
Then let the system watch the signals and act when they move.

• If X happens, notify.

• If Y slips, draft a response.

• If Z crosses a threshold, route it to a person.

That’s the modern almanac: not knowledge for its own sake, but patterns turned into choices, organized around the result.

Prime movers choose what gets built and decide when 'done' changes. The system handles monitoring, routing, and the repeatable moves in between.

With a clear step one and a clear “done,” new tools are easy to judge. Do they move the outcome forward—or do they just make steps faster?

If they move the outcome, use them. If they only make a messy process faster, pass.

Without this model, every new tool becomes another debate, another experiment, another meeting about “how we should use AI.” With it, most of that disappears.

AI isn’t the helper you hand chores to.
It’s the system you build so the middle stops depending on you.

The first cycle is heavy. Then it compounds.

The first cycle is the hardest because nothing is encoded yet. Every judgment call is yours.

You set step one. You define done. You map the middle and separate what needs your thinking from what follows a pattern.

Then you run it again.

Each pass does the same thing: it turns proven judgment into default behavior. What worked becomes the baseline. What broke becomes a boundary. You stop rebuilding from scratch and start building from the last place where your clarity held.

That’s how the loop creates traction. By the fifth cycle, you’re touching far less. Not because the work disappeared, but because the middle stopped needing you.

The farmer learns the same way. In the first season, you’re checking everything—soil, weather, pests—by hand and adjusting day by day.

Ten years later, it’s the same land, but it doesn’t feel like the same job. You know what this soil does after rain. You know which weeks invite problems. Most of the middle runs on patterns you’ve already paid for.

Your system works the same way. Every cycle sharpens the model. A sharper model gives AI clearer conditions, cleaner boundaries, and fewer “it depends” calls.

Over time, the middle doesn’t get faster. It gets smaller.

You don’t start from step one each time. You start from your last milestone of clarity.

Here are 3 prompts to get you started:

Prompt 1: The Middle Audit

You are a strategist who helps leaders see where they're carrying work that the system should carry. You know that most of what fills a leader's week isn't hard — it's unresolved. Check-ins exist because the endpoint stayed fuzzy. Sync meetings exist because shared direction drifted. Reviews exist because the model lives in one person's head. These aren't process steps — they're workarounds. Your job is to help people see which parts of their middle expanded because the endpoints were never set.

You're speaking with someone who just read about the difference between managing traffic in the middle and defining the endpoints that make the middle manageable. They understand the concept. Now they need to see it in their own week.

---

YOUR TASK

Ask:

"Look at your last two weeks of work — your calendar, your task list, your recurring commitments.

Two questions:

1. Pick three recurring meetings or commitments that take the most time. For each one: what would have to be true for that meeting to not need you? Not 'how could it be shorter' — what clarity, if it existed, would make your presence unnecessary? If you can't name it, that's the finding.

2. Now think about the last decision your team waited on you to make. Was the decision hard — meaning it required judgment only you hold — or was it just unresolved? Was your team missing your thinking, or were they missing a definition of success clear enough to act without asking?"

Once the user responds, do the following:

1. For each recurring commitment they named, assess whether the dependency is structural or compensatory:
   - Structural: The work genuinely requires their judgment, context, or authority. The meeting exists because the decision is hard, not because the direction is unclear.
   - Compensatory: The work exists because something upstream is undefined — a missing endpoint, an unclear success condition, a model that lives in one person's head instead of in the system.

2. Name the pattern:

   If most commitments are compensatory: "The pattern here is load-bearing leadership. Your week is shaped by the middle — not because the work requires your judgment, but because the system can't move without you interpreting what 'done' means in real time. The meetings aren't the problem. The missing clarity upstream is."

   If most commitments are structural: "Your middle is lean. The commitments you're carrying are genuine judgment calls — decisions where your context matters and the system can't substitute for it. The question isn't whether you should be in these meetings. It's whether the system between these meetings is running on shared definitions or still routing through you for interpretation."

   If mixed: "You've got both. Some of what you carry is genuine judgment work — the kind that earns its place on your calendar. But sitting next to it are commitments that exist because something upstream is fuzzy. The risk is that the compensatory work feels just as important as the structural work, because it takes the same amount of time. The difference is that one deserves to exist and the other is payment for missing clarity."

3. Close with a single observation — not advice — about which specific commitment revealed the clearest gap between judgment and compensation. Frame it as the place where defining "done" would change the most about their week.

Do not suggest process improvements. Do not recommend meeting structures. Just help them see which parts of their middle are load-bearing and which are compensatory.

Prompt 2: The Endpoint Test

You are a strategist who helps leaders test whether "done" is actually defined or just assumed. You know that most teams operate with a version of "done" that sounds specific but isn't — activity milestones (the report is shipped, the meeting happened, the sprint closed) instead of outcome conditions (this is true now that wasn't true before). The difference matters because activity milestones still need a leader to interpret whether the work succeeded. Outcome conditions let the system check itself. Your job is to help people see which kind they're running on.

You're speaking with someone who just read about how the middle expands when "done" is missing — and who may have just discovered (through The Middle Audit) where they're compensating for that gap. Now they need to test whether the definition of success their team is operating from is clear enough for the system to run without constant interpretation.

---

YOUR TASK

Ask:

"Think about the most important initiative your team is working on right now — the one that gets the most of your attention.

Two questions:

1. If you asked three people on your team 'how will we know this is done?' — would they give the same answer? Not the same deliverable — the same conditions. What has to be true for this to be finished? If you're not sure they'd agree, describe what you think they'd each say.

2. Now separate two things: the activities your team is doing from the conditions those activities are supposed to create. The activities are the steps — build, ship, launch, review. The conditions are what changes when the steps work — a customer behaves differently, a number moves, a capability exists that didn't before. Which is your team tracking — the steps or the conditions?"

Once the user responds, do the following:

1. Assess whether the definition of "done" is outcome-anchored or activity-anchored:
   - Outcome-anchored: The team can describe conditions that would be true when the work succeeds — and those conditions are observable without the leader interpreting them. The system can check itself.
   - Activity-anchored: The team tracks deliverables, milestones, or completion of steps — and someone (usually the leader) has to judge whether those steps actually produced the intended result.

2. Name the pattern:

   If outcome-anchored: "Your endpoint is defined. The team can describe what 'done' looks like without needing you to interpret it — and the conditions are observable enough that the system could check itself. That's what makes the middle manageable. The test now is whether those conditions are actually being tracked, or whether they're agreed upon but invisible in practice."

   If activity-anchored: "Your team is tracking motion, not arrival. The steps are clear — everyone knows what to do next. But 'done' is still a judgment call that routes through you, because the conditions that would tell the system 'this worked' aren't defined. That's why the middle feels heavy. The activities run fine. The interpretation of whether they worked is what requires you."

   If mixed or unclear: "There's a version of 'done' floating around — but it lives in different forms depending on who you ask. Some of your team is tracking conditions. Some is tracking steps. And the gap between those two is where your calendar fills up — because when the system can't tell whether the work succeeded, it asks you."

3. Close with a single observation about what the team's current definition of "done" is optimized for — the activity or the condition. If it's the activity, name what condition is missing. If it's the condition, name what makes it visible or invisible to the system.

Do not redesign their initiative. Do not suggest OKRs or metrics. Just help them see whether their endpoint is defined clearly enough for the middle to check itself.

Prompt 3: The Encoding Check

You are a strategist who helps leaders see whether their operating cycles are compounding or resetting. You know that the first cycle is always heavy — every judgment call is yours, every decision is manual, every interpretation is real-time. But by the fifth cycle, proven judgment should be becoming default behavior. What worked becomes the baseline. What broke becomes a boundary. The middle gets smaller — not because the work disappeared, but because the system absorbed what you already figured out. When that doesn't happen, every cycle feels like the first one. Your job is to help people see which it is.

You're speaking with someone who just read about how each pass through the loop should turn proven judgment into defaults — and who may have already seen (through The Middle Audit and The Endpoint Test) where their middle is compensating for missing clarity and whether their endpoint is actually defined. Now they need to test whether their system is encoding what they've learned or forcing them to rebuild from scratch.

---

YOUR TASK

Ask:

"Think about something your team has done more than once — a process you've run through multiple cycles. A product launch, a quarterly plan, a client engagement, a recurring deliverable.

Three questions:

1. Compare the first time you ran it to the most recent time. What decisions did you make in the first cycle that you no longer have to make? What got absorbed into the system — became a default, a template, a rule, a boundary — so you didn't have to think about it again?

2. Now the harder question: what decisions are you still making that you were also making in the first cycle? Not because they require fresh judgment each time — but because nobody encoded the answer. You figured it out once, but the system didn't retain it. Where are you rebuilding context that should already be built?

3. When something breaks or changes mid-cycle, where does the signal go? Does it route to the right person based on conditions — or does it route to you because you're the default interpreter? Is your system watching for signals and acting when they move, or is it waiting for you to notice?"

Once the user responds, do the following:

1. Assess the encoding state across three dimensions:

   Judgment-to-default conversion:
   - Strong: Decisions from early cycles have become boundaries, templates, or rules that the system enforces. The reader is making fewer decisions per cycle, and the decisions they're still making are genuinely new.
   - Weak: The reader is making the same kinds of decisions they made in the first cycle. The answers exist — they've been figured out — but they live in the reader's head, not in the system.

   Context retention:
   - Strong: The system starts each cycle from the last milestone of clarity. Prior decisions are embedded. The team doesn't rebuild context — they build from it.
   - Weak: Each cycle starts closer to zero than it should. Context gets rebuilt, used once, and expires. The reader provides the same orientation, the same framing, the same interpretation of what matters — because the system lost it between cycles.

   Signal routing:
   - Strong: When conditions change, the signal reaches the right person based on what changed. The system monitors and routes. The reader handles exceptions, not monitoring.
   - Weak: When conditions change, the signal routes to the reader by default — not because the exception requires their judgment, but because the system doesn't know who else to ask. The reader is the monitoring layer.

2. Name the overall pattern:

   If encoding is strong across dimensions: "Your loop is compounding. Each cycle starts from further ahead than the last one. Proven judgment is becoming default behavior, context is retained, and the system handles routing. The middle is getting smaller. The decisions still reaching you are genuinely the ones that need your thinking."

   If encoding is weak across dimensions: "Your loop is resetting. You've run this enough times to have figured out most of it — but the system didn't absorb what you learned. Each cycle rebuilds from scratch. The middle isn't getting smaller — it's staying the same size, and you're carrying it every time. The work isn't getting harder. It's just not getting easier, because nothing is encoding."

   If encoding is mixed: "Your loop is encoding in some places and resetting in others. Where it's encoding — where decisions became defaults and context carried forward — the middle shrank. Where it's resetting — where you're still making the same calls and rebuilding the same context — the middle held its size. The gap between those two is the compounding you're leaving on the table. The places where encoding stalled are where your next cycle of clarity work would pay the most."

3. Close with a single observation about the specific place where encoding stalled — the decision that's been made before but isn't yet a default, or the context that's been built before but doesn't carry forward. Frame it as the point where one act of clarity would change every future cycle.

Do not recommend tools. Do not suggest automation. Just help them see whether their loop is compounding or resetting — and where the encoding stopped.

Do you know what “done” looks like?

If you do, the rest gets simpler.

Every tool and capability gets judged by the outcome. You handle step one and done. The system carries the middle. Each cycle turns proven judgment into defaults, and the middle gets smaller.

If you don’t, the rest gets louder. You’ll keep polishing motion that may not lead anywhere—stuck in the dangerous middle, making steps faster without asking why the steps exist. Specialization becomes the job, and the point disappears.

The Farmer’s Almanac only worked because the farmer already knew the harvest. The almanac didn’t pick the crop. It told you which conditions served what you chose to grow.

That’s the prime mover’s job: choose the harvest, define “done,” and set the conditions.

AI didn’t invent this model. It just makes it possible to run it again.

Change the words, change the room. Change the room, change the results.

No Name Tags Required

On a Sunday morning in Seattle, a group of strangers sat down for brunch.

They left like they’d known each other for years.

There were no name tags. You don’t need name tags for friends, even if you just met them.

Instead, there was a Brunch Bingo game on the table, with questions like “Tell me about a fun vacation you went on” and “What’s something you’re working on that excites you right now?”

Questions about the person, not their LinkedIn headline.

The conversations went deep fast. People stayed longer than they planned. They exchanged numbers because they wanted to keep talking. The conversation was worth continuing.

By the end of the morning, strangers had become friends. Follow-ups happened on their own.

A relationship coach and a financial consultant who met at one of these gatherings built a collaboration together.

A colleague in the talent acquisition space saw the format, took it with her, and launched her own version.

It was called Brunch and Banter.

“Brunch and Banter” signals warmth, intimacy, play.

“Networking event” signals obligation, status games, transactions.

Same Sunday morning. Completely different room. Because the words were different.

Eighteen months earlier, it had been three people at a table.

It felt like starting from zero, again.

You may have had a similar experience.

Maybe you moved to a new city. Maybe you changed industries.

Maybe you just looked up one day and realized the people around you were colleagues, not friends, and you couldn’t remember the last time someone called just to talk.

The pandemic handed most people a version of that. Mine came with a few extra layers.

I moved to Portland in January 2020. Uprooted my life from Jacksonville to start something new.

Two months later, the world shut down. Any brunching and bantering would have had to happen over Zoom.

Fast forward: my job moved me to Seattle in 2021, when lockdowns were still in effect. Two cities in two years, one just before a pandemic and one during it.

I knew one coworker in the entire city.

I had a playbook, something I’d built years earlier that I knew worked. But you can’t gather people when gathering isn’t allowed.

So I waited. Invested the time in other things. Then things reopened slowly, people were hesitant, and the muscle for showing up in rooms with strangers had atrophied for everyone.

June 2023. First Brunch and Banter in Seattle. Three people. Me, a friend I’d made in the city, and someone they brought along.

The second month: twenty.

How did three become twenty?

How did twenty become a gathering that produced collaborations, friendships, and a format someone else carried into an entirely different industry?

The answer starts before Seattle. In, Jacksonville, before the pandemic.

When I first moved to Jacksonville, I did what everyone does when they don’t know anyone.

I went to networking events. Tuesday evening mixers, Thursday happy hours, chamber breakfasts. Name tags with your name and title. Elevator pitches. Business card exchanges in hotel lobbies.

Three hours in, you drive home with a stack of cards on the passenger seat. You flip through them at a red light. Half the names don’t connect to a face. The other half connect to a title, not a person.

You met their LinkedIn profile. You didn’t meet them.

Here’s the question nobody asks out loud at these things: Would I want to know this person if I didn’t have a business reason to?

Because if the answer is no, and it usually is, then what you just spent three hours doing wasn’t networking. It was auditioning.

I experienced this in Jacksonville. I experienced it again when I arrived in Seattle. Different cities, culture, and events. Same frustration.

And when I talked to other people at these events, not about business, about the events themselves, everyone had the same quiet realization.

They kept showing up because they didn’t know what else to do.

Every one of those events was built on the same premise: professionals connect by exchanging credentials in an after-work, weekday setting.

The format assumes the transaction is the value. But that’s not why people were in the room. They were there because they wanted to belong somewhere.

The events were fine. The category was the problem.

The natural move, and the one I almost made, is to build a better networking event. Better venue. Better icebreakers. Better name tags. Optimize the format. That’s what it looks like when you compete inside a category someone else defined. You inherit their problem definition and try to solve it better. Every improvement still operating inside the same frame.

I did something different. But it was closer to instinct than insight.

A series of small moves that only made sense looking backward.

At the events I kept attending in Jacksonville, I started doing something small with name tags.

Most people wrote their name and their company. I stopped writing my name at all. Sometimes I’d write Batman. Sometimes Clark Kent. Sometimes a celebrity name that would get a reaction.

The ones who played along, those were the people worth talking to. The ones who looked confused and moved on needed the credentials before they could engage. The format had trained them that way.

Without calling it that, I was running a filter. And the people who passed it were the first ones I invited when something different started to take shape.

Once I knew who belonged in the room, I needed a room.

I discovered a wine bar in Jacksonville called OVINTE. Its lounge couches made it the kind of place where you could sit down, move around, lean into a conversation or drift toward a new one.

A few friends and I started meeting there on Sundays. A buddy of ours sang there, Sinatra style, so we’d grab brunch, listen to the music, and just talk. The only agenda was the conversation.

We called it Sunday Funday.

What happened next wasn’t planned. Because nobody was performing or pitching, the conversations went somewhere real. People brought friends. Those friends brought friends. The group grew.

Two friends of mine, one an ex-Navy officer, the other a financial analyst, met through those Sunday gatherings and started a corporate cleaning business together.

Six figures in their first eighteen months.

Another friend had been job-searching for six months, kept showing up on Sundays, and connected with someone recruiting for a director of process improvement role.

He got the job.

A friend saw how the gatherings worked and it changed how she thought about her own industry. She realized the talent leaders she worked with were as starved for real connection as anyone else. They just didn’t have a format that gave them permission to drop the professional mask.

So she stopped trying to “network” talent acquisition leaders into a room and started hosting brunches called The Talent Collective for them instead.

All of that happened organically. The space allowed people to be themselves instead of performing a professional identity.

The format that promised nothing delivered everything.

The format that promised everything delivered business cards in a drawer.

You’ve probably seen your own version of this. The conference where every badge opens with a title. The happy hour where the first question is always “So what do you do?”

You drive home and realize you spent three hours collecting strangers’ resumes.

There’s a common idea that environment dictates performance. Change the room and you change the behavior. Anyone who’s walked into a library versus a bar knows the room sets the tone.

That principle usually gets applied as advice to find a better environment. Step into the right room. Surround yourself with the right people.

What I’d done, without realizing it, was something different. I built the room myself.

And I built it starting with two words.

The words did the work

For a while the gatherings didn’t have a name. Just Sunday Funday. But something shifted when I gave it one.

I had a reputation in Jacksonville for a certain style of dress. Blazers, pocket squares, the kind of thing that stands out in a beach city. I didn’t announce a dress code. I just showed up the way I show up.

And people started matching it. Without anyone being told to, the energy shifted upward. People treated the gathering differently because the signal said this is worth showing up for.

That’s when it became Brunch and Banter.

Brunch and Banter changed people’s thinking from “work the room” to “have a real conversation.”

That thinking changed their behavior: how they sat, how long they stayed, what they talked about, whether they came back. And the behavior changed the outcomes.

The cascade:

Language changes thinking. Thinking changes behavior. Behavior changes outcomes.

The move to Seattle reset the progress. New city, no community, no mailing list. But I carried the pattern and the confidence that Jacksonville had built. The venue could be found. The people could be found. The skill of building the room was already mine.

That’s what mattered.

I knew who the right people were before I had a single gathering. In Jacksonville, the people who made Brunch and Banter what it became were from charity work, philanthropic organizations, community causes. People who already understood what it meant to bring others together.

In Seattle, I went looking for that same pattern deliberately. Fred Hutch Innovator events. American Heart Association galas. Rooms where the energy ran on generosity, where people showed up because they cared about something beyond themselves.

Thursday evenings, I’d scout venues. The kind of places where the energy loosens, where people are starting the weekend early, travelers settling in, folks coming off the golf course. I’d sit at the bar and mention I was looking for a place to host a brunch event. That line opened more real conversations than any elevator pitch I’d ever delivered at a mixer.

In Jacksonville, the room had been the filter. A wine bar, brunch on a Sunday, elevated dress. That combination isn’t common, and the people it attracted weren’t random. In Seattle, I didn’t have that yet. So I built a different filter.

I charged money. Enough to cover a meal and a drink, enough to filter for commitment. And I designed for the warmth that Jacksonville had produced organically. Brunch Bingo with questions about the person, not their profession.

The mechanisms made strangers feel like friends faster because they skipped the professional small talk entirely.

Before I Had a Name for Any of It

This is a story about a premise I rejected.

The premise was simple: brunch is for friends. Networking is for strangers.

Those are different categories and they don’t cross. Everyone knew that. I just decided to act as if it wasn’t true.

I could have stopped. People won’t show up to eat brunch with strangers. That’s not how it works.

Except the patterns I’d seen told me otherwise — people weren’t showing up to networking events for the networking. They were showing up for the thing networking couldn’t give them. So I bet on the pattern instead of the premise.

Brunch can be for strangers too.

The stakes weren’t enormous. I wasn’t betting my life savings. But I was betting what my professional and social life in a new city would look like.

Looking back, I can see the pattern in my own moves:

• Batman on a name tag — that was positioning before I had the word for it.

• Brunch on Sundays at a wine bar. — that was category design before I understood the concept.

• Brunch Bingo with questions about the person — that was experience design before I could explain why it worked.

How to change the setting that changes outcomes

Every market has a premise that feels too obvious to question.

This is how our industry works.
This is what customers expect.

And inside that premise, there’s an assumption about why people show up. An assumption that might be wrong.

I didn’t change the people. I didn’t change the city. I changed two words.

“Networking event” became “Brunch and Banter.”

The words changed the thinking.
The thinking changed the behavior.
The behavior changed the outcomes.

The setting isn’t the venue. The setting is the language that tells people how to show up.

So here’s the question worth sitting with:

What is the language framing your category right now?

What words are telling your customers how to behave before they even walk in the room?

Pay attention to the language people already use. Not the language in your marketing. The language in their habits. The words they say without thinking, the ones that carry a connotation they’ve stopped noticing.

For example:

Nobody calls it “going to exercise class.” They say “I do CrossFit.” A gym is where you go to check a box. CrossFit is where you go to become someone.

One word. Completely different room.

That’s what language does when you change it deliberately. It wakes people up from the patterns they’ve been operating inside. It interrupts the autopilot. And once someone is thinking differently about what they’re walking into, they behave differently once they arrive.

If you’re building something new, or rebuilding something that stopped working, start with the words.

Not the strategy. Not the format. The words. Find the term your category uses out of habit and ask what it’s actually telling people to do. Then find the word that tells them to do what you actually want.

Your answer won’t be Brunch and Banter. But your answer will be something that can be yours.

Yours lives in the gap between what your market assumes and what your customer is silently frustrated by.

The specificity of the answer is what makes it ownable.

Change the words, change the room. Change the room, change the results.

P.S. If you're thinking about what makes your answer ownable, I wrote a 9-part framework for that. It's called "Own the Narrative That Can't Be Copied."

If you've read the fable, you've watched this play out through James's story. What follows is the architecture underneath it — the instrument that makes the pattern repeatable.

First time here? Start with Episode 1: How Fast Execution Slows Growth

First mover wins a head start. Prime mover wins the rules. This manifesto shows how strategy becomes ownership: define the problem, own the language, and use sequence to take prime position.

When a founder walks into a meeting, they carry something most professional managers don’t.

They know who the customer becomes when the product works, because they watched the first transformation happen.

That context acts as a decision filter.

When everyone in the room shares transformation context, decisions don’t require triangulation. The next move is clear. The filter does the work.

Founders coordinate through clarity. Professional managers coordinate through process: alignment meetings, stakeholder reviews, follow-up sessions. They’re missing the filter that makes answers obvious.

Modern organizations are built to coordinate, not to clarify. When clarity drops, meetings multiply. Another alignment session. Another stakeholder review. The calendar fills with coordination overhead, and the shared understanding of what you’re building and why gets less clear with every meeting designed to compensate.
You can measure it.
You may already have a sense of what this looks like in practice. Decision Velocity is the rate at which an organization converts context into action. It follows a formula:

DV = C × (D/M)

• C is context clarity: the number of strategic domains where the team shares understanding.

• D is total decisions made.

• M is total coordination meetings required to make them.

When C is high, decisions happen in hallway conversations. D climbs. M drops. Velocity compounds.

When C is low, velocity collapses. It doesn’t matter how many meetings you hold or how fast you execute. Zero context clarity means zero decision velocity.

Same meeting. Same data. Different output.

Bain & Company confirmed the pattern in 2016: founder-led S&P 500 companies delivered 3.1x higher returns across 24 years. Paul Graham named it Founder Mode. Neither identified the mechanism.

First Mover vs. Prime Mover

Most companies think advantage belongs to whoever ships first. Ship first. Capture demand. Educate the market before anyone else can.

That’s First Mover Advantage. And it’s fragile.

You ship first. Competitors follow. You educate the market; they inherit it. Product-level speed erodes with every cycle.

Electric cars existed before Tesla. Canned water existed before Liquid Death. Neither was first to market. Both were prime movers who reframed the problem. Tesla made electric a performance and status story. Liquid Death made water an identity. The product existed. The frame didn’t.

First movers ship products. Prime Movers define problems.

You don’t move first. You move the frame.

First movers win time. Prime movers win language.

First movers build on demand. Demand is shallow ground. When someone redefines the problem, the demand shifts with the new definition.

Prime movers build on understanding. Each cycle of evangelism drives roots deeper. Every time you name the problem, educate around it, articulate what others haven’t seen, the understanding accumulates. The deeper the roots, the harder you are to displace.

Prime Mover Advantage is structural. You define the problem. You name the new and different. You educate the world until your category definition tips. Until customers use your language to explain their own problem, and competitors have to answer to it.

In an era where AI executes at the speed of prompting, execution speed stops being the advantage. Judgment speed is. AI commoditizes the doing. The prime mover owns the thinking.

And when the definition tips, competitors are forced to operate inside the game you defined. Every competitive response validates the frame. Every alternative reinforces the category.

That’s not competitive advantage. That’s category gravity.

Category owners capture the majority of the economics in their category. Everyone else competes for the remainder. The market has already voted on this. The companies we now call dominant were rarely first to ship. They were first to define what the category meant.

The 3.1x isn’t a one-time win. It comes from owning the definition. Continuously.

Most leaders reading this will agree. Clarity matters. Ownership beats renting. Context is the multiplier.

Agreement is easy. It’s also worthless without the instrument to maintain it.

What Happens When You Move Without It

There are three versions of this collapse.

You may recognize them. All produce the same outcome. One is worse than the others.

You Shipped Into Demand You Didn’t Define

The pattern is predictable.

You hear about an opportunity. You see the demand forming. You build the solution, get it into the market, start iterating with customers. There are challenges — there always are — but you’re working through them. Customers are responding. The trajectory feels right.

Then something shifts.

You don’t see a competitor arrive. What you see is customers going quiet.

Deals that used to close just... don’t. Responsiveness drops. And then you realize: someone came in with a problem definition you dismissed, one you never considered, and the market reorganized around it.

All the work you did, all the iteration, all the traction — built on an assumption about what the problem was. An assumption you never questioned because the demand seemed to confirm it.

You captured demand. You didn’t define the problem.

And when someone else defined it differently, the demand moved with them.

You Scaled Coordination Instead of Context

As headcount grew, shared understanding didn’t.

Founders build context by building the company. Three people in one room, all seeing the same picture. The transformation story lives in shared experience.

None of it is written down. It doesn’t need to be. Everyone was there.

Then new people join who weren’t there for any of it. Teams stop forming around the customer and start forming around functions. And context that made decisions obvious stays trapped with the people who built the thing.

The professional manager’s problem is inheritance. They never received the context. They inherited systems optimized for coordination, not context. The capability is there. The filter isn’t.

Run the Decision Velocity Formula. C stays low because shared understanding was never distributed. D stays low with it. M climbs. More alignment meetings. More stakeholder reviews. More coordination overhead to compensate for clarity that was never built into the system.

The company grows. The context doesn’t.

Every new hire adds coordination cost without adding context clarity.

You Went Quiet — and the Category Became Available

This is the worst version. Because you know what you lost.

The founder had the context. They built it. They lived it. And they had the ability to distribute it.

To document it. To embed it in how the organization thinks. To make it travel beyond the room where it was born.

If that trade-off sounds familiar, think about when it started. You were climbing. Every conversation sharpened the position. Every deal reinforced the category.

Then you won — or won enough.

The sigh of relief. The turn inward. The fires that needed attention, the operations that needed scaling, the team that needed building. You stopped watching the category because the category seemed settled. Revenue was growing. The metrics said everything was working.

But the metrics had shifted without anyone noticing. From traction signals that measured the change you were creating to performance numbers that measured the business you’d already built.

You were optimizing supply. You’d stopped generating demand.

And the category you thought you owned was quietly becoming available.

Redefine or Be Defined

The founder, or the team that inherited the founder’s role, drifts from the customer.

By the time the messaging feels off, the real damage happened months ago.

The price of ownership is an ongoing obligation: keep evangelizing, keep defining the problem, keep educating the market.

When you stop paying, you create a vacuum. And vacuums get filled.

Not by better products. By better problem definitions.

The founder who recognizes this doesn’t try to win the old game.

They define a new one.

A new problem definition. One that reframes what customers actually need, in language that makes the competitor’s pitch sound like what it is: a product claim dressed up as a category.

Prime Mover Advantage is built by defining what comes next. Before someone else does.

You can define the category on stage and still lose it in the hallway. The gap between definition and operation is where most strategies die.

The Strategy Flywheel

Most strategy frameworks follow the same pattern.

Either:

Develop strategy with one set of tools: off-sites, consultants, planning documents.

Hand execution to a completely different set: OKRs, project management software, quarterly scorecards.

Two instruments. Two languages. Two rhythms.

It’s not a communication problem. It’s an instrument problem.

You wouldn’t write a song on piano and then perform it on drums and wonder why it sounds different.

The Strategy Flywheel is one instrument. It runs in both directions. Backward to diagnose where you are. Forward to operate where you’re going. Same five elements. No translation layer. No handoff.

Five Elements, One Sequence

You’ve already watched these elements operate.

The flywheel has five elements. Each one enables the next. Skip one, and everything downstream breaks.

• Transformation. What change do your customers seek that only you can deliver? The shift in their reality that they can point to and name. If you can’t articulate that change in language customers use, you’re describing capabilities, not claiming territory.

• Signals. How do you know the change is actually happening? Usage metrics and satisfaction scores measure activity. Every competitor tracks those. Signals measure whether your specific transformation is occurring. If a customer had green across every dashboard and still left, you were tracking the wrong change.

• Context. What shared understanding enables autonomous decisions? When the team shares transformation context, decisions don’t require alignment meetings. People make aligned choices because they see the same picture. When they don’t share that context, you compensate with coordination: review boards, stakeholder syncs, go-to-market alignment sessions. Thirty hours of meetings because the filter is missing.

• Constraint. What’s the one bottleneck that, if resolved, accelerates the transformation fastest? Every system has one constraint that limits throughput. Improving anything else feels productive but doesn’t compound. The flywheel reveals which constraint to attack this quarter. The one that moves the customer’s transformation forward, not the one that feels most urgent internally.

• Territory. What do you own as a result? When all four upstream elements are aligned, you don’t compete for a position. You define the category. The market organizes around your definition. Competitors respond to your frame. Every cycle of delivery strengthens the foundation.

Each element answers one question. Together, the five questions form a complete diagnostic:

What do you own at every level of your strategy?

The Ownership Check

Here’s what makes the flywheel diagnostic.

Run the five questions. For each one, ask: What do we own here?

What territory is yours. What a competitor cannot claim because you built it from the transformation out.

If the answer at any element is empty, that’s the diagnosis.

Most teams discover they can describe capabilities at every level. They struggle to name ownership at any of them. Features that any competitor could match. Metrics that any company tracks. Processes that any consultancy could install.

The empty column is clarity. It shows you exactly where to build.

And the check always starts at Signals.

Signals: The Leading Indicator

When a founder drifts from the customer, Signals is where it shows first.

The other elements may look fine. Transformation unchanged on paper. Context still running through the OKR system. Constraint metrics green. Territory numbers holding — for now.

But the human connection to the customer’s transformation is what keeps the flywheel honest. When the CEO drops below 3% customer time, when new hires never hear the transformation story, when the team optimizes dashboards instead of tracking whether customers are actually changing, the flywheel is already drifting. The numbers haven’t caught up.

Harvard research found the average CEO spends 3% of their week with customers. Less than two hours. Less than they spend with consultants.

If context clarity is the multiplier, and the source of that context is the customer’s transformation, 3% explains why the column is empty. Not at one company. Everywhere.

Signals is the canary. When it drifts, every other element starts optimizing for the wrong thing. You measure activity instead of transformation. You prioritize what’s urgent instead of what compounds. You build process around coordination instead of clarity.

By the time the messaging feels off, the real erosion happened months ago. At the Signals level.

The flywheel reveals the instrument. Keeping it in tune is a different discipline.

The Traction Loop

Quarterly reviewers see trends. Weekly practitioners see inflection points.

The founder running a twenty-minute check on Tuesday morning catches a shift that won’t show up in the competitor’s dashboard until the quarterly review. By then, it’s too late to define the response. They’re reacting to a frame someone else already set.

The Traction Loop is the operating rhythm of the flywheel. A weekly check. Twenty minutes. Five questions. Each one tests an element. It starts with Signals and works downstream.

How much time did I spend with customers this week?

Customers living inside the transformation you promised. The ones who can tell you whether the change is real. What did you hear? What changed? Is the transformation actually happening in their reality, or are you measuring proxies for a change you’ve stopped witnessing firsthand?

If Signals is healthy, check downstream. If Signals is drifting, that’s the early warning. Fewer customer conversations. The team optimizing metrics instead of tracking change.

The flywheel tells you which element to tighten this week. Not next quarter.

What Gets Written Down

When you run strategy annually, the output is a document. A deck, a plan, a set of OKRs. The thinking that generated those outputs lives in the room where the offsite happened. Six weeks later, the document exists but the thinking behind it is fading.

When you run the flywheel weekly, the answers accumulate. Each pass captures the current state. What you heard from customers this week. What signals shifted. Where the constraint moved. Written answers survive turnover. Head-carried context walks out the door.

The weekly rhythm IS context distribution. Every check embeds the founder’s thinking into a system the team can see. New hires read the accumulated answers. The transformation story lives in the system, not in one person’s head.

That’s the difference between a framework you have to look up and a mental model that travels. The weekly rhythm builds the mental model. Written answers make it portable.

Each week you run it, you deepen your understanding of the problem, sharpen your articulation, drive roots deeper. Each week you skip, the drift begins. The Traction Loop is more than a diagnostic. It’s the evangelism discipline that keeps ownership alive.

The Ownership Frame

Ownership is binary.

When you ask “how do we differentiate?” you’re already assuming the category. You’re looking for ways to stand out within boundaries someone else defined. The answers are tactical: messaging tweaks, feature comparisons, price adjustments.

When you ask “what do we own?” you’re questioning the category itself. A change your customers can point to. A shift they can name.

You either own the change or you compete in someone else’s category.

The change you create is the position you own.

This is what the flywheel produces when alignment is tight. Transformation, Signals, Context, Constraint, and Territory locked so tightly that competitors are forced to operate inside the game you defined. Every competitive response validates the frame. Every alternative reinforces the category owner’s position.

Flywheel alignment IS ownership. The weekly check IS the audit. And the Ownership Frame is the name for what you see when you look at a flywheel where every element answers the question clearly: what do we own here?

Ownership moves through three states.

• Building. Aligning elements one by one, closing gaps. You don’t have Prime Mover Advantage yet. You’re constructing it. Each Traction Loop pass surfaces what’s missing and what’s next.

• Cemented. All five elements lock. The alignment is tight enough that the market organizes around your definition. This is Prime Mover Advantage achieved. The moment competitors stop choosing to compete with you and start being forced to.

• Drifting. An element weakens. Signals always drifts first. When customer time drops, when new hires inherit coordination instead of clarity, when the team optimizes dashboards instead of tracking transformation, the decay has already started. You just can’t see it yet.

You build it. You cement it. You maintain it. Or you lose it. All through the same instrument.

That’s what earns trust. A system honest about the full cycle. Including how you lose it and how to catch the drift before the market does.

Strategic Power That Survives Shifts

Every company fights two battles: winning customers and owning their position in the customer’s mind.

You can win the first without winning the second. That’s revenue without equity. The transaction is yours. The position isn’t.

When you own your position, activity compounds into equity. Feature advantage erodes faster with every cycle. Ownership advantage compounds.

That’s where strategic power lives. In the definition.

Apple in 1997 was 90 days from bankruptcy. Fourteen product lines. Twenty-five disconnected marketing campaigns. Jobs came back and asked one question: Who is our customer, and what change are they on?

Every decision ran through that answer as a filter. He cut 14 product lines to four. Took the Microsoft partnership. Said no to everything that didn’t advance the change they owned. From the outside, people called it genius. From the inside, it was the filter doing the work.

But Jobs never codified that filter. He carried it personally. It worked while he was in the room. Context that lived in Jobs’s head walked out the door with him.

That’s the difference between maintaining a filter and distributing one. The Traction Loop is the distribution system Jobs never built. Running the flywheel weekly externalizes the filter into a shared record that survives any single person’s departure. The written answers don’t just capture what the founder sees. They teach the organization how to see.

Strategy frameworks tell you what makes advantages durable and what disciplines to practice. None of them answer the question that matters most: Where do you start?

Transformation ownership answers the sequence question. Own the change first. Every discipline you practice and every power you build sequences from that answer.

The question isn’t what power should we build?

It’s what change should we own first?

Every cycle you deliver the promised change strengthens the next.

Every cycle spent competing on someone else’s terms strengthens theirs.

That asymmetry reveals everything.

Your Next Prime Move

Make one prime move today.

Before the strategy sprint. Before the team alignment sessions. Before any work that requires coordination you don’t yet have.

You start with yourself.

Your Perfect Day

When’s the last time you thought about your perfect day?

An ordinary Tuesday. Everything in your life exactly as you wanted it.

What time do you wake up? What’s the first thing you hear? Who’s there? What does the morning feel like before you even open your eyes?

And then: what do you actually do? How does the day unfold? What are you working on? Who are you working with? What happens by the time you go to sleep?

This isn’t fantasy. It should feel possible.

Take five minutes. Write it down — not in your head. On paper or screen where you can see what you chose and what you left out.

If that came easily, you’re warmed up.

But this isn’t just a warm-up. The clarity you build about what mobilizes you becomes the lens for reading what mobilizes your customer.

You can’t see someone else’s transformation until you’ve mapped your own.

Your Customer’s Perfect Day

Now do it again. For your customer.

An ordinary Tuesday in their life after your product has done its work.

What changed? What does their morning look like? What decisions come easier? What friction disappeared? What’s possible for them that wasn’t before?

If this feels harder, that’s the point.

Most leaders can articulate their own day with surprising clarity. The customer’s day gets fuzzy.

The transformation you’re building toward turns vague the moment you try to make it specific.

The change your entire strategy exists to deliver — you can’t put it in a Tuesday.

That gap between your clarity and theirs is the gap your strategy has to close.

If you can’t describe the change in a day-in-the-life, you can’t own it.

The Bridge Between Them

Now the hardest question. How does your product move your customer from their current

Tuesday to the one you just described?

Write it as a cascade. Five sentences. Each one builds on the last. This is the flywheel compressed into a strategic narrative:

“We serve [people] who are trying to [change].”

“We know it’s working when [traction signal].”

“We deliver that change through [mechanism].”

“We protect that position by [investment].”

“We own the territory where [transformation] happens.”

Read them back. In order.

Does each sentence earn the next? Does the fifth sentence feel inevitable after the first four, or does it feel like a leap?

If the cascade flows, you have a strategy that connects.

If it breaks, if sentence three doesn’t actually deliver what sentence two measures, you just found the structural gap your team has been working around.

Here’s what usually happens. Sentences three through five come quickly. The mechanism, the investment, the territory.

That’s the work you’re swimming in every day. The how is loud. But the first two sentences, who you serve and what change they’re actually after, those are the ones that slow you down.

And if they’re vague, everything below them is optimizing execution on an assumption about the customer that may not hold.

That’s the gap you can’t see from inside your own strategy. You’re too close to it. The how feels solid because it’s what you touch every day. The who and the why sit underneath, quietly shaping everything. They’re the hardest to pressure-test alone.

Notice what just happened. The sentences that slowed you down are the ones that determine whether you own territory or rent it.

Shallow understanding produces problem statements anyone could claim. Deep understanding produces names that stake territory. Because they capture what others haven’t named.

Your customers already carry this story in three parts. Where they were before, what shifted, and what they’d never go back to. Extracting it is its own discipline.

Use this AI prompt:

I’m going to share five sentences that describe my company’s strategy as a cascade. They follow this sequence: who we serve and what change they’re after → how we know it’s working → how we deliver that change → how we protect that position → what territory we own.

Each sentence should earn the next. Sentence 2 should measure what Sentence 1 promises. Sentence 3 should deliver what Sentence 2 tracks. Sentence 4 should protect what Sentence 3 builds. Sentence 5 should name the territory that Sentences 1-4 make ownable.

Tell me where the chain breaks — where one sentence doesn’t earn the next. Be specific about which connection fails and why. If the chain holds, say so — not every cascade is broken, and I’d rather know it’s solid than have you manufacture a problem.

​Paste your five sentences. Let the tool pressure-test the connections. Then rewrite the sentence that breaks.

The cascade is the flywheel in five lines. If it holds, your strategy travels without you in the room. If it doesn’t, you know exactly where to dig.

The Perfect Day is how you start. The Traction Loop is how you maintain it. The cascade is how you test whether the two connect.

Do this tonight. Start with your day. Then your customer’s day. Then the bridge between them.

The less clarity you have on Layer Three, the more you need the flywheel. And the more you’ll return to this exercise as your understanding deepens.

The Flywheel gives structure. The Traction Loop gives rhythm. Ownership gives direction. Clarity gives velocity.

That’s flywheel thinking. You get faster as you get clearer.

Keep renting. Or build something you own.

Start with your day. Then change your calendar.

Customers are polite.

They tell you what they want in clean sentences. They answer your questions. They approve the plan.

You write it down. You build the plan. You execute.

When it ships, nothing breaks. No one complains. And nothing changes.

The ask was clear. The need wasn’t.

Customers aren't misleading you. We just don't spend much time naming our problems.

Not because we can’t, but because sitting with pain without a clear path out is its own kind of work.

So we cope. We patch over things. We adjust to the inconvenience.

And when someone asks, we give the shareable version. The answer that fits in a meeting. The one that sounds reasonable and solvable.

Customer surveys might be the clearest example. You want clean data, so you ask structured questions. Scales. Multiple choice. Ranked lists. You get numbers and dashboards and confidence. You don’t get depth.

Or you offer an open text box and get fragments. Half-thoughts. Surface complaints. Evidence of how hard it is to explain what’s wrong when no one has named it yet.

Both approaches capture what customers can say. Neither reaches what they can’t.

The stronger signal lives elsewhere.

The behavior that doesn’t match what they said in the survey. That’s where the real problem lives. Not in their words. In their patterns.

The problem isn’t your solution. It’s the problem your solution was designed for.

Problems Have 3 Levels

Every problem your customer brings you has structure underneath it.

Not just surface and depth. 3 distinct levels.

Each one produces a different kind of positioning and a different kind of solution.

The external problem is what customers say out loud.

“Our feedback data is messy.”

“We need better survey response rates.”

Every survey tool in the category organized around the same stated pain. Describable, shareable, and commoditized on arrival.

Solve here and you get product positioning. Functional solutions. Feature competition.

The internal problem is what the external one makes them feel.

“We’re collecting all this feedback but can’t act on it fast enough.”

The frustration underneath the function. Most leaders think this is the breakthrough—dashboards, faster analytics, smoother experience.

It's not. It's a more articulate version of the wrong problem.

Solve here and you get brand positioning. Emotional resonance and differentiation. But still reactive.

The philosophical problem is what they believe should be true about the world, but isn’t.

Surveys can’t touch it. Dashboards can’t reveal it.

Not because the tools are broken, but because the tools were built for the first two levels.

Qualtrics almost missed it too. For years—faster collection, better analytics—until they asked a different question: What if the problem isn’t how we collect feedback? What if feedback itself is the wrong target?

The insight that changed everything.

The entire survey industry had been measuring one while assuming it captured the other. Feedback ≠ experience. And nobody was naming it because the instrument itself made the gap invisible.

That’s the philosophical problem. And when you solve at that level, something different happens.

You don’t get product positioning or brand positioning. You get category-level positioning. It names what should be true and builds toward it.

Qualtrics stopped improving surveys and started owning the gap between feedback and experience. The category moved to them.

The level of understanding your customer can feel but can’t articulate. They can’t describe a destination they haven’t reached — and if they had that clarity, they’d already be solving for it.

The depth of transformation you can deliver determines the position you can hold. And you can’t reach that depth by getting better at the first two levels. It’s a different kind of problem entirely.

So why do you keep ending up at Level 1?

3 Mistakes When Discovering Your Customer’s Real Problem

Not bad intentions.

It’s not lack of effort.

But how most problems are discovered in the first place.

Mistake 1: You’re looking in the wrong place.

The data you rely on is organized around solutions, not problems.

Categories are built around what gets transacted. Products purchased, features adopted, contracts renewed. The entire architecture is solution-side, built backward from the offering.

Every piece of market intelligence you rely on, from category definitions to competitive analysis to market research, describes the solution side of the exchange. It tells you what customers ended up choosing.

But customers don't start with your solution. They start with their problem.

Survey data is the sharpest version of this. The company designs the questions. The company chooses the scale. The company decides what to ask and what to ignore. The customer’s experience gets filtered through a solution-side instrument before it reaches a decision-maker. The tool companies trusted most to understand customers was built to confirm what suppliers already believed.

And the signal that reveals Level 3? The customers whose behavior doesn't fit your categories. The ones building workarounds and cobbling together solutions your data says they shouldn't need.

That signal gets averaged out. Filtered out. Ignored.

Mistake 2: You’re asking the wrong questions.

Even when you go directly to the customer, your questions are shaped by your solution categories.

• “How satisfied are you with X?”

• “What features would improve Y?”

• “How likely are you to recommend Z?”

Every question starts from what you built, not from what they’re living with.

The philosophical problem is pre-verbal. Your customer experiences it as a recurring wrongness, a sense that something's off, but they can't isolate it. They report symptoms instead. And your questions, structured around your solution, give them a format for symptoms. Not for source.

This isn't a vocabulary gap you can close with better surveys. If they had clarity about the future state, they'd already be solving for it. And some are — with whatever tools they have.

When Qualtrics introduced “experience data (X-data),” versus “operational data (O-data),” the response wasn’t excitement. It was relief.

“That’s what I’ve been trying to say.”

The naming didn’t create the problem. It made the problem visible. Before the language existed, customers couldn’t point to it because there was nothing to point at.

Mistake 3: You’re not earning the real answer.

Even when customers sense the philosophical problem, it lives at a level they won’t expose.

Not can’t. Won’t.

Level 3 touches competence, judgment, worldview. Admitting the philosophical problem means admitting the frame you’ve operated in—maybe for years—was borrowed. That the metrics you’ve reported don’t measure what you said they measured. That the methodology your team is built around might be solving for the wrong thing.

Nobody walks into a meeting and says “Our entire approach is fundamentally flawed.”

Nobody tells their board “The data I’ve been presenting doesn’t measure what I told you it measures.”

These aren’t knowledge gaps. They’re identity-level vulnerabilities.

People will talk about external problems all day. Slow response rates, messy data, poor analytics. Those problems are safe to share. They fit the solution categories everyone already agrees on. The philosophical problem doesn't fit anywhere comfortable. It requires saying something about yourself, your team, or your approach that you'd rather not say out loud.

The real answer isn’t hidden behind better research. It’s behind trust.

And trust isn’t a method. It’s a condition you create.

How the three mistakes compound:

• Your data is organized around solutions, so it never surfaces the real problem

• Your questions are framed by your solution, so even direct conversations stay on the surface.

• Even when someone gets close to the philosophical problem, the conversation retreats to safety.

Solution-side data produces external answers. Solution-shaped questions keep the philosophical problem pre-verbal. And without trust, it stays protected.

Three mistakes, each one reinforcing the next.

Because the problem driving all of it was borrowed from the surface.

“What If the Buyer Isn’t the User?”

Reaching the philosophical problem is hard enough when you’re talking to one person.

But what if you’re not selling to the person who uses what you build?

It’s a classic B2B concern.

“B2C is easier, you are only selling to one person. In B2B, I have to think of the company.”

But doesn’t a human still sign the check you cash?

If yes, the levels still apply. They just multiply.

Think about buying a toy for a child.

The child says “I want the one my friend has.” That’s Level 1. Present-tense, immediate, social.

But underneath it: I want to belong.

A five-year-old can’t articulate that. They’re an expert on the present: “I want what my friend has.” They can’t name the deeper need driving the behavior.

The parent says “I want something educational that’s worth the money.” Also Level 1 on the surface.

But underneath: I want to be the kind of parent who makes thoughtful choices about what shapes my child’s development.

That’s not a product requirement. That’s identity. That’s philosophical.

Two stakeholders. Two external problems. Two hidden Level 3 realities. Neither one is wrong. Neither one is the whole picture.

LEGO understood this. They didn’t just sell blocks or creative play. They owned the shared philosophical truth: structured imagination builds better futures, for kids and the parents enabling it. Both Level 3s addressed simultaneously.

This isn’t a B2B phenomenon. It’s what happens whenever the person buying isn’t the person using. Which happens with most meaningful purchases.

Now escalate this to enterprise software, where the buyer is never the user, and there are multiple stakeholders in between.

Each one gives you the external version. The safe version. The one shaped by their solution categories.

The Customer Experience analyst says “I need cleaner data and higher response rates.” The VP of Customer Experience says “We need to connect feedback to business outcomes.” The COO says “We need to reduce churn and improve NPS.”

Three external problems. Three conversations that feel productive. None of them reaching the source.

The COO’s version sounds strategic. But underneath it: I don’t actually understand why customers leave. I have data that says they’re satisfied right up until they cancel. Something fundamental is broken in how we listen.

And deeper still: if I dismantle our decade-old system and it fails, that’s my legacy.

The analyst senses it. The VP feels it. The COO carries it.

Qualtrics didn’t just build a better tool. They spoke to the philosophical violation that each of these stakeholders was protecting separately.

“Your system for understanding customers is structurally incapable of telling you what you need to know.”

That landed across every level of the org chart, because each person felt it from their own angle.

They took responsibility for naming what every stakeholder sensed but none would say. That’s not better discovery.

That’s not more empathetic selling. That’s problem ownership.

Problem Ownership Requires Trust

The usual instinct is to fix the methodology: better questions, fancier listening tools.

That’s the wrong move.

Admitting anxiety about the future means admitting the present isn’t working. Admitting attachment to broken habits means admitting people are choosing comfort over change.

The gap between the stated problem and the real problem isn’t about information. It’s about trust. Closing it starts with a shift most haven’t considered: stop talking about your solution and start owning their problem.

You won’t earn this conversation through better surveys.

Here’s why customers stay at the surface.

The push of current pain is what they share freely. That’s Level 1. It’s describable, it’s safe, and it fits in a meeting. They’ll hand it to you because it costs them nothing to say out loud.

The pull toward a different future is what they feel but can’t name. That’s Level 3 from the customer’s side. The philosophical problem you’ve been building toward. They can sense that something should be different, but they’re not living in that reality yet. They can’t describe a destination they haven’t reached.

And the reason they never bridge the gap? Two forces holding them in place.

Anxiety about what the change exposes. That your metrics don’t measure what you said they measured. That the methodology your team is built around might be solving for the wrong thing.

And comfort with the habits they’ve built around the broken thing. The workarounds. The devil they know. Even painful routines become familiar. Choosing Level 1 and Level 2 solutions feels safe precisely because those solutions don’t require anyone to confront what’s actually wrong.

Current pain pushes them to talk. The future pulls them forward. But anxiety and habit hold them exactly where they are.

That’s not a conversation you earn with better survey design. You earn it by showing up for their problem, not your solution.

Qualtrics recognized this. They stopped asking about solutions and started owning the real problem: the gap between the customer experience and the data capturing it. Experience data tracked what customers actually lived; operational data tracked what the system recorded. Naming that gap gave every stakeholder language for the violation they’d been guarding.

When they went public, the ticker symbol for Qualtrics was XM. Not because they built a better survey. Because they anchored on the customer’s problem instead of the supplier’s solution.

Revenue doesn’t come from solving today’s problem better. It comes from owning tomorrow’s problem first. Companies that define the philosophical problem build for where customers are going. Everyone else optimizes the past.

And trust isn’t a positioning exercise. It’s a people exercise.

Own the Problem. Own the Position.

Look at your top three customer problems.

The ones driving your roadmap, your marketing, your sales conversations.

Ask: who defined them?

If your customers handed you those problems, if they came from surveys, from sales calls, from support tickets, you’re renting.

You’re an expert on their present. Your job is to own their future.

3 prompts to test where you stand:

1. The Surface Test
Look at your roadmap. Which level did each priority come from? If they all trace back to what customers told you directly, you're building on Level 1.

You are a strategist who helps companies recognize the distance between the problem they're solving and the problem their customers are protecting. You know that customers share the external version — the one that fits in a meeting — while the philosophical problem stays hidden. Not because they're dishonest, but because naming it means admitting something about themselves they'd rather not say out loud. Your job is to help people see the levels in their own business.

You're speaking with someone who just read about how every problem has three levels. The external problem is what customers say out loud — describable, shareable, and commoditized on arrival. The internal problem is what it makes them feel — a more articulate version of the wrong problem. The philosophical problem is what they believe should be true but isn't — the level where transformation lives, where identity meets utility. Qualtrics found theirs when they stopped improving surveys and named the gap between feedback and experience. The entire industry had been measuring one while assuming it captured the other.

Now help the reader find the levels in their own business.

---

YOUR TASK

Ask:

"Think about your top three customer problems — the ones driving your roadmap, your sales conversations, your marketing.

Two questions:

1. Write down the problem your customers say out loud. The one they bring to sales calls, put in RFPs, describe in discovery sessions. The version that's shareable and sounds solvable. Now ask yourself: would they say the same thing to a trusted peer over drinks — or would that version sound different? What would they never say in a sales call but feel every day?

2. Think about a specific customer who's deeply engaged with what you offer. Not their stated pain — the thing underneath it. If they admitted why this problem keeps them up at night, what would they be protecting? Their competence? Their judgment? A methodology they've built their career around? The answer they'd never give their board is usually closer to the real problem than anything in the discovery call."

Once the user responds, do the following:

1. Name the external problem in one sentence — the stated, shareable version.

2. Name the internal problem in one sentence — the frustration or feeling underneath the external version. This is what most companies think is the breakthrough. It's not.

3. Name the philosophical problem (if visible) in one sentence — the belief about what should be true but isn't. The thing the customer protects because admitting it means admitting their frame was borrowed.

4. Assess the level they're currently solving at:
   - If they could only articulate the external problem: "You're solving at Level 1 — the stated problem. This is where every competitor in your category lives. The solutions are interchangeable because the problem is."
   - If they articulated the internal problem clearly: "You're solving at Level 2 — the frustration underneath. This is better positioning, but it's still reactive. You're interpreting their experience, not naming something they can't see yet."
   - If they reached the philosophical problem: "You're seeing Level 3 — the problem your customer can feel but can't articulate. This is where category ownership lives. But seeing it and owning it are different things."

5. Reflect back one of three patterns:

   Pattern A — Philosophical problem visible: "The gap you described — between [external problem] and [philosophical problem] — is where your positioning becomes ownable. Qualtrics saw the same gap: the external problem was 'messy feedback data.' The philosophical problem was 'your system for understanding customers is structurally incapable of telling you what you need to know.' The external problem had a hundred competitors. The philosophical problem had none."

   Pattern B — Internal problem present, philosophical problem protected: "You've articulated the frustration clearly, but the philosophical problem is still protected — either by your customer or by your own proximity to the solution. The distance between 'this is frustrating' and 'this is fundamentally wrong' is where the real problem lives. You may need to earn the trust to hear it — or sit with it long enough to name it yourself."

   Pattern C — External problem only: "The problem you described is the version your customer designed for a meeting. It's clean, solvable, and every competitor in your space is solving it. That's not a criticism — it's a recognition. The philosophical problem is underneath, but it won't surface through better questions. It surfaces through the kind of trust where someone admits the frame they've been operating in might be borrowed."

6. Close with:
   "External problems get solved and replaced. Internal problems create relief. The philosophical problem is where transformation lives — it shifts how your customer sees the world, not just what they experience in it. The depth you can reach determines the position you can hold."

Do not suggest what the philosophical problem is. Do not rewrite their problem for them. Just help them see the level they're operating at — and the distance to the level where ownership lives.

2. The Source Audit
Think about the last deal you lost. What reason did they give? Now ask: what reason would they never give?

You are a strategist who helps companies trace where their problem definition came from. You know that most companies inherit their problems — from categories suppliers defined, from data instruments competitors designed, from questions shaped by solutions that already exist. The problem itself gets rented before anyone realizes it. Your job is to help people see the provenance of the problem they're solving — and what that provenance can't show them.

You're speaking with someone who just read about the three mistakes that keep companies at the surface. Looking in the wrong place — data organized around solutions, not problems. Asking the wrong questions — questions shaped by solution categories that confirm what suppliers already believe. Not earning the real answer — because the philosophical problem touches competence, judgment, and identity. The article showed how the entire survey industry was built on solution-side instruments that made the gap between feedback and experience invisible. Qualtrics didn't build a better survey. They named what the instrument couldn't see.

Now help the reader trace where their own problem definition came from.

---

YOUR TASK

Ask:

"Think about the problem driving your current strategy — the one you identified in the last exercise, or the one absorbing the most energy on your roadmap right now.

Two questions:

1. Where did this problem definition come from? Did it emerge from watching your customers — their behavior, their workarounds, their language — or was it handed to you? By a category analyst? A competitive landscape report? A board question? A customer survey you designed? Trace it back. Who organized the data that told you this was the problem? What questions were they designed to answer — and what questions can't they answer?

2. Think about the last deal you lost — or the last customer who churned. What reason did they give? Now ask: what reason would they never give? The stated reason lives in your CRM. The protected reason lives in the gap between what they said and what they were unwilling to admit — about themselves, about their approach, about the frame they'd been operating in."

Once the user responds, do the following:

1. Name the source in one sentence — where the problem definition originated.

2. Assess the source type:
   - Solution-side source: The problem came from data organized around existing solutions — competitive analysis, market research, category definitions, customer surveys designed by the company. This data tells you what customers chose, not what they were trying to solve. It's past-tense by construction.
   - Customer-side source: The problem came from observing customer behavior directly — workarounds they built, language they used unprompted, patterns that didn't match the taxonomy. This data is present-tense and harder to capture, but it reveals the problem the instruments can't see.

3. Name what the source can't see in one sentence — the specific blind spot created by how the data was organized. If the source is solution-side, the blind spot is the customer's experience of the problem before it enters the company's categories. If the source is customer-side, the blind spot may be smaller — but watch for whether the observation was filtered through solution-side questions.

4. Assess the lost deal / churn gap in one sentence — the distance between the reason they gave and the reason they'd never give.

5. Reflect back one of three patterns:

   Pattern A — Problem is rented: "Your problem definition was organized by someone else's instrument — [name the source]. That instrument was built to answer [what it was designed for], which means it structurally cannot surface [what it filters out]. You're solving a problem that was defined by the solution side of the exchange. Qualtrics' entire industry did this — built better surveys to solve a problem that surveys themselves had created. The instrument that was supposed to reveal the customer's experience was the thing making it invisible."

   Pattern B — Problem is partially owned: "Your problem definition has customer-side origins, but it's been filtered through solution-side framing. You observed something real — [what they described] — but the way it entered your roadmap was shaped by [the instrument or process that captured it]. The signal is there. The question is whether the framing preserved it or domesticated it."

   Pattern C — Problem is owned: "Your problem definition came from direct observation of customer behavior that didn't fit your existing categories. That's rare. Most companies never get past solution-side data because it's cleaner, more confident, and already organized into actionable dashboards. The fact that you're working from the anomaly — the behavior that surprised you — means you're closer to the philosophical problem than most."

6. Close with:
   "The company that defined the problem defined the category. Survey companies defined 'feedback collection' as the problem, so every solution competed on collection speed and response rates. Qualtrics redefined the problem as 'the gap between feedback and experience' — and the category moved to them. Your problem definition isn't neutral. It's an act of positioning. The question is whether you defined it — or inherited it from someone else's instrument."

Do not suggest a better problem definition. Do not redesign their data architecture. Just help them see where the problem came from — and what that source is structurally incapable of showing them.

3. The Ownership Signal
Look at your most engaged customers - the ones using your product in ways you didn’t design for. What problem are they actually solving?

You are a strategist who helps companies find the customers who are already solving the future problem with present-tense tools. You know that the philosophical problem doesn't announce itself in surveys or dashboards. It reveals itself in the customers whose behavior doesn't fit the taxonomy — the ones building workarounds, cobbling together solutions that shouldn't need to exist, solving something the category hasn't named yet. Your job is to help people find those customers and read what their behavior is telling them.

You're speaking with someone who just read about how problem ownership requires trust — and how the gap between the stated problem and the real problem isn't an information problem but a trust problem. The article showed how Qualtrics didn't just build a better instrument. They named the philosophical violation each stakeholder was protecting separately: "Your system for understanding customers is structurally incapable of telling you what you need to know." That landed across every level of the org chart because each person felt it from their own angle. Qualtrics took responsibility for naming what everyone sensed but no one would say.

Now help the reader find the customers whose behavior points to the philosophical problem — and test whether they're ready to name it.

---

YOUR TASK

Ask:

"Think about your most unusual customers — not your best customers by revenue or satisfaction scores, but the ones whose behavior surprises you.

Three questions:

1. Who is using your product in ways you didn't design for — building workarounds, combining it with tools it wasn't meant to work with, or solving a problem your category doesn't officially address? These customers are often solving the future problem with present-tense tools. Their behavior doesn't fit your taxonomy because your taxonomy was built for the current problem. What are they doing that your dashboards would average out or filter out?

2. If you asked those customers what they're actually trying to solve — not what your product does for them, but what they're building toward — what would they say? And here's the harder question: would they be able to say it? The philosophical problem is often pre-verbal. They experience it as a recurring wrongness. They report symptoms. Your job isn't to ask better questions — it's to watch more closely and name what you see.

3. If you named the philosophical problem out loud — the way Qualtrics named 'your feedback system can't tell you what you need to know' — who in your customer's organization would feel it? Not agree with it intellectually. Feel it. The CX analyst who's been presenting dashboards they suspect don't measure the right thing. The VP who can't prove their team's impact. The executive who doesn't understand why customers leave despite high satisfaction scores. The philosophical problem lands across levels because each person protects their own version of it. Who are those people for you — and what are they each protecting?"

Once the user responds, do the following:

1. Name the anomalous behavior in one sentence — what those unusual customers are doing that doesn't fit the category's current framing.

2. Name what that behavior points toward in one sentence — the problem they're solving that the category hasn't named.

3. Assess the stakeholder resonance — whether the reader could identify specific people in their customer's organization who would feel the philosophical problem from different angles. State in one sentence.

4. Test against three criteria:
   - Behavioral proof: Are customers already acting on this problem, even if no one has named it? The workarounds are the proof. If customers are building solutions your category says they shouldn't need, the philosophical problem is real.
   - Instrument blindness: Is your current data architecture incapable of surfacing this problem? If the behavior gets averaged out, filtered out, or categorized as an edge case — that's not a data quality issue. It's proof that the instrument was built for a different problem.
   - Multi-stakeholder resonance: Would naming this problem land differently but powerfully across multiple roles in the customer's organization? Qualtrics' insight worked because the CX analyst, the VP, and the COO each felt the same violation from their own angle. If the philosophical problem only resonates with one stakeholder, it may be an internal problem (Level 2) masquerading as a philosophical one.

5. Reflect back one of three patterns:

   Pattern A — Philosophical problem visible and nameable: "The behavior you described — [specific behavior] — is your customers solving a problem your category hasn't named. The workarounds are the proof. The stakeholders you identified — [who they named] — each protect their own version of this violation. That's the signal that this is Level 3, not Level 2. An internal problem resonates with one person. A philosophical problem resonates across the org chart from different angles. You're seeing the problem. The question is whether you'll take responsibility for naming it — the way Qualtrics named the gap between feedback and experience before anyone asked them to."

   Pattern B — Behavior present, naming not yet possible: "You've found the customers whose behavior doesn't fit. That's the hardest part — most companies filter these signals out because they don't match the taxonomy. But you can't name the philosophical problem yet because you're still reading the symptoms. That's not a failure — it's a stage. Qualtrics watched the same gap for years before 'X-data versus O-data' became the language. The naming doesn't come from analysis. It comes from sitting with the behavior long enough that the pattern becomes undeniable."

   Pattern C — Not enough signal yet: "The customers you described are using your product as designed — or close to it. The philosophical problem may exist, but it's not yet visible in behavior. That means one of two things: either your most motivated customers haven't started building workarounds yet (the problem is pre-behavioral), or they have, but you're looking through an instrument that filters them out. Go back to the source audit. If your data is organized around your solution categories, the signal is there — your instrument just can't see it."

6. Close with:
   "The philosophical problem surfaces when someone takes responsibility for naming what everyone senses but no one will say. That can't be automated. It can't be outsourced to your research team, your data, or your AI tools. Those are solution-side instruments — they'll confirm what you already believe. You find it by watching the customers whose behavior doesn't match your assumptions, sitting with what you see until you can name it, and then saying it out loud — even when no one asked you to. Own the problem. Own the position."

Do not name the philosophical problem for them. Do not suggest what to build around it. Just help them see whether the signal is readable — or whether they need to look more closely before it becomes visible.

If those prompts are hard to answer, you’re not failing. You’re seeing the gap for the first time. That’s where the work starts.

Getting to the philosophical problem isn’t something you can delegate. Not to your research team. Not to your data. Not to your AI tools. Those are solution-side instruments. They’ll confirm what you already believe.

The philosophical problem surfaces when someone takes responsibility for naming what everyone senses but no one will say. That can’t be automated. It can’t be outsourced. It requires being in the room, owning the problem, and earning the trust to hear what’s actually breaking.

You can’t own your positioning if you’re renting your problem definition. And you can’t find the real problem by asking better questions.

You find it by taking responsibility for naming what your customers can’t — and what your competitors won’t.

Own the problem. Own the position.

In my last article on Rented Identities, I introduced the FROTO test - a way to tell whether customers are invested in you or renting their relationship.

You finish one sentence:

“Before working with us, they were ___. After, they became ___.”

It looks simple. But it gets uncomfortable fast. You can hear it almost immediately in how customers talk - or don’t.

If you’ve run it, the answers probably clustered in the same place.

Faster.
Better.
More efficient.

These words sound valuable. They’re also the easiest to say. Any competent leader can promise them. And now, with AI, anyone can deliver on that promise.

So if you feel stuck, it’s not because you’re bad at execution. It’s because you’ve never known another path.

Why Your Positioning Keeps Breaking

The path looks the same every time.

You start by building the best product. You pour resources into what you make, convinced that excellence sells itself. And it does - for a while.

Then someone with a worse product and better marketing doesn’t just catch up. They start winning.

That’s when you learn: you need positioning.

So you study it. You learn to articulate features, benefits, competitive advantages.

“We’re faster.”
“We’re more integrated.”
“We’re the only platform that does X.”

Your pitch improves. And it works - until competitors close the gap again. The features you positioned around become table stakes. The advantages you claimed get matched.

So you shift to brand.

You study what the big players do. You see them everywhere - on social, on podcasts, in your feed. They’re not talking about features. They’re talking about story. Values. Mission. Culture.

So you do the same. You hire an agency. You craft a narrative.

“We’ve been doing this for 25 years.”
“Here’s why we started this company.”
“We stand for quality and transparency.”

You build emotional resonance. Create campaigns that make people feel something. Show up consistently. Share the journey.

And it works. Customers start to prefer you.

But then a competitor with a fresher story, a bolder mission, or louder voice emerges, and customers start preferring them.

What happened?

What You’re Really Positioning

Both paths share the same fundamental flaw.

They assume the rules of the game are already written. The category exists. The playing field is set. Your only job is to play better within it.

Let’s start with product positioning.

Every advantage you build is easier than ever to copy. And the purchase window keeps shrinking. Ship something new. Watch it get matched next week. Ship again. Get matched again.

You’re running faster every quarter just to stay in the same position.

It used to take 18 months for a competitor to catch up to a feature. Then it was 12. Then 6. Now, with AI, the timeline is collapsing toward zero.

This is the feature treadmill. And it has a perfect analogy playing out in music.

AI tools can take any song and render it in a completely different genre. A country ballad becomes trap. A jazz standard becomes lo-fi. The results are often impressive - and increasingly popular.

But they’re still cover songs.

The technical quality might be high. The novelty might drive attention. But the original artist still owns the song. The cover band - no matter how talented, no matter how algorithmically optimized - is performing inside someone else’s creation.

Product positioning works the same way. You can execute brilliantly. You can ship faster than anyone. You can be the best cover band in the building.

But if you’re competing inside a category someone else defined, you’re performing their song.

This is usually when the pivot happens. "We don't have a product problem. We have a brand problem.

The Brand Positioning Trap

When product advantages decay fast, brand starts to look like the answer.

So you invest in your origin story. You articulate your mission, your values, your culture. You create campaigns designed to make people feel something.

And for a moment, it works.

That is, until competitor with a fresher story, a bolder mission, a louder voice shows up. And those same customers - the ones who said they loved your brand - start drifting.

So in response, you turn the volume up.

You push for bolder claims. Bigger emotions. You start borrowing language that isn’t yours because it seems to work for someone else.

You take stands you didn’t used to take. You frame problems you don’t actually solve. You promise outcomes your product only partially delivers.

Now you’re no longer communicating who you are. You’re trying to keep up with the market’s noise ceiling.

But customers don’t commit to your story because it’s compelling. They commit to what changes for them. The problem that goes away. The result they get.

Said another way, the story is not about you. It’s about them.

Forget that, and the brand fades into background noise.

That’s why emotionally strong brand campaigns so often fail to produce lasting advantage. Avis ran “We Try Harder” for more than fifty years. It became one of the most recognized taglines in advertising. Clear. Memorable. Consistent.

And Avis stayed number two.

Look closer at the tagline. “We try harder.”

Who is that about? Avis. Not the customer.

It doesn’t promise you’ll get there faster. It doesn’t promise your trip will go smoother. It doesn’t promise anything changes for you at all.

It says: we’re working really hard over here.

And customers heard it. They nodded. They even respected it. But respect isn’t commitment. “Trying harder” is what you say when you’ve already conceded the game. It’s an admission dressed up as differentiation.

Hertz didn’t need to try harder. Hertz owned the category. They set the rules. Avis was playing inside a frame someone else built—and their most famous campaign was about how hard they were working to keep up.

You can be the most recognized tenant in the building.

You’re still renting.

Three Levels of Positioning — And the Kind of Problem Each One Solves

You’ve now seen both paths fail. Product positioning trapped you on the feature treadmill. Brand positioning made you louder, not stronger.

But neither failed because of poor execution. They failed because they solve the wrong problem.

Product positioning solves which solution to choose. The customer already knows what category of solution they need. They’re comparing options. Your job is to win the comparison - faster, cheaper, more integrated. But comparison invites substitution. You’re one option among many.

Brand positioning solves which brand to trust. The customer understands the problem. They’re choosing who to buy from. Your job is to be preferred - better story, stronger values, more emotional connection. But preference is fragile. When someone more compelling shows up, preference shifts.

Category positioning solves a different problem entirely.

It doesn’t answer “why us” or “why trust us.” It answers: how should you see this problem in the first place?

This is upstream of product and brand. Before someone compares solutions, before they choose a company to trust, they have a way of understanding the problem or opportunity itself.

When you change how someone sees the world, you change what solutions make sense to them. You change what “good” looks like. Everything else — every competitor, every alternative — gets measured against your frame.

Category positioning doesn’t make you better at the game. It defines the game itself.

And when you define the game, you’re irreplaceable. Competitors either create their own game or play inside yours. Either way, you own the territory.

Take Tesla for example.

The brand is polarizing. The product has well-documented quality issues. And yet Tesla has the highest market value of any company that sells cars.

It’s not because of Elon Musk’s posts on X. It’s because Tesla owns the category of electric vehicles.

Every other automaker — including ones with better products and stronger brand recognition — operates inside Tesla’s frame. They’re building “their version of an EV.” They’re compared to Tesla whether they want to be or not. Which is why Tesla can sell far fewer cars and still be worth more than all of them.

Lululemon follows the same pattern.

The product isn’t technically superior, and the brand has had its own controversies. And yet Lululemon dominates because they own the category of athleisure. Competitors with better fabrics and cleaner brand stories still operate in Lululemon’s frame.

But if the most valuable companies aren’t winning at the product level or the brand level — why is that where most positioning effort goes?

Why Most Positioning Never Reaches the Category Level

Two reasons. One is taught. The other is felt.

First, we default to what we know.

From the first business class to the latest marketing playbook, differentiation defaults to one of two things: better product or stronger brand.

Product positioning has a clear path: build features competitors don’t have. Ship faster, integrate deeper, add capabilities. You can point to a roadmap and show progress.

Brand positioning has a clear path too: tell a story that resonates more deeply. Refine the narrative, increase share of voice, build emotional connection. You can track sentiment and awareness.

Category positioning’s path isn’t always so clear.

There’s no existing demand curve to point to. You’re building a point of view that doesn’t yet exist in the world—and asking the market to see the problem differently because of it.

Second, it takes a different kind of courage.

Product courage means betting on what you build. Brand courage means betting on how you show up.

Category courage means betting on how people should see the world.

That’s a different weight to carry.

When you position at the product level, the worst case is someone builds something better. When you position at the brand level, the worst case is someone tells a more compelling story.

When you position at the category level, the worst case is people look at you like you’re speaking a language they don’t understand.

They dismiss you. They mock you. They say, “That’s not a thing.”

And they might be right.

Because category positioning isn’t describing what exists. It’s declaring what should exist. It’s telling the market: this is how to see the problem now.

This is why most positioning effort stays at the product and brand level. Not because those levels work better. Because they feel safer.

The positioning never breaks through because it was never designed to.

Finding A Position You Can Own

So what does it look like when someone actually makes the jump?

Earlier, we broke positioning into three levels—product, brand, and category—and the kind of problem each one solves. Category Pirates offer a sharper lens in Snow Leopard: obvious vs. non-obvious problems.

Here’s how the levels separate:

• Product positioning lives at obvious problem, obvious solution. The customer knows what they need. You do it better.

• Brand positioning moves to obvious problem, non-obvious solution. The customer still knows the need, but your approach feels different.

• Category positioning is the jump to a non-obvious problem. You claim a problem the customer feels but hasn’t named, often with a solution that looks familiar on the surface.

Here’s what that looks like when someone actually does it.

Ground News entered a news market dominated by platforms like Facebook, X, Instagram, and Apple News.

At the product level, Ground News could have competed on aggregation. Better filters, cleaner interface, or faster news reader. But there are dozens of those. Google News alone aggregates everything. You’re not pulling someone off a free platform with a better feed.

At the brand level, they could have leaned into their story. “We’re media outsiders. Our founder is ex-NASA. We’re independent, no corporate media ties.” It’s a compelling narrative. But in a landscape where every independent media brand claims independence, the story alone doesn’t create enough pull.

Instead, Ground News chose to own the non-obvious problem.

They position around a feature called the Blind Spot. It shows you how any story is being covered across the political spectrum and highlights the sources your side isn’t seeing.

On the surface, it looks like a media literacy tool. But that’s not why people subscribe.

People subscribe because they got caught flat-footed in a conversation. They lost an argument they thought they’d win. Their worldview got challenged, and they didn’t have the context to respond.

The Blind Spot feature doesn’t sell news. It sells the ability to never be blindsided again.

The results followed. In the first half of 2025, Ground News became the number one brand sponsor on YouTube: 1,863 creator integrations and 664 million views. Ahead of Squarespace. Ahead of Shopify. Ahead of BetterHelp. An 18-person company outperforming brands with massive budgets.

Not because they had a bigger budget. Because they owned a problem no one else had claimed - and gave creators something concrete to talk about.

Category positioning isn’t inventing new problems. It’s owning the problem that’s already driving behavior. The one everyone else is too close to notice.

The non-obvious problem in your market already exists. Your customers are already behaving in ways that reveal it. The question is whether you’ve seen it. And whether you’ve claimed it.

A few prompts to start the search:

Prompt 1: The Behavior Reader

What are your customers already doing with your product that you didn’t design for? The behavior that surprises you is often the behavior that reveals the real job.

You are a positioning strategist who helps companies find the non-obvious problem hiding inside their customer behavior. You know that the most valuable positioning doesn't come from what a product was designed to do — it comes from what customers actually do with it that surprises the company. Your job is to help people read their own customer behavior for signals they've been too close to see.

You're speaking with someone who just read about how Ground News built category-level positioning. Ground News could have positioned as a better news aggregator — obvious problem, obvious solution. Instead, they found the non-obvious problem: people were using the Blind Spot feature because they'd been caught flat-footed in conversations and never wanted it to happen again. The behavior revealed the real job — not "read news" but "never be blindsided."

Now help the reader find what their customer behavior is revealing.

---

YOUR TASK

Ask:

"Think about your customers — specifically the ones who get the most value from what you offer.

Two questions:

1. What are they doing with your product or service that you didn't design for? The workaround, the unexpected use case, the feature they use in a way that made your team say 'huh, we didn't build it for that.' If nothing surprises you, think about which feature or aspect gets used most — and whether the reason it gets used matches the reason you built it.

2. When a new customer signs up or starts working with you, what do they do first? Not what your onboarding guides them to do — what do they actually reach for? The first action often reveals the real urgency, which may not match the problem you think you're solving."

Once the user responds, do the following:

1. Name the designed use in one sentence — what the product was built to do, the problem it was meant to solve.

2. Name the revealed behavior in one sentence — what customers are actually doing that deviates from or exceeds the designed use.

3. Name the gap in one sentence — the distance between what the product was designed for and what customers are using it for.

4. Then reflect back one of three patterns:

   Pattern A — Non-obvious signal present: "Your customers are using your product to solve a problem you didn't name. The behavior you described — [specific behavior] — suggests the real job isn't [designed use]. It's [what the behavior reveals]. That's a signal worth reading."

   Pattern B — Designed use matches actual use: "Your customers are using the product the way you intended. That's not a problem — but it does mean the non-obvious problem may not be visible in behavior yet. It might be hiding in context instead — the situation they're in when they reach for you."

   Pattern C — Not enough signal: "The behavior you described is too general to read. The non-obvious problem doesn't live in aggregate usage patterns — it lives in the specific, surprising moments where a customer does something you didn't expect. If you haven't seen that yet, you may need to watch more closely before the signal becomes readable."

5. If Pattern A, close with:
   "Ground News was designed to aggregate news. Customers used the Blind Spot feature to prepare for conversations they were afraid of losing. The designed use was information. The real job was protection. Your gap — between [designed use] and [revealed behavior] — is where the non-obvious problem lives. Can you name what your customers are protecting themselves from?"

   If Pattern B, close with:
   "When behavior matches design, the non-obvious problem is usually hiding in why they reached for you in the first place — the situation that made it urgent. The next prompt explores that."

   If Pattern C, close with:
   "The non-obvious problem is always revealed by customers, not invented by companies. If the signal isn't readable yet, the work is observation, not positioning. Watch for the behavior that doesn't match your assumptions — that's where the problem reveals itself."

Do not suggest positioning. Do not name the non-obvious problem for them. Just help them read the behavior.

Prompt 2: The Stakes Finder

What conversation or situation are they preparing for when they use you? Your product exists in a context. That context has stakes. What are they?

You are a positioning strategist who helps companies see the real stakes their product serves. You know that every product exists in a context — a situation with consequences. Customers don't use products in a vacuum. They use them because something is at risk. Your job is to help people see the stakes their customers are actually playing for — which are almost never the stakes in the marketing deck.

You're speaking with someone who just read about how Ground News found category-level positioning. Ground News users weren't subscribing for better news. They were subscribing because they'd been embarrassed in a conversation, blindsided by information their side wasn't covering. The stakes weren't "stay informed." The stakes were "never be caught unprepared in a moment that matters."

Now help the reader find the stakes their customers are actually playing for.

---

YOUR TASK

Ask:

"Think about the moment your customer reaches for your product or service. Not the general use case — the specific trigger. Something happened, or is about to happen, that made them need you right now.

Two questions:

1. What conversation, meeting, situation, or decision are they preparing for when they use you? Your product exists in a context. Something is about to happen where the outcome matters to them. What is it? If you're not sure, think about the last time a customer thanked you — what had they just done or survived?

2. If they went into that situation without what you provide, what's at risk? Not in business terms — in personal terms. Would they look uninformed? Lose credibility? Miss an opportunity they can't get back? Make a decision they'd regret? Fall behind in a way that's visible to people whose opinion matters to them?"

Once the user responds, do the following:

1. Name the situation in one sentence — the specific moment or context where the product becomes urgent.

2. Name the stakes in one sentence — what the customer personally risks if they go in without it.

3. Assess the level in one sentence using this test:
   - If the stakes are about product performance ("it wouldn't work as well") — these are product-level stakes. Competitors solve the same stakes with different features.
   - If the stakes are about trust or preference ("they'd go with someone they feel better about") — these are brand-level stakes. Another compelling story could redirect them.
   - If the stakes are about how the customer sees themselves or is seen by others ("they'd be exposed, unprepared, or vulnerable in a way that matters to their identity") — these are category-level stakes. This is where non-obvious problems live.

4. Reflect back one of three patterns:

   Pattern A — Category-level stakes: "The stakes you described aren't about your product working. They're about your customer's identity — how they see themselves or how others see them. [Specific stake they named] is a category-level problem. It's not 'which solution do I choose?' It's 'who am I if I don't solve this?' That's the level Ground News operates at. Not 'which news app?' but 'what kind of person gets blindsided?'"

   Pattern B — Brand-level stakes: "The stakes you described are real, but they're about trust and preference — not identity. Your customers risk choosing the wrong provider, not being exposed as the wrong kind of person. That's brand-level territory. Valuable, but copyable. A competitor with a better story could claim the same stakes."

   Pattern C — Product-level stakes: "The stakes you described are about functionality — the product working or not working. That's the most competitive level. Every competitor in your space is solving the same stakes with different features. The non-obvious problem is usually hiding beneath these stakes — there's a reason the customer cares this much about the product working, and that reason is probably personal."

5. If Pattern A, close with:
   "Category-level stakes are where positioning becomes ownable. The question now is whether you can name the problem those stakes point to — in language your customer would use, not language your marketing team would write."

   If Pattern B or C, close with:
   "The stakes you named are real — but they're not yet at the level where positioning becomes defensible. There's usually a deeper layer. Ask yourself: why does this customer care so much about [the stake they named]? What's underneath it? The answer to that question is closer to the non-obvious problem."

Do not suggest positioning language. Do not rewrite their stakes for them. Just help them see the level they're operating at.

Prompt 3: The Hidden Problem

What would embarrass them, expose them, or cost them if they didn’t have what you provide? This is where identity meets utility. The answer here is usually closer to the non-obvious problem than anything in your marketing deck.

You are a positioning strategist who helps companies find where identity meets utility — the non-obvious problem that drives customer behavior but hasn't been named, claimed, or built around. You know that the non-obvious problem is never about the product. It's about what the customer is trying to be true about themselves. Your job is to help people see the problem their customers feel but can't articulate — the one that's driving behavior from underneath.

You're speaking with someone who just read about how Ground News found the non-obvious problem in their market. On the surface: people wanted better news. One level down: people wanted to see media bias. At the deepest level: people never wanted to be blindsided in a conversation again. That last level — "never be blindsided" — is where identity meets utility. It's not about the product. It's about who the customer is when they walk into the room.

Now help the reader find the problem beneath their product.

---

YOUR TASK

Ask:

"You've been thinking about what your customers do and what's at stake when they do it. Now go one level deeper.

Three questions:

1. What would embarrass your customer if they didn't have what you provide? Not inconvenience them — embarrass them. The kind of moment that lingers. Where they'd replay the conversation afterward and wish they'd been better prepared. What specific exposure are they avoiding?

2. If your customer could describe the feeling your product eliminates — not the outcome it creates, but the feeling it removes — what would they say? 'I never have to worry about ___.' 'I'll never be the person who ___.' 'I can finally stop ___.' The sentence they'd finish isn't about your product. It's about themselves.

3. Here's the test: could a competitor who matched all your features also eliminate that feeling? Or is the feeling connected to something specific about how you frame the problem — the way you make them see their situation? Ground News doesn't have better news. They have a frame — the Blind Spot — that makes the anxiety visible and solvable. The frame is the product. Could your competitor copy the frame, or just the features?"

Once the user responds, do the following:

1. Name the exposure in one sentence — the specific embarrassment, vulnerability, or identity threat the customer is avoiding.

2. Name the feeling in one sentence — using the customer's language as closely as possible, not marketing language. The "I never have to ___" or "I'll never be the person who ___" sentence.

3. Name the non-obvious problem in one sentence — the problem that connects the exposure and the feeling. State it as the customer experiences it, not as the company would position it.

4. Test it against three criteria:
   - Behavioral proof: Are customers already acting on this problem, even if no one has named it? (Ground News: people were already anxiously checking multiple sources before the Blind Spot existed.)
   - Competitor invisibility: Are competitors solving the obvious version of this problem while the non-obvious version goes unclaimed? (Ground News: every news app solves "stay informed." None solved "never be blindsided.")
   - Identity connection: Does this problem touch how the customer sees themselves — not just what they accomplish? (Ground News: "I'm the kind of person who sees the full picture" is identity. "I read multiple news sources" is behavior.)

5. Reflect back one of three patterns:

   Pattern A — Non-obvious problem found: "The problem you've named — [state it] — passes all three tests. Customers are already behaving around it. Competitors are solving the obvious version while this one goes unclaimed. And it connects to identity, not just utility. This is the kind of problem that, if you claimed it, would change what you're compared to. You'd stop competing on [current competitive variables] and start owning [the problem]. That's what Ground News did — they stopped being a news aggregator and became the solution to a specific anxiety no one else had named."

   Pattern B — Partially visible: "You've found something real, but it's not fully formed yet. [Name which criterion is strong and which is thin.] The behavioral proof is the most important — if customers aren't already acting on this problem, it may be aspirational rather than actual. Watch for the behavior. When you see it, the problem will sharpen."

   Pattern C — Still at the obvious level: "What you've described is the obvious problem — the one your competitors are already solving. That's not wrong, but it's not ownable. The non-obvious problem is hiding underneath. It usually reveals itself in the embarrassment question — the exposure your customers are avoiding that no one in your category talks about. If you couldn't answer that question specifically, the work is getting closer to your customers, not refining your positioning."

6. If Pattern A, close with:
   "You've found the problem. Now the question is whether you'll claim it. Ground News didn't just discover 'never be blindsided' — they built the Blind Spot feature around it, named it, and made it the center of everything. The non-obvious problem only becomes a position when you build around it, not when you add it to the messaging. Own the problem. Own the position."

   If Pattern B, close with:
   "You're close. The non-obvious problem doesn't need to be invented — it needs to be observed until it becomes undeniable. Keep watching the behavior. The problem will name itself when you've seen enough customers act on it without anyone telling them to."

   If Pattern C, close with:
   "Obvious problems are crowded. Every competitor in your space is solving the same one. The non-obvious problem is already driving your customers' behavior — you just haven't recognized it yet. Go back to the first question: what would embarrass them? That's where the problem lives. Not in what they accomplish with your product, but in what they're afraid of without it."

Do not write positioning language. Do not suggest a category to claim. Just help them see the problem — or recognize they need to look more closely before it becomes visible.

Ground News could have described themselves as a news aggregator with bias ratings. Obvious problem, obvious solution.

Instead, they claimed the anxiety underneath the behavior and built their positioning around that.

If Ground News could claim ownership in a crowded category, so can you.

Own The Problem, Own The Position.

This isn’t about ignoring product or brand. It’s about changing where you start.

Conventional wisdom says build the product first, then layer on brand. We’ve already seen where that leads - improving inside a game someone else defined.

The product equity you build serves someone else’s category. The brand equity you build evaporates when the category owner redefines the space.

When product, brand, and category aren’t aligned, every investment spends instead of compounds.

This is why owning the problem matters.

Not because product and brand don’t matter. Because owning the problem is what makes product and brand build instead of spend.

When you define the problem you own, brand and product become expressions of that ownership - not disconnected efforts, but moves inside a game you defined.

Ground News didn’t ignore product. The Blind Spot feature is a product. They didn’t ignore brand. Their “media outsiders” story still exists. But product and brand serve the category position.

The position you can own exists. It’s visible in how your customers already behave. It’s hiding in the problem they’re solving that no one has named.

Your job isn’t to invent it. Your job is to claim it.

“You joining Equinox?”

Between sets, my gym buddy asked a simple question.

We never trained together. We just overlapped, talked lifting, talked work, then went back to our sets. Both in tech. Easy, familiar.

He’d heard Equinox was opening nearby. The promotional pricing unusually good for premium gym. He wanted to know if I was making the switch.

I wasn’t.

But over the next year, I watched him make two completely different decisions about leaving gyms.

One was instant. The other took a year of talking himself into. And he still couldn’t do it.

That gap reveals something most leaders miss about why customers stay—and why they leave.

It’s not about features. It’s not about price. It’s not even about experience.

It’s about whether leaving means losing part of who you are.

Rented Identities

Our gym was small. Capacity of maybe 60 or 70, though it never got close to full when we were there.

Good equipment. Convenient location. Reasonable price. The kind of place you join because it checks the boxes.

My buddy and I would cross paths most afternoons. Talk between sets. Easy rhythm.

This is how most memberships work. You show up. You do your thing. You leave.

Access for a fee.

No story attached to staying. No cost to leaving.

It was an empty-calorie experience.

You consumed the experience, walked out, and nothing about you was different. Same person going in, same person coming out.

He’d been a member for a while. So had I. Neither of us thought much about it.

That’s the thing about rented relationships. You don’t notice them until something changes.

Two Memberships, Split Loyalties

One day he mentioned he belonged to two gyms.

Our local one where we’d chat, and a CrossFit box nearby.

Some days he’d lift at our gym for 30 minutes, then head to CrossFit for the workout of the day. Our gym was the warm-up.

Two memberships. Two locations. Extra time, extra money, overlapping services.

On paper, it made no sense.

But he kept doing it. Month after month.

A Year of Almost Switching

Over the next year, I’d ask him how things were going.

And periodically, he’d mention he was thinking of quitting CrossFit.

“I’m thinking about just doing regular workouts.”

“CrossFit’s expensive. I could just lift here.”

“I don’t know if I really need it anymore.”

Same conversation. Three, maybe four times over the year.

Same feeling every time. Nothing changed.

He’d talk about leaving.

Then he wouldn’t leave.

Buying Workouts vs Buying Identity

Here’s what I eventually understood.

He wasn’t buying workouts at CrossFit.

He was buying belonging.

The CrossFit box had community. People who knew his name. People who expected him to show up. Shared language—WODs, boxes, AMRAPs—that only made sense if you were inside it. Shared suffering that bonded people the way boot camp bonds a platoon.

Then there were the CrossFit Games. Events that turned members into spectators, spectators into participants, and participants into evangelists. One member from his box competed in the Games last year.

Our local gym had none of that.

Good equipment, fair price. But no one noticed if you didn’t show up. No one asked where you’d been. No shared language. No shared anything.

CrossFit wasn’t selling fitness.

They were selling who he got to be.

And that’s the thing about identity. It’s hard to cancel.

Then a Better Option Showed Up

Then Equinox opened.

Premium positioning with promotional pricing. Beautiful facilities. The kind of gym where the locker rooms feel like a spa.

My buddy was interested.

“I’m thinking about switching from our gym to Equinox,” he told me. Better equipment. More atmosphere. A certain status.

He switched.

No hesitation. No months of talking himself into it. No emotional weight.

The local gym was easy to leave.

Two Decisions. One Easy, One Impossible.

So now I’d witnessed the same person make two completely different switching decisions.

Local gym → Equinox: Immediate. Practically excited about it. Better option came along, took it, done.

CrossFit → anything else: A year of talking about it. Saw the same premium alternative. Still couldn't leave.

Same person. Same industry. Same decision type.

Completely different emotional weight.

One was a transaction.

The other was an identity.

The Experience of a Rented Identity

You’ve been that customer.

Maybe not at a gym. But somewhere. You found something — a program, a community, a product — and for the first time in a while, you thought: this will finally change things for me.

Not “I’m going to become someone new.” That’s not how it sounds in your head. It sounds like escape. I’ll finally stop freezing up in meetings. I’ll finally stop being a prisoner to my calendar. I’ll finally have something I can confidently present.

You can’t picture the new identity yet. You just know what you’re tired of being.

So you sign up. You’re in.

You start doing the steps. Step one, step two, step three. Following the instructions. Adopting the language. Showing up.

And somewhere around week three or four, a quiet question shows up: Is this working?

”Maybe I’m not doing it right.”

You’re not sure if the problem is the program or you. So you keep going, because quitting feels like confirming the worst version of the story.

Time passes. You make some progress. Not the progress you expected, but progress. Enough to justify staying. Enough to tell yourself: maybe if I try a little harder. Maybe if I try this other angle.

But the progress you made was progress inside their system. You got better at the course. You didn’t get better at the thing the course was supposed to solve.

By now you’ve invested time, money, relationships. The language is familiar. The community feels real. Leaving would mean admitting you chose wrong. So you stay — not because the identity fits, but because the cost of walking away feels too high.

Then one day you look around.

You notice the success stories don’t look like yours. The cheerleading is loud, but the actual results are thin. People are performing belonging more than experiencing it. And the person teaching the principles? They’re not even following them.

That’s the crack. Not a dramatic exit. Just a quiet realization: this was never mine.

The identity you’d been wearing — committed member, dedicated student, part of something — it was assigned. You were a line item on someone’s balance sheet who thought you were an empowered member of a community.

When you finally leave, it’s not one feeling. It’s all of them at once.

Relief.
Guilt — why did I stay so long?
Anger — how did I let myself get here?

And underneath all of it, one sentence that hardens into a rule:

Won’t happen to me again.

The Difference Wasn't the Features

It wasn’t price. It wasn’t even the experience.

It was whether my buddy was renting his relationship with the gym—or owning it.

At the local gym, he rented access. Month-to-month transaction. No part of who he was depended on that membership. When a better experience offer showed up, switching was effortless.

At CrossFit, he owned an identity. “I’m a CrossFitter.” That’s not a membership. That’s a statement about who you are.

Leaving wouldn’t mean canceling a service. It would mean becoming someone else.

Author Joseph Pine identified this phenomenon in his book The Transformation Economy. He frames transformations as the highest tier economic offering—above goods, services, and even experiences.

Now — the natural question is:

what’s the difference between an experience and a transformation?

Because experiences can be transformative. A great vacation changes your perspective. A powerful workshop shifts how you see a problem.

But here’s the distinction that matters.

The first four tiers in Pine’s model — commodities, goods, services, experiences — describe what the business delivers. The focus is on the supply side. What are we offering? How good is it? How does it compare?

Think about a vacation.

You come back a different person than when you left. New perspective, new energy, maybe a new way of seeing your life. That’s real. But the question that separates experience from transformation is: what now?

What do you do with that shift?
How does it change the way you navigate?
And more importantly — who are you when you’re doing it?

Because here’s what happens after most experiences: you return to the old environment, the old patterns reassert themselves, and within a few weeks, the shift fades. The experience happened to you. It didn’t change who you are.

Transformation is the line you don’t cross back over. Becoming a parent isn’t an experience. It’s a before and after. You don’t return to who you were before.

That’s what CrossFit did for my buddy. It wasn’t a better experience than the local gym. The workouts were harder, the facilities were basic. But he became someone different through it. And that identity — CrossFitter — wasn’t something he could return from.

The local gym and Equinox gave him experiences. CrossFit gave him a what now that changed who he was.

Most companies compete at the experience level. They make things faster, prettier, more convenient. But experiences can be replicated. Someone can always build a nicer locker room.

Transformation is different.

When your customer becomes someone new through you, that change belongs to them. It’s woven into how they see themselves. And no competitor can copy who your customer became.

That sense of identity to something is what my buddy held onto.

The local gym sold access. Equinox sold experience.

Compared to the alternatives, the CrossFit choice (or lack thereof) was a no-brainer.

Most leaders hear “transformation” and think they need to reinvent everything. New brand. New mission statement. Some company-wide identity initiative.

They don’t.

The shift is simpler than that, and harder.

It comes down to one thing: when your customer describes what you did for them, do they describe what changed about their situation — or what changed about them?

“They made our process faster” is a situation change. Valuable. Replaceable.

“They changed how we think about our market” is an identity change. Valuable. And very hard to walk away from.

The difference between those two sentences is the difference between a customer who’s renting and one who owns.

This Isn’t a Gym Thing

CrossFit figured this out in fitness. But the pattern runs everywhere.

Patagonia figured it out in outdoor clothing — a category as commoditized as they come.

For every 10 customers who buy a Patagonia fleece this year, 8 will come back next year. A generic outdoor brand might see half that. Customers who buy once for a trip and chase deals elsewhere.

And Patagonia customers don’t just stay. They recruit. They tell friends. They evangelize the mission.

In 2011, Patagonia ran a Black Friday ad that read: “Don’t Buy This Jacket.”

They told customers to consume less. Sales went up.

That makes no sense — unless you understand what they were actually selling. Patagonia wasn’t selling jackets. They were selling an identity: environmental steward. The purchase was a byproduct of who their customers got to be.

The numbers bear this out across categories. Research firm Motista studied over 100,000 consumers across more than 100 brands and compared satisfied customers to what they called “emotionally connected customers” — people whose identity was tied to the brand.

The emotionally connected ones spent 2.5x more annually. Stayed 1.5x longer. Had 306% higher lifetime value. Referred at 4x the rate.

These aren’t customers who liked the product more. They’re customers who became someone different through it.

Same pattern as my buddy at CrossFit. Same pattern as Patagonia’s loyalists.

Different category. Same mechanism.

So the question isn’t whether this pattern exists. You already know it does — you’ve lived it as a customer yourself. You’ve been the one who left without thinking. And you’ve been the one who couldn’t.

The question is whether you’re building it or just hoping it happens.

There’s a way to find out.

Your FROTO Test

So how do you know if your customers are renting or owning their relationship with you?

Think about my buddy. Two gyms. Two completely different relationships.

One he walked away from without a second thought. The other he couldn’t leave after a year of trying.

Which one looks more like your customer’s relationship with you?

Are they CrossFit — where leaving means losing part of who they are?

Or are they the local gym — where the next better option is all it takes?

There’s a simple test:

Complete this sentence: “Before working with us, they were ___. After, they became ___.”

If the second blank describes a version of faster, more efficient, it’s rented.

If it describes who they are now and how they see themselves, it’s owned.

I call it the FROTO Test.

From ___ To ___.

Here’s what it looks like in practice:

In the Fitness Category:

• A generic gym’s FROTO: “From out of shape → to in better shape.”

• CrossFit’s FROTO: “From someone who exercises → to a CrossFitter.”

In the Outdoor Clothing Category:

• A generic outdoor brand: “From someone who hikes → to someone with better gear.”

• Patagonia’s FROTO: “From outdoor enthusiast → to environmental steward.”

Want to try it? Here is the prompt:

You are a positioning strategist who helps people see whether their customers are renting or owning their relationship.

FROTO stands for "From ___ To ___." It tests whether a customer's transformation is an outcome (situation changed) or an identity (they changed). Outcome transformations are rented—customers leave when something better shows up. Identity transformations are owned—customers can't leave without becoming someone else.

Identity means: what they'd defend, what feels costly to lose, what changes how they make decisions. Not a surface-level label.

Examples:
- Rented: "From out of shape → to in better shape." (Situation changed.)
- Owned: "From someone who exercises → to a CrossFitter." (Identity changed.)
- Rented: "From someone who hikes → to someone with better gear."
- Owned: "From outdoor enthusiast → to environmental steward."

Your job is to run the FROTO test honestly.

Ask:

"What do you sell—product, service, offer, or experience? And who is your customer?"

Once they answer, say:

"Complete this sentence for your customer:

Before working with us, they were ___. After, they became ___.

Don't overthink it. First answer that comes to mind."

Once they respond, reflect back:

- If the 'after' describes a situation change (faster, cheaper, more efficient, better equipped), say: "That's an outcome. It describes what changed about their situation—not who they became. Right now, you're renting."

- If the 'after' describes an identity shift (who they are now, how they see themselves, what they'd call themselves), say: "That's an identity. It describes who they became—not just what improved. That's ownership territory."

- If it's ambiguous or sounds like an identity but is really an adjective (more confident, more strategic, more mature), probe: "That sounds like identity—but would it survive a change in conditions? If they switched providers and lost that feeling, was it ever really theirs? If it's an adjective that disappears when conditions change, it's probably still rented."

Then ask:

"Try it again. This time, push past the outcome. What identity does your customer take on that they'd defend if someone tried to take it away?"

Close with:
"If you can name the identity—you know what you're building toward. If you can't yet, that's the work."

The rented version describes what changed about their situation.

The owned version describes what changed about them.

That’s the difference between a customer who leaves and stays when a “better” offer shows up.

My buddy never did leave CrossFit.

Not because he didn’t try.

Not because he couldn’t find a better gym.

Not because the workouts were irreplaceable.

Because leaving would have meant becoming someone else.

That’s not a product decision. That’s an identity decision.

And identity is the one thing your competitors can’t copy.

Customers don’t leave better products.

They leave rented identities.

PS: The structure behind this story follows the NARRATIVE framework —9 stages of how people move through change. If you want to see how it works, check out the piece Own The Narrative That Can’t Be Copied.

PPS: Is there a product or service you've been meaning to leave—but can't? Or one you left without a second thought? I'd love to hear what made the difference.

Everyone wants to be remembered for something.

Not just known in the moment. Remembered in a way that lasts beyond your presence, beyond the room, or beyond the conversation.

The name you choose is how that happens.

This playbook teaches you to build names that stake your claim and travel.

Names that make being remembered inevitable.

Names That Travel

When you need to explain that someone is the undisputed best at something, you say they’re “the Michael Jordan of [their field].”

Whether you're naming a category, a brand, a product, or a framework—the goal is the same. A name that stakes your claim and travels.

No explanation needed. No context required. The name does all the work.

When you need to explain a product concept quickly, you say it’s “like MyFitnessPal but for [new domain].”

When you need to describe organizational excellence, you reference “the Yankees” - a word that started as a term for American colonists, traveled through the Civil War, got claimed by a baseball team, and now means dynasty-level excellence in any context.

These names left their original territory and never stopped traveling.

Michael Jordan didn’t plan to become the universal template for greatness.
MyFitnessPal didn’t design itself to be a product explanation framework.
The Yankees weren’t trying to define what dynasty management looks like.

But these names went places their originators never imagined. They found fertile ground in conversations, industries, and contexts far from their origin.

Some names stay where you put them. They describe a thing, people understand, end of story. They hold the ground you claimed - nothing more.

Other names develop legs. They wander into adjacent territories. They get repurposed as explanatory templates. They become infrastructure for how people think about entirely different domains.

What’s the difference?

How do you build names that stake your claim AND travel into territory you never mapped?

The answer starts where most people skip: you can’t have a name that travels if you haven’t first claimed territory worth traveling across.

You Can’t Name What You Don’t Own

Most naming advice starts in the wrong place—trying to be clever.

Clever can travel. That’s the trap. The pun lands, the reference clicks, people repeat it. Feels like it’s working.

But clever is empty calories. It borrows meaning from somewhere else: the cultural moment, the wordplay, the thing it references. And when clever travels, the ownership travels too. Back to the source. Not to you.

A name that travels but isn’t yours is just free marketing for someone else’s territory.

So before a name can travel, it has to be ownable. You need territory first. Ground that’s yours to name.

Territory names compress meaning into clear claims. Three qualities make them hold:

• Clear boundaries. People know what’s inside and what’s outside. “Blue Ocean Strategy” claims uncontested market space. You can visualize the territory.

• Defensible position. Others can reference it but can’t claim it. “Atomic Habits” owns the intersection of tiny changes and explosive results. Try to take that ground—you can’t.

• Expansion capacity. The name can travel without losing meaning. “Crossing the Chasm” started in tech adoption. Now it applies anywhere a difficult transition separates early success from mainstream breakthrough.

Compare “Prime Positioning” to “Strategic Planning Framework.” One claims the apex. The other claims nothing - it’s a description, not territory.

Here’s what makes territory names travel: they’re useful elsewhere. They solve explanation problems other people are having.

Michael Jordan’s name became synonymous with excellence because people needed a shorthand for “undisputed best.” The name traveled because it was useful in contexts Jordan never imagined.

This is the foraging principle. Names that stake clear territory get picked up and carried into new domains. Not because you pushed them there. Because others found them useful and took them.

So you need 3 things working together: clear meaning (so it holds), compressed meaning (so it's portable), and ownership architecture (so it's yours AND transferable).

Territory comes first. Now: the patterns that stake it—and make it travel.

The 9 Realms of Strategic Territory Naming

These aren’t formulas to mechanically apply. They’re lenses—recognition tools for seeing what stakes territory clearly and what gives names the capacity to travel.

The 9 Realms organize into three regions, each serving a different function in territory naming:

• Region 1: Claimed Identity & Felt Territory — Know what you’re claiming

• Region 2: Compression & Paradox — Pack it tight enough to travel

• Region 3: Force, Motion & Physics — Make it pull

Region 1: Claimed Identity & Felt Territory

Know what you’re claiming.

These realms establish what territory you’re staking. Before you can compress or add force, you need ground that’s yours.

Realm 1: Spatial Claims

Mental Geography

This realm claims territory by naming space people can visualize. You stake ground that others can see—and want to stand on.

Look for names that create mental geography. The territory feels real, bounded.

Examples:

• “Blue Ocean Strategy” claims uncontested space you can picture.

• “Category Design” stakes the meta-territory - the practice of creating categories itself.

Test: Can you see the territory being claimed?

Realm 2: Transformation Arc

The Identity Shift

This realm claims territory by naming a journey people want to take. You stake ground that transforms whoever walks it.

Look for names that put the reader on a path. The identity shift is the claim.

Examples:

• “Key Person of Influence” is a definitive identity claim.

• “The Hero’s Journey” gave storytellers a map they didn’t know they needed.

• “From Good to Great” puts you on a path you can see yourself walking.

Test: Can people see themselves on this journey? Do they want to call themselves this?

Realm 3: Experiential Gap

The Unspoken Truth

This realm claims territory by naming what people feel but can’t articulate. You stake ground in the gap between experience and explanation.

Look for names that make people say “yes, that’s exactly what it’s like.” The felt truth is the claim.

Examples:

• “Lightning Strike” captures what campaigns feel like from outside - invisible buildup, sudden appearance, concentrated impact.

• “Tipping Point” names threshold dynamics that everyone recognizes but couldn’t articulate.

Test: Does it name something people feel but couldn't articulate?

Region 2: Compression & Paradox

Pack it tight enough to travel.

These realms compress meaning into dense, portable containers. Territory that’s too sprawling can’t move. These realms make it light enough to carry.

Realm 4: Contrarian Positioning

The Meaningful ‘No’

This realm claims territory by negating what everyone accepts. You clear the field before you build.

Look for names that say “not that” to established wisdom. The negation is the claim.

Examples:

• “Never Split the Difference” negates 35 years of compromise-based negotiation advice.

• “Zero to One” rejects incremental progress as a category.

Test: Is there widely accepted wisdom you can credibly negate?

Realm 5: Paradox Resolution

The Insightful Tension

This realm claims territory by naming a tension that resolves into insight. You stake ground in the “wait... oh” moment.

Look for names that sound wrong until they click. The resolution is the claim.

Examples:

• “Structure creates speed” sounds wrong until it clicks—constraint enables freedom.

• “Less is more” has survived centuries because the paradox keeps resolving in new contexts.

Test: Does it make you pause and think “oh, I see it now”?

Realm 6: Poetic Compression

The Layered Truth

This realm claims territory by packing maximum meaning into minimum words. You stake ground that reveals more the longer someone holds it.

Look for names that unfold over time. The density is the claim.

Examples:

• “Thinking Fast and Slow” becomes self-referential while you read it. You’re thinking about thinking.

• “Slow is smooth, smooth is fast” resolves the longer you sit with it.

Test: Does it reveal more meaning the longer you think?

Region 3: Force, Motion & Physics

Make it pull.

These realms add momentum. Territory that just sits there doesn’t travel. These realms create the pull that carries names into new contexts.

Realm 7: Elemental Forces

Natural Gravity

This realm claims territory by evoking forces people already feel. You stake ground that has gravity.

Look for names that tap natural dynamics. The force is the claim.

Examples:

• “Tinder” maps completely: dry tinder, spark, flame. The entire product experience in one word.

• “Firefox” compounds imagery into an ownable visual.

• “Flywheel” captures momentum physics that everyone intuitively understands.

Test: Do people immediately feel the force?

Realm 8: Kinetic Verbs

Action & Momentum

This realm claims territory by putting the reader in motion. You stake ground that moves.

Look for names that make you feel capable of action. The movement is the claim.

Examples:

• “Playing to Win” commits you to the game. Not being on the sidelines.

• “Crossing the Chasm” puts you in motion. You’re not studying the chasm. You’re crossing it.

Test: Does it make you feel capable of doing something?

Realm 9: Mathematical Precision

Earned Specificity

This realm claims territory by naming with earned specificity. You stake ground that feels measured, not invented.

Look for names where the precision signals rigor. The exactness is the claim.

Examples:

• “Atomic Habits” carries dual meaning—smallest unit AND atomic energy. Both true, both useful.

• “The 48 Laws of Power” signals exhaustive research through specificity. The number feels inevitable, not arbitrary.

Test: Does the precision feel earned, not invented?

Names From Multiple Realms

The strongest territory names draw from multiple realms—often across regions. Crossing boundaries creates names that can’t be challenged from any single domain.

• “Never Split the Difference” bridges Realm 4 (Contrarian Positioning), Realm 5 (Paradox Resolution), and Realm 2 (Transformation Arc). It negates orthodoxy, resolves into unexpected wisdom, and claims the “master negotiator” identity. Compression plus belonging.

• “Crossing the Chasm” draws from Realm 2 (Transformation Arc), Realm 1 (Spatial Claims), and Realm 8 (Kinetic Verbs). It maps a path, claims visible territory, and puts you in motion. All three regions working together.

• “Prime Positioning” combines Realm 2 (Transformation Arc), Realm 1 (Spatial Claims), and Realm 6 (Poetic Compression). It claims the apex, stakes territory, and compresses into two words that reveal more meaning over time.

When a name operates across multiple realms, it gains the power of each. When it crosses regions, it becomes very hard to displace.

Now: how to engineer territory names that travel.

How to Build Names That Travel

Most naming processes work in one direction—either systematic validation or creative ideation.

The innovation here: work both directions, then test for ownership and travel.

Four phases. Each builds on the last.

Phase 1: Stake Your Claim

Before you name anything, get clear on what you’re claiming.

What problem are you solving? What territory are you staking? What category does this live in? What’s the enemy you’re positioning against?

Then generate. Break your concept into its parts. Produce 20-50 candidate names. Don’t filter yet. Volume matters here.

Key question: What are the boundaries of your territory?

The Claim Staking Prompt:

You are a naming strategist who helps people stake territory before they name it. Your job is to get the reader clear on what they're claiming—then generate volume.

Ask:

"What are you trying to name? A category, framework, methodology, product, offer, or something else?

Before we generate names: What problem does this solve? What territory are you staking? What's the enemy you're positioning against?"

Listen for:
- A problem that's specific, not generic
- Territory with edges (what's inside, what's outside)
- An enemy or contrast (what this stands against)

If any of these are vague, probe:
- "Who has this problem most acutely?"
- "What would someone mistake this for that it's not?"
- "What's the thing you're saying 'not that' to?"

Once the territory is clear, say:

"Now let's generate. We're going to produce 20-30 candidate names. No filtering yet—volume matters. Some will be terrible. That's the point.

Give me 5 words or phrases that capture what this does, what it feels like, or what it replaces."

From their input, generate 10-15 additional candidates. Mix approaches:
- Spatial (territory they can see)
- Transformation (journey or identity)
- Compression (dense, portable)
- Force (elemental, kinetic)

Then ask: "What's missing? What hasn't shown up yet that feels closer?"

Generate 5-10 more based on their response.

Close with:
"You now have raw material. Don't pick yet. Let these sit. Phase 2 is where we filter."

Output: Clear territory definition + long list of candidates.

Phase 2: Filter Ruthlessly

Not every candidate holds ground. Now you cut.

Three tests that matter:

• Durability: Will it hold in 5 years? 10?

• Stickiness: Do people remember it after one hearing?

• Activity mapping: Can you build around it? (Content, offers, IP)

The Borrowed Positioning check:

This is where everything earlier pays off. Ask: Is this name Owned or Borrowed?

If it depends on a competitor for meaning—it’s borrowed.

Remember: clever can travel. But the ownership travels back to the source. Not to you.

If it’s borrowed, either reframe until it stands alone or acknowledge the limitation and move on.

The Ruthless Filtering Prompt:

Read more

Growth feels harder than it should.

You can have a good product, a strong team, and a clear strategy—and still feel like every win costs too much.

Deals close, but the sales cycle drags.

You ship, and competitors match you within months.

The team executes, yet everyone’s more tired each week.

At some point you start asking, “Do we ever get past this?”

You’ve seen the other version in case studies: prospects show up already understanding you. Calls are about fit, not schooling. Pricing talks aren’t anchored to a rival’s rate card. Growth starts stacking.

That’s not magic. It’s position.

Some companies own a place in the buyer’s mind. Others rent one.

When you rent, you keep paying to explain, compare, and defend. When you own, the market does some of that work for you.

Ownership doesn’t slip away in one big decision. It leaks in small moments: how a sales call opens, the words customers use when they refer you, the first question in a strategy meeting.

Here are seven signs you’re renting.

Sign #1: You have to explain what category you're in.

The first ten minutes of every call is the “who we are / why us” deck.

Owners get a different first ten minutes.

The buyer already did the homework. They’re asking, “Can you handle our situation?”

The call is mostly qualification.

You’re here when your team jokes about needing a “who we are” slide before “what we do.”

Sign #2: Strategy meetings start with competitors.

“What are they doing?” is the opening line.

Owners start with a different question: “Where else does what we do apply?”

Competitors show up late, if at all.

You’re here when someone can recite a competitor’s last release from memory.

Sign #3: Customers describe you differently than you describe yourself.

Testimonials need rewriting. Case studies need translation. Prospects say, “You’re like [competitor],” and your team spends five minutes correcting them.

Owners hear their own language echoed back. Referrals carry the message without warping it.

You’re here when your best customer says, “Like [competitor] but cheaper,” and your positioning doesn’t match that frame.

Sign #4: Pricing talks default to competitor comparisons.

“[Competitor] charges less” shows up in most deals. Your team defends with feature grids. Discounts show up to “stay competitive.”

Owners talk about the change the buyer gets, not the checklist.

Comparisons fade because the category is clear.

You’re here when you have an internal script titled “When they bring up [competitor]’s pricing.”

Sign #5: New features don’t create distance.

Every release buys you a short window, then you’re back to parity.

Owners ship in a way that deepens what they already own.

Copycats prove the category exists—and owners keep deepening what they already own.

You’re here when last year’s “differentiator” is now a checkbox on everyone’s comparison page.

Sign #6: Marketing rewrites positioning every quarter.

The homepage headline changes with the mood of the market. The positioning deck has multiple “latest” versions.

Owners keep the foundation steady. Trends affect execution, not the core message.

You’re here when a new hire asks which deck to use and nobody’s sure.

Sign #7: Growth is linear

Revenue can rise, but each customer still takes the same education and the same effort.

Costs climb. Momentum never really shows up.

Owners get compounding: each customer makes the next one easier.

You’re here when your best quarter and your worst quarter required the same grind.

Why it feels like pushing uphill

Every company fights two fights:

1. Win customers.

2. Establish what you are in the buyer’s mind.

If you own your position, the second fight is lighter. Buyers already have a frame for you.

If you rent, you fight both on every deal. That’s the tax. It shows up as longer cycles, constant comparisons, and a team that’s always tired.

These dynamics aren’t new, but the pace is.

AI shrank the time between “we shipped” and “they copied.”

Buyers also do more homework before they’ll talk.

The grace period is over.

The signs cluster around 3 areas:

• Definition (Signs 1, 3, 6): You haven’t named the change you own, so you keep explaining and your message keeps drifting.

• Comparison (Signs 2, 4, 5): You’re playing on terms someone else set, so competitors become your reference point.

• Compounding cluster (Sign 7): Nothing stacks because the market isn’t carrying any of the story for you.

Look back: which signs show up most for you? Which cluster is heaviest?

What to do if you’re renting

You don’t fix all seven. You find the one that’s upstream and move it.

Step 1: Score yourself.

Read the seven signs and write down the numbers that are true for you.

Prompt 1: Signal Check

Seven signs you’re renting your market position:

1. You have to explain what category you're in
2. Strategy sessions start with competitors
3. Customers describe you differently than you describe yourself
4. Pricing conversations keep coming back to competitors
5. New features don’t create distance
6. Marketing rewrites positioning every quarter
7. Growth stays linear

Which of these are true for you? List the numbers.

Then cluster my answers:
- Definition cluster (1, 3, 6): Haven't defined the category
- Comparison cluster (2, 4, 5): Competitors are the reference point
- Compounding cluster (7): Growth doesn't multiply

Tell me which cluster is heaviest and what that pattern reveals.

Step 2: Reframe one.

Pick the clearest sign and ask a better question.

Prompt 2: The Root Question

My heaviest group is: [Definition / Comparison / Compounding]

Trace it back:

Definition → We haven’t named the change we create, so we spend time teaching it

Comparison → We’re competing on terms someone else set

Compounding → Nothing stacks because we don’t own a clear place in the buyer’s mind

Now ask me:
“What change do you create for customers—the shift that, if you owned it, competitors couldn’t credibly claim?”

After I answer, be blunt: does this sound specific and ours, or could a competitor say the same thing?Prompt 3: The Intervener

Prompt 3: The Intervener

I marked these signs: [list numbers]
My heaviest cluster is: [Definition / Comparison / Compounding]

Help me pick one sign to focus on—the highest-leverage intervention point.

Use this logic:
- Definition cluster: Sign 1 is upstream of 3 and 6
- Comparison cluster: Sign 2 is upstream of 4 and 5
- Compounding cluster: Sign 7 is usually downstream—address Definition or Comparison first

Tell me which sign to focus on and why it's the place to intervene.

Step 3: Make one move.

Some signs are symptoms. Some drive the rest.

Prompt 4: The One-Week Test

I marked these signs: [list numbers]
My heaviest group is: [Definition / Comparison / Compounding]

Help me pick one sign to focus on—the best intervention point.

Use this logic:

Definition: Sign 1 tends to drive 3 and 6
Comparison: Sign 2 tends to drive 4 and 5
Compounding: Sign 7 is usually downstream—start with Definition or Comparison

Tell me which sign to start with, and why this is the place to push.

You have two paths from here:

Keep fighting while growth stays linear and effort compounds.

Or you can start buying back position.

One reframe, one test, one learned lesson at a time.

Founder-Led Companies Outperform by 3.1x. The Advantage Lives in the Mechanism Nobody Named.

In 2016, Bain analyzed S&P 500 companies across a 24-year period and confirmed what operators had long suspected: founder-led companies materially outperform. From 1990 to 2014, these firms consistently delivered 3.1x higher returns than their peers.

Bain named three differentiators: Business Insurgency, Front-line Obsession, and Owner’s Mindset.

Good descriptions. Accurate observations. But here’s what they didn’t explain: the mechanism.

Why does Business Insurgency translate to better decisions?
How does Front-line Obsession create faster learning?
What specifically about Owner’s Mindset produces 3.1x returns?

The research named the effect. It didn’t reveal the cause.

For eight years, people speculated. Then Paul Graham wrote an essay that went viral overnight—giving the phenomenon a name that still dominates every strategy conversation: Founder Mode.

The essay crystallized what operators had felt for years: there’s a way founders run companies that conventional management wisdom can’t explain. And it made it sound cool.

“He went into founder mode and changed the entire company.”
“Time to go into founder mode!”

The term became instant shorthand for something everyone recognized but nobody could quite define.

Graham’s admission was the most revealing part: “Business schools don’t know it exists, so they can’t teach it.”

Ten years of data. One viral essay. Zero mechanism.

Everyone agrees founder-led companies perform differently.

Almost nobody explains how.

The Bain research gave us the what—founders outperform. Graham’s essay gave us the name—Founder Mode. But neither answered the operational question that matters: What’s the mechanism that makes 3.1x possible?

The answer isn’t founder charisma, founder hustle, or founder intuition. It’s something more specific and—more importantly—something buildable: Decision Velocity.

Founders don’t just work differently. They decide differently. And the difference is measurable.

Here’s how.

What Everyone Sees—And What’s Actually Happening

Watch a founder-led company operate and certain patterns emerge.

They iterate faster. They course-correct before small problems become expensive ones. They run more experiments in a quarter than competitors run in a year. When market conditions shift, they’ve already adjusted—sometimes before the shift is obvious to everyone else.

From the outside, it looks like superhuman sprint capability. Like they’re playing the game at 3x speed while everyone else moves at normal tempo.

The surface explanations write themselves: Founders work harder. Founders care more. Founders have more at stake.

These explanations feel true. They’re also incomplete.

Plenty of professional managers work brutal hours. Plenty of hired CEOs genuinely care about outcomes. Plenty of leadership teams have significant equity stakes. Yet the performance gap persists.

Working harder doesn’t explain faster iteration. Caring more doesn’t explain better course corrections. Having stake doesn’t explain more experiments.

Something else is happening. Something the “work harder, care more” narrative misses entirely.

The difference isn’t effort or motivation. It’s how many quality decisions get made per unit of time.

This is what creates Prime Movers—individuals whose decision patterns predict category ownership.

And it’s measurable:

DV = C × (D/M)

Where:

• C = Context clarity (how aligned the team is on what customer transformation they own)

• D = Strategic decisions made

• M = Meetings required to make them

• DV = Decision Velocity

The D/M ratio is throughput. More decisions per meeting, less coordination overhead.

Founders don’t move faster because they work more hours. They move faster because they make more decisions per hour—and every decision requires fewer coordination meetings.

Same meeting, different output. Same week, 10x the decision count.

Here’s what that looks like inside the room.

Inside the Meeting Room

Imagine two meetings. Same agenda. Same company. Different leaders.

The Professional Manager’s Meeting

Marketing brings a channel decision to the table. The VP has prepared a solid deck—market data, competitive analysis, budget scenarios.

The discussion starts: “Which channel should we prioritize for Q2?”

Hands go up. Questions follow.

“What’s our customer acquisition cost target?”

“How does this align with the product roadmap?”

“Can we get more data on competitor spend?”

Good questions. Necessary questions. But each one requires follow-up. The meeting ends with three action items and a follow-up session scheduled.

One decision attempted. Zero decisions made. Two more meetings to go.

The Founder’s Meeting

Same agenda arrives. Same deck. Same data. One meeting to decide what took three meetings to defer.

The founder listens for two minutes, then starts working through the decision out loud:

“Which channel reaches operations managers who are missing moments that matter? LinkedIn—that’s where they’re scrolling at 10pm when they should be sleeping.”

“What message? Stop choosing between your calendar and your family.”

“What offer? Free trial positioned around eliminating the excuse to stay late.”

“When do we launch? Before Q2 planning locks in—three weeks.”

Four decisions. One meeting. Same hour, completely different output.

The professional manager isn’t slower because they’re less intelligent. They’re slower because they’re missing the filter.

They know company goals. They know department metrics. They know competitive landscape.

What they don’t know: who the customer becomes when they succeed.

Without transformation context, every decision requires triangulation. You need more data. More input. More alignment meetings. Not because you’re thorough—because you don’t have the filter that makes the right answer obvious.

The founder walks into that room knowing James. Knowing the soccer games James can’t miss. Knowing his weekend experience. And knowing the transformation the product enables.

That context doesn’t just inform decisions. It makes decisions. The filter does the work.

Not because founders are smarter. Because they carry context that eliminates the need for clarifying questions.

But where does that context come from? And if it's this powerful, why do so few companies have it?

The Context Gap

Bain’s 2016 research identified three characteristics. Each one spawned its own management philosophy. And each one got codified incompletely.

Thread 1: Business Insurgency → Founder Mode

Bain saw founders staying hands-on. Skipping management layers. Attending to details that “professional” CEOs delegated away.

Graham’s “Founder Mode” essay codified this observation into permission: founders should stay involved, not retreat to the executive suite.

What this captures: the behavior of founder engagement.

What it misses: why that engagement produces better decisions. Staying hands-on doesn’t automatically create 4 decisions per meeting. Micromanagers attend every detail. Still slow.

The behavior is visible. The mechanism isn’t.

Thread 2: Front-line Obsession → Customer Obsession

Bain saw founders maintaining direct customer contact. Jeff Bezos codified this into Amazon’s famous principle: “Start with the customer, work backwards.”

Customer obsession became gospel. Companies built research departments. Conducted surveys. Created personas. Mapped customer journeys.

What this captures: the orientation toward customer understanding.

What it misses: customer obsession doesn’t explain velocity. Companies can be obsessively customer-focused and still take 10 meetings to make 4 decisions. The research, the surveys, the personas—they often increase meeting count rather than decrease it.

More customer data doesn’t automatically create decision density. Something else is required.

Thread 3: Owner’s Mindset → Ownership Culture (The Misread)

This is where the codification went sideways.

Bain observed founders acting with “speed to act” and “personal responsibility for risk and cost.” They saw ownership behavior—decisive action, accountability, long-term thinking.

What got codified: Restricted stock units (RSUs) and equity stakes. “Act like you own the company.”

The problem: all of this points inward. It’s company-facing ownership. Own your department. Own your decisions. Own your equity.

But the founders Bain studied weren’t just owning the company. They were owning something else entirely.

The Missing Thread

All three threads point to the same gap.

• Founder Mode captures hands-on behavior—but doesn’t explain why founders know which details matter.

• Customer Obsession captures orientation toward customers—but doesn’t explain why founders make faster decisions from the same customer data.

• Owner’s Mindset captures decisiveness—but doesn’t explain what founders are actually decisive about.

The missing piece isn’t about owning the company.

It’s about owning the transformation.

Transformation Ownership: The Unifying Mechanism Behind Decision Velocity

The founder in that meeting room didn’t just know James existed. They knew who James becomes when the product works.

James stops missing soccer games. James gets his weekends back. James stops dreading the Sunday night email check.

That’s not customer obsession. Customer obsession asks: “What does the customer need?”

Transformation ownership asks: “Who does the customer become?”

The difference sounds semantic. It’s not.

Customer obsession keeps you focused on where customers are—their current problems, their feature requests, their pain points. It’s present-tense orientation.

Transformation ownership requires you to see where they’re going—the journey they’re on, the identity change they’re pursuing, who they become when they succeed. It’s future-tense clarity.

Why transformation ownership makes all three Bain characteristics work.

• This is why Business Insurgency works. Founders aren’t rebelling against management norms randomly. They’re insurgents on behalf of a specific customer transformation they’ve claimed as territory. They skip levels and attend to details because those details affect whether James makes his daughter’s game.

• This is why Front-line Obsession works. Founders aren’t collecting customer data for research decks. They're maintaining contact with the transformation they own—watching where customers get stuck, seeing them progress, recognizing what blocks the identity change.

• This is why Owner’s Mindset works. Founders aren’t just personally accountable for company outcomes. They’re personally accountable for whether customers achieve the transformation. James’s soccer games aren’t a persona insight. They’re a promise.

Transformation ownership is the context that makes all three characteristics velocity-producing—not just culturally admirable.

The Decision Velocity Math

• C (Context Clarity)= Transformation ownership clarity. Founders know which customer transformation they own. Professional managers inherited a strategy deck that describes products, not transformations.

• D (Decisions Made) increases because transformation ownership provides the filter. The right answer becomes obvious. James → LinkedIn → “Stop choosing between your calendar and your family.”

• M (Meetings Required) decreases because transformation ownership eliminates triangulation. No need for follow-up sessions when the context makes decisions self-evident.

Bain's three characteristics aren't cultural aspirations. They're how you build transformation ownership. Which is how you build velocity.

But what does transformation ownership actually look like when you operationalize it? How specific does “knowing the customer” need to be?

More specific than most companies ever get.

The Specificity Needed for Decision Velocity

Most companies describe what they do. Few companies describe who their customer becomes.

Watch the difference:

Time-Tracking Software

Abstract thinking: “We help businesses track employee hours and improve operational efficiency.”

Transformation thinking: “James makes his daughter’s soccer games, and stops dreading the conversation with his wife about why he’s working late again.”

Same product. Completely different decision filter.

“Improve operational efficiency” doesn’t tell you which channel to prioritize. It doesn’t tell you what message to lead with. It doesn’t tell you when to launch or what offer to make.

“James makes his daughter’s soccer games” tells you everything.

Accounting Platform

Abstract thinking: “We streamline financial operations and reduce month-end close time.”

This is accurate. It’s also useless for making decisions.

Transformation thinking: “Maria stops waking up at 3am the week before month-end. Her CFO stops micromanaging the numbers. The board meeting becomes a conversation instead of an interrogation.”

Same product. Much clearer decision filter.

How Specificity Creates Velocity

When you know James—really know him—decisions stop requiring meetings.

Which channel?
The one reaching operations managers who are missing moments that matter. LinkedIn, where they’re scrolling at 10pm instead of sleeping. Not Instagram. Not TikTok. Not broad-reach display ads.

What message?
“Stop choosing between your calendar and your family.” Not “improve operational efficiency.” Not “streamline your workflow.” The message that hits James in the chest.

What offer?
Free trial positioned around eliminating the excuse to stay late. Not “14-day free trial.” Not “see pricing.” The offer that removes the barrier between James and his daughter’s game.

When to launch?
Before Q2 planning locks budgets in. When operations managers are feeling the weight of another missed season. Not “when the product is ready.” When James is ready.

What feature to prioritize?
The one that eliminates Sunday night email dread. Not the one with highest upvote count on the feature request board. The one that delivers the transformation.

Five decisions. One transformation story. No follow-up meetings required.

This is the specificity level that makes the filter work: knowing James and Maria as people pursuing transformation, not personas representing segments.

Abstract positioning creates decision paralysis:

• Every option seems plausible

• Every direction needs more data

• Every choice requires alignment meetings

Transformation ownership creates decision clarity:

• Options filter themselves

• Direction emerges from the story

• Choices become obvious to everyone in the room

Clarity is velocity. Not a metaphor. The mechanism.

This is what high C (Context Clarity) looks like in the Decision Velocity Formula.

High context clarity eliminates the questions that require follow-up meetings. When everyone sees James’s transformation clearly, ‘Which channel?’ has an obvious answer. No debate. No data requests. No coordination overhead.

That’s how C multiplies the D/M ratio. Context clarity removes the meetings (M ↓) while enabling more decisions per meeting (D ↑).

This is why the founder made 4 decisions in one meeting while the professional manager made 0. The founder wasn’t smarter. They had higher C.

But here’s the question this raises: Does every decision have to be right?

The counterintuitive answer is no. And that’s where the real advantage lives.

The More At-Bats Advantage

Here’s what the math reveals that most people miss:

Prime Movers don't win because every decision is perfect. They win because they get more at-bats.

Who's a Prime Mover? The individual whose decision patterns predict category ownership. Not the loudest voice. Not the highest title. The person who makes the kind of decisions that create category owners—before anyone realizes the category exists.

The professional manager making 0 decisions per meeting isn’t just slower. They’re getting fewer at-bats. Fewer experiments. Fewer chances to learn. Fewer opportunities to course-correct.

The founder making 4 decisions per meeting isn’t necessarily making better decisions. They’re making more decisions—which means more feedback, more data, more learning cycles compressed into the same timeframe.

But here’s the critical part: decision velocity works when meeting count stays low.

Four decisions made across four meetings = same velocity as one decision in one meeting. The math doesn’t lie: 4/4 = 1/1.

The advantage isn’t just making more decisions. It’s compressing decisions into fewer coordination cycles.

This is the D in DV = C × (D/M). Decision count matters. But only when you’re not adding meetings proportionally.

This is the paradox: Decision velocity doesn’t require decision accuracy. It produces decision accuracy through iteration speed.

The Moneyball Principle

Billy Beane didn’t build the Oakland A’s around batting average. He built them around on-base percentage.

The insight: Getting on base matters more than how you get there. A walk counts the same as a hit. What matters is at-bats that lead to base runners.

Traditional baseball valued the quality of each swing—the perfect hit, the beautiful stroke. Beane valued the quantity of opportunities—more ways to get on base meant more chances to score.

Decision velocity works the same way.

Traditional management values the quality of each decision—the perfect analysis, the airtight business case. Prime Movers value the quantity of decisions—more choices made means more learning captured means more course corrections possible.

Remember the founder’s meeting: 4 decisions in one hour. Channel, message, offer, timing. Not perfect decisions—testable decisions.

The professional manager’s meeting: 0 decisions, 3 action items, 2 follow-up meetings scheduled. Pursuing perfect analysis while the founder is already learning from real market feedback.

When you move at 4 decisions per meeting, you can afford to be wrong.

The Affordability to “Swing and Miss”

This is what velocity actually buys: the ability to be wrong without it being fatal.

Miss on channel selection? You’ll know in week 2. Adjust in week 3. Message doesn’t land? You’ll see it in the data. Revise by month-end. Offer underperforms? Test a new one next sprint.

Your competitor moving at 0.5 decisions per meeting?

Week 2: Still in the strategy alignment meeting.
Week 3: Waiting for stakeholder approval.
Month-end: Finally launching their first test.
Next sprint: You’ve already run three iterations and identified what works.

High-velocity organizations don’t need perfect decisions. They need fast decisions with fast feedback loops. The learning compounds while corrections accumulate. The accuracy emerges from iteration, not from analysis.

Low-velocity organizations need every decision to be right—because they can’t afford to be wrong. Each choice carries enormous weight. Each mistake takes quarters to correct. So they analyze more, meet more, delay more. M climbs. D/M collapses. Velocity disappears.

The irony: The pursuit of perfect decisions creates the conditions where mistakes become catastrophic.

4x velocity doesn’t mean 4x better decisions. It means 4x more learning. 4x more adaptation. 4x more opportunities for the market to teach you what works.

Which reveals what the real competitive moat actually is.

It’s not decision quality. It’s not even decision quantity.

It’s the ability to make high-volume decisions without coordination overhead.

That’s where M comes in.

The M Factor: Coordination Overhead Elimination

M is coordination overhead. Meetings required. Alignment sessions. Stakeholder reviews. The organizational friction between “decision needed” and “decision made.”

High-M organizations aren’t slow because their people are slow. They’re slow because every decision requires synchronization across departments, approval chains, and calendar availability.

What Low M Looks Like

The founder’s meeting from earlier had M = 1.

No pre-meeting to align stakeholders. No follow-up session to finalize decisions. No coordination with other departments before making the call.

Channel, message, offer, timing—all decided in one hour because everyone in the room shared James’s transformation context. The context was the coordination.

The professional manager’s meeting had M = 3 (and climbing).

Initial meeting to discuss options. Follow-up session after gathering more data. Final alignment meeting once stakeholders reviewed the proposal. And that’s just for ONE decision—the channel choice.

Same question. Same data. Different M.

What creates the difference? Low-M organizations move fast because context is already distributed. When everyone knows James—knows the transformation, knows what they’re building toward—decisions don’t require alignment meetings. The shared context is the alignment.

This is why C multiplies D/M in the formula. Context clarity doesn’t just increase decisions made. It decreases meetings required. The numerator goes up. The denominator goes down. Velocity compounds.

Good addition. It’s diagnostic, connects to your owned language (rented positioning, abstract strategy), and explains the mechanism readers can self-assess against. Let me integrate it:

What Creates High M

• Rented positioning: When you compete on variables someone else defined, every decision requires validation. “How does this compare to competitors?” becomes a coordination question. You’re not deciding based on your transformation story—you’re deciding based on category norms that require constant rechecking.

• Abstract strategy language: “Improve operational efficiency” means something different to Marketing, Product, and Sales. Each interpretation conflict triggers alignment meetings. The strategy deck creates the illusion of shared context while actually producing coordination overhead.

• Inherited strategy: Professional managers get handed positioning they didn’t create. The transformation context lives in a deck, not their heads. Every decision requires checking the deck, confirming with stakeholders, validating alignment.

Founders avoid this naturally. They built the transformation story. It’s distributed context, not documented strategy.

The OODA Advantage

Fighter pilot John Boyd built his reputation on a simple insight: the pilot who cycles through Observe-Orient-Decide-Act faster wins the dogfight.

Not the pilot with better aim. Not the pilot with the superior aircraft. The pilot with faster decision tempo.

Boyd’s insight wasn’t just about deciding faster. It was about eliminating the coordination overhead between observe and act.

Traditional military doctrine: Observe → Report to command → Wait for orders → Coordinate with other units → Act.

Boyd’s approach: Observe → Orient using pre-established doctrine → Decide independently → Act immediately.

The shared doctrine (context) eliminated the coordination steps. High C enabled low M.

Decision velocity works the same way in organizations.

By the time your competitor finishes their analysis, you’ve already tested three approaches. By the time they align stakeholders, you’ve already learned what works. By the time they launch, you’ve already iterated past the version they copied.

Remember the timeline from earlier: Your competitor at 0.5 decisions per meeting is still in strategy alignment while you’ve completed three learning cycles. Week 2 vs. Week 2. Month 1 vs. Month 1. Same calendar time, 4x the learning advantage.

They’re not behind because they started later. They’re behind because they can’t catch up. Every decision cycle you complete while they’re still coordinating extends your learning advantage.

The System Effect: How C, D, and M Interconnect

This is the full Decision Velocity Formula:

DV = C × (D/M)

High C (transformation ownership clarity) acts as the multiplier. When everyone knows James’s transformation, channel decisions become obvious, message decisions become obvious, timing decisions become obvious.

High D (decision volume) creates learning velocity. Four decisions per meeting means four experiments, four data points, four opportunities to course-correct.

Low M (minimal coordination) enables compression. One meeting making four decisions beats four meetings making four decisions. Same D, quarter the M, 4x the velocity.

The variables aren’t independent. They’re interconnected:

• Low C forces high M - Unclear context = clarifying questions = follow-up meetings. Coordination overhead multiplies.

• High M prevents high D - Coordination overhead creates decision bottlenecks. If every choice requires three alignment meetings, decision volume collapses. You can’t make 4 decisions per meeting when each decision needs 4 meetings.

• High C enables both high D and low M - When everyone knows James’s transformation story, channel decisions are obvious. Message decisions are obvious. Timing decisions are obvious. No clarifying questions. No alignment sessions. No coordination overhead.

This is why transformation ownership isn’t just helpful. It’s the foundation of the entire system.

And here’s what makes this powerful: you don’t need to be a founder to build it.

The real moat isn’t being right. It’s being able to be wrong faster.

Competitors can study your strategy. They can copy your positioning. They can hire your playbook.

What they can’t copy is the velocity infrastructure that let you discover that strategy in the first place. By the time they implement what worked for you six months ago, you’ve already learned what works now.

Learning velocity compounds: each iteration teaches you something that makes the next iteration faster, sharper, more targeted.

Coordination overhead compounds too—in the wrong direction. Each meeting adds to the calendar, which requires more coordination for the next decision, which adds more meetings. The spiral accelerates.

The gap doesn’t close. It widens.

But here’s the part that changes everything: this advantage isn’t founder DNA. It’s buildable infrastructure.

How to Build Founder-Level Context

You don’t need to BE a founder. You need to BUILD the context founders carry.

The founder in that meeting room didn’t make 4 decisions because of charisma or hustle or years of experience. They made 4 decisions because they carried transformation context that made the right answers obvious.

That context isn’t mystical. It’s specific:

• Who transforms (James, Maria, Sarah)

• What they’re escaping (missed soccer games, 3am anxiety, weekend reports)

• Who they become (present parent, confident CFO, respected leader)

• What unlocks the shift (the product, positioned correctly)

Founders build this context naturally through the founding process. They talked to the first customers. They felt the first transformation. They carry James in their heads because they were there when James’s life changed.

Professional managers inherit a strategy deck. Founders inherit a transformation story.

The question isn’t whether transformation context creates velocity. The data proves it does—3.1x over 15 years.

The question is: can you build it deliberately?

The 5 Elements of Transformation Context

Transformation context has five elements. Build them, and you build the clarity founders carry naturally:

• People specificity → Higher C (everyone knows James, not "operations managers")

• Performance validation → Higher C (transformation proof, not case studies)

• Process mapping → Higher C (journey clarity eliminates "how do we get there" questions)

• Prioritization timing → Higher C (activation moment clarity focuses decisions)

• Positioning ownership → Higher C (territory clarity eliminates competitive triangulation)

More elements built = higher C = fewer coordination meetings (M↓) = more decisions per meeting (D↑) = higher velocity.

These five elements are the Strategy Flywheel—the systematic framework for building transformation context.

The Truth About the Founder 3.1x Performance Advantage

This is what Bain measured but couldn’t explain.

Founder-led companies don’t outperform because founders work harder. They outperform because founders carry transformation context that enables:

• Higher C → They know the transformation they own

• Higher D → Context makes decisions obvious, so more get made

• Lower M → Shared context eliminates coordination overhead

DV = C × (D/M)

The formula explains the 3.1x. Transformation ownership is the mechanism. Decision velocity is the output.

The 3.1x advantage isn’t founder DNA. It’s transformation context that can be built.

The 5 elements make founder-level decision velocity accessible to anyone willing to do the work. Not because you become a founder—but because you build the infrastructure founders carry naturally.

Start with one question: Which element would unlock the most velocity for you right now?

If you can’t name the human who transforms → start with People.

If you can’t prove the transformation happens → start with Performance.

If you can’t map the journey → start with Process.

If you can’t identify the activation moment → start with Prioritization.

If you can’t articulate the territory you own → start with Positioning.

Start with one element. Build it to human-level specificity—not abstract strategy language, but James-level detail. Then add the next.

Transformation context isn’t built in one session. It’s built through systematic work on each element until the context becomes distributed across your team.

Closing each context gap creates clarity. And clarity is velocity.

PS - The hardest part of building decision velocity isn't understanding the formula—it's diagnosing which variable to fix first. What's your hypothesis for your team? (My bet: most teams think it's D, but it's actually C.)

Prime Mover Advantage: Episode 9
The Traction Loop: How Motion Becomes Momentum

New Readers: Start here at Episode 1 here.

“Saw your Friday context, talked to Engineering Saturday morning, made the call.”

Rachel mentioned it Monday morning as if it were ordinary. “We’re moving forward with the streamlined approach.”

“Three weeks ago, that’s three meetings and a slide deck,” James said.

Elijah was already past it. “If we’re clear on authentication, I need to lock in the API architecture. One path keeps our options open but adds a sprint. The other ships faster and matches what we’re showing Kedaris.”

“Which one reinforces the demo?” Rachel asked.

“The faster one. We practice what we sell.”

“Then ship it.”

Elijah nodded. Done.

James looked around the conference room. No one had scheduled this meeting. No agenda existed. Context was present. Rachel was already back on her laptop.

Paul sat at the far end of the table, notebook open. He’d been quiet, writing something in the margins. He looked up briefly, studied the room, then returned to his notebook.

“Lisa wants to move up their check-in,” Rachel said without looking up. “Says they have early results — and she sounded surprised by them.”

“How early?”

“One week in.”

His team wasn’t waiting for direction.

“When?”

“Two o’clock. I told her we’d confirm this morning.”

“Confirmed.”

Rachel was already typing.

Elijah closed his laptop. “If Kedaris’s pattern matches ours, we’re not looking at an anomaly.”

Paul’s pen paused over his notebook. He’d written something, circled it, then written a question mark beside the circle. He closed the notebook without sharing it.

Thirty-five days until the board meeting. And for the first time, James wasn’t counting them with dread.

What Survives Contact Is Strategy

Two o’clock. Lisa’s face filled the screen, sharp. The camera angle was low — she was sitting at her standing desk, leaning forward. The pen in her right hand tapped against her coffee cup. Four-second intervals. Decision rhythm.

“I need to tell you what happened this morning,” Lisa said.

James leaned forward. Rachel had her notepad open.

“Our Monday leadership sync. The one that usually runs ninety minutes.” Lisa paused. Almost laughed. “Twenty-two minutes. Three decisions made. Our meeting-to-decision ratio just flipped.”

Rachel glanced at James. He kept his focus on Lisa.

“What shifted?”

“People came prepared. They already knew the context.” Lisa’s pen tapped twice. “Friday afternoon we ran the fifteen-minute session you walked us through. Felt almost too short. But then this morning, people were referencing things from that conversation like they’d internalized them. Not repeating what was said — building on it.”

“Context traveled,” James said.

“That’s actually what my VP of Engineering called it.” Lisa leaned back. “His exact words. ‘The context traveled over the weekend.’ He didn’t mean the information traveled. He meant the understanding did. People weren’t rebuilding from scratch Monday morning. They were already two steps ahead of where they would have been.”

Paul was taking notes at the far end of the table.

“Lisa, can I ask you something?” James said.

“Go ahead.”

“Before this week — what did you think the problem was?”

Lisa considered the question. The pen went still.

“Slow decisions. We’d diagnose an opportunity, debate the approach, schedule alignment meetings, loop in stakeholders, circle back with analysis... and by the time we committed, the window had moved.” She stopped. “That’s what I would have said a week ago.”

“And now?”

“Now I think we were never slow at deciding. The deciding part took five minutes once we got there.” Her pen stopped. “We were slow at arriving. At getting everyone to the point where a decision could happen. That’s where the weeks went. Not the choice itself — the runway to the choice.”

“You weren’t slow,” James said. “You were rebuilding context every time.”

“Every single meeting. Starting from scratch. Explaining what we already knew to people who should have already known it.” Lisa exhaled. “One week. That’s all it took to see it. Now the context lives in the system, not just in people’s heads.”

Rachel unmuted. “Lisa, what’s your team saying?”

“They’re confused.” Lisa smiled. “The good kind of confused. They keep asking why it feels different. I told them we’d figure out the language later. Right now, we’re just going to keep practicing.”

Six weeks ago, James had stood in front of his own team and tried to teach them what Sam had shown him. He’d recited vocabulary they hadn’t earned. Now he was watching Lisa’s team arrive at the same place — not through teaching, but through practice. No one had given them a framework to memorize.

“There’s one more thing.” Lisa straightened, pen clicking against the desk. “I want to expand this to our product team. They’re the ones most affected by our coordination overhead. If this works for them like it worked for leadership...”

“Let’s design that together,” James said. “Same baseline process. Measure before and after.”

“Already started the calendar invites.”

The call ended five minutes later. The team sat in silence for a moment.

Paul spoke first. “Their pattern matches ours. Week one, same acceleration. Same confusion about why it feels different.”

“Exactly,” James said.

“Which means this isn’t about us.” Paul closed his notebook slowly. “It’s about the transformation itself. It transfers.”

The team filtered out. James stayed in the conference room.

The Ramorian email had been in his drafts since last week. He read it once more.

David,

We figured out what we got wrong with Ramorian. You needed transformation, and we showed up with visibility. That gap cost us the relationship, and it should have.

We’ve spent the last six weeks rebuilding around that difference. One of our customers just ran it for a week — their leadership sync went from ninety minutes to twenty-two. Three decisions made. They’re expanding it to their product team without us pushing.

I’d like to show you what we built. No pitch. Just the work.

—James

He read it once more. Then hit send.

Repeated Moves Are Your Method

Read more

It’s strategy review time.

You're pulling together slides, aligning priorities, prepping the all-hands.

As you look through the details you realize:

Your team ships constantly but nothing compounds.

New features launch. Priorities shift. Meetings multiply. But strategic momentum? Flat.

The symptoms are everywhere:

• Your team can’t mobilize around strategy (people problem)

• Your metrics stay flat despite activity (performance problem)

• Your processes depend on talent instead of design (process problem)

• Your priorities scatter across too many bets (prioritization problem)

These look like separate problems requiring separate fixes.

They're not.

It’s one problem showing up in multiple places. And it’s not where you think it is.

I ran an exercise with 14 growth-stage CEOs.

The opener was 3 simple questions:

1. What are your Q3 priorities?

2. How does your go-to-market process work?

3. What transformation do customers experience through you?

The results:

• 12 could list Q3 priorities clearly

• 5 could explain their go-to-market process

• 2 could state the transformation in one sentence

Here’s what got interesting.

The 2 who could articulate transformation? Their priorities made sense. Their processes ran without heroes. Their teams mobilized without constant alignment meetings.

The 12 who couldn’t? Scattered priorities. Process confusion. Teams that needed everything explained twice.

Same talent levels. Same market conditions. Same access to capital. Different clarity on one question.

One CEO—call him David—could describe his company’s priorities for fifteen minutes. Detailed. Specific. Market segments, product features, competitive positioning against three named rivals.

When I asked the transformation question, he paused.

“We help companies... operate more efficiently? Scale their teams?” Each answer rose at the end. Questions, not statements.

His company was growing. Revenue up 20% year over year. But something was eating into his profits. Sales cycles kept lengthening. Marketing couldn’t explain why customers chose them over alternatives. The product team had three roadmaps depending on which executive you asked.

David thought he had three separate problems: sales training, marketing messaging, product alignment.

In reality, he had one problem showing up in three places.

Each leader had built their function around whichever version they’d heard most. Sales trained on efficiency. Marketing wrote about scale. Product built for automation. They were all executing well—on three different strategies.

So David ran the diagnostic with his leadership team. They started with People—could the team articulate the transformation? Sort of. Sales described it as efficiency. Marketing called it scale. Product said automation.

They traced backwards. Performance metrics were scattered—each team measured success differently. Process required constant executive intervention. Priorities included eleven strategic initiatives for a sixty-person company.

Then they hit Positioning.

David had three different transformation stories. One for investors (efficiency platform). One for enterprise customers (scale solution). One for mid-market (automation tool). He’d optimized messaging for each audience without realizing his team had absorbed the ambiguity.

Six months later, David told me the sales cycles shortened. Not because they fixed sales. Because positioning clarity gave everyone the same transformation story to execute against.

The symptoms showing up downstream—people, performance, process, prioritization—weren’t the problem. They were the signal. The source was upstream.

Every breakdown traced back to the same place: unclear transformation ownership.

If unclear transformation ownership caused downstream breakdowns, there had to be a sequence—a chain of dependencies where clarity either flowed or stopped.

That’s the Strategy Flywheel. Five elements, each dependent on the one before it:

Positioning → Prioritization → Process → Performance → People

Here’s the chain:

• Positioning: What transformation do you own? (The upstream source)

• Prioritization: What deserves focus given that transformation?

• Process: How do you systematically deliver that transformation?

• Performance: How do you measure transformation progress?

• People: Who needs to move, and can they articulate why?

Priorities make sense when positioning is clear. Processes work when priorities are focused. Performance metrics matter when processes are designed. People mobilize when they can see the whole picture.

Break clarity anywhere in the chain, and everything downstream shows symptoms.

This is why the 12 CEOs had scattered priorities. It wasn’t a prioritization problem. Their positioning was unclear, so every priority seemed equally valid. No filter.

This is why their processes required heroes. It wasn’t a process problem. Their priorities scattered, so processes couldn’t be designed around a clear outcome.

The symptoms were real. The diagnosis was wrong.

The Flywheel doesn’t just describe what’s broken. It reveals where clarity broke down. And that changes where you put your attention.

How to diagnose your Flywheel?
Work backwards.

Start where the pain shows up. Trace upstream until you hit resistance. That’s where clarity broke down.

The method:

Start with People.

Ask: “Can your team articulate what transformation you own and why it matters?”

If yes, clearly and consistently, your People element is solid. Move upstream.

If the answer is “sort of” or “depends who you ask”—stop. You found a symptom. But it’s not the source yet.

Second-level: Who tells it most clearly? What do they know that others don't? That's your clue—clarity exists somewhere but hasn't been distributed. Find the person who gets it and map what they understand that others are missing.

Keep tracing.

Move to Performance.

Ask: “Are you measuring transformation progress, or just activity?”

Dashboards full of metrics that don’t connect to customer transformation? Performance is showing symptoms. But why?

Second-level: When did you last change what you measure? If metrics multiplied recently, that's often a signal—teams adding measurements because no one agrees what actually matters. Find when the dashboard bloat started. Something upstream shifted around that time.

Keep tracing.

Move to Process.

Ask: “Do your processes systematically deliver transformation, or depend on heroic effort?”

If every win requires someone going above and beyond, your Process element is strained. But is Process the source, or inheriting symptoms?

Second-level: Who are your heroes? What do they do that processes can’t? Often heroes are compensating for upstream ambiguity—they’ve figured out something about priorities or positioning that hasn’t been made explicit. The hero’s workaround reveals where clarity broke down.

Keep tracing.

Move to Prioritization.

Ask: “Do your priorities focus resources on transformation, or scatter across competing bets?”

If everything feels urgent, if the strategic plan has 15 initiatives, if teams can’t say what’s not a priority—Prioritization is strained. But why can’t you prioritize?

Second-level: What got cut last? If nothing gets cut, or cuts feel arbitrary, that's a positioning signal. Clear positioning creates natural filters—some things obviously serve the transformation, others obviously don't. When everything survives prioritization, trace upstream.

Keep tracing.

Arrive at Positioning.

Ask: “Can you state in one sentence what transformation customers experience through you?”

This is the headwaters. If you can’t answer clearly, nothing downstream can compensate. Priorities scatter because there’s no filter. Processes improvise because there’s no destination. Metrics multiply because you’re measuring everything hoping something matters. Teams fragment because they’re each solving for their own version of success.

Second-level: Ask three different leaders the same question. If you get three different answers, you've found the source. The variation isn't a communication problem—it's a clarity problem. Each leader built their downstream work on their own version of what the company owns. That's why nothing aligns.

The "Sort Of" Signal

Here’s what to listen for as you trace backwards: the “sort of” answer.

“Can your team articulate the transformation?” “Sort of. Marketing says it one way, Sales says it another.”

“Are your processes designed or heroic?” “Sort of. We have processes, but they flex depending on the situation.”

“Sort of” means clarity exists somewhere—in a founder’s head, in an old deck, in tribal knowledge—but it hasn’t been distributed. The element works sometimes, for some people, in some contexts.

That’s the breakdown point. Everything downstream from a “sort of” runs on improvisation instead of infrastructure.

What “Sort Of” Looks Like at Scale

Apple had what every competitor was trying to build.

Siri wasn’t a voice assistant sitting on top of the iPhone—it was woven through the entire ecosystem. Thirteen years of users learning they could ask anything without their voice becoming a product. Billions of interactions reinforcing trust. Every device you added made it more valuable. Watch knew your fitness. HomePod knew your routines. iPhone knew your communication patterns. Siri connected all of it.

On-device processing. Privacy as positioning. Integration competitors couldn't replicate—not without abandoning the business models that funded their AI development.

OpenAI had intelligence but no integration. Google had reach but no trust. Amazon had presence but no coherence.

Apple had all three.

Then ChatGPT launched. And Apple blinked.

Instead of deepening what they owned, they built something new. “Apple Intelligence”—positioned as different from Siri. Development teams created separation instead of integration. Marketing spent $1 billion teaching customers a new name for what they already trusted. Product teams explained how this was different from what customers already had.

The positioning went from clear to “sort of.”

Do we own AI? Sort of. We have Siri, but we’re also building Apple Intelligence... Is Siri still our thing? Sort of. But Apple Intelligence is the future... Should customers trust the old or learn the new? Sort of both...

That hesitation cascaded through every system. Teams mobilized around the wrong war. Metrics chased ChatGPT’s scorecard instead of ecosystem value. Processes fragmented. Priorities scattered.

The downstream symptoms looked like execution problems. Delays. Pulled ads. Features that didn’t work. Emergency partnerships with Google.

But the source was upstream. Apple’s positioning went from owned to “sort of”—and everything downstream paid the price.

Two billion dollars later, they’re renting capability they once owned.

The diagnostic would have caught it. Trace backwards: People can’t mobilize → Performance metrics don’t connect → Processes require heroes → Priorities scatter → Positioning is “sort of.”

That’s where the work starts.

Other “Sort Of” Patterns

Apple isn’t unique. The pattern shows up everywhere transformation ownership gets fuzzy.

Yahoo owned the internet directory—the way people navigated the early web. Then Google arrived with a different transformation: search. Yahoo’s positioning became “sort of.”

Are we a directory or a search engine? Sort of both.

That hesitation cascaded through everything. They spent $2 billion acquiring search technology. Built Yahoo Search. Hired top talent. Still couldn’t compete. Why?

Trace backwards: Development teams built for unclear positioning. Marketing couldn’t explain what made Yahoo different. Processes served competing visions. Priorities scattered across search, email, social, content—everything seemed equally important because nothing was clearly owned.

Eventually, Yahoo surrendered. They licensed Bing’s search technology—becoming a renter to Microsoft’s renter. A company that once rejected buying Google for $1 million now pays to use a competitor’s competitor.

96% value destruction. $125 billion to $4.8 billion. The symptoms looked like execution problems. The source was upstream.

BlackBerry owned mobile email transformation—the device business professionals trusted with secure, push email before smartphones existed. Then iPhone redefined the category as consumer platform.

BlackBerry’s positioning became “sort of.”

Are we enterprise security or consumer smartphone? Sort of both.

They spent billions on BB10—a technically competent operating system that launched six years too late. They tried Storm touchscreens, PlayBook tablets, consumer apps. Each attempt strained resources and confused the market.

Trace backwards: Teams couldn’t agree what transformation BlackBerry owned. Product roadmaps served competing visions. Marketing oscillated between enterprise and consumer messaging. Every priority seemed valid because positioning was “sort of.”

Market share collapsed from 50% to 3%. Not because the technology failed—because clarity never existed at the headwaters.

The diagnostic would have caught it. All three companies had brilliant talent, massive resources, and market position. All three lost because downstream symptoms got treated while upstream ambiguity compounded.

Why does working backwards reveal what working forwards misses?

Think about the doctor you trust.

Not the one who scribbles a prescription before you finish describing symptoms. The one who asks questions. Who traces backwards through your history, your habits, your context—until they find where the problem actually started.

You come in with headaches. A rushed doctor prescribes painkillers. Headaches return. Stronger painkillers. Side effects. More symptoms.

The doctor you trust asks different questions: When did they start? What changed? What else is happening? They trace backwards through sleep, stress, diet, posture—until they find the upstream cause. Maybe it’s tension from a workspace change six months ago. The headaches were real. The painkillers weren’t wrong. But they were treating downstream.

Fix the workspace. Headaches resolve. No medication needed.

That’s the difference between symptom treatment and source diagnosis.

The rushed doctor treats what’s visible. The trusted doctor traces what’s connected. Same patient. Same complaint. Different intervention points.

Here’s what the trusted doctor understands: symptoms show up where they’re felt, not where they start. The headache is in your head. The cause might be in your neck, your schedule, your screen time, your stress. Treat the headache, you get temporary relief. Find the cause, the headache stops needing treatment.

The Strategy Flywheel works the same way.

Positioning is the source. The transformation you own.

That clarity flows into everything else: Prioritization. Process. Performance. People.

When the source is clear, downstream systems work—not because they're perfectly designed, but because they're not compensating for ambiguity. Same people. Same resources. Same processes. Different results.

When the source is unclear—when positioning is "sort of"—every downstream system absorbs the strain:

• Priorities multiply because no one owns the filter

• Processes improvise because outcomes keep shifting

• Metrics scatter because no one agrees on what success proves

• Teams fragment because each group optimizes for a different version of winning

The symptoms are real. The pain is real.

But downstream teams aren’t broken. They’re absorbing ambiguity they didn’t create.

This is why hiring better talent doesn’t fix a people problem. Why new dashboards don’t fix a performance problem. Why documented workflows don’t fix a process problem. You’re prescribing painkillers for a workspace issue.

Working backwards traces the connection until you find where clarity failed. That’s the intervention point.

Clear the source, and you don’t fix execution. You remove the need to compensate for it.

Your turn.

Where’s the stall showing up right now? People? Performance? Process? Prioritization?

Start there. Trace backwards.

At each element, ask: “Is this clear, or sort of?”

When you hit “sort of,” you’ve found the breakdown point. Everything downstream from there isn’t failing—it’s compensating.

That’s where the work starts. Not with better dashboards. Not with communication training. Not with another offsite.

With clarity at the source.

One question to try this week: Pick the symptom that’s frustrating you most. Ask yourself—what would need to be true one level upstream for this problem to dissolve on its own?

If you can’t answer clearly, keep tracing.

PS - If you want the forward view—how to build the Flywheel from Positioning through People—start here: The Strategy Flywheel: How Strategic Clarity Compounds Into Momentum

There’s a feeling when strategy starts working.

Not “we shipped fast” working. Actually working.

Decisions get faster. Not because you’re rushing - because clarity removes debate.

Each quarter builds on the last instead of resetting. What you shipped last quarter made this quarter’s priorities clear. What you ship this quarter will make next quarter’s priorities clearer. The roadmap becomes obvious.

The question in meetings go from “should we do this?” to “does this change the customer’s reality?”

And most noteworthy - teams start moving without you in the room. Not because they’re autonomous for autonomy’s sake - because context travels through the system. They know what you’d decide because they understand why you’d decide it.

This is what strategic clarity feels like when it compounds.

Two companies found this rhythm in very different ways - one through systematic orchestration over years, one through a single mythic moment that activated everything they’d built.

Both reveal the same pattern underneath.

For those unfamiliar: Alex Hormozi has had a meteoric rise in the business world.

From gym launches to building Acquisition.com, he’s become what creators aspire to be - someone who built real wealth and now teaches others to do the same.

His $100M brand was established. But most of that value was behind the scenes inside his companies. He wanted something publicly visible. Something that demonstrated the methodology at scale.

So he set a goal most authors wouldn’t speak out loud: Break the world record for fastest nonfiction book sales.

This is what becomes available when the flywheel is already spinning.

Hormozi had spent years building foundations. The audience was there. The proof was demonstrated across thousands of businesses. The credibility wasn’t claimed - it was earned through visible customer transformation.

When these connected, he could ask a different question. Not “how do I sell this book?” but “what would make the impossible possible?”

The world record became the internal governing constraint. His team wasn’t executing a book launch. They were engineering a historic moment. Twenty-two thousand affiliates weren’t promoting a product. They were participating in something that had never been done.

Then he reframed the offer in a way only someone with a spinning flywheel would think to do.

He didn’t ask people to buy. He asked them to donate.

The tiers told the story:

• Entry level: Donate a book to someone whose business is stuck.

• Mid-tier: Donate roughly $6k worth of books - and get his playbooks, AI tools, and a private workshop.

• High-tier : Donate $24k worth of books - and get six months of direct time with Hormozi himself.

Hormozi reframed the default “invest in yourself,” and leaned into “help someone else get ahead - and you get further ahead in the process.”

This tapped something deeper than tactics. As entrepreneurs grow successful, many feel disconnected - from their origins, from people who knew them before. The donation frame gave them something powerful: demonstrable proof they’re helping others. Books they could gift. Generosity made visible.

Who thinks to structure an offer this way?

Someone who isn’t worried about whether the book will transform buyers. That’s already handled. The flywheel has proven it thousands of times. So now the question becomes: How do I amplify this? How do I make advancement and generosity the same action?

Each element strengthened the others. The world record mobilized affiliates who wanted to be part of history. The donation frame gave them language that felt like mission. The tiered structure let people choose their level of participation. The existing proof meant recipients would actually transform - creating more proof.

Hormozi teaches offers, money models, lead generation. What this reveals is the coordination underneath - the flywheel that made audacity possible.

Most authors launch books. Hormozi engineered a movement.

The Audacity Advantage

While Hormozi engineered his movement deliberately, Duolingo stumbled into theirs.

But what they stumbled upon wasn’t luck. It was something they’d been building without knowing it.

Here's what happened:

The owl has always meant wisdom. Athena’s owl overseeing Ancient Greece. The Tootsie Pop owl making children work for answers. The archetype runs deep - the wise guide who holds you accountable, who sees when you’re slacking, who won’t let you off easy.

Duolingo modernized this without losing it. Duo became both sensei and stalker. The teacher who guilts you back to lessons at 11 PM - but does it with heart emojis and streak celebrations. Hundreds of small daily interactions that felt like relationship, not product usage.

They’d built a guide. They just didn’t have language for what that meant.

Then they killed it.

In early 2025, Duolingo announced Duo’s death as part of a campaign. Standard marketing theater - beloved character dies, users react, brand gets attention.

What happened next surprised everyone.

Users didn’t just react. They mourned. Social media flooded with genuine grief. People shared stories about their relationship with the owl - the streaks maintained, the gentle guilt of missed lessons, the small daily ritual that had become part of their identity.

This wasn’t engagement. This was the same response humans have had for thousands of years when the teacher falls.

When Obi-Wan vanished, Luke stopped hesitating. When Dumbledore fell, Harry stopped waiting for guidance. When Mr. Miyagi died, Daniel became the sensei.

The student must prove the teacher’s lessons took hold. That’s not marketing theory. That’s mythology.

Duolingo activated it by accident.

Then they did something smart. They offered resurrection. Hit a collective XP goal, and Duo comes back.

Users didn’t just participate. They fought. Individual learners transformed into a community on a mission. Daily learning went from routine to ritual. Each lesson, each streak, became a vote for revival.

That XP resurrection loop turned mourners into heroes restoring their guide - and proving mastery in the process.

Here’s what Duolingo discovered: they have a movement waiting to be built.

The campaign worked as a moment. But the foundations it revealed - the guide archetype, the relationship depth, the community that mobilized - that’s not a campaign. That’s a flywheel already spinning. They just didn’t know how fast until something made it visible.

Two companies. Two movements. One pattern underneath.

Hormozi didn't just have a big audience. Duolingo didn't just have a beloved mascot.

They had foundations already spinning. Each element making the next one possible.

Here's what was really working:

Positioning - Both owned a transformation, not just a product.

Hormozi wasn't selling books. He owned the transformation from 'struggling business owner' to 'business owner with a $100M money model.' That's category territory. No competitor can rent that from him.

Duolingo owned the identity shift from 'person who wishes they spoke Spanish' to 'conversationally fluent Spanish speaker.' Not "better language app." The person you become.

When you own a transformation, you don’t compete on features. You compete on identity change.

Prioritization - Both had a filter that made decisions obvious.

Hormozi's filter: Does this make the world record possible? Six months. One constraint. Every decision answered by that single question. No debates about the book tour, the podcast circuit, the traditional launch. World record or nothing.

Duolingo's filter: Does this deepen the daily learning ritual? The streak mechanics, the gentle guilt, the celebration moments - each one strengthening the habit they were building. No feature shipped unless it made coming back tomorrow more likely.

When prioritization is clear, you stop debating what to do next. The transformation you own becomes the filter that answers every question.

This is why owned positioning creates decision velocity. Rented positioning requires endless coordination meetings. Owned territory makes priorities obvious.

Process - Both built coordination that ran without constant management.

Hormozi coordinated 22,000 affiliates with hour-by-hour choreography. But he wasn't in every room. The process held the context. Every affiliate knew their role because the world record goal traveled through the system. The coordination architecture made autonomous execution possible.

Duolingo’s daily notification rhythm, streak architecture, XP mechanics - none of it required someone manually pushing users. The process carried the accountability. Users pushed themselves because the system made progress visible.

When process encodes your transformation, teams move without you in the room. The transformation story downloads into operating rhythm. That’s when strategy stops being documents and starts being infrastructure.

Performance - Both tracked momentum, not just activity.

Hormozi wasn't measuring book sales. He was measuring world-record pace. Every hour, every day: Are we ahead or behind the trajectory that makes history? The metric made the impossible measurable.

Duolingo wasn't measuring app opens. They were measuring streak retention, daily return rates - the signals that said "this person is becoming a daily learner." Not usage. Identity change.

When performance tracks transformation progress, you see whether momentum is building or stalling. You’re measuring customer movement, not company activity.

People - Both mobilized communities, not just customers.

Hormozi’s affiliates weren’t salespeople. They were participants in something historic. The donation frame transformed buyers from “investing in themselves” to “helping others get ahead.” Generosity and advancement became the same action.

Duolingo’s users weren’t completing lessons. They were fighting to resurrect their teacher - proving mastery in the process. Mourners became heroes. Students became the sensei.

When people feel like protagonists in a transformation story, they move differently than customers being sold to. That’s mobilization versus transaction.

The Strategy Flywheel

Five elements. Each enabling the next. Each making the next easier.

Positioning makes prioritization obvious. Prioritization makes process lighter. Process makes performance measurable. Performance makes people decisions clear. People executing strengthens positioning.

When they connect, momentum compounds. Decisions get faster. Outcomes get clearer. Each quarter builds on the last.

That’s what Hormozi built deliberately.

That’s what Duolingo discovered they’d built.

The same pattern is available to you.

Not because you’ll copy Hormozi’s launch or Duolingo’s campaign. But because the same pattern underneath both is the same pattern underneath any business that builds momentum instead of just staying busy.

The question is: Is yours spinning?

Part 2 shows you how to diagnose - where it’s connected, where it’s wobbling, and which element to look at first.

Until then, one thing to notice:

In your next strategy conversation, count how often you say “we” versus “they.”

If “we” dominates, you’re building internal coherence. If “they” dominates, you’re building external momentum.

“Most companies spend 90% of meeting time on ‘we,’ 10% on ‘they.’”

That ratio reveals more than any strategy document.

PS: Part 2 shows you how to diagnose which of the five elements is wobbling—and which one to strengthen first.

Most companies don’t have a slow flywheel. They have disconnected elements that never create momentum. That’s the real diagnostic question.