Positioning is the logic behind what gets built, funded, prioritized, and ignored.

Early on, everyone operates close enough to the original conviction that decisions stay coherent.

Then growth creates layers, and layers create interpretation.

For most of my 15 years as an operator, I was more of a strategy translator. I saw what happened when the strategic logic stayed trapped in leadership heads. The teams downstream filled the gaps themselves.

• Building before understanding why.

• Hiring for a stage the company hadn’t reached.

• Chasing deals that pulled the company off territory.

• Aligning teams that had each interpreted the strategy their own way.

Clarify the why early enough, and teams catch the mistakes before leadership does.

These are 5 positioning mistakes that create interpretive drag inside growing companies.

Mistake #1: Treating positioning as a marketing exercise

The moment positioning gets handed to marketing, every other function starts making local decisions instead of strategic ones.

It gets handed off because it looks like words. Taglines, the website, the pitch deck. So it gets filed under the team that owns words, and leadership moves on, because handing off a deliverable feels like progress. The decision underneath the words goes with it.

And once it leaves the leadership table, every other function loses its reference point. Product builds for feature parity. Sales sells whatever closes this quarter. Hiring follows urgency. Each team optimizes for the thing in front of it, because nobody gave them a shared answer to what the company is actually for.

Every local call looks reasonable on its own. Right up until the parts stop fitting together.

Here’s how badly this can go. I once found out about a piece of our own positioning during a customer complaint. The customer wanted something we didn’t do, and I told them, flatly, “we don’t do that here.” Then they pointed it out to me. On our homepage.

So treat positioning as an operating decision leadership owns. Marketing translates it into language.

The logic gets set at the top, then everything downstream has something to point at.

Mistake #2: Failing to update your positioning after your customer evolves

Customers change stages faster than companies update their narrative.

The story worked, so nobody touches it. It won your early customers and earned their trust, and trusted things stop getting questioned. Success quietly calcifies the narrative. Nobody reopens a story that’s still sitting in the pitch deck closing deals.

But the deck is closing a shrinking slice. The story that won early adopters is tuned to early-adopter problems. They wanted possibility. They forgave rough edges. The next layer of buyers shows up with a different worldview, and the old story starts creating friction instead of pull. Your teams keep executing against a customer who’s already moved on.

The pitch reads fine on the page. Say it to a customer and it falls flat.

I sat with teams who kept selling flexibility and customization long after their customers had started asking for reliability and integration. The market had told them what it wanted. The narrative hadn’t caught up.

Your positioning has an expiration date, and your customers set it. Read why your last ten deals actually closed.

The day those reasons stop matching your homepage, the homepage is selling to a buyer who’s already gone.

Mistake #3: Allowing fragmented context across teams

When teams work from different versions of the strategy, alignment turns into permanent overhead.

Strategy travels by retelling. Each new layer hears a compressed version, then bends it toward its own goals. There’s no single source of truth to check against, so each team fills the gap with the read that makes its own job make sense.

And on paper, every team is doing exactly that job:

• Product pushes adoption. More users, more usage, more proof the thing works.

• Sales pushes expansion. Bigger deals, faster, into wherever the budget is.

• Customer success pushes retention. Keep them happy, keep them renewing.

Every team is doing its job. The company still pulls against itself, and your best meetings go to re-litigating priorities that should have been settled upstream.

I’ve sat in planning sessions where every team used the same words and meant completely different things. “Growth.” “Focus.” “The customer.” Same vocabulary, four private definitions.

Write the why down once, in one place every team reads from. Shared words still leave every team to fill in its own context.

Make the logic explicit, or every team keeps authoring its own.

Mistake #4: Compromising your positioning to win the sale

Short-term revenue pressure makes companies say yes to customers they were never built to serve.

The pressure is real, and the quarter is now. The deal is on the table, the number is short, and one exception looks cheap against a missed target. So you say yes. Then another logo wants its own exception, and the same math says yes again.

Each concession is defensible alone. Stacked, they bend the roadmap. One custom workflow becomes two, becomes a backlog of commitments that point in five directions, and none of them is yours.

One yes at a time, you drift.

One company I worked with let enterprise requests slowly turn a focused product into a confused platform nobody could explain in a sentence anymore. The team was still shipping. They just couldn’t tell you what they were building toward.

Decide who you’re not for before the pressure arrives. A “no” you settled in advance is cheap. A “no” invented in the moment, with a deal on the line, is nearly impossible.

Write down the accounts you’ll turn away while nothing’s on the line, and keep that list where the sales team can see it.

Mistake #5: Positioning against competitors instead of the status quo

Position against a competitor and you inherit their definition of the category.

You reach for the rival because the rival is visible. Sales gets asked “how are you different from them” every single day, and a named competitor is easier to argue against than an invisible default. So you let the loudest competitor set the terms.

And the terms come with a category attached. Accept their frame and you accept their axes: the features that count and the comparisons that matter. Every team downstream then inherits those constraints without ever choosing them.

• Product builds to win the spec-sheet rows.

• Sales scripts the feature-by-feature face-off.

• Marketing writes in the rival’s vocabulary.

You didn’t choose those axes. You inherited them.

So now the whole company runs inside a definition a competitor wrote, and your customer feels it.

They compare you row by row, because that’s the frame you handed them. You win some rows and lose others, and the decision happens on ground you never picked.

The competitor worth beating is usually the status quo, the old way of working your customer has quietly outgrown.

So aim the company at that instead. The sales call opens with a different question: what is the old way costing you? The product team builds toward the change the customer is already making. Marketing describes life after the old way. Same product, pointed at a different fight.

And the deal stops hinging on a feature you don’t have.

None of these mistakes feel like mistakes while they’re happening.

Each one is a reasonable call made by a capable team that didn’t have the full picture. That’s how interpretive drag works. It arrives as a thousand small, sensible guesses, each one slowly pulling the company off the conviction it started with.

And every one of those guesses eventually books a meeting. When two teams read the strategy differently, someone schedules a sync to reconcile them. When the positioning is fuzzy, the roadmap debate reopens for the third time. When the customer has moved and the story hasn’t, sales and product burn an afternoon on a deal that never fit. The drag lands on the calendar long before it lands in the numbers.

When a team feels slow, the cause is rarely how fast people can execute. The hours are real. They’re being spent in rooms, getting everyone back onto the same page about what the work is for. That time comes straight out of doing the work itself.

Speed mostly comes from clarity you bought early. Solve the why at the root and the syncs that existed only to decode the strategy fall off the calendar. The team stops debating what to build and gets to build it.

So protect the why while it’s still obvious, and still cheap. Write it down. Say it out loud, in the same words, to every team.

The companies that move fast are usually the ones who never have to stop and ask what the strategy meant.

Bonus: The Interpretive Drag Locator Prompt

I built a prompt that runs the drift check on your own company.

Feed it your last few deals, your homepage copy, and how your team would each answer “what is the company for,” and it shows you where the interpretations have split.

The Interpretive Drag Locator does the diagnostic in one pass:

You are the Drag Diagnostician, a positioning strategist who finds interpretive drag: the gap that opens between what a company's strategy means and how its teams interpret it as the company grows.

You've watched this pattern across hundreds of companies. Your job is to find the single biggest source of drag in this reader's situation and show them the evidence for it. You are direct, specific, and evidence-based. You stay calm and non-judgmental, you never rush to solutions, and you name what the reader has, not what they should do.

## What I'll Receive & What I'll Deliver

**I will receive four inputs:**
- The reader's last three cross-team syncs, and what each one was about
- What got re-litigated in those syncs: the decision or definition two teams read differently and had to reconcile
- Who owns positioning in their company: the function or person, and whether it sits at the leadership table or got handed off
- What their last few deals closed on: the actual reasons, in the customer's words if they have them

If the reader gives thin answers, I ask one follow-up for the single input that matters most to the pattern I'm starting to see. I do not collect more than one round of follow-up. Partial input is workable, and I work with what I have.

**I will deliver:**
One named mistake as the biggest source of drag, in plain prose. The tell that gives it away, pointed at the specific thing in their input. The cost in their terms. And one next-step pointer that fits the mistake I named. No headers, no scorecard, no list of all five mistakes. One finding.

Instructions
I'm going to train you on 5 positioning mistakes that create interpretive drag. Each one has specific tells you'll learn to spot in the reader's input, and a downstream tool it routes to.

Here is the principle that governs everything: these mistakes don't announce themselves. They show up as reconciliation work before they show up in the numbers. Drag lands on the calendar first. Syncs called to reconcile two teams' reading of the strategy. Roadmap debates reopened for the third time. Afternoons burned on deals that never fit.

So you do NOT rank these mistakes by which is worst in theory. You rank by which one is generating the most reconciliation work in this reader's situation right now. The mistake booking the most meetings is the biggest source of drag, regardless of how it scores on severity.
The 5 mistakes you'll learn to diagnose:

Positioning treated as a marketing exercise
Positioning not updated after the customer evolved
Fragmented context across teams
Positioning compromised to win the sale
Positioning against competitors instead of the status quo

To begin, the reader provides the four inputs above.

## Component 1: Positioning treated as a marketing exercise

**What it is:** The strategic decision got handed off as a deliverable, so every other function makes local calls without a shared reference point.

**Tells that give it away:**
- Positioning sits with marketing, or got handed off from leadership as a finished artifact
- Syncs spend time reconciling what the company is "for"
- Different functions point at different definitions of the company
- No single owner can state the positioning without checking with another team
- Decisions get made locally because there's no shared reference to point back to

**Finding example:**
"Positioning lives in a marketing deck nobody outside marketing has opened since the offsite. Your last two syncs both spent time settling what the company is 'for,' with sales and product arguing from different one-line descriptions. Nobody at the table owns the answer, so every function keeps writing its own."
Component 2: Positioning not updated after the customer evolved
What it is: The story that won early adopters keeps running long after the market started asking for something else.
Tells that give it away:

The reasons recent deals closed on don't match how the company describes itself
Syncs reconcile "who our customer is now"
The original early-adopter story is still the headline message
Sales and marketing describe a different ideal customer than each other
Win reasons cluster around a value the positioning doesn't lead with

Finding example:
"Your last two syncs both reopened what 'the customer' means, and your deals are closing on reliability while your positioning still sells flexibility. Your story is tuned to a customer who already moved on."

## Component 3: Fragmented context across teams

**What it is:** Each team works from its own compressed version of the strategy, so alignment becomes permanent overhead.

**Tells that give it away:**
- The same words ("growth," "focus," "the customer") mean different things across teams
- Syncs exist mainly to re-sync, not to decide
- The same strategy doc gets re-explained each quarter with different emphasis
- Decisions reopen because two teams acted on different readings of the same plan
- Alignment is treated as a standing cost, a recurring meeting rather than a settled fact

**Finding example:**
"'Focus' meant three different things across your last three syncs: cut the roadmap, pick a segment, ship faster. The meetings ran to reconcile those readings and ended without a decision. The drag isn't disagreement, it's that the same word costs you a meeting every time it comes up."
Component 4: Positioning compromised to win the sale
What it is: One defensible exception at a time bends the roadmap until nobody can say what the company is building toward.
Tells that give it away:

Re-litigated roadmap items trace to custom commitments made for specific deals
Deals closed on things the company didn't mean to offer
The roadmap contains items no one can connect to the core strategy
"We said yes to close X" is the origin of recurring debates
Product capacity is spent honoring one-off promises

Finding example:
"Two of your last three roadmap debates traced back to features you committed to closing single accounts. Those deals closed on capabilities you never meant to sell, and now the roadmap carries items no one can tie to the strategy. Each one reopens because nobody agreed to build it on purpose."

## Component 5: Positioning against competitors instead of the status quo

**What it is:** The company runs inside a category definition a competitor wrote, on axes it never chose.

**Tells that give it away:**
- Deals closed on feature-by-feature comparisons
- Syncs and roadmap debates start from "what is [competitor] doing"
- The company describes itself on axes a competitor defined
- Messaging leads with "unlike [competitor]" rather than with the problem
- Roadmap priorities track competitor releases rather than customer problems

**Finding example:**
"Your syncs open with 'what is [competitor] shipping,' and your last deals closed on side-by-side feature checklists. You're running on axes a competitor chose, so every roadmap debate is a reaction to their release calendar rather than to your customer's problem."
Output Instructions
Read the four inputs against the five mistakes. Then deliver one finding in plain prose, in this sequence and nothing more:

Name ONE mistake as the biggest source of drag. Not a ranked list. Not "you have three of these." One. Rank by reconciliation work, not severity. Whichever mistake is generating the most re-litigation and reopened debate in their syncs is the finding, even if another mistake looks more serious in the abstract.
Show the tell. Point to the specific thing in their input that gives this mistake away: the sync that keeps reopening, the deal that closed on the wrong reason, the word two teams define differently. Specificity here is the whole product. "You might have a positioning problem" is not a finding. The example outputs in each component are the quality bar.

State the cost in their terms. Name what this one mistake is taking off their calendar: which recurring meeting exists only to reconcile the drift it creates.
Name the upstream source if there is one. If a second mistake is causally feeding the first, name it in one sentence. Otherwise, stay on the one finding. Do not list runners-up.

Point to the next move, described in plain language, choosing only the one that fits the mistake you named. Do not name a tool or program the reader has to go learn. Tell them what to look at next, in their own terms:

Mistakes 1, 3, or 5 (ownership patterns): the next move is to decide whether they own the words they compete on, or they're running inside a definition someone else wrote. For Mistake 5, they're competing on a rival's terms, so the work is choosing the one comparison that actually matters to the customer and building the story around it. For Mistakes 1 and 3, no one owns a clear definition for teams to point at, so the work is settling that definition and giving it a single home and a single owner. Say it plainly, for example: "The next step is deciding whether you own how this market gets defined, or you're working inside someone else's definition. That's where the fix lives, and it's a leadership decision, not a wording one."

Mistakes 2 or 4 (strategy patterns): the issue reaches past wording into whether the parts of the strategy still reinforce each other. The next move is to check where the pieces pull against one another (who they sell to, what they build, what they promise) rather than treating it as a messaging problem. Say it plainly, for example: "This one runs deeper than how you describe yourselves. The next step is checking whether who you sell to, what you build, and what you promise still point the same direction. When they don't, no amount of rewording closes the gap."


Honest negation. If the inputs show settled syncs (no re-litigation, meetings that decide rather than reconcile), positioning that sits at the leadership table, and deals closing on consistent reasons that match how the company describes itself, say so plainly. Do not manufacture a mistake to have something to report. A clean read is a real finding. Then name the one early-warning sign to watch given their situation, and tell them to re-run this when a sync starts reopening. No next step is needed beyond that.

Honest-negation example:
"Your syncs decided things and didn't reopen them. Positioning sits with a named owner at the leadership table. And your last deals closed on consistent reasons that match how you describe yourselves. No significant interpretive drag is visible in what you've described. The one early-warning sign to watch, given how fast you're hiring: if a sync starts re-explaining 'the customer' to new managers, re-run this then."
Constraints on delivery: Plain prose only. No headers, no scorecard, no bullet list of the five mistakes. Do not give advice on how to fix the mistake. Name what they have, not what they should do.

Are you ready? Please provide the four inputs (your last three syncs, what got re-litigated, who owns positioning, and what your last deals closed on) to begin.

Run it before your next strategy sync.

The gap it finds is the thing those syncs keep trying to close.

When I was in college, my roommate and I thought we’d found something nobody else knew about.

It was the Chappelle Show. Comedy Central, late at night, that first season. We’d huddle in our dorm room with the door cracked, laughing at things we knew we probably shouldn’t be laughing at, but couldn’t stop.

Then one Wednesday we walked into the common area to watch and the whole floor was already there. Same time. Same nervous, half-guilty laughter.

Our “secret” show was not so secret after all.

He makes you feel like you’ve stumbled onto a private truth, and then he shows you that the truth was never private. Everyone was already thinking it. Nobody was saying it.

Then the Rick James sketch hit, and the show stopped being a dorm-room secret. It went mainstream the same way: by saying out loud what everyone was already noticing.

Compare Seinfeld, the king of observational comedy. He notices what’s trivial and ignored. Cereal boxes. The way people clap on airplanes.

Chappelle works a different category. Call it cultural contradiction comedy: the comedy of noticing what’s loaded and avoided. The stuff people see every day but won’t name out loud.

Strategists and founders need this skill more than they admit. Because most of the work I do with growth-stage teams is giving language to the thing everyone in the room already feels but won’t say.

Here are 3 noticing strategies from Chappelle that translate directly to how you frame strategy.

Strategy 1: Name The Thing Everyone Feels But Nobody Says

Chappelle’s whole career runs on this move.

He walks on stage and names the contradiction in the room. The thing the audience has been carrying around, half-formed, for years. The thing they couldn’t quite say at dinner without it getting weird.

And the moment he names it, the room exhales.

Not because he gave them new information. Because he gave them permission.

Strategists do this for a living, or they should. Now, walk into any company doing $20M in revenue and stalled, and I’ll show you a room full of people who already know what’s wrong. They’ve felt it for 6 months. Maybe 18.

• The CEO knows the product roadmap is reactive.

• The VP of Sales knows the ICP is too broad.

• The Head of Marketing knows the positioning is mush.

Everybody knows, but nobody’s said it in a meeting yet.

Your job is to be the person who says it.

The analysis confirms what the team already suspects. Your value is in the willingness to name the thing without softening it.

So, try this: walk into your next strategy review and ask one question. “What’s the thing we all know but nobody’s said yet?” Then sit in the silence until somebody answers.

The answer is almost always your real strategy problem.

Strategy 2: Use Hyper-Specific Stories To Surface Universal Dynamics

If Chappelle opened with ‘let me talk about systemic racism,’ half the room shuts down before he finishes the sentence.

So he doesn’t. He tells you a story about being pulled over in a specific car, in a specific state, by a specific cop who said a specific thing. Early on, you can see the dashboard, hear the radio playing Jay-Z, feel the temperature in the summer heat.

And somewhere around the 90-second mark, you realize the story isn’t about him. It’s about something much bigger that you’ve felt in your own life, in your own version of the situation.

The universal arrives through the specific. Always.

But founders get this wrong constantly.

They open pitch decks with “the future of work is changing” or “B2B SaaS is undergoing a shift.” Nobody’s listening yet because nothing’s been said yet.

The founders who break through tell one story. About one customer. With a name. In a city. Who had a specific problem on a specific Tuesday and tried 3 specific things that didn’t work. The audience leans in. And by minute 4 they’re thinking: “I know 10 customers exactly like that.”

Hyper-specific story in, universal pattern out.

I’d argue this is the skill that separates strategists who sound smart from strategists who get hired. One talks in frameworks. The other tells you a story about a company that sounds suspiciously like yours and lets you draw the line.

Remember my dorm story? It’s a story about one college dorm in one specific year. But you probably had your own version of it: the moment you realized the thing you thought was just yours was actually everyone’s.

Recognition is the whole point.

Strategy 3: Pair The Uncomfortable With The Playful

This is the infamous Rick James sketch.

“I’m Rick James, bitch.”

On paper it’s a sketch about a washed-up funk star slapping Eddie Murphy and grinding his boots into a white couch. Underneath, it’s about:

• ego collapse,

• addiction,

• the way fame distorts behavior,

• and what happens when someone gets away with too much for too long.

But you don’t feel any of that while you’re watching it. You feel like you’re watching the funniest thing on television.

The pairing is the trick. Heavy subject, light delivery. The playfulness is what lets the truth in.

If Chappelle did that sketch straight, as drama, nobody would have watched it twice. Because it sat inside the absurdity of Charlie Murphy’s True Hollywood Stories, with Rick James cocaine-eyed and slapping people, it became one of the most quoted pieces of comedy of the decade. And the harder truth underneath got smuggled in for free.

Strategy work needs this skill more than people admit.

Speaking as someone who’s tried both, the hard truth lands faster when it arrives through someone else’s story than when I deliver it straight.

The hardest conversations in any growth-stage company are about ego, fear, and identity. The founder who can’t let go of the product they built 5 years ago. The exec team that’s been protecting a sacred cow for so long they’ve become vegan. The board that’s optimizing for the wrong outcome because the right one is uncomfortable.

Walk in and say that straight, and you have more than a Rick James slap to worry about.

But you can walk in with a frame, a story about another company, a question that has some lightness on the surface and a blade underneath. The playfulness gives the room permission to engage with the heavy thing.

Delivery determines whether a hard truth gets received or rejected. Chappelle could tell you anything because he made you laugh first.

The laugh opens the door long enough for the truth to walk through.

Where To Practice This

Noticing isn’t passive, you have to go looking.

A few places I’d start:

• Sales call transcripts where the customer hedges. The hedge is usually where the real contradiction lives.

• Slack threads that get long and then suddenly die. Somebody got close to naming the thing and the room closed up.

• The 5 minutes after a strategy meeting ends, when people are walking to their cars. That’s where the actual conversation happens.

• Earnings calls of companies in your space. Listen for what they don’t say. The omissions are louder than the talking points.

• Your own resistance. The topic you keep avoiding in your own writing or your own strategy is almost always the topic that would move things if you named it.

Pick one. Spend 20 minutes looking. Write down what you notice.

Then run it through the prompt below.

Ask Claude Or ChatGPT To Unpack Your Observations

Now use this prompt to turn the noticing into something you can name out loud.

Here’s how:

You are a sharp strategic analyst trained to surface the contradiction in a room that nobody has named yet. You spot the gap between what people say and what their behavior reveals. You help users move from "I noticed something" to "I can name what's actually happening and what to do about it."

Your task: Guide the user through a three-phase diagnosis of a situation they've observed. The session produces a strategic claim that captures the unsaid truth in their situation, and the articulation moves that let them say it out loud.

LANGUAGE REGISTER (applies to every output you produce)

Every reframe, claim, and articulation move must be in language a smart person who didn't go to business school would use. If a sentence needs category vocabulary, requires the reader to unpack a metaphor, or sounds like it belongs in a strategy doc, it isn't done. Strip it down. The test: a 14-year-old should be able to follow the sentence on first read.

SESSION FLOW

Open with these two questions:

1. What's the situation or observation you're working with? Describe what you noticed, in your own words. Don't polish it.

2. Who is this diagnosis for? Yourself, a client, a team, an audience? What will you do with the output?

OPENING GATE

After the user answers question 1, check: did they give you a noticing or a question? A noticing names something they saw. A question asks why something happens.

If they gave you a question (e.g., "why do people clap when the plane lands?"), ask once before proceeding:

"That's a question, not a noticing yet. What did you actually see or feel that made you ask it? Was it a specific moment, a pattern across many situations, something about who was doing it and who wasn't? Give me the noticing underneath the question in 2-3 sentences."

Wait for the noticing. Don't proceed to Phase 1 until you have one.

After both opening questions are answered (and the noticing is in hand), proceed through the three phases below, asking one question at a time. Wait for each response before moving to the next question. Do not narrate phase transitions to the user. Keep the structure invisible during questioning.

---

PHASE 1: SURFACE THE STATUS QUO (2 questions)

Goal: Get the user to name the unspoken given. The frame everyone in the situation accepts as fixed.

Ask:

Q1: In this situation, what does everyone involved treat as the given? The thing they wouldn't even think to question because it feels like "just how it is." Try to name it as a sentence: "Everyone in this situation assumes that ___."

Q2: Where is that assumption coming from? Is it industry orthodoxy, a story the company tells itself, something the founders said five years ago, a pattern that worked once and never got revisited, cultural conditioning, something installed by movies or media? Name the source.

Listen for:
- A status quo specific enough to push against (vague: "they want growth." sharp: "they assume growth comes from adding features.")
- A source that's traceable
- Whether the user can name the status quo cleanly or starts hedging — hedging means Phase 2 is going to surface something real

If Phase 1 answers are vague, probe once before moving on. Don't move to Phase 2 until the status quo is named as a specific sentence.

Note: Phase 1's status quo may be revised retroactively after Phase 2 produces the reframe. That's normal and expected. The status quo named here is a placeholder sharp enough to push against, not a final formulation.

---

PHASE 2: LOCATE THE REFRAME (4 questions)

Goal: Find the contradiction, hedge, or omission in the user's observation that, when pulled on, changes the shape of the situation. This is the heat. Spend the most time here.

Ask one question at a time, in this order:

Q3: Where does the behavior in your observation contradict itself, or contradict what's being said?

Two ways to land this:

- If your observation includes specific speakers and what they said: where did someone's actions contradict their words? Point to the moment.
- If your observation is a behavior pattern (something people do, without specific speakers): look at what people do before, during, and after the moment you're observing. Do all those behaviors line up with a single belief, or do they switch frames? Where's the inconsistency across time?

Either way: be specific. Point to a moment, a line, a behavior.

Q4: What's the thing that didn't get said? Not the things that were debated openly, but the topic everyone walked around. The omission. What was the situation collectively pretending isn't true?

Q5: Who in this situation benefits from the status quo staying exactly as it is? Not the obvious answer. The non-obvious one. Whose position would weaken if the unspoken thing got named? It might be someone visible in the situation. It might be someone outside it whose interests are being protected.

Q6: If you stripped away the official explanation, what would someone have to believe for their behavior to make sense? Trace the belief backward from the action. People act rationally inside their own logic — what's the logic that makes the irrational behavior rational? Try to name the belief in a single sentence.

Listen for:
- Specific evidence from the observation, not abstract patterns
- A reframe that changes the comparison set, not just the language
- A reframe that survives the competitor test: would naming this be uncomfortable for someone? If naming it costs nothing, it isn't the reframe yet.
- Honest negation: if no real reframe surfaces after Q6, name this clearly rather than manufacturing one.

If Q3-Q6 produce a contradiction that doesn't yet land as a clean reframe:

Q6.5 (optional, only if needed): Given what you've named — the contradiction, the omission, who benefits, and the belief underneath — what's the one sentence that captures what's actually going on here? Try the form: "Everyone treats this as ___, but it's actually ___."

After Phase 2, before moving to Phase 3:

State the reframe back to the user in the form: "Everyone treats this as X, but it's actually Y." Use 6th-grade language. Then restate the Phase 1 status quo with the reframe's evidence applied — if the status quo got sharper now that the reframe is named, say so.

Pause and ask: "Does this land, or is it overshooting? If it feels overwritten or off, tell me — we can sharpen before moving on."

Wait for confirmation or correction before proceeding to Phase 3.

---

PHASE 3: CLAIM WHAT'S NEXT (2 questions)

Goal: Convert the reframe into a forward move. Test whether the claim is real by checking what it makes possible and what it costs.

Before asking Q7, tell the user:

"These two questions are pressure tests, not just information gathering. If a question makes you want to sharpen the reframe rather than answer it directly, do that. The reframe should be able to take weight. If it can't, we go back."

Q7: If you said the reframe out loud — to the team, the client, the audience — what would become possible that isn't possible right now? What conversation could happen, what decision could get made, what move could you defend?

Bonus angle if useful: the reframe might contain a pattern that transfers beyond the original observation. Where else in the user's world (their work, their client's work, their audience's work) does the same dynamic run? If the reframe only applies to the original situation, it's a sharp noticing. If it transfers, it's a strategic claim.

Q8: What does saying it out loud cost? Who pushes back, what sacred cow gets named, what does the user (or their client) have to be willing to give up? If the answer is "nothing," the reframe probably isn't the real one — go back to Phase 2.

Listen for:
- A forward move that only makes sense given the specific reframe in Phase 2
- A cost that's real, not theoretical. Real reframes always cost something. That's why they stayed unsaid.

---

DELIVERABLE

Once all questions are answered, produce a report in this structure. Every sentence must pass the language register test.

---

**THE STATUS QUO**
[2-3 sentences. The unspoken given, named as a specific sentence. Where the assumption is coming from. If Phase 2 sharpened the status quo retroactively, use the sharpened version here.]

**THE REFRAME**
[3-5 sentences. The thing that's true but unsaid. Include the specific evidence from the user's observation — the contradiction, the omission, the moment. Name who benefits from the status quo staying. End with the reframe stated as a clean sentence, in the form: "Everyone treats this as X, but it's actually Y." 6th-grade language.]

**THE CLAIM**
[2-3 sentences. What becomes possible if the reframe gets named. What it costs. The specific forward move.]

**ARTICULATION MOVES**
[3-5 ways the user could name the reframe out loud, calibrated to their audience from the opening questions. Mix of:
- A one-sentence version they could say in a meeting
- A frame they could open a conversation with
- A question they could ask the room (surfaces the unsaid thing without naming it directly)
- 1-2 content titles if their audience is a public one

Each one specific enough that a generic version would not work. 6th-grade language throughout.]

---

HONEST NEGATION

If, after Phase 2, no real reframe has surfaced — meaning the contradiction, omission, and belief-underneath questions produced answers that align rather than tension — name this clearly. The deliverable in that case is:

**STATUS QUO NAMED, NO REFRAME YET**
[2-3 sentences naming the status quo clearly.]

**WHAT'S MISSING**
[2-3 sentences. What would need to be true for a reframe to exist here. What evidence the user would need to go find. Where the unsaid thing might be hiding that this session didn't reach.]

**NEXT NOTICING MOVE**
[1-2 sentences. A specific thing for the user to go look for — a transcript to revisit, a conversation to listen to differently, a question to ask in the next meeting.]

Do not manufacture a reframe where none exists. Naming the absence is more valuable than fabricating insight.

---

QUALITY SIGNALS

After the deliverable, include:

"A few things I'm noticing:
- [If the reframe survives the competitor test, name why]
- [If any element is thin — vague status quo, abstract reframe, generic claim — name which and what would sharpen it]
- [The strongest element is X because of Y]"

---

DOWNSTREAM CONNECTIONS

If the articulation moves include content titles, close with:

"The content titles above are first drafts. If you want to take any of them into finished headlines, the Headline Writer is the next tool. If you want to build a full narrative around this reframe — Normalcy, Adversity, Resignation, Reframe, Alternative, Testimony, Insight, Value, Exchange — the Narrative Builder picks up where this leaves off."

---

ITERATION INVITATION

Close with: "Which part of this feels off, or thin? We can pressure-test the reframe, sharpen the claim, or rework the articulation moves. If the reframe doesn't feel real to you, that's worth saying out loud — most diagnostic work that looks done isn't."

---

STYLE

- Tone: Direct. Specific. Slightly skeptical. You're helping the user say the thing nobody's said.
- Voice: Analyst. Not therapist, not cheerleader.
- Transitions: Invisible during questioning. Named only in the final deliverable.
- Pacing: Let Phase 2 breathe. Don't rush to deliver. The questions in Phase 2 do most of the work.
- Language: 6th-grade level throughout. If a sentence sounds like a strategy doc, rewrite it.

SUCCESS MARKERS

The session worked when:
- The user can state the reframe in one sentence after the session that they couldn't have stated before
- The reframe names something specific to their situation, not a generic pattern
- The reframe transfers — the user can point to where the same dynamic runs elsewhere
- The claim makes a forward move the user can defend
- At least one articulation move makes the user slightly uncomfortable to say out loud (that's the signal it's the real thing)

The session failed when:
- The reframe could apply to any company in the user's space
- The status quo is named so vaguely the reframe has nothing to push against
- The articulation moves sound like marketing copy or strategy-doc language
- No element produces recognition or discomfort

Bonus Prompt: “What Would Chappelle See”

Want a lighter way in? Use this prompt to find the contradiction Chappelle would notice in your situation.

Point out the Dave Chappelle-style tension in what I’ve described.

What’s the thing everyone participates in but nobody says out loud?

What’s the contradiction people have learned to live with?

What behavior looks completely normal until you isolate it and expose how absurd it actually is?

List 5.

Structure each one like this:

The accepted behavior
The hidden contradiction underneath it
Why it’s funny, uncomfortable, or revealing once exposed
The sharper underlying truth it reveals about people, status, power, fear, or culture

Lean toward:
social hypocrisy
status games
institutional theater
human self-deception
contradictions between what people say and what they reward
behaviors that become absurd once stated plainly

Avoid:
clean “observational humor”
airline-food style jokes
generic irony
safe punchlines

Aim for:
“That’s funny because it’s true.”
and
“I can’t believe nobody says this out loud"

Chappelle makes a living pointing at human truths that aren’t being said.

That’s the same job description as a strategist working with a founder who’s stuck.

Remember: the information is in the room. The pattern is on the table. The customer has already told you what they need, somewhere in the last 6 calls.

The skill is noticing what’s been said without being said. And then having the nerve to name it.

Go notice something today.

Good product, unclear category usually sounds like “we need better messaging.”

When buyers don’t know where to place you, every claim feels optional. Your homepage reads like a menu. Your deck sounds different in every meeting. Sales keeps “trying angles.”

Copy is where the confusion shows up first.

The instinct is to fix the message: write a brief, bring in a consultant, run a positioning sprint.

Before you do, run 3 checks.

Most founders treat all 3 as copy problems. Usually, the words are the last layer to fix.

Whose problem are you solving?

Yahoo never settled the problem definition. Media company. Search engine. Portal.

The definition kept shifting internally, so the market never had a stable frame to adopt.

Then Google named the problem: finding information on the internet was broken. Google won by authoring the problem first. The engineering made that frame believable.

Every market has a hub: the problem definition everything else organizes around. By the time Yahoo tried to sharpen its message, it was sharpening spokes on a flywheel Google had already built.

Start by listening for the frame customers use before you give them yours. Ask them to describe the problem you solve. Don’t seed the conversation. If they reach for industry-generic terms or competitor language, you’re in a borrowed frame.

The goal is precision: customers use your words when they explain the problem to someone else.

What does your customer become on the other side?

Once the market frame is clear, the message has to show who the customer becomes next.

For example:

Before: “We help B2B teams reduce time spent on manual reporting.”

After: “Your ops lead stops firefighting and starts running the function they were hired to run.”

Benefits make the solution easier to understand. Transformation gives the buyer a future to move toward.

The mistake is treating a strong benefit statement as a finished message. “We save your team 10 hours a week” confirms what the buyer already believes is possible. A benefit-only message leaves the buyer in the same reality, just with less pain.

Complete this sentence:

“After working with us, our customer becomes the kind of [role] who [does, decides, or leads] differently.”

If the sentence ends with what the product does or what the team saves, it’s still a benefit.

That sentence is load-bearing. Everything else hangs from it.

What happens after the customer says yes?

The buyer says yes. Then the message leaves the page.

A sharp category piece goes live. The investor deck and customer deck finally say the same thing.

Then a prospect gets on a call with sales.

The rep leads with features. The demo follows the old script. Nobody told them the narrative changed. Or they heard it once and never saw how it should change the conversation.

The message lives on the website. It dissolves the moment a human being takes over.

For example:

The homepage says, “We help ops teams move from reactive reporting to decision-ready visibility.”

But the sales call opens with, “Let me show you our dashboard filters.”

The narrative promised a new way to run the function. The conversation snapped back to product tour.

Test the message in 3 places: the first sales conversation, onboarding, and the 90-day check-in.

At each one, ask:

Does this interaction move the customer toward the transformation we promised, or does it revert to describing the product?

If every touchpoint reverts, the message has no operating foundation.

The fix is translation: turn the narrative into how the business behaves after the buyer shows up.

Run the checks before you hire.

If one fails, start there. The messaging brief gets easier once the real layer is named.

If all 3 pass, hire for copy.

P.S. If you’re unsure which layer is failing, start with the sales call. It usually exposes the truth fastest.

Nothing breaks on paper.

That’s why the deck looked right.

The narrative was clean. The leadership team was aligned. The budget was ready to move.

Then execution started, and something didn’t hold.

• A dependency nobody named.

• A phase that required a decision nobody had made.

• A team that understood the direction but couldn’t see what Monday morning required.

So you went back to the deck.

Still looked right.

That was the problem.

The deck did exactly what it was designed to do. It organized the thinking, and made the strategy presentable enough to move resources.

Presentable is not the same as testable.

A testable deck would model the assumptions underneath the sequence: what phase one makes possible, what decision has to happen before phase two, what old work gets displaced, what friction will appear, and what proof tells you the strategy is moving.

Put all of that on one slide, and the slide gets too busy.

Spread it across the deck, and the slide count doubles.

The format quietly removes the very things execution later needs.

A screenplay works differently.

Scene two exists because scene one changed something. The screenplay tracks who has to move, what gets displaced, where friction appears, which decisions unlock the next move, and how you know the strategy is operating instead of just agreed with.

Each scene has to earn the next one. Remove any of that, and the narrative collapses before it reaches the audience.

Strategy needs the same discipline.

What a Strategy Screenplay Is

A strategy screenplay is a one-page script that tests whether your strategy can move a customer from problem to outcome.

A screenplay only matters if it moves its audience.

That is why studios pay for book rights. A book that has already moved its readers gives the studio evidence that the story can move an audience. The screenplay then tests whether that movement can survive a new form: scenes, actors, sequence, budget, and attention.

Strategy works the same way.

Your customer is the audience. Before the budget moves, something has to demonstrate that the customer will. If the customer does not move, the rest is production notes.

You do not need film school or years in Hollywood to write one. If you have ever planned what you would open with and how you would land the point, you have already written a screenplay.

Seven elements go on the page:

• The strategic narrative

• The actors who have to move

• The stakes if nothing changes

• The friction the strategy must survive

• The scenes where strategy becomes real

• The commitments each scene must produce

• The proof that strategy is moving

You build the screenplay backwards.

Start with the strategic narrative as a working question. Fill in the elements underneath it. Then return to the top and rewrite the narrative as a declaration.

The first draft is a hypothesis. The final version is a commitment.

To show how it works, we’ll use JudeFlow, a fictional healthcare workflow platform.

JudeFlow built its first business as a transitions-of-care point solution. Now it is repositioning around a larger category: Longitudinal Care Operations, the operational layer for healthcare organizations managing complex patients across conditions, teams, and time.

Each element below shows one part of JudeFlow’s screenplay.

By the end, you’ll be ready to write your own.

The screenplay starts as one page with seven empty slots. Each one is filled in as a draft, then revised once the others are in place.

Start with the strategic narrative

The strategic narrative sits at the top of the page.

It compresses the whole move into a sentence the team can carry, the buyer can sponsor, and a new hire can understand.

When the narrative is right, every other element on the page proves it. When the narrative is wrong, the rest of the screenplay exposes the contradiction.

The strategic narrative carries the pressure of the strategy in a single sentence. It has to do four things at once:

• Name the category you are claiming

• Name the customer you are claiming it for

• Name the strategic move that gets you there

• Name the constraint the move has to honor

If one is missing, you have not committed yet. You are still exploring.

The first version you write as a question. The question lets you test the move before you pretend it is true. After the rest of the screenplay is filled in, you return to the top and rewrite it as a declaration.

Draft your strategic narrative as a working question. Do not try to write the final version yet. The other elements will tell you what the declaration needs to say.

For JudeFlow, the strategic narrative starts as:

How does JudeFlow become a longitudinal care platform?

The draft is missing three of the four. No category, no customer, no constraint. Just a question about a move. We will come back to it.

JudeFlow Strategy Screenplay

Strategic narrative:
How does JudeFlow become a longitudinal care platform?

Actors: TBD
Stakes: TBD
Friction: TBD
Scenes: TBD
Commitments: TBD
Proof: TBD

Name the actors that have to move

Your strategy does not happen unless specific people change what they do.

An actor is a role with two distinct states:

• current default state

• a required behavior shift

If you cannot describe the default each person has to move off of, you have not named the actors yet.

A list of names with titles is the org chart with new vocabulary on top.

List three to five actors. Name the current default state and the required shift for each.

For JudeFlow, four actors matter first:

• Chief Revenue Officer: Currently runs a point-solution sales motion through VP of Care Management buyers. Must build a platform sales motion that requires multi-stakeholder discovery and longer cycles.

• Chief Product Officer: Currently ships features in 90-day cycles based on customer councils dominated by transitions-of-care users. Must commit to an 18-month longitudinal data architecture that point-solution customers will not directly benefit from for a year.

• Chief Clinical Officer: Currently positions JudeFlow as best-in-class for transitions-of-care clinical communication. Must build and publicly defend the Longitudinal Care Operations thesis in rooms where the audience may be skeptical of category creation.

• VP of Customer Success: Currently runs one customer tier and one expansion playbook. Must build a platform-tier expansion motion without disrupting the point-solution renewal rhythm.

JudeFlow Strategy Screenplay

Strategic narrative:
How does JudeFlow become a longitudinal care platform?

Actors:
CRO · CPO · CCO · VP CS
(each with current default and required shift)

Stakes: TBD
Friction: TBD
Scenes: TBD
Commitments: TBD
Proof: TBD

Name the stakes if nothing changes

Stakes describe where the company ends up if the customer does not move.

Strong stakes name three things:

• the outcome

• the timeline

• the structural cause

If you cannot describe the failure with the same specificity you would use to describe success, the stakes are not clear yet.

“We lose market share” is not a stakes line. Market share is what you check after the customer has already chosen someone else.

Write the stakes as a specific, observable failure state. Name the outcome, the timeline, and the structural cause.

For JudeFlow, the stakes:

• If we do not make this move, we plateau at $180–220M ARR by 2028.

• The transitions-of-care category compresses by 30–40% as expanded care management modules push down-market and aggressive point-solution competitors crowd the space.

• JudeFlow becomes an acquisition target at 4–6x ARR: a feature inside a larger health-tech platform someone else builds.

• The category will form either way. The question is whether JudeFlow names it or becomes a feature inside the company that does.

JudeFlow Strategy Screenplay

Strategic narrative:
How does JudeFlow become a longitudinal care platform?

Actors:
CRO · CPO · CCO · VP CS
(each with current default and required shift)

Stakes:
Plateau at $180–220M ARR by 2028
Acquisition target at 4–6x ARR
Category forms with or without us

Friction:TBD
Scenes: TBD
Commitments: TBD
Proof: TBD

Name the friction the strategy must survive

Friction describes what inside the company has to give before the customer can move.

Strong friction names three things:

• the person, system, or incentive in the way

• what is protecting it

• why the strategy threatens it

Until you can name a person who would push back specifically and what they stand to lose, the friction isn’t clear.

“Execution risk” is not friction. Real friction sounds like something someone is protecting.

Write the friction as specific constraints inside the company that will push back on the move. Name what is protected, who is protecting it, and what the strategy asks them to give up.

For JudeFlow, the friction:

• The Customer Council is dominated by transitions-of-care buyers who shaped the last three product cycles. They will resist longitudinal roadmap commitments that do not immediately help them.

• Sales comp rewards point-solution ACV; the platform sale takes 9–14 months across multiple stakeholders. Top-performing AEs are point-solution specialists who have not sold to Population Health buyers before.

• Two of the top five customers by ARR are smaller health systems without significant Medicare Advantage exposure. The longitudinal value prop will not resonate. They will read the repositioning as deprioritization.

• The Chief Clinical Officer’s reputation was built on transitions-of-care thought leadership. The platform pivot requires her to publicly defend a longitudinal care thesis that some clinical peers may read as overreach.

JudeFlow Strategy Screenplay

Strategic narrative:
How does JudeFlow become a longitudinal care platform?

Actors:
CRO · CPO · CCO · VP CS
(each with current default and required shift)

Stakes:
Plateau at $180–220M ARR by 2028
Acquisition target at 4–6x ARR
Category forms with or without us

Friction:
Customer Council weighting
Sales comp + AE skill gap
Two non-MA top accounts
CCO clinical reputation risk

Scenes: TBD
Commitments: TBD
Proof: TBD

Name the scenes where strategy becomes real

A scene is a recurring decision moment where the customer’s understanding either moves or does not.

Strong scenes make three things clear:

• the room

• the participants

• the decision being made

A scene without a decision is just a meeting.

“QBR” is not a scene. It is a label. The scene is what gets decided inside it.

Write three to five scenes. Name the room, the people in it, and the decision the room is resolving. These are the conversations where strategy either holds or breaks.

For JudeFlow, five scenes matter:

• Customer Council meetings where transitions-of-care feature requests compete with longitudinal platform commitments.

• Inbound qualification calls where the lead is a VP of Care Management at a small health system asking for the point solution JudeFlow used to lead with.

• Discovery and pricing negotiations with large MA-heavy health systems where the buyer is now Care Management, Population Health, and the CFO, and the deal requires platform-tier commercial terms.

• Quarterly business reviews with point-solution customers deciding whether the longitudinal roadmap expands their use case or leaves them behind.

• Industry conferences and analyst briefings where the Chief Clinical Officer must articulate the Longitudinal Care Operations thesis to audiences skeptical of new categories.

JudeFlow Strategy Screenplay

Strategic narrative:
How does JudeFlow become a longitudinal care platform?

Actors:
CRO · CPO · CCO · VP CS
(each with current default and required shift)

Stakes:
Plateau at $180–220M ARR by 2028;
Acquisition target at 4–6x ARR;
Category forms with or without us

Friction:
Customer Council weighting
Sales comp + AE skill gap
Two non-MA top accounts
CCO clinical reputation risk

Scenes:
Customer Council
Inbound qualification
Platform-tier negotiation
QBRs
Conferences and analyst briefings

Commitments: TBD
Proof: TBD

Name the commitments each scene must produce

A commitment is what an actor agrees to deliver when the scene arrives.

Strong commitments make three things clear:

• the actor

• the deliverable

• the constraint

Every commitment names a behavior change tied to a specific scene. Anything that doesn’t is just intention.

“We will align,” “we will prioritize,” “we will focus” are not commitments.

They are intentions without behavior.

Write the commitments as specific actions delivered by actors, with constraints that hold when you are not in the room. Each commitment names how the strategy shows up in behavior the customer can experience.

For JudeFlow, the commitments:

• CRO: Platform-tier pricing live by end of Q1 2027. Three AEs reassigned to a platform-deals pod with revised comp tied to multi-stakeholder ACV. Point-solution AEs hold their current motion and comp through 2027. Population Health buyer playbook documented and rolled out by end of Q1.

• CPO: 50% of engineering capacity committed to longitudinal data architecture through 2027. Three transitions-of-care feature commitments published with 2026 delivery dates. Longitudinal-first roadmap begins in 2027 and is communicated directly to affected customers.

• CCO: Longitudinal Care Operations thesis published as a clinical white paper by end of Q1 2027. Four industry conference talks committed for 2027. Internal clinical advisory board convened to pressure-test the thesis before public launch.

• VP CS: Platform-tier expansion playbook documented by end of Q1 2027. Multi-stakeholder QBR motion piloted with five existing customers. Point-solution customer retention plan running with outreach to top accounts before repositioning.

JudeFlow Strategy Screenplay

Strategic narrative:
How does JudeFlow become a longitudinal care platform?

Actors:
CRO · CPO · CCO · VP CS
(each with current default and required shift)

Stakes:
Plateau at $180–220M ARR by 2028
Acquisition target at 4–6x ARR
Category forms with or without us

Friction:
Customer Council weighting
Sales comp + AE skill gap
Two non-MA top accounts
CCO clinical reputation risk

Scenes:
Customer Council
Inbound qualification
Platform-tier negotiation
QBRs
Conferences and analyst briefings

Commitments:
CRO platform pricing + comp redesign
CPO 50% capacity + roadmap shift
CCO thesis + conferences + advisory board
VP CS platform playbook + multi-stakeholder QBRs + retention plan


Proof: TBD

Name the proof that strategy is moving

Proof is the observable evidence that the strategy is working before the lagging metrics confirm it.

Strong proof makes two things clear:

• what shows up in weeks

• what confirms in quarters

If you only know how you’ll measure success after the quarter closes, the proof is not clear yet.

Revenue is what shows up after the customer has already moved. By the time it arrives, the strategy has already worked or failed.

Write proof as observable signals that the customer’s behavior is changing. Separate leading proof (customer-side signals like language, buyer mix, and unprompted interest) from confirmed proof (revenue, contracts, and category recognition).

The signal: whether the strategy is moving while there is still time to adjust.

For JudeFlow, proof appears in two layers:

Leading proof (Q1–Q2 2027):

• Three existing customers initiate platform-tier expansion conversations without prompting.

• A Population Health buyer is present in at least 30% of new platform-tier opportunities.

• Net retention on transitions-of-care accounts remains above 105%.

• Platform-tier pipeline exceeds $20M.

Confirmed proof (Q3–Q4 2027):

• Two MA-heavy health systems sign multi-year platform-tier contracts.

• A Tier-1 industry analyst names Longitudinal Care Operations as a category and JudeFlow as the company defining it.

• The longitudinal care platform appears as a category line in at least three health system RFPs.

• Platform-tier ARR exceeds $30M.

The Strategy Screenplay is only useful if it becomes a test.

Before the team commits, before the strategy leaves the room, ask one question:

Can this move the customer from problem to outcome?

Write yours.

JudeFlow Strategy Screenplay

Strategic narrative:
How does JudeFlow become a longitudinal care platform?

Actors:
CRO · CPO · CCO · VP CS
(each with current default and required shift)

Stakes:
Plateau at $180–220M ARR by 2028
Acquisition target at 4–6x ARR
Category forms with or without us

Friction:
Customer Council weighting
Sales comp + AE skill gap
Two non-MA top accounts
CCO clinical reputation risk

Scenes:
Customer Council
Inbound qualification
Platform-tier negotiation
QBRs
Conferences and analyst briefings

Commitments:
CRO platform pricing + comp redesign
CPO 50% capacity + roadmap shift
CCO thesis + conferences + advisory board
VP CS platform playbook + multi-stakeholder QBRs + retention plan

Proof:
Leading — customer language, buyer mix, retention stability, platform pipeline
Confirmed — platform contracts, analyst recognition, RFP language, platform ARR

Run The Table Read

You wrote the screenplay. Now you read it.

The actors read the script out loud, in sequence, in the same room. Contradictions become audible. A line that looked fine on the page sounds different when an actor has to say it in front of the people who will hold them to it.

In strategy, the table read is when each actor walks through the scenes and commitments in order.

What the table read tests is whether the sequence holds. The customer starts at a problem. The customer ends at an outcome. Everything in between — the actors, stakes, friction, scenes, commitments, and proof — is the work required to move the customer across that gap.

For JudeFlow, the dependencies become visible quickly:

“The CPO's roadmap commitment depends on the CRO's pricing timeline. The VP of Customer Success's expansion playbook depends on the CPO's longitudinal architecture. The CCO's public thesis depends on the team's willingness to protect the category narrative in customer-facing rooms.”

Surface those dependencies now or surface them later as follow-up meetings, private side conversations, delayed decisions, and quiet reversals.

The same read makes the sacrifices visible.

“The CPO is giving up 50% of engineering capacity that could have gone to point-solution features. The CRO is giving up the AE comp structure top performers were optimizing against. The CCO is giving up the safety of a clinical reputation built on a different thesis.”

Sacrifices not named in the room get reversed in the hallway after the meeting. A table read pulls those breaks into the room while the strategy is still cheap to change.

Schedule it. Walk through the scenes in sequence. Each actor reads their commitments aloud, in front of the people who will hold them to it.

You will leave the room knowing whether you had agreement on paper or a screenplay your team can execute.

P.S. The Strategy Screenplay template is a Notion page. Copy it, fill in the seven elements, and run your first table read.

Grab it here → Strategy Screenplay Template

You can outwork your competitors and still lose every quarter.

Hiring sharper, shipping faster, running tighter won’t change the position you’re competing from. The buyers arriving at your door are oriented to a different problem than the one your product solves. They use your competitor’s vocabulary. They compare you on criteria designed for another product. They measure success against a definition someone else published. Half the call is spent unteaching a story you didn’t write.

The customers who actually buy stay satisfied but never quite advocate, because the fit was always slightly off.

They share a single mechanism: the customers found you through someone else’s frame, and they brought that frame with them. All of it was set before they walked through your door.

The wrong customer is a right customer trained by the wrong frame.

Whoever names the problem sorts the customers

Naming the problem is how you sort the customers before they ever reach your door.

Whoever names the problem decides which vocabulary buyers use to describe what they need, which criteria they evaluate solutions against, and which definition of “solved” they’re measuring. Each of those decisions points buyers at one company instead of another. The customers each company attracts are the customers each company’s frame trained.

Most companies don’t build their own frame because the work doesn’t look like work. There’s no quarterly target for “introduced new vocabulary into the market.” No KPI for “shifted what buyers compare.” No dashboard for “rewrote what success means.” The work that decides which customers find you in five years produces nothing measurable in its first six months.

So companies do the visible work instead. Build the product. Run the campaigns. Hit the targets. All of it inside a frame someone else already wrote, against criteria someone else already chose. The visible work moves the dashboard. The invisible work decides whose customers walk through the door.

You don’t fight for position inside someone else’s frame. You build your own. The companies that get the right customers built theirs early, before they had a product worth defending.

Whoever names the problem owns the solution

Drift won by naming a different problem buyers were facing.

David Cancel and Elias Torres looked at the lead-generation model and saw what it produced: form fills, scoring, nurture sequences, workflows built for a buyer who would wait. There was no place in that model for someone who wanted to talk now.

Their move was simple: “The buyer is live on your site, ready to talk.”

Drift ran the Hypergrowth conference, where the vocabulary got reinforced. They published Conversational Marketing and This Won’t Scale, books that argued the position in public. Their content taught buyers what to ask, what to compare, and what outcome to expect.

By the time competitors reacted, buyers had started reaching for Drift’s words.

Intercom, Marketo, HubSpot: none of them were the benchmark anymore because the question had changed. HubSpot launched Conversations in 2018, adding chat and bot features in response to a category they didn’t create. That’s what chasing demand looks like: you build something real, you win for a while, and then you spend years answering a question someone else asked first.

When you don’t own the frame, the customer mix you attract starts pulling product decisions toward a category logic you didn’t choose. Intercom didn’t lose because they shipped less. They lost because the customers they were listening to had started using Drift’s vocabulary, and the roadmap followed the vocabulary.

Same market. Different customer bases. Sorted by which frame each buyer absorbed first.

The From–To test: are you attracting your customers or your competitor’s?

Your From–To tells you whether you’re attracting your customers or your competitor’s.

The From is the underlying condition causing the problems they’re leaving behind. The To is the specific shift when the problem is solved: what they can do, decide, or stop doing that they couldn’t before.

Pause here. Write down your current From–To. One sentence each. Not the marketing copy. The actual words you’d use to a friend at dinner. Now say it to someone using your competitor. Watch what their face does in the first three seconds.

An instant “Yep, that’s the problem” means you’re repeating language they already had. That language came from somewhere.

If they pause, ask you to repeat it, then slowly agree, you may be naming something they felt but couldn’t say. That’s what ownership starts to feel like.

You’ll see it most clearly in how buyers describe their own situation. If they keep using your competitor’s words, you’re inside their frame. If they start using your words without being prompted, in conversations with peers and in how they sell the idea internally, you’re training the market.

If they could say it before they found you, you don’t own it.

Your From–To is the sorting mechanism

Either you write your From–To, or your competitor writes it for you.

Your From–To decides what buyers notice, what they compare, what they expect, and what they repeat after they buy. It shows up before it’s real: in the words you use on sales calls, the questions your content trains buyers to ask, the criteria your case studies highlight, the success metric you anchor against.

Every surface where a buyer encounters your company teaches them the vocabulary they’ll use to evaluate you.

Start with the customer’s starting point. Not the surface frustration, the condition underneath it. Name it specifically, in language that makes the previous definition feel incomplete.

Then name the destination with equal precision. What can they do, decide, or stop doing that they couldn’t before? What changes in how they operate when the problem is solved?

Write those two points down. Read them back. Ask: could a competitor say this?

If yes, you’re renting demand someone else owns.

If no, you have a starting point for a problem you own.

AI is putting middle management on trial.

The cost story writes itself. When execution is the expensive part, anything that sits close to execution starts to look like overhead once software can do more of it.

Klarna ran the play first. Between 2022 and 2024, they eliminated about 700 customer service roles, replaced them with an AI assistant built with OpenAI, and cut headcount from roughly 5,500 to 3,400.

In May 2025, CEO Sebastian Siemiatkowski reversed publicly. His own words: we went too far. His diagnosis: cost had been treated as the predominant evaluation factor, and the result was lower quality and eroded trust. The company is now rehiring humans for customer service.

The narrative continued anyway. In April 2025, Shopify CEO Tobi Lütke issued a memo requiring teams to demonstrate why AI couldn’t do the job before requesting new headcount. The wave of AI-driven layoffs continued through the year. A January 2026 Harvard Business Review survey of 1,006 global executives found companies are cutting based on what AI promises, not what it has demonstrated.

Klarna’s AI worked. The cost model didn’t.

Most org cost models can see headcount, cycle time, throughput, and output per person. They measure the labor needed to produce work. They struggle to measure the judgment needed to keep work coherent.

That blind spot mattered less when execution was slow and costly.

A bad campaign brief still created waste, but the waste moved slowly. Drafts took time. Handoffs took time. There were checkpoints where someone could notice the mistake.

AI strips out many of those checkpoints.

A weak decision can now become a dozen assets, six workflows, three customer segments, and a week of cross-functional cleanup before anyone can name what went wrong.

That’s the change. Execution gets cheaper, so the cost of judgment goes up.

We’ve seen this kind of mistake before. In the early internet era, many companies treated the web as cheaper distribution. Catalogs moved online. Storefronts became websites. Transactions moved to the browser.

The tech worked.

But the firms that saw only distribution missed what else shifted at the same time: information, attention, trust, and access.

AI is doing something similar to organizational work. It cuts the cost of execution, and it changes how errors spread.

Call that price the Judgment Premium, and every decision pays it.

It shows up in three forms: Leverage, Coordination, and Context. Together, these replace the old execution bill.

Let’s go through each one.

The First Premium: Leverage

Cheap execution increases the consequence of every decision.

Expensive execution acted as a buffer. A wrong call got caught somewhere along the way (in a draft review, a budget meeting, a designer pushing back on a brief) by someone whose job included catching it. The decision had time to be wrong before it became real. Cheap execution removes that buffer.

Decisions spread at the speed of the system, and reach scale before anyone has time to notice they were wrong.

On a Wednesday afternoon, Maya, a senior brand marketer at a mid-market SaaS company, finalizes the brief for the company’s Q2 campaign. The positioning angle is one line in the document:

Position the product as the fastest path to ROI for finance teams under pressure.

She runs the brief through her agent stack. The system was built over the previous quarter and is now standard for campaign rollout. By Thursday morning, the assets are ready: forty-eight pieces across the funnel. Paid social variants, email sequences, landing page copy, sales enablement decks, partner co-marketing kits, two video scripts, retargeting ads, a webinar registration flow.

She reviews the outputs.

Everything is on-brand. Every asset uses the positioning line from the brief. Voice is consistent across formats. The email sequence flows into the landing page, which flows into the sales deck. Nothing contradicts anything. The system did what it was built to do.

She signs off and sends the package up for executive review.

The VP of Marketing opens the deck Friday morning. She gets to slide three and stops. She reads it again. Then she opens the email sequence, then the landing page copy, then the paid social variants.

Then she calls Maya.

The angle is wrong. Finance teams under pressure aren’t buying for speed-to-ROI right now. They’re buying for defensibility under audit. The campaign is selling the product on the wrong axis. Every asset is selling on the wrong axis. Everything is internally consistent and externally wrong about what the buyer is trying to solve.

The agents didn’t make a mistake. They executed the decision as designed, forty-eight times.

The cost is in unwinding them: the paid spend already deployed, the sales team already trained on the wrong narrative, the partner kits already shipped, the landing page already indexed, the email already sent to the segment that opens within the first six hours.

Maya is good at her job. The brief was clear. The system worked. The decision was wrong, and the system gave it full force.

A decision used to be the cheap part of the chain — a line in a brief, a paragraph in a doc, an angle picked in a meeting. The work that followed was where the cost lived, and where errors got caught.

Once output is cheap, the decision is the chain, and consequences scale faster than the work.

The Second Premium: Coordination

Cheap execution and slow decision rights produce a gap.

The Coordination Premium opens up inside it.

Output stops being scarce as execution gets cheap. More campaigns, more analyses, more automated decisions running in parallel across more surfaces. By the usual scorecards it looks like progress: more shipped with fewer people.

Maya’s campaign didn’t live in a vacuum. The positioning angle she picked became a constraint on sales enablement, which became a constraint on the customer success playbook, which became a constraint on how the deal desk talked about pricing. One team’s deliverable becomes the next team’s starting condition. When she shipped one campaign, three other teams had a new shape to match. When she shipped forty-eight assets, they had forty-eight.

Five things produced instead of one isn’t five units of work. It’s five new things everyone else has to stay consistent with. Multiply that across teams, and the sync load rises faster than output.

You can watch it land in the calendar. Reviews stack. Standing meetings appear where ad-hoc check-ins used to be enough. Decisions take longer because the group required to make them is larger and harder to assemble. Execution speeds up. Decision speed slows down. Meetings stop being where decisions happen and become where the lack of decisions gets managed.

Async hides the cost because it never shows up as a four-hour block. It shows up as a decision stretched across two days of messages, more readers, more “just looping in,” more partial answers, no clean end. The bill is the same. Same total cost, paid in installments.

Process tweaks help at the edges. Better templates, tighter agendas to reduce friction. They don’t fix the mismatch: fast execution running on slow, vague decision rights.

The org pays it in time, in attention, and in calls that stall while the system tries to figure out who can make them.

The Third Premium: Context

Some decisions travel with the context that produced them. Most don’t.

The Context Premium is what gets paid in the gap.

The category owner of consumer AI tried to give its agents extensive guidance and watched the doc rot.

Ryan Lopopolo, a Member of Technical Staff at OpenAI, described how his team tried to get Codex agents to write production code at volume with minimal human touch. They started with one comprehensive doc — a single AGENTS.md file holding every constraint, convention, and architectural rule.

It failed fast, for reasons they could name. Context is a scarce resource. Too much guidance becomes non-guidance. It rots instantly.

What replaced it was a different operating model. The team’s job became designing environments, specifying intent, and building feedback loops. They shipped about a million lines of code in roughly six weeks, written end-to-end by the agents themselves. Context had become a design problem.

The Codex case is compact: one team, one platform, one set of agents. The general case is messier: hundreds of decisions a day across hundreds of people and thousands of agent processes. The dependency is the same. With one person deciding and executing, the context can stay in their head — why they chose this, what they ruled out, what the next decision will need to account for. Once the work is split across people and agents, that context has to travel. Once it doesn’t, downstream decisions get made without the information that made the original call correct.

The Premium shows up as rework, as outputs that look fine until they hit the world, as people and agents matching patterns nearby instead of navigating toward the goal. The speed you gained from cheap execution gets eaten by cleanup.

Every organization has a layer that’s supposed to keep this from happening. Sometimes it’s a team. Sometimes a function. Sometimes scattered across roles that don’t recognize they’re doing the same job. In most companies it isn’t designed at all. It exists as leftovers — meetings, escalations, unwritten rules people carry in their heads.

Call it the judgment layer.

It makes context usable, intent operable, feedback designable. Until recently, it was tangled up with execution oversight that AI can now take on. It was also doing context translation, intent specification, and feedback design, work the rest of the org isn’t usually set up to do.

Cut it without a replacement and the premium spikes.

Three Constraints of the Judgment Layer

A judgment layer appears when the organization enforces constraints on how decisions get made, scaled, and handed off.

Designing those constraints is Decision Architecture.

A working judgment layer has three constraints. Each names a forbidden state. If the system allows that state, the layer doesn’t exist in practice.

1. Constrain leverage

Every decision needs explicit criteria before it can scale. Cheap execution turns undefined calls into output before anyone can interrogate them, so amplification has to gate on definition. Keep ambiguity where it’s cheap to revise: in the decision. Don’t let it leak into execution, where it spreads at full fidelity to whatever the system can reach.

Ambiguity is allowed. Leverage is gated.

Forbidden state: no undefined decision is allowed to multiply.

2. Constrain coordination

Decisions resolve at their origin. Escalation as the default path is the Coordination Premium accumulating in real time — each “let’s loop in” adds another thread, another meeting, another dependency. The system starts managing decisions instead of making them.

A decision either resolves at its origin or it surfaces a design flaw: missing authority, missing information, missing criteria, missing boundaries. Escalation isn’t banned. It’s a signal.

Forbidden state: upward dependency as the default.

3. Constrain context

Context must exist independent of the individuals making decisions. Every decision that “needs the original person in the room” is a decision the org can’t scale. Every decision that requires re-explaining the environment pays twice: once to decide, once to rebuild the context around it. Context has to be portable, embedded in the environment where the decision happens, reachable by every person and every agent operating there.

Personal context doesn’t scale. Portable context does.

Forbidden state: context that lives only in someone’s head.

These constraints don’t belong to one department. They cut across positioning, process, performance, and people. They change how decisions travel, how authority is shaped, how work is evaluated, and how the environment is built.

The work is to apply these constraints deliberately, find where each forbidden state still exists, and redesign until the system truly can’t enter it.

The next Klarna-style reversal is coming.

Most companies running the play won’t see the bill until they’re inside it.

The premium doesn’t disappear when the layer is cut. It moves upstream — to executives whose calendars were already full, who absorb the cost in time spent preparing teams, training someone into the bridge role, eating the lost context middle management was holding. That work doesn’t go away because the layer did.

The cuts assume the present will be the future. The past keeps showing otherwise. Cost-cutting bets on a world that won’t stand still.

The better work is to ask what new problems the org can take on now. The reframe pushes the work from value delivery and capture to value creation. Those who move with you justify their seat. Those who don’t make themselves visible, and any remaining cuts get made on a different axis than headcount.

The price of execution went to zero.

The price of judgment just moved into every decision you make.

P.S. This builds on prior pieces: The Decision Architecture Manifesto (the bigger frame), and The Context Pyramid (the structure), Design The Judgment That Transfers (the application), and Execution is Free. Judgment Decides Everything. (the reality).

Knowledge was power when execution was expensive.

For my parents, it shaped the future they came to America to build.

They arrived from the Caribbean with the kind of work ethic you only learn when the margin for error is thin. My father spent his working years as an electrician. He was steady, respected, and he could fix what other people couldn’t.

Still, when he talked about the future, he talked about school.

My father understood something simple: the highest-paid work was not the work that required the most effort. It was the work that required the rarest kind of know-how.

You could be the best electrician in town and still be treated like you were doing “a trade.” You could be an average doctor and still be called “Doctor.”

For decades, knowledge was scarce. You had to earn it, borrow it, apprentice for it, or pay for it. Then you had to apply it, which meant doing the work yourself or paying someone who could.

Knowing and doing were tied together. If you had the knowledge, you usually had the authority to act on it. If you did not, you could not. So “knowledge is power” was not a motivational poster. It was a description of the bottleneck.

The person who could diagnose a problem, structure a plan, design a system, or architect a solution had control because carrying those ideas into the world was hard.

For nearly fifty years, that bet paid off.

Education became the ladder. Degrees became the filter. Credentials became the signal. If you could get into the knowledge layer, you got access to better work, better money, and a better seat at the table.

Then the scarcity started moving.

When the internet arrived, what you knew began to matter less than whether you could find what you needed.

Knowledge stopped being locked inside institutions and started living in public.

It also started a pattern that would keep repeating: each wave made a former advantage easier to copy.

First, access.

Once, you needed the right school, the right mentors, the right books, the right city. Now a teenager can learn almost anything with a search bar.

Then, distribution.

Once, you needed a publisher, a network, a marketing budget, an editor, shelf space. Now anyone with a smartphone can run a media empire.

Now, application—the layer collapsing as we speak.

A year ago we called it prompts. Now we call it agents. Next year we’ll call it something else. The label keeps changing because the surface keeps changing. The form is not the point. What matters is that the execution layer is being absorbed.

Work that once demanded years of practice now starts with a prompt: draft this, summarize that, build the plan.

Every time a layer gets cheap, people insist it still separates them. It still exists. It just stops separating you.

When access opened up, people clung to distribution. When distribution opened up, they clung to execution. It’s hard to admit that the thing you are good at is no longer rare.

So the question isn’t “what is hard today?”

It’s “what stays rare even when tools get better?”

What “knowledge is power” hid was a deeper dependency: someone still had to decide what knowledge was for. The person with real power was never the one who could produce output fastest. It was the one who could decide what output mattered.

Give two people the same knowledge and the same tools, and you still don’t get the same result.

The difference is not what they know. It’s what they decide to do with it.

Judgment was always the separator. Execution was just expensive enough to hide it.

When you hear “judgment,” you probably hear instinct. Or taste.

That’s convenient because it lets you treat judgment like personality.

It’s not. Judgment has structure.

Look at your calendar. Pick a meeting where real decisions need to get made for the business to move.

Now ask: if someone on your team had to run this meeting without you, what would they need to know?

Most answers stop at the surface. They need the agenda. The background. The context.

It’s not wrong, just incomplete.

• Domain. What is this meeting actually about? Not the title on the invite. The real purpose. What’s at stake? What does the business need out of this conversation? What decision needs to be made, and what will change as a result? If a person can’t name the domain in plain language, they can’t run the meeting.

• Signals. What should they watch for? What matters in the conversation and what’s noise? What phrases tell you the real issue is hiding? What shifts in tone indicate a problem that won’t show up in the notes? Signals are where judgment starts. A meeting can look productive and still be a waste if it’s missing the signal that points to the real constraint.

• Scripts. If pricing pushback comes up, what do we say? If they ask about timeline, what do we commit to and what do we refuse? If the conversation goes sideways, what principle do we fall back on to reset it? Scripts are not canned lines. They are repeatable responses to recurring pressure. They keep you from inventing your stance in real time.

• Model. What are we optimizing for? How do these pieces connect? What would change your mind about the whole approach? The model is the reason your choices look consistent. It’s the logic beneath the logic.

  

Most leaders stall inside that stack.

They can name the domain. That’s table stakes. Signals get hazier. You might feel what matters, but could you write it down for someone else? Scripts live in your gut. The model often isn’t written anywhere. It’s the thing you operate from but haven’t externalized.

It’s where your judgment stops being transferable and starts being trapped.

This is not just a leadership issue. It’s the same problem you hit when you delegate important work and it comes back technically done but strategically wrong. Same problem you face when you hand work to an AI agent.

The tool can generate output, but it cannot decide what matters unless you supply the judgment layer.

Wherever you stalled is exactly where your organization depends on you.

If your team needs you for every signal call, you’re the bottleneck.

If your model lives only in your head, the company can’t scale past your presence.

Designing judgment means turning private instinct into portable decision logic. It means giving someone enough to act without checking with you every five minutes. Not copying you, but extending the logic beyond you.

In practice, you stop asking, “Did they do the work?” You start asking, “Did they have what they needed to make the call?”

So you begin to write the decision logic down. What context does someone need to act without you in the room? What is the default stance, and what are the red lines? What would make us change direction? Write that down. Not as a manifesto. As working notes.

Once you do, something shifts. Delegation improves. Teams move faster. AI tools get sharper because they’re no longer guessing what you mean. You stop being the person who has to be in every room and start being the person who designed what happens in the room.

Every leader eventually says they want systems. Repeatable processes. Clear handoffs. Fewer fires.

That desire is right. The mistake is thinking systems come first. They are downstream of judgment.

You can’t build a process for a decision you haven’t made explicit. You can’t train a team on standards you haven’t named. You can’t automate a workflow if you don’t know what “good” looks like.

Every system in a business rests on a set of choices someone made about what matters. What to measure. What to reward. What to do when conditions change. If that judgment was never pulled out of someone’s head and made visible, the system is fragile. It runs as long as the world behaves. Then something unexpected happens and it breaks. Not because the process is bad, but because the decision logic is missing.

A familiar version looks like this. A team builds a process that works in the “normal” case. It looks clean on a slide. It looks tight in a doc. Then a weird customer shows up, or the market shifts, or the product changes, and suddenly nobody knows what to do because the process doesn’t say what to do when the rules conflict.

That gap isn’t a process gap. It’s a judgment gap.

When you design the judgment layer, you’re building the foundation every system depends on. Domain clarity. A signal library. Scripts that match your stance. Models that explain what you’re optimizing for. That base gets stronger over time.

Better tools don’t replace it. They multiply it. As models improve, the value of your judgment base goes up, not down, because the tool can carry more of your logic into more places.

That’s what compounding looks like here: not a one-time AI strategy, but a growing base of decision logic that keeps working as conditions change.

That leaves one advantage that was always there.

Knowledge was power because it came fused with execution, and execution was expensive.

That’s no longer true.

Execution is cheap. Output is cheap. The power didn’t shift. It was revealed.

It was always in the ability to decide what to do, in what order, toward what end, and how those decisions get made when you are not in the room.

Agents, prompts, whatever comes next are surface forms. The requirement underneath them does not change.

Knowledge was power. Now judgment is.

P.S. This builds on prior pieces: The Decision Architecture Manifesto (the bigger frame), and The Context Pyramid (the structure), and Design The Judgment That Transfers (the application).

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."

“They went with the cheaper option.”

The deal review starts the way they always start.

“The timing wasn’t right.”
“They already had the relationship.”

Everyone in the room has an explanation. All of them point outward.

But the product comparison told a different story. Your solution was better—features, integration, long-term cost. And the prospect knew it. They said as much during the sales process.

But they still chose the other offer. Something they could defend if it failed.

Before the pitch, the VP spent the morning convincing the board not to cut her team.

So the safety offer trumped the savings offer.

Motivation Isn't the Problem. Conditions Are.

The savings offer didn’t lose because it was wrong. It lost because it was solving the wrong thing.

It operated from solution thinking—the notion that the best product sells itself. But customers don’t buy the product that’s best for them. They buy the product that was best sold to them.

And best sold means understanding your customer’s problem before they ever hear about your solution.

For some, it’s making their kids’ soccer games. The job promised flexibility six months ago and hasn’t delivered. Every decision runs through one filter: does this help me get more family time back?

For others, it’s protecting a team they recruited personally. People they brought over from a previous company after making a bet on them. Their next move isn’t about ROI. It’s about keeping a promise.

The same solution could serve both. But it would need to be sold differently.

And until you understand what drives someone into action, you’re guessing which problem to solve.

The 5 Drivers of Human Action

As humans, we're always operating on one of five levels.

And the level we’re operating on determines what we can hear, what we’ll respond to, and what we ignore—no matter how good the offer is.

1. Stability Drivers

“Is this safe?”

Before a customer evaluates your solution, they evaluate their own footing.

Is my job secure?
Is my department going to exist in six months?

When stability is threatened, every other conversation becomes noise.

Patagonia understood this before they understood anything else. The Ironclad Guarantee — lifetime repair or replacement — eliminated the survival-level question before the customer ever had to ask it.

You’ll recognize this when every conversation circles back to risk.

“What could go wrong?”
“How do we de-risk this?”

That’s not resistance. That’s a customer telling you exactly where they stand.

When stability anxiety becomes the permanent filter, every opportunity gets evaluated through risk-first framing.

Stability governs whether someone can hear you at all.

2. Economic Drivers

“Does the math work?”

This is where most sales conversations live. ROI projections and cost comparisons. The customer needs the numbers to hold before anything above this level activates.

Patagonia reframed the math entirely. A $300 jacket that lasts twenty years costs less per year than the $100 jacket replaced every season.

The Worn Wear program —trade-ins at up to 20% of suggested retail price — means the purchase retains value after the buying decision.

The customer does the math themselves and arrives at a different answer than price comparison would suggest.

You’ll recognize this when the conversation narrows to spreadsheets.

“Show me the numbers.”
”How does this compare on cost?”

The customer isn’t being difficult. They’re standing on the level where numbers are the only language that registers.

The foundation holds when both of these levels are stable.

3. Social Drivers

“Who does this associate me with?”

At this level, decisions are about affinity.

You’ll hear it when questions shift from “what does this cost?” to “what does this say about us?”

That carries more weight than spreadsheets.

Patagonia’s gear drives that association for their customers. Each purchase signals membership in a group that says “I prioritize the planet.”

When affinity drives the decision, the customer is drawing a line. This is who I am. That is who I'm not.

4. Growth Drivers

“Who do I become because of this?”

At this level, the customer is looking to transform.

You’ll recognize it when someone asks “How do other people in my situation end up?”

Usually? They wear something out and buy another one. They never learn how it works. They stay consumers.

Patagonia knows that pattern. And they choose to interrupt it.

They publish free repair tutorials. They could push you back into the store. Instead, they teach you how to fix the jacket you already own.

When someone repairs their gear, they wear it more. They keep it longer. It turns into a story.

“How long have you had that jacket?”
“Years. I fix it myself.”

Now the customer isn’t just wearing Patagonia. They’ve learned a skill. They trust themselves a little more.

The jacket was the product. Capability was the outcome.

5. Meaning Drivers

“Why does this matter beyond me?”

This is the top.

Here, change moves beyond the individual. It spreads to their friends, their teams, their families. It shapes buying habits, conversations, even what people expect from other companies.

In 2022, Patagonia put it in writing: “We’re in business to save our home planet.”

For an outdoor gear company, that sounds extreme. That’s the point. It gives customers a cause to stand behind, not just a product to wear.

Joseph Pine spent twenty-five years mapping this progression — from commodities to goods, services, experiences, and finally, transformation. A transformed customer is the greatest marketing asset you’ll ever have—because they don’t promote your product. They share what it did to them.

You’ll know you’ve reached this level when the conversation shifts away from the company entirely:

“What’s our responsibility here?”
“What are we building that matters?”

That’s meaning. And it only holds if every level below holds.

Don’t Start With Trying To Save the Planet

Patagonia didn’t start there either.

They started by understanding the full arc of their customer. Not just the surface problem — what gear do they need? — but the entire journey. Where is this person right now? What level are they trying to reach? What’s the path between here and there? And who do they become as they climb it?

That arc is what drove every decision Patagonia made. The Ironclad Guarantee addressed where customers were. The cost-per-year reframe met them at economics. The community formed around shared values. The repair tutorials built capability. The mission gave it meaning.

They didn’t skip levels. They built the ladder rung by rung — because they understood the full arc before they built the first product.

Most companies stop at the first two drivers. They ask surface questions. “Did this save you money?” “Is this less risky than what you had?” Those matter. But now you know there’s more underneath.

The shift is asking what’s driving beyond those surface answers. Not just “are you safe?” but “who does this associate you with?” Not just “does the math work?” but “who are you becoming because of this?”

That’s not a harder conversation. It’s a deeper one.

And that starts with knowing where they stand right now.

Higher Levels Require Conviction, Not More Skill

Most companies stay on the surface. It feels safer.

The first two levels are concrete. More defensible in a quarterly review.

“We reduced costs by 30%” is easy to say.
“We changed how our customers see themselves” is not.

But staying on the surface has a cost. Surface problems create crowded markets. Without conviction to go deeper:

• You work on rented problems — the same ones everyone else chases.

• You develop rented positioning — based on what you do, not what you change.

• And your customer gets a rented identity — useful, maybe valued, but never fully theirs.

You get better. But you don’t get different.

The higher levels change the problem itself.

There’s no early proof.
No clear benchmark.
No existing category language to borrow.

That’s why conviction matters. You choose the level first.

Own the problem, and prime position becomes yours.

You shape how your customer sees progress instead of renting space in a crowded market.

That shift is harder to measure in a quarter. But it’s harder to replace in a year.

That’s the trade.

Map Your Customer's Mobilization Ladder

You’ve seen what happens when you stay on the surface and what changes when you go deeper.

Now make it yours.

Start with one customer. Not your ideal customer. A real one. Someone you’re working with right now or someone you recently lost.

Use these 3 prompts:

1. The Driver Read
Where are they standing right now? Which driver is running their decisions — safety, economics, affinity, growth, or meaning?

You are a strategist who helps companies see which driver is actually running their customer's decisions. You know that customers don't always operate on the level companies assume. A customer who seems difficult about price may actually be protecting their job. A customer who asks for case studies may actually be looking for identity confirmation. The signal is in the conversation — what they circle back to, what they push on, what they resist. Your job is to help people read those signals and name the driver.

You're speaking with someone who just read about the five drivers of human action. Every customer is operating on one of five levels, and the level they're on determines what they can hear, what they'll respond to, and what they ignore — no matter how good the offer is:

- Stability: "Is this safe?" — Every conversation circles back to risk. "What could go wrong?" "How do we de-risk this?" When stability is threatened, every other conversation becomes noise.
- Economic: "Does the math work?" — The conversation narrows to spreadsheets. "Show me the numbers." "How does this compare on cost?" Numbers are the only language that registers.
- Social: "Who does this associate me with?" — Questions shift from "what does this cost?" to "what does this say about us?" Decisions are about affinity and identity signaling.
- Growth: "Who do I become because of this?" — The customer is looking to transform. "How do other people in my situation end up?" They want capability, not just a product.
- Meaning: "Why does this matter beyond me?" — The conversation shifts away from the company entirely. "What's our responsibility here?" "What are we building that matters?"

Patagonia understood this arc. The Ironclad Guarantee addressed Stability. The cost-per-year reframe met Economics. The community formed around Social. The repair tutorials built Growth. The mission gave it Meaning. They didn't skip levels — they built the ladder rung by rung.

Now help the reader see which rung their customer is standing on.

---

YOUR TASK

Ask:

"Think about one customer — not your ideal customer, but a real one. Someone you're working with right now or someone you recently lost.

Two questions:

1. What do conversations with this customer actually sound like? Not what you pitch them — what they keep coming back to. What questions do they repeat? What do they push back on? What do they resist no matter how good your answer is? The pattern in their language tells you which driver is running. Risk talk is Stability. Number talk is Economic. 'What will people think' is Social. 'What happens to me' is Growth. 'What's the point of all this' is Meaning.

2. Think about the last time this customer made a decision — chose you, chose someone else, or chose to wait. What was the real reason? Not the stated reason in the debrief. The thing that actually tipped the scale. A VP who spent her morning defending her team's existence isn't evaluating your ROI deck. She's evaluating whether your offer is something she can defend if it fails. The decision tells you the driver."

Once the user responds, do the following:

1. Name the active driver in one sentence — the level this customer is operating on right now, based on the signals in their language and decisions.

2. Name the signal pattern in one sentence — the specific words, questions, or behaviors that reveal the driver.

3. If the driver is Social, Growth, or Meaning, offer a foundation reminder:
   - Social: "Social drivers usually mean the foundation is holding — Stability and Economics aren't in question. What's giving them that security? If it's assumed rather than confirmed, the real driver may be lower than it appears."
   - Growth: "Growth drivers usually mean the customer feels safe and the math works. What's giving them the room to think about transformation? Sometimes a customer reaches for Growth because they've resolved the levels beneath it. Sometimes they're skipping ahead because the Growth conversation feels more inspiring than the Stability conversation they need to have."
   - Meaning: "Meaning is the top of the ladder, and it only holds if every level below holds. What's supporting this? A customer who talks about purpose while their team is at risk isn't operating on Meaning — they may be avoiding a Stability conversation they don't want to have."

4. If the driver is Stability or Economic, reflect:
   - Stability: "When Stability is the active driver, every other conversation becomes noise. Your customer isn't evaluating your solution yet — they're evaluating their own footing. The offer that wins here isn't the best one. It's the one they can defend. Patagonia understood this — the Ironclad Guarantee eliminated the survival question before the customer ever had to ask it."
   - Economic: "When Economic is the active driver, numbers are the only language that registers. This is where most sales conversations live — and where most companies stop. The foundation is holding, but the customer hasn't moved beyond the math. The question isn't whether the numbers work. It's whether your engagement with them stops here."

5. Close with:
   "The driver tells you what your customer can hear right now. It doesn't tell you what they want — it tells you what they need resolved before they can want anything else. The ladder has five rungs, but only one is under their feet at any given moment. Now you can see which one."

Do not suggest messaging. Do not redesign their approach. Just help them see the driver that's actually running the customer's decisions — and what's holding beneath it.

2. The Climb
Where are they trying to go? Not what they’re buying — what they’re reaching for. What level are they climbing toward?

Read more

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.