I’ve watched this play out for 30 years in companies with $5 million to $100 million in revenue. The pattern isn’t a thinking problem. It’s a testing problem. Strategies don’t fail because the logic is wrong. They fail because the logic was never tested before commitment.

This is what the Strategy Arcade is for. It’s the part of a BUILD engagement, and a recurring part of SYSTEM, where we stop projecting and start probing. We put your strategy in a structured sandbox and try to break it before the market does.

The Arcade has two halves: a red-team session where we run the strategy against the disruptions most likely to materialize (regulatory shifts, technological displacement, economic shocks), and a Pre-Mortem, where we assume the strategy has already failed two years from now and work backward to identify the logic leaks today.

What you walk away with isn’t a 50-page document. It’s a tested logic of choice and a leadership team that has practiced the discipline.

I wrote up the full method this week. Why it matters more in 2026 than it did in 2019, what an Arcade actually looks like, and the honest answer for whether your strategy is ready for one.

Originally published at haasstrategy.com.

Read the full article on the Strategy Arcade

Reading time: 5 minutes

THE SHORT VERSION

Over the past six weeks, we’ve worked through the full Sprint sequence.

You’ve named the actual problem instead of the symptom. You’ve built genuine options instead of defaulting to Option A. You’ve run WWHTBT to test the logic. You’ve identified the assumptions with high stakes and low confidence.

Now what?

You put it on one page.

Not because brevity is a virtue in itself. Because if the strategy can’t fit on one page, the choices haven’t been made yet. Fuzzy thinking expands to fill whatever space you give it. One page means you made the hard calls.

A 40-slide strategy deck isn’t evidence of rigor. It’s evidence that nobody decided what mattered most.

WHAT GOES ON THE PAGE

The CEO Summary has five elements. Not sections, not chapters. Five things, all on one page.

1. THE PROBLEM STATEMENT

One sentence. The specific strategic challenge this plan is designed to address. If it takes more than one sentence, the diagnosis isn’t finished. It’s OK to redraft this a few times. Maybe write a paragraph and chop away.

2. THE STRATEGIC CHOICE

Where you’re competing and how you plan to win. Which option from the Possibility Set did you choose, and what does that choice foreclose? This is the hardest element to write because it requires saying no to something visible. Who likes to say no?

3. THE KEY INITIATIVES

Three or four concrete actions required to execute the choice. Not the full roadmap. The things that have to happen for the strategy to be real. Each needs an owner and a date. These are things where absence or underperformance is existential.

4. PRIORITY UNCERTAINTIES STILL OPEN

What you don’t yet know but must figure out before committing the next level of resources. This is the honest part of the page. Most strategy documents omit it entirely. Turn assumptions that everyone thinks are facts back into assumptions with uncertainties.

5. OWNER AND REVIEW DATE

Who’s accountable and when you’ll assess whether the strategy is working. Without this, the page is interesting reading. It’s not a working document.

THE TEST EACH ELEMENT PERFORMS

Every element on the page forces a discipline that the full strategy process was building toward.

The problem statement forces you to commit to a diagnosis. You can’t fit a vague description in one sentence. Either you know what the actual problem is, or you don’t. The page makes that visible immediately. It gets better with experience.

The strategic choice forces specificity about where you compete and why you expect to win there. ‘We’ll pursue growth across all segments’ doesn’t fit. That’s not a strategy either. The format demands a real answer.

Key initiatives force prioritization. You’ll have more ideas than will fit. Good. The exercise of deciding which three or four make the list is the strategy work, not a summary of it.

Priority uncertainties force honesty. Listing what you don’t know is uncomfortable. Most leadership teams skip it. Teams that include it make better decisions because everyone is working from the same picture of the risks.

Owner and review date force accountability. A strategy without a specific person responsible and a specific date for assessment is a preference, not a commitment.

THE ‘NO’ TEST

One diagnostic worth applying before you call the page done: can someone who reads it tell you specifically what your organization has decided not to do? Not Sophie’s Choice; just something(s) that is not a top priority

Real strategic choices have costs. Specific customers you won’t pursue. Market segments you’re leaving to competitors. Capabilities you’re choosing not to build because they don’t fit the direction.

If the page doesn’t describe any costs, the choices haven’t been made. You have a document about strategy rather than a document that is strategy.

A COO I worked with in Virginia had a beautifully written one-pager. Smart language, clean structure. When I asked her what market segments the company had explicitly decided not to pursue, she paused. ‘I don’t think we put that in there,’ she said.

That’s the tell. The page described aspirations. The choices were still pending.

WHO READS IT AND WHY

The CEO Summary has three audiences, and it needs to work for all three.

The leadership team. The page is the alignment artifact. Everyone should be able to read it and agree it accurately describes what they decided. If two people read it and come away with different understandings of the strategic choice, the choice wasn’t actually made.

The board. Directors don’t need the full analysis. They need to understand the strategic logic, the key risks, and what questions to ask management. A one-page summary gives them exactly that in the time it takes to read a page. A 60-slide deck gives them data and no clear point of view. More likely, they won’t bother reading it.

New executives. When someone joins the leadership team six months after the Sprint, they should be able to read the CEO Summary and understand where the organization is (and was) pointed and why. If they can’t, something about the organization’s strategy communication is broken.

WHAT THIS CLOSES

This is the sixth and final article in the Sprint sequence.

Weeks 9 (March 24) through 15 (this week) walked through every Sprint deliverable: the problem statement, the Possibility Set, the as-is strategy cascade, the WWHTBT logic test, the priority uncertainties, and now the CEO Summary. Together, they form a complete picture of what it takes to go from strategic fog to documented clarity in 6 weeks.

Some organizations stop here. They have what they need: a shared, honest picture of the situation, genuine options evaluated rather than assumed, and a one-page synthesis that the leadership team will stand behind. That’s real value. More than most organizations produce from a much longer planning process.

Others use the CEO Summary as the starting point for a Build engagement, in which priority uncertainties are investigated, and the strategy is validated against actual market feedback before making big bets. The page tells you what you’ve decided. Build tells you whether the decisions were right.

Sprint gives you clarity. Build gives you confidence. The CEO Summary is the document that connects them.

BUILD YOUR OWN THIS WEEK (I DARE YOU!)

Use the five-element structure above and give yourself 90 minutes.

Start with the problem statement. Write it in one sentence. If you find yourself reaching for a second sentence, that’s the signal the diagnosis still has work to do.

Move to the strategic choice. Write specifically where you compete and how you expect to win. Then write one sentence about what that choice forecloses.

Name three or four initiatives. Real ones, with owners attached.

List your priority uncertainties. The conditions from your WWHTBT analysis that are both high-stakes and not yet confirmed. Two or three is plenty. If you have more than that, you haven’t sorted them yet.

Add the review date. Pick a specific date, not a quarter. Specific dates produce accountability. Quarters produce drift.

When you’re done, give it the ‘no’ test. Then give it to someone outside the leadership team and ask them: What has this organization decided not to do?

Their answer will tell you whether the page is done.

Next week: A personal piece on strategic patience and what coaching youth sports taught me about the pace at which real development happens.

If you’ve been following this sequence and want to run a Sprint with a structured facilitator, the HSS Sprint engagement is built around exactly these five deliverables. Start with a Fit Call.

Run ‘What Would Have to Be True’ on three strategic options and you might end up with 15 conditions on your list. Could be more.

The temptation is to treat them equally, assign someone to research each one, and reconvene in a month. That approach burns time and misses the point.

The conditions on a WWHTBT list aren’t equivalent. Some are well-established facts that don’t need investigation. Some are uncertain but won’t hurt the strategy much even if they’re wrong. And a few are both uncertain and load-bearing. Those are your priority uncertainties. They’re where the work needs to go before you commit.

A priority uncertainty is an assumption with high stakes and low confidence. Everything else can wait.

HOW TO SORT THE LIST

Two questions tell you which conditions belong at the top.

First: how confident are you that this condition is currently true? Not confident in principle. Specifically. What evidence do you have? When did you last check? ‘We’ve always assumed this’ isn’t confidence. It’s a habit (one we need to break).

Second: what breaks if this condition turns out to be false? Does the option underperform, or does it fail completely?

Run those two questions against your list and it sorts itself. High-stakes and uncertain ones go to the top. Certain conditions or low-consequence conditions can wait or be set aside.

A manufacturing firm near Frederick ran this exercise on a planned market expansion. They had eleven conditions on their WWHTBT list. Nine were either well-established or relatively low-consequence. Two were neither. Both involved the same thing: whether their primary distribution partner would actively support the new territory, or treat it as a low-priority extension of their existing relationship.

Nobody had asked the partner directly. The expansion plan assumed active support. The entire unit economics depended on it.

That’s a priority uncertainty. Two questions, fifteen minutes of honest discussion, and the whole research agenda reorganized itself.

WHAT TEAMS DO INSTEAD

The most common alternative is researching what’s comfortable. Teams gravitate toward conditions they can answer quickly, or conditions that will confirm what they already believe. The spreadsheet fills up. The work feels thorough. The high-stakes uncertain assumptions stay untouched because addressing them requires going somewhere uncomfortable, usually outside the organization, to hear something that might not be welcome.

There’s also a version where teams name their priority uncertainties correctly and then don’t act on them. That’s bad. They get listed in the strategy document as ‘areas requiring further study,’ and the plan proceeds anyway. Also bad. That’s not risk management. It’s documentation of a known problem while ignoring it.

Naming a priority uncertainty without investigating it is just a more organized way of not knowing what you’re doing.

THE INVESTIGATION QUESTION

Once you’ve identified your priority uncertainties, the next question is: what’s the fastest credible way to reduce the uncertainty before committing resources?

Sometimes that’s a conversation. Talk to the distribution partner. Ask directly. The answer might be uncomfortable, but it takes a week, not a quarter.

Sometimes it’s a small test. A pilot program in one geography before committing to three. A single client engagement in a new segment before restructuring the whole delivery team.

Sometimes it’s external research. Relevant market data exist, you just haven’t looked for it. Trade associations, regulatory filings, competitor reports, and customer surveys from industry groups.

The point is to match the investigation to the uncertainty, not to run a comprehensive research project that takes six months and produces more uncertainty than it resolves. Priority uncertainties deserve fast, specific answers.

HOW THIS CONNECTS TO BUILD

In a Strategy Sprint, identifying priority uncertainties is one of the five deliverables. The analysis tells you what you know well enough to act on and what you don’t. The CEO Summary captures both.

When an organization moves from Sprint to Build, the priority uncertainties become the research agenda. Build is largely the work of going out and testing those conditions against reality. Customer interviews, partner conversations, pilot programs, competitive analysis. The priority uncertainties from Sprint tell you exactly where to look.

If all you do is Sprint, you leave with clarity. You understand the problem, you have genuine options, and you know what you’d need to believe for each option to succeed. That’s valuable. But the most consequential assumptions are still open. Build is what closes them.

YOUR MOVE THIS WEEK

Take your WWHTBT list from last week’s exercise, or build one now for your current strategy.

Sort it. Which conditions, if false, would cause the strategy to fail rather than underperform? Which of those do you have strong evidence for, and which are you essentially assuming?

The ones at the intersection of ‘would cause failure’ and ‘we’re assuming rather than knowing’ are your priority uncertainties. Write them down explicitly.

Then ask: what’s the fastest credible way to get a real answer on each one?

That’s your research agenda. Everything else is secondary.

Next week: The One-Page CEO Summary. Sprint’s final deliverable and the test of whether the strategy is actually clear enough to act on.

If your team has named its priority uncertainties but isn’t sure how to investigate them, that’s exactly where the Sprint-to-Build conversation starts. Learn more about the Build engagement at HSS.

Every strategic option rests on conditions that have to hold for it to work. Most leadership teams never write those conditions down.

They pick a direction. Build a plan. Get moving. The assumptions underneath stay invisible, untested, and occasionally wrong in ways that matter quite a lot.

There’s one question that fixes this.

“What would have to be true” for this option to succeed?

Six key words. The real trick is to actually answer the question.

WHY STRATEGY DEBATES GO NOWHERE

Sit in enough planning meetings and you’ll see the same pattern. Someone pushes for Option A. Someone else proposes Option B. They go around the table. Positions get restated in slightly different language. The meeting ends with a decision, a stalemate, or enough ambiguity that everyone can claim they got what they wanted.

Nobody examined the assumptions underneath either position. The debate was about conclusions, and conclusions are hard to test.

Roger Martin, who did strategy work at P&G for years and wrote one of the most useful books on strategy I know of, identified why this happens. The real disagreement isn’t about the option. It’s about what each person believes to be true about the world. Those beliefs stay hidden inside the argument. Surface them and you can actually examine them.

WWHTBT is how you surface them.

When you ask what would have to be true for your preferred option to succeed, you stop defending a conclusion, surface biases, and start naming conditions. Market conditions. Customer behavior. Operational performance. Competitor response. Things that have to hold for the option to work. Some are well-established. Some are guesses nobody has checked in two years. Many are grounded in irrefutable data. The ones that are shaky and load-bearing at the same time are where your attention should go.

HOW IT WORKS IN PRACTICE

Consider a leadership team that has developed a Possibility Set with three options: Option A extends the current direction, Option B pivots toward a new customer segment, and Option C proposes a joint venture with a complementary firm.

The WWHTBT question is applied to each option.

For Option A, what would have to be true? The current customer segment must remain loyal despite increased competition. Existing pricing power must persist. Delivery capacity must scale without a proportional rise in overhead. Each is a testable assumption.

For Option B, the new customer segment has to be large enough to justify transition costs. The team has to be able to reach them through channels not currently owned. Core capabilities need to translate to buyers with different needs. Again, these are testable.

For Option C, the partner has to provide capabilities that can’t be developed internally within the required timeframe. The economics have to benefit both parties. Integration has to be manageable while both organizations continue their core operations. Each of these conditions can be evaluated.

This approach gives the conversation momentum. Rather than debating preferences, the team examines whether the necessary conditions for each option are present.

The focus shifts from voting on options to auditing the underlying assumptions.

A vague debate about whether to pursue the federal market just became a set of specific questions. That’s the mechanism.

TWO QUESTIONS THAT DO THE MOST WORK

Once you’ve listed what would have to be true for an option, you run two questions against each condition.

First: how confident are you that this is actually true right now? Not confident in general. Specifically. What’s the evidence? When did you last check?

Second: what breaks if it turns out to be false? Does the option underperform, or does it fail entirely?

A condition that’s both uncertain and load-bearing is a priority uncertainty. That’s where the investigation needs to go before you commit resources. We’ll get into that specifically next week.

The conditions that are certain and low-stakes? Stop spending time there. The analysis is designed to concentrate attention on what actually matters. Most planning processes don’t do that.

THE UNCOMFORTABLE APPLICATION

Something uncomfortable tends to happen when you run WWHTBT on Option A, the default direction, the current plan extended.

Teams often realize they have never formally tested their default strategy.

Option A feels safe because it is familiar. But familiar is not the same as validated. The conditions that made Option A work two or three years ago may no longer hold. The customer loyalty assumption has not been examined. The pricing power assumption has been taken for granted. The competitive landscape assumption is based on last year’s data.

Applying WWHTBT to your current strategy is often more revealing than using it on alternatives. It quickly shows whether decisions are based on evidence or habit.

A CEO in Bethesda described realizing his company’s entire growth plan depended on a single assumption: that their largest client would continue to grow the relationship. This assumption had not been tested or discussed with the client in over a year.

Familiar isn’t the same as validated. Option A gets the least scrutiny and often deserves the most.

The assumption turned out to be wrong. They found out through the WWHTBT process rather than through a surprise non-renewal. That is not a small thing.

THREE WAYS TEAMS MISUSE THIS

The WWHTBT question is straightforward but often misapplied. We mess this up in three common failure modes.

Listing conditions that are already known to be true. If a condition is an established fact, it does not belong on your WWHTBT list. You are looking for the things that must hold but have not been confirmed. Padding the list with certainties is comfortable and useless.

Second, framing conditions as goals instead of facts. For example, ‘Our sales team would have to perform at a higher level’ is a hope, not a condition. A valid condition is specific and externally verifiable, such as ‘Our conversion rate on qualified leads would have to reach X percent, compared to our current Y percent.’ Only the latter can be tested.

Third, stopping after generating the list. Creating WWHTBT conditions is only the start of the analysis. Teams must examine these conditions before selecting an option. The list has value only if it is investigated.

HOW THIS FITS THE SPRINT

In a Strategy SPRINT, WWHTBT serves as the analytical engine connecting the Possibility Set to the final deliverables.

Options are developed in weeks two and three of SPRINT, followed by WWHTBT analysis for each. Conditions identified as both uncertain and high-stakes become priority uncertainties. These inform the CEO Summary and guide subsequent validation work in a Build engagement.

This analysis also forms the intellectual foundation of BUILD, which will be discussed later. Build involves engaging with customers, partners, competitors, and stakeholders to test whether the identified conditions hold.

However, the process begins here, with a single question.

You can’t validate assumptions you haven’t named. WWHTBT is how you name them.

YOUR MOVE THIS WEEK

Take one strategic option you’re currently considering. Or just take the direction you’re already executing.

Write down four or five conditions that would have to be true for it to succeed. Not goals. Conditions. External facts the plan depends on.

Then ask: when did we last actually check whether this is still true?

If the honest answer is “a while ago” or “I assumed it,” you’ve found your starting point.

Next week: Priority Uncertainties. Once you’ve named the conditions, the question is which ones to investigate before committing capital and talent. Not all uncertain conditions are equally consequential.

WWHTBT is a core part of every Strategy SPRINT at HSS. If your team’s working through options and needs a structured way to test the logic, the SPRINT is built for exactly that.

Get the “adventurous” (i.e., dangerous) stuff out of your system first.

One Saturday morning, I drove out to a small airfield before dawn with three friends. I was going to jump out of a perfectly good airplane.

FOUR HOURS ON THE GROUND

The training took most of the morning. We packed parachutes. We practiced body position. We jumped off a platform and rolled on the ground, over and over, until it felt automatic. We covered emergency procedures for scenarios none of us expected to actually face.

By the time we walked toward the plane, I had consumed more information about skydiving than I had about most things I do regularly. (That’s me on the left)

I was not particularly nervous. I have a commercial pilot’s license, and I recognized the aircraft. That helped. My three friends were quieter than usual.

Before we boarded, the instructor gathered us on the tarmac. The engine was running. He had to shout to be heard.

“You are so anxious that you have forgotten everything from this morning. Just remember three things: push back from the plane, arch your back, and smile.”

I remember thinking: why did I get up before dark and spend four hours learning all this if three things were the whole answer?

THE JUMP THAT WENT SIDEWAYS

Nobody wanted to go first. I volunteered.

What I did not know: the wind had nearly stopped between takeoff and jump time. That moved my exit point farther from the airport than planned.

I did everything right. I pushed back from the plane. I arched. I smiled, more or less.

It was not enough. I came down short of the landing zone and settled into a line of trees at the field’s edge. I ended up suspended about 6 feet off the ground, my chute tangled in the branches above me.

And here is where the morning’s four hours came back to me.

Somewhere in the training, an instructor had said: if you land in trees, one hand covers your face, the other protects your groin. It had seemed like a footnote at the time. A contingency nobody actually expected to use.

I used it. The branches did exactly what branches do. The preparation did exactly what preparation is supposed to do.

I landed shaken but unscratched. When the instructor asked where my chute was, I pointed to the line of trees where I had left it hanging in the trees.

THE LESSON THAT STAYED WITH ME

Standing at the edge of that field, picking pine needles out of various places, I thought about what had just happened.

On the way up, the instructor’s three-item rubric had seemed like the whole story. Push back, arch, smile. Simple. Elegant. Sufficient.

Then conditions changed. The wind quit. The landing zone moved. And suddenly, the contingency training, the scenarios we had rehearsed but did not expect to need, was the only thing standing between me and a bad outcome.

Preparation looks unnecessary right up until the moment it is not.

This is not a metaphor I had to stretch to reach strategy work. It is exactly the same dynamic.

When a leadership team builds a problem statement, runs a Possibility Set, and names their priority uncertainties, most of that work will not feel necessary in the moment. The obvious path will look clear. Option A seems fine. Contingency scenarios feel like overhead.

Until conditions change. A competitor moves. A key client leaves. A regulation shifts. A cost assumption turns out to be wrong. Technology evolves.

Teams prepared are not surprised. They recognize the situation. They have already thought through it, at least partially. They respond faster and with more discipline than the teams that skipped the diagnostic work because everything looked fine on a clear day.

The instructor was right. Three things were enough for the jump itself.

He was also right about everything else he taught us.

Both of those things were true at the same time.

Next week: What Would Have to Be True? The core logic test that separates wishful strategy from testable strategy. Tuesday, 10:15 am.

Most leadership teams never actually choose their strategy.

They inherit one. They extend the current year’s plan. They tweak last year’s budget. They launch the initiative that everyone had already agreed to before the offsite began.

What they rarely do is build a genuine set of options and then choose among them.

That is the Possibility Set. And skipping it is why so many strategies feel like the only thing anyone could have done, right up until they stop working.

A choice is only real if there was something else you could have chosen.

THE OPTION A PROBLEM

Here is a pattern I see in almost every planning process I walk into.

The leadership team has been living with a problem for months. They have opinions. They have built convictions. By the time they sit down to do strategy work, Option A is not really on the table. It is the table.

The facilitated discussion, the offsite agenda, the consulting engagement, all of it is structured around arriving at a destination that was already chosen informally, in hallways and one-on-ones, long before the formal process began.

This is not cynicism. It is human. People (all of us) form views. Leaders especially.

But it’s a problem. Because Option A, the obvious move, the safe extension of the current direction, is often the wrong choice. Markets shift. Assumptions decay. Technology changes. What worked last year may not work next year.

Defaulting to the familiar is not strategy. It is inertia with a slide deck.

WHAT THE POSSIBILITY SET IS

The Possibility Set is a structured collection of two or three genuine strategic options. Not variations on a theme. Not slight adjustments to the current plan. Real alternatives that each represent a different answer to the strategic problem you named in the March 31 post, The Strategic Problem Statement.

Each option in the set should pass four tests.

1. It is actually different.

If you squint and Options A and B look the same, you have one option with cosmetic variation. That does not count. A real option takes you somewhere meaningfully different.

2. Someone in the room would choose it.

If no rational person would pick Option C, it is a strawman, not an option. Every option in the set should have a credible case behind it.

3. It is internally consistent.

Each option should have its own logic. Its own target customer, its own value proposition, its own competitive rationale. A half-formed idea is not an option.

4. It forecloses something.

Real strategic choices say no to something. If Option B does not require giving anything up, it is not a real strategy. It is a wish list.

If every option is comfortable, you have not built a Possibility Set. You have built a list of things you were already going to do.

HOW TO BUILD GENUINE OPTIONS

The hardest part of building the Possibility Set is not generating ideas. It is generating ideas that are genuinely different from the current direction.

Here are four moves that reliably surface real options.

Start with the customer, not the product. Ask: Who else could we serve that we currently ignore? What would we have to change to reach them? This often reveals a market adjacency or a segment expansion that the current plan does not consider.

Ask what you would do if your biggest asset disappeared. If you lost your largest client, your lead product, or your most important distribution channel, what would you build instead? Constraint thinking surfaces alternatives that comfort thinking never reaches.

Look at what competitors are not doing. In every market, there are moves no one is making. Sometimes that is because those moves are bad ideas. Sometimes it is because everyone is following the same assumptions. Asking why a space is empty often reveals an option worth considering.

Consider the exit logic. If you were going to sell the company in three years, what would you build to maximize its value? That target state often defines a strategic option that pure operating logic would not generate.

You do not need a dozen ideas. You need two or three that are genuinely different and genuinely defensible.

A STORY ABOUT OPTIONS THAT CHANGED EVERYTHING

I worked with a professional services firm that had been growing steadily for a decade. Revenue was solid. The team was good. The obvious Option A was to keep doing what was working, hire more people, and serve more clients in the same segment.

We pushed them to build a real Possibility Set.

Option B: stop serving small and mid-size clients entirely and reposition as a high-fee specialist for a narrower, larger client base. Fewer clients, deeper relationships, significantly higher margins.

Option C: productize their core methodology into a licensed training program and sell it to firms that could not afford their direct fees. Different business model, different growth ceiling, different risk profile.

Option A still won. But it won differently. The team stress-tested it against B and C and came out with sharper clarity about why they were choosing it and what it would require. They made specific commitments they had never made before, around client minimums, service boundaries, and hiring profiles.

That is what a real Possibility Set does. Even when you end up at the obvious choice, you arrive there with more conviction and more discipline. At a minimum, more insight and a little humility.

THE CONNECTION TO CHOICE

In Strategy Is Choice, Not Aspiration (March 3), we covered the idea that strategy is choice, not aspiration. Roger Martin’s framework, the strategy cascade, starts with a winning aspiration and then forces choices about where to play and how to win.

The Possibility Set is where those choices get structured.

You cannot choose where to play if you have only one place on the map. You cannot choose how to win if you have only one theory of winning. The Possibility Set forces the team to put multiple answers on the table before any of them are selected.

This is also where the problem statement from Week 10 does its work. A clear problem statement shapes which options are relevant. If the problem is customer churn, Option A should address churn. If it does not, it belongs in a different conversation.

The Possibility Set is not brainstorming. It is a structured option generated in response to a named problem.

WHAT HAPPENS AFTER THE POSSIBILITY SET

The Possibility Set is not the endpoint. It is the setup for the next moves in the Sprint.

Once you have two or three genuine options, the next question is: what would have to be true for each one to succeed? That is the WWHTBT framework we will cover in the April 21 post. It is the core logic test that separates wishful thinking from testable strategy.

In the Sprint, the Possibility Set typically takes the middle two weeks to build properly. It is not a one-session exercise. Options need to be drafted, challenged, thought about, refined, and stress-tested before they are ready for validation.

Teams that do this well arrive at their final strategy choice with something rare: confidence they can explain. Not just conviction that they are right, but a clear account of what they considered and why they chose what they chose.

Boards respond to that. Investors respond to that. Executive teams execute better because of that.

YOUR MOVE THIS WEEK

Take the strategic problem you identified last week. The one sentence that describes the actual challenge.

Now write down your current answer to it. The direction you are heading. That is your Option A.

Then ask two questions:

• What is a meaningfully different answer to this same problem that a reasonable person could argue for?

• What would we have to give up to pursue it?

If you cannot answer the second question, you haven’t yet found a real option.

That discomfort is useful. It means you are doing strategy, not planning.

Next week: What Skydiving Taught Me About Preparation. A personal piece on why the work you do before the jump determines everything about the jump itself. Connects directly to why the Sprint invests 30 days in diagnosis before committing to direction.

If your team is stuck at Option A and you know it, the Sprint is designed to get you unstuck. Learn more about the Strategy Sprint at Haas Strategy Solutions.

Most leadership teams are solving the wrong problem.

Not because they are careless. Because naming the actual problem is harder than it looks, and skipping that step is faster. So they move straight to solutions, initiatives, and roadmaps built on a problem nobody formally agreed on.

This is the single most common reason strategy fails.

If you solve the wrong problem brilliantly, you still lose.

THE SYMPTOM TRAP

Here is how it usually goes.

Revenue is flat. The leadership team gathers. Someone says the sales team needs better training. Someone else says the product needs a refresh. A third person says the brand is tired and needs a campaign.

Three weeks later, there are three new initiatives underway. Revenue is still flat.

What nobody asked: why is revenue flat?

Flat revenue is a symptom. It could mean many things. Customers are churning faster than new ones arrive. The market segment you serve is shrinking. A competitor has undercut your price. Your best salespeople left. Your product solves a problem customers used to have but no longer do.

Each of those is a different problem. Each requires a different response. Launching a sales training program when the real issue is a shrinking market segment does not fix anything. It just creates activity.

Activity is not strategy. Busy is not the same as effective.

WHY TEAMS SKIP THE PROBLEM STATEMENT

The problem statement step gets skipped for predictable reasons.

It is slow. Writing a clear problem statement requires conversation, debate, and often a few uncomfortable revelations. That takes time. The team would rather start doing.

It is political. The real problem often implicates someone in the room. Naming it means naming whose decisions, assumptions, or territory are part of the issue. That is uncomfortable.

It feels obvious. Leaders often assume everyone already agrees on the problem. They rarely do. The agreement is usually surface-level. Push one layer deeper and the versions diverge fast.

I learned this in the field, watching ecologists describe the same system in completely different terms depending on what they were trained to see. A soil scientist and a wildlife biologist standing in the same wetland see entirely different problems. Leadership teams are no different.

WHAT A REAL PROBLEM STATEMENT LOOKS LIKE

A good problem statement does five things.

• It names the gap between current reality and desired outcome.

• It is specific enough to be falsifiable. You could imagine evidence that says the problem is solved.

• It does not contain the solution. If your problem statement says ‘we need a new CRM,’ that is a solution, not a problem.

• It is short. One to three sentences. If it takes a paragraph to describe the problem, the problem has not been diagnosed yet.

• The leadership team agrees on it. Not nods-in-a-meeting agrees. Actually agrees.

Here is what a weak problem statement looks like:

“We need to grow revenue by improving our go-to-market strategy and investing in customer success.”

That is a solution list dressed up as a problem statement. It assumes the cause and prescribes the response before any diagnosis.

Here is what a stronger version looks like:

“We are losing mid-market customers within 18 months of acquisition at a rate that offsets new customer growth, and we do not have a shared understanding of why.”

That version names the gap, points to what we do not know, and leaves the solution open. Now the team can actually work the problem.

THE PROBLEM BEHIND THE PROBLEM

The most useful discipline in problem statement work is asking one question repeatedly:

“Is that the problem, or is that a symptom of the problem?”

Revenue is flat. Is that the problem? Or a symptom?

Customer churn is high. Problem or symptom?

The sales team is underperforming. Problem or symptom?

Keep asking until you hit something that does not dissolve into a deeper layer. That is the problem worth solving.

In ecology, this is the difference between treating an invasive species and asking why native species stopped competing effectively. One is a response. The other is a diagnosis.

The diagnosis takes longer. It is worth it.

A STORY FROM THE FIELD

Consider a manufacturing company in the mid-Atlantic losing market share. The leadership team was convinced the problem was pricing. A competitor had come in low and was taking contracts.

Now run the problem statement process before anyone touches a spreadsheet.

What surfaces is on-time delivery rate dropped from 94 percent to 81 percent over 18 months. Customers were not leaving because of price. They were leaving because delivery had become unreliable, and the competitor’s lower price made the switch easy to justify.

The pricing problem was real but secondary. The delivery problem was primary.

A pricing response would have cut margin and not stopped the churn. The actual fix was in operations.

They never would have found it without the problem statement work.

HOW THE SPRINT USES THIS

In a Strategy Sprint, the problem statement is the first deliverable and the hardest one. We don’t move forward until the leadership team agrees on it.

This often takes more time than people expect. That isn’t a failure. It’s the work.

Last week, I described the Sprint as delivering clarity before commitment. The problem statement is where that clarity starts. Everything else, the possibility set, the business model canvas, the priority uncertainties, builds on top of it.

A weak problem statement produces a well-executed response to the wrong situation. A clear problem statement makes every subsequent decision faster and more defensible.

Sprint does not guarantee the right answer. It guarantees you are answering the right question.

YOUR MOVE THIS WEEK

Try this before your next planning conversation.

Write down your company’s single most important strategic challenge in one sentence. Then ask two or three of your senior leaders to do the same, independently.

Compare the sentences. Look for three things:

• Do they describe the same gap?

• Do any of them contain a solution hidden inside the problem description?

• Does anyone describe a symptom where someone else describes a root cause?

What you find in that comparison is more useful than most strategy offsite agendas.

That is where the real work begins.

Next week: Building the Possibility Set. Before you choose a direction, you need genuine options on the table. Most teams default to Option A without realizing they never built a real Option B (or C).

Most strategy engagements take too long to produce anything useful.

You hire a consultant. Three months later, you have a thick report, a slide deck, and a roadmap that was outdated before the ink dried.

There is a better way to start. It is called a Strategy Sprint.

A Sprint is 30 days of structured work that delivers clarity on the real problem, your realistic options, and the logic connecting them. It does not produce a final strategy. It produces the foundation you need to build one.

Thirty days. Five deliverables. Clarity without premature commitment.

WHAT A SPRINT IS NOT

Before describing what a Sprint is, it helps to clear out the lookalikes.

A Sprint is not a discovery phase. Discovery phases in traditional consulting are open-ended. The consultant learns about your business, interviews stakeholders, and eventually proposes a scope of work. That can take months and often leads to a larger engagement, whether you need one or not.

A Sprint is not a strategic plan. A strategic plan has budgets, timelines, and accountability structures. It is the output of the strategy, not the strategy itself. SPRINT does not produce a plan. It produces the clarity needed to make a plan worthwhile.

A Sprint is not a workshop. A one-day or two-day offsite can surface energy and ideas. What it rarely produces is a disciplined analysis of your actual competitive position. Good intentions are not a substitute for a structured diagnosis.

The Sprint is none of these. It is something more specific.

WHAT A SPRINT IS

A Strategy Sprint is a 30-day structured engagement focused on one question: what is the real problem, and what are the genuine options for addressing it?

That sounds simple. It is not easy.

Most leadership teams have never formally named their strategic problem. They have symptoms, challenges, goals, and concerns. They do not have a crisp, agreed-upon problem statement. The Sprint starts there.

In Week 10, we will go deep on the problem statement. For now, understand this: if your team cannot agree on the problem in one sentence, you are not ready to choose a direction. The Sprint creates that agreement.

THE FIVE SPRINT DELIVERABLES

A Sprint produces five things. Each one is concrete. Each one is yours to keep.

1. Problem Statement

A single, agreed sentence describing the core strategic challenge. Not symptoms. Not goals. The actual problem.

2. Strategy Cascade (As-Is)

A map of your current strategy: your winning aspiration, where you play, how you compete. This is often the first time a leadership team has made this explicit. It is almost always revealing.

3. Business Model Canvas v1

A structured view of how your business actually creates and captures value today. This is the starting point for evaluating whether your strategy and your business model are aligned.

4. Priority Uncertainties

The assumptions have high stakes and low confidence. These are the things you must figure out before committing significant resources. Naming them is not a weakness. It is an intellectual discipline.

5. CEO Summary

A one-page synthesis of the above. If your strategy cannot fit on one page, it is not clear enough yet. The CEO Summary is designed for board conversations, investor discussions, and team alignment.

If you cannot explain your strategy on one page, the problem is not the page.

WHO THE SPRINT IS FOR

Not every company needs a Sprint. Some leadership teams already have clarity. They know their problem. They have a working model. They need execution discipline, not diagnosis.

But a Sprint is the right starting point in three situations.

New CEO. You have inherited someone else’s strategy and someone else’s assumptions. Before you commit to a direction, you need to know what is actually true. The Sprint gives you that map without requiring you to blow up the organization in the process.

Major decision pending. An acquisition. A new market. A significant pivot. These are the moments when clarity is most valuable and most absent. The Sprint forces the diagnosis before the commitment.

Strategy debt. The team has been executing on momentum, not strategy. The original logic has drifted. Nobody has stopped to ask whether you are still playing the right game. The Sprint creates that pause.

If any of those fit, keep reading.

HOW 30 DAYS WORKS

The Sprint is structured, not open-ended. The work happens in three phases.

Week 1: Diagnosis. We map current reality. Leadership team interviews. Financial and competitive review. Problem statement drafts. This is where the metaphor exercise from Week 8 pays off. We want to know how the team sees the organization, not just how the org chart describes it.

Weeks 2-3: Possibility Set. We build two or three genuine strategic options. Not variations on the current plan. Real alternatives. Option A does not win by default in a well-run Sprint. The team has to look hard at Options B and C before committing.

Week 4: Synthesis. We complete the five deliverables and stress-test the logic. The CEO Summary is drafted. The priority uncertainties are named. The leadership team is aligned on the problem, the options, and the next questions to answer.

Thirty days. Structured work. Real output.

THE CONNECTION TO CHOICE

In Week 6, we covered the idea that strategy is choice, not aspiration. A mission statement is not a strategy. Real strategy requires specific decisions about where to play and what to say no to.

SPRINT creates the conditions for those choices.

You cannot make good choices without an honest picture of current reality. You cannot make good choices without genuine options on the table. You cannot make good choices when your leadership team is arguing from different maps.

SPRINT addresses all three. It is not the strategy. It is what makes strategy possible.

YOUR MOVE THIS WEEK

One diagnostic question:

If your top three leaders each wrote one sentence describing your current strategic challenge, would the sentences be compatible?

Not identical. Compatible.

If the answer is yes, your team has the shared picture needed to move forward. If the answer is no or you are not sure, that is your starting point.

SPRINT is designed for exactly this situation.

Next week: The Strategic Problem Statement. Why naming the actual problem is harder than it sounds, and what happens when teams skip it.

I ask each member of the leadership team, separately, to tell me what metaphor they use for their company. Not what the company does. How they picture it in their minds.

The answers vary wildly. And that variation tells me more than any financial statement.

The Metaphor Exercise

One executive says the company is a machine. Inputs, outputs, efficiency. If something breaks, you fix the part.

Another says it is a family. Loyalty, relationships, taking care of each other. Conflict feels like betrayal.

A third says it is a war. Competitors are enemies. Market share is territory. Victory means someone else loses.

A fourth says it is a work of art. The product is an expression. Quality matters more than scale. Compromise is failure.

These are not wrong answers. They are revealing answers. Each metaphor shapes how that person thinks about problems, priorities, and tradeoffs.

The machine person wants to optimize. The family person wants harmony. The war person wants to win. The artist wants to create.

When a leadership team holds different metaphors, they talk past each other. They use the same words but mean different things. They disagree about decisions without understanding why.

What the Variation Reveals

The first thing the exercise shows is alignment, or its absence.

If six executives give six different metaphors, they are not on the same page. They have not agreed on what kind of organization they are running. Their strategic debates are really metaphor debates, and nobody knows it.

This is useful information. Before you can choose strategy, you need a shared picture of what you are.

The Metaphor I Push Toward

After I hear their answers, I push the team toward a different frame.

Think of your company as a population. A species. You have individuals within the company, each a little different, each contributing something. You exist within an economic ecosystem alongside other populations: customers, suppliers, competitors, and regulators.

In an ecosystem, you need both cooperation and competition. You cooperate with some species, compete with others. Sometimes you do both with the same player. The boundaries shift.

The goal is not to win a war. Wars end. The goal is not to optimize a machine. Machines become obsolete. The goal is not to preserve a family. Families can become insular.

The goal is to survive and expand. To adapt as conditions change. To find niches where you can thrive. To build the capacity to keep adapting when the next shift comes.

Why This Metaphor Works

The population metaphor does several things.

It makes variation a strength. A healthy population has diversity. Different individuals, different capabilities, different perspectives. When the environment shifts, some variants are better suited than others. The population adapts.

It makes competition normal. Ecosystems have competition. It is not personal. It is structural. You do not hate your competitors. You outcompete them or find a different niche.

It makes the time horizon long. Species think in generations. They do not optimize for this quarter. They build reproductive capacity, resilience, and adaptability. Short-term sacrifice for long-term survival is natural.

It makes sensing essential. Species that do not notice environmental changes go extinct. Populations that sense and respond quickly survive. Continuous awareness is not optional.

The Connection to Strategy

Every tool I use with clients connects to this frame.

The Weekly Assumption Scan is sensing. You monitor the environment for shifts.

The Possibility Set is diversity. You maintain strategic options like genetic variation.

The Strategy Arcade is stress testing. You simulate environmental shocks before they arrive.

Continuous governance is adaptation. You keep adjusting as conditions change.

I learned to see systems this way in forests and wetlands, studying actual populations. The logic transfers. Companies are not machines. They are living systems competing to survive.

Once a leadership team shares that metaphor, strategy conversations change. They stop arguing about whether to optimize or harmonize. They start asking: what does survival require?

None of this is wrong. Input is valuable. Analysis helps. But at the moment of decision, strategy cannot be delegated.

Here is why.

Strategy Requires Tradeoffs

As I wrote last week, strategy is choice. Real strategy closes doors. It says: we will serve these customers and not those, compete this way and not that, invest here and not there.

Tradeoffs create losers. The business unit that loses investment. The executive whose pet project gets cut. The function that shrinks while another grows.

Only the CEO has the authority to make those calls stick. A chief strategy officer can recommend. A consultant can analyze. But when someone’s budget gets cut or their initiative gets killed, they will appeal. They will escalate. They will work around.

If the CEO did not make the decision, it will not hold.

Strategy Requires Integration

A company’s strategy must hold together. The market position, the capabilities, the operating model, the financial structure, they all need to fit.

No one else sees the whole picture. The head of sales sees the market. The head of operations sees the cost structure. The CFO sees the financials. The head of product sees the roadmap.

Only the CEO sits at the intersection. Only the CEO can see where the pieces connect and where they conflict. Only the CEO can make the judgment calls when functions want different things.

Delegation fragments this view. Each delegate optimizes their piece. The whole suffers.

What Happens When CEOs Try to Delegate

I have seen the same pattern many times.

A CEO hires a strategy consulting firm. The firm does excellent analysis. They produce a thick deck with market data, competitive benchmarks, and three strategic options.

The CEO reviews the deck. They pick Option B. They announce the new strategy. They move on to other priorities.

Six months later, nothing has changed. The organization is still doing what it was doing before. Middle managers ignored the new direction because the CEO did not enforce it. Executives pursued their own agendas because the CEO did not resolve conflicts.

The strategy was never real. It was a document the CEO approved, not a set of choices the CEO owned.

Owning Means Deciding, Enforcing, and Revising

CEO ownership has three parts.

First, the CEO must decide. Not approve someone else’s recommendation. Decide. This means understanding the options deeply enough to defend the choice. It means being able to explain why this path and not that one. It means being ready to answer when a board member or investor asks hard questions.

Second, the CEO must enforce. When an initiative contradicts the strategy, the CEO kills it. When a leader works around the direction, the CEO corrects them. When resource allocation drifts, the CEO pulls it back. This is not micromanagement. It is making strategy real.

Third, the CEO must revise. Conditions change. Assumptions prove wrong. The CEO must notice when the strategy needs adjustment and have the authority to adjust it. A delegated strategy becomes rigid because the delegates lack permission to change it.

The Role of Help

None of this means the CEO works alone. Good strategy requires input the CEO cannot generate themselves.

Consultants can bring outside perspective. They see patterns across industries. They ask questions insiders have stopped asking. They challenge assumptions that have become invisible.

Staff can do analysis. They can gather data, model scenarios, and prepare options. They can identify uncertainties and surface risks.

The leadership team can test thinking. They know the organization’s capabilities and limits. They see implementation challenges the CEO might miss.

All of this is valuable. But it is input to a decision, not a substitute for one.

The CEO takes the input, makes the choice, and owns the result. The moment that ownership transfers to someone else, the strategy loses force.

What This Means for How I Work

When I work with clients, I do not deliver a strategy deck and leave. I work with the CEO to build their capability to make and own strategic choices.

The Strategy Maturity Session is a conversation with the CEO, not a presentation to them. We assess where they are, what they understand, what they are avoiding. The output is clarity about what the CEO needs to decide, not a decision made for them.

In Sprint, we generate options and test logic together. The CEO is in the room, wrestling with tradeoffs, not reviewing a finished product.

This is harder than handing over a deck. It is also the only way strategy becomes real.

The Question for You

If you are a CEO, ask yourself: do I own my company’s strategy?

Not “did I approve it.” Do I own it?

Can I explain, without notes, where we compete and why we win? Can I articulate what we stopped doing because of this strategy? Do I enforce it when people drift?

If the answers are no, you have a strategy document. You do not have a strategy.

The work is yours. No one else can do it for you.

They have mission statements about being the leading provider or delivering exceptional value. They have vision statements about transforming industries. They have core values lists, annual goals, and thick planning documents.

None of that is strategy.

Strategy is choice. Specifically, it is choosing where to compete and how to win, and, just as important, choosing what you will not do.

The Aspiration Trap

Aspirations are comfortable. “We will be the preferred partner for innovative solutions” offends no one. It commits to nothing. It requires no sacrifice.

Strategy is uncomfortable. It says: we will serve these customers and not those. We will compete on this basis and not that. We will invest in these capabilities and let others atrophy.

The reason most companies have aspirations instead of strategy is that strategy requires saying no. And saying no is hard.

Saying no to a customer segment means walking away from revenue. Saying no to a product line means admitting it was a mistake. Saying no to a geographic market means telling someone their pet project is over.

Leaders avoid these conversations. Instead, they write mission statements broad enough to include everything. They call it strategy. It is not.

What Real Strategy Looks Like

Roger Martin, who has studied strategy for decades, defines it as an integrated set of choices that positions an organization to win. The key word is choices.

A real strategy answers five questions. What is our winning aspiration? Where will we play? How will we win? What capabilities must we have? What management systems do we need?

The hard work is in questions two and three. Where will we play forces you to define boundaries. How will we win forces you to commit to a way of competing that is different from your rivals.

If your answer to “how will we win” is “by being better,” you do not have a strategy. Everyone claims to be better. The question is: better at what, for whom, in a way competitors cannot easily match?

The Test

Here is a simple test for whether you have strategy or aspiration.

Look at your strategy document and ask: what have we decided not to do because of this?

If the answer is nothing, you have an aspiration.

A real strategy closes doors. It says: we will not pursue customers who buy primarily on price. We will not expand into markets where we lack the capabilities to win. We will not build products that dilute our focus.

These are painful commitments. That is why they matter. If your strategy does not hurt a little, it is not making real choices.

Why This Matters When Pressure Arrives

Aspirations collapse under pressure. When revenue drops or a competitor attacks, a broad mission statement gives you no guidance. Everything seems worth protecting. Resources get spread thin. The organization flails.

Strategy provides a decision framework. When pressure arrives, you know what to protect and what to sacrifice. You know which customers matter most and which you can afford to lose. You know where to double down and where to retreat.

This is not about being rigid. Strategy should adapt as conditions change. But adaptation requires something to adapt from. A clear set of choices can be revised. Vague aspirations just dissolve.

The Possibility Set

In the Sprint process I use with clients, we force choices through what I call the Possibility Set. Before committing to any direction, we articulate three to five genuinely different strategic options.

Not variations on a theme. Different answers to “where will we play” and “how will we win.”

Option A might be: focus on enterprise customers in the Northeast, competing on integration and support. Option B might be: expand to mid-market nationally, competing on price and simplicity. Option C might be: build a platform that others sell, competing on ecosystem and reach.

These are different strategies. Each requires different capabilities, different investments, different tradeoffs.

The discipline of generating real options prevents premature commitment. It forces you to see alternatives before you choose. And when you do choose, you know what you are choosing against.

What Would Have to Be True

After generating options, we ask: what would have to be true for each option to be a winning strategy?

This is not “what do we hope is true.” It is the conditions that must hold for the strategy to work.

For Option A to win, it might require: enterprise buyers value integration enough to pay a premium, our support capability is genuinely superior, and competitors cannot match our integration depth within three years.

For Option B, the conditions are different: mid-market buyers are underserved by current options, our cost structure allows sustainable low pricing, and scaling nationally does not require capabilities we lack.

Writing out these conditions turns strategy from argument into analysis. Instead of debating opinions, you test assumptions. You figure out which uncertainties matter most. You make better choices.

The Work Ahead

If you do not have a strategy, you have work to do. Not mission statement work. Choice work.

Start by articulating where you actually compete today. Not where you want to compete. Where you win and why. Then ask: is this where we should compete going forward? If not, what changes?

The goal is a small number of clear commitments. Customers you will serve. Ways you will win. Capabilities you will build. Things you will stop doing.

That is strategy. Everything else is aspiration.

Leaders skip the hard work of seeing their situation clearly. They rush to solutions. They build plans on assumptions they never tested. Then reality arrives, and the strategy collapses.

The first discipline of strategy is not choosing a direction. It is seeing the terrain.

Why Diagnosis Gets Skipped

Diagnosis is uncomfortable. It means admitting what you do not know. It means looking at problems you would rather not see. It means accepting that the story you have been telling yourself and your board may not be true.

Leaders face pressure to act. Boards want plans. Employees want certainty. Investors want growth projections. Nobody wants to hear “we need three months to understand what is actually happening.”

So leaders skip ahead. They pick a direction based on intuition, industry trends, or what worked at their last company. Sometimes they get lucky. More often, they build a strategy on sand.

What Confronting Reality Means

Confronting reality is not pessimism. It is seeing what is actually happening, without the filter of what you wish were true.

This means looking at your market position honestly. Not your brand promise, but what customers actually think when they compare you to alternatives. Not your stated differentiation, but the real reasons customers choose you or choose someone else.

It means understanding your organization’s true capabilities. Not the capabilities on your website, but what your people can actually deliver under pressure. Not your stated culture, but how decisions really get made when resources are tight.

It means seeing the feedback loops in your system. When sales decline, does the organization respond with better products or with more discounting? When a competitor moves, does information flow quickly to decision makers, or does it get filtered through layers until urgency disappears?

The Traps That Block Clear Seeing

Three traps prevent leaders from confronting reality.

The first is success. Organizations that have won in the past assume they understand why. They attribute success to their strategy when luck or market tailwinds did most of the work. They stop questioning because questioning feels disloyal to what got them here.

The second is consensus. Leadership teams develop shared assumptions that nobody challenges. The assumptions become invisible. “Our customers value quality over price” becomes fact, even when no one has tested it in years. Dissent feels risky, so people stay quiet.

The third is speed. The pressure to move fast crowds out reflection. Leaders mistake activity for progress. They launch initiatives before understanding problems. They solve the wrong things quickly.

What to Look For

If you want to see your situation more clearly, start with these questions.

What do customers say about us when we are not in the room? Not in surveys, which invite polite answers. In conversations with people who have no reason to flatter you. The gap between your brand story and their actual experience is diagnostic.

Where do we lose deals? Not the deals you never had a chance to win. The ones where you were a serious contender and something went wrong. The pattern in those losses tells you more than the pattern in your wins.

What decisions take too long? Slow decisions reveal unclear authority, competing priorities, or fear of accountability. They signal where the organization’s structure fights its strategy.

What information do leaders not see? Every organization filters information as it moves up. By the time it reaches executives, bad news has been softened and context has been stripped. Find out what is getting filtered and why.

Where are we fooling ourselves? Every leadership team has at least one belief that feels true but is not. Often, it is about competitive position. Sometimes it is about internal capability. The question is whether you have the discipline to find it before the market does.

The Payoff

Leaders who confront reality catch problems earlier. They notice market shifts before competitors do. They make choices based on what is happening rather than what they hope is happening.

This does not mean paralysis. Diagnosis should lead to action. But action built on clear sight is different from action built on assumption. It adapts when conditions change. It survives contact with reality because it was built on reality.

The Weekly Assumption Scan I described last week is one tool for this. Every week, your leadership team should ask: “What do we believe that we have not tested recently? What would change our strategy if it turned out to be wrong?”

This is not comfortable. It is necessary.

Strategy begins with seeing. Get that right, and the choices become clearer. Get it wrong, and even brilliant execution leads nowhere.

In biology, metabolism is how your body converts fuel into energy. High metabolism means efficient processing, quick adaptation to environmental changes, and fast self-repair.

In business, Strategic Metabolism is how your leadership team converts market signals into coordinated decisions. And most mid-market firms are running dangerously slow.

The Annual Planning Trap

Here’s the pattern I see in companies between $20M and $50M in revenue:

Every fall, the leadership team disappears for two days. They emerge with a strategic plan. It goes into a binder. The binder goes on a shelf. For the next eleven months, everyone executes against assumptions that were already stale by Thanksgiving. Deployment to employees? Not so much.

This is “Low Strategic Metabolism.” A massive annual feast followed by months of sluggish digestion. By the time the organization realizes the market has shifted, it’s too bloated with old assumptions to move. This is “Strategy Debt.”

Rita McGrath calls this the danger of treating competitive advantage as sustainable. It isn’t. Advantages erode. Customers shift. Competitors adapt. Technology moves. The companies that win aren’t the ones with the best strategy in January. They’re the ones who can update their strategy in March without calling an emergency board meeting.

What High Strategic Metabolism Looks Like

A leadership team with high strategic metabolism does three things differently:

They process new information weekly, not annually. They eliminate strategic waste quarterly. And they push decision rights down to the people closest to the data.

This isn’t about working faster. It’s about building a cadence of organizational habits that makes adaptation routine instead of heroic.

My college major was biology. I spent years studying ecosystems, feedback loops, and how organisms adapt to environmental pressure. The lesson that stuck: survival doesn’t go to the strongest or the smartest. It goes to the most responsive.

The same is true for your company.

Ritual 1: The Weekly Assumption Scan

Every strategy rests on assumptions. You assumed your biggest customer would renew. You assumed your competitor wouldn’t cut prices. You assumed the regulation wouldn’t pass until next year.

Most leadership teams never revisit these assumptions until something breaks.

The fix takes ten minutes per week. At the end of your regular leadership meeting, ask one question: “What did we learn this week that makes our strategy more or less valid?” Ask what core assumptions underlying your strategy seem to be shifting. This keeps attention on both what and why of the strategy.

Not “what happened this week.” That’s a status update. The question is narrower: what new information challenges or confirms the bets we’ve already made? That’s an Assumption Audit.

This isn’t about changing strategy every week. It’s about noticing when the ground shifts before you fall into the hole.

Write down what you learn. Review the list monthly. Patterns will emerge.

Ritual 2: The Quarterly Burn

Every organization accumulates strategic debt. Projects that made sense two years ago but now consume resources without generating results. Initiatives that nobody wants to kill because someone important sponsored them. Meetings that exist because they’ve always existed.

Good strategy requires choosing what not to do. But most leadership teams are better at adding priorities than subtracting them.

Every 90 days, schedule a two-hour session with one purpose: identify what to stop. Not pause. Stop.

The test is simple. For each active initiative, ask: “If we weren’t already doing this, would we start it today?” Be aware of the Sunk Cost Bias. If the answer is no, cut it. Redirect the resources to something that matters.

This is uncomfortable. It requires admitting that past decisions were wrong or that conditions changed. But the alternative is worse. Low-metabolism organizations die slowly, suffocated by their own accumulated commitments.

Ritual 3: Distributed Decision Rights

Here’s a question: if your market shifted by 20% tomorrow, how many layers of approval would it take for your front-line team to respond?

In most mid-market companies, the answer is “too many.” A salesperson notices a competitor undercutting on price. They escalate to their manager. The manager escalates to the VP. The VP schedules time with the CEO. By the time a decision gets made, the customer is gone.

High-metabolism organizations push decision rights down to the people closest to the information. Not every decision. Not bet-the-company choices. But the micro-pivots that compound into strategic agility.

This requires two things. First, strategic clarity across the company. If people don’t understand where you’re trying to win and how, they can’t make good judgment calls. Second, trust. You have to believe that people will make reasonable decisions even when you’re not in the room.

The CEO’s job isn’t to make every decision. It’s to build a system where good decisions happen without top-level executive involvement.

The Bottom Line

The winners of 2026 won’t be the companies with the best PowerPoint decks. They’ll be the ones who can digest a market shift on Monday and have a coordinated response by Friday.

That doesn’t require genius. It requires three rituals practiced consistently:

Scan your assumptions weekly. Burn your dead weight quarterly. Push decisions to the people with the data.

Do this for a year and you won’t recognize your organization. You’ll have built something most mid-market companies lack: a leadership team that can adapt as fast as the market demands.

Question for the week: When was the last time your leadership team killed a project that was “working fine” but no longer fit your strategy?

When you originally subscribed to CEO Growth Snapshot, the focus was on broad concepts for growing mid-market businesses, drawn from leading business sources. But leading a company has changed a lot, especially for those of us in the DMV business community.

Big changes in technology and federal government policy have made the traditional, static, multi-year strategic plan nearly obsolete.

Success isn’t about following a rigid, long-term roadmap. It’s about having high Strategic Metabolism. This is your company’s ability to anticipate market shifts, challenge assumptions, digest new data, and make effective decisions faster than your competitors. Strategy itself has evolved from a planning document to an agile capability.

To better serve you in this new reality, I launched a new company, Haas Strategy Solutions (HSS), and I am upgrading your old AEG subscription to my new publication: Strategy Snapshot.

What is Strategy Snapshot?

This is where I share the practical, field-tested frameworks I use with leadership teams at $5M–$100M firms.

Instead of general theories, every week you’ll get actionable insights designed to help your executive team move from reactive firefighting to disciplined strategic governance. Our focus is on building the clarity, confidence, and control needed to navigate a constantly shifting environment and make valid and impactful decisions.

What happens next?

You don’t need to do anything. Your subscription has already been transferred, and you will start receiving regular insights soon.

I respect your inbox. Saying “no” is a strategic power. If your professional focus has changed and this no longer feels relevant, you can unsubscribe using the link at the bottom of this email. I suggest you explore these tools for a few weeks to see if there is a million-dollar idea waiting for you.

But if you are facing the challenge of leading a growing organization through unpredictable markets, welcome. I look forward to sharing the tools that are working right now and to your joining the conversation.

To your stronger metabolism.

P.S. Most "Low Metabolism" teams I work with aren't lazy. They’re just stuck in their 12-month rhythm in a 3-month world. If you’re curious about where your team's decision-making is bottlenecked, let's grab 20 minutes to find the signal in the noise. You can schedule a brief introductory call here. We’ll determine the best path forward for your team.

That model is not wrong. It is incomplete. And for many companies, it has become dangerous.

The assumption behind sustainable advantage is that markets move slowly enough for barriers to hold. But the forces that once protected advantages have weakened. Technology spreads faster. Information is harder to hoard. Competitors emerge from unexpected places. Customers switch more easily than before.

The result is that advantages have a shorter half-life. What took a decade to erode now takes three years. What took three years now takes one. Companies that build strategy around defending a single advantage often find themselves defending a position that no longer matters.

The Evidence

Rita McGrath, a professor at Columbia Business School, studied this pattern across industries. Her research found that the average time a company stays in the top quartile of profitability has declined steadily. Companies fall from industry leadership faster than they used to. The ones that sustain performance are not the ones with the strongest barriers. They are the ones that continuously build new advantages as old ones fade.

This matches what I have seen in 30 years of consulting. The companies that struggle most are often the ones that succeeded for a long time. They built a strong position, defended it well, and then watched it erode as the market shifted underneath them. Their strategy was sound. It was also static.

The companies that thrive treat advantage as temporary by design. They do not wait for an advantage to erode before building the next one. They assume every edge has an expiration date and plan accordingly.

What Transient Advantage Means

If advantages are temporary, strategy has to change in three ways.

First, strategy becomes continuous. The old model treated strategy as a periodic event. Every three to five years, you conduct a strategic review, set a new direction, and execute until the next review. In a world of transient advantage, that cycle is too slow. By the time you complete a five-year plan, the conditions that shaped it may have changed twice.

Continuous strategy does not mean constant chaos. It means building a rhythm of regular review, testing, and adjustment. Quarterly, not annually. You hold the direction steady while adjusting the specifics as conditions shift.

Second, you manage a portfolio of advantages, not a single position. Instead of betting everything on one edge, you cultivate multiple advantages at different stages. Some are mature and generating returns. Some are emerging and require investment. Some are fading and need to be wound down. The goal is a pipeline, not a fortress.

Third, you get better at exits. The hardest part of transient advantage is knowing when to stop. Leaders fall in love with the positions that built the company. They defend advantages past their expiration date, pouring resources into battles they cannot win. Strategic discipline means recognizing when an advantage has run its course and redeploying resources before returns turn negative.

The Emotional Challenge

This is harder than it sounds. Sustainable advantage is comforting. You find your edge, build your moat, and protect it. There is clarity in defense. You know what you are protecting and why.

Transient advantage is less comfortable. You build something valuable, knowing it will fade. You invest in new positions before the old ones fail, which feels like abandoning what works. You exit businesses that still make money because you see the decline coming. This requires a different emotional relationship with strategy.

I have watched CEOs struggle with this transition. They understand the logic. They see that their industry is changing faster than it used to. But when it comes time to wind down a legacy business or cannibalize a profitable product line, they hesitate. The old advantage feels real. The new one feels speculative. So they defend the old position too long and arrive late to the new one.

The companies that manage transient advantage well treat this as a discipline, not a feeling. They build triggers and signposts that tell them when an advantage is peaking, when it is declining, and when it is time to exit. They make the decision in advance, based on evidence, so they do not have to make it in the moment, based on emotion.

What This Means for Your Strategy

If you lead a company in the $5-100 million range, you are not immune to this shift. In some ways, you are more exposed. Large companies can sustain declining advantages longer because they have more resources to burn. Midsize companies feel the pressure faster.

Here is what I would ask:

How old is your current advantage? If your competitive edge is more than five years old and you have not refreshed it significantly, it may be weaker than you think. Competitors have had time to study it, copy it, or route around it.

What is your next advantage? If you cannot answer this question, your strategy is incomplete. You should be able to point to the emerging positions that will generate value when your current edge fades.

How would you know if your advantage is eroding? What signals would you see in customer behavior, pricing power, or competitive activity? If you do not have clear signposts, you may not notice the decline until it is too late to respond.

Do you have the discipline to exit? Have you ever voluntarily walked away from a profitable position because you saw decline coming? If not, you may have a bias toward defending too long.

The Shift in Mindset

Sustainable advantage asked: How do I protect what I have?
Transient advantage asks: How do I continuously build what is next?

Both questions matter. You still need to execute your current position well. But if you only ask the first question, you will eventually run out of advantage to protect.

Strategy in a world of transient advantage is not more complicated. It is more continuous. The tools are the same. The choices are the same. What changes is the rhythm. You make strategic choices more frequently, test them more regularly, and adjust them more willingly.

This is not comfortable. But it matches how markets actually work. And companies that embrace it outperform those that keep waiting for their advantage to become sustainable again.

(Hint: It won’t).

Strategy is not a static document gathering dust in a binder. It is a continuous leadership behavior.

Most organizations today are drowning in Strategy Debt. This is the friction caused by vague choices, artificial alignment, and a lack of clear governance. When you have high Strategy Debt, your team moves slowly, second-guesses decisions, and struggles to pivot when the market shifts.

To solve this, you must measure your Strategic Metabolism: the speed at which your leadership team can learn, correct, and pivot.

The Audit

Answer these 10 questions honestly. If you cannot answer more than three with absolute certainty, you aren’t alone. You are simply operating in a “strategic fog” that is costing you time and capital.

1. The “No” Test: Can you name three specific market opportunities or projects you have explicitly decided NOT to pursue in the last six months?

2. The “WWHTBT” Filter: For your #1 strategic priority, can your team list the five specific things that “Would Have To Be True” for it to succeed?

3. The Evidence Gap: Is your current strategy based on validated market signals, or is it built on internal assumptions and “As-Is” historical data?

4. The Logic of Choice: If your strategy was “Red Teamed” today, what is the first thing that would break, and how fast would you know?

5. The Alignment Check: If I asked your top five leaders to define “How we win,” would I get five identical answers or five different versions of the truth?

6. The Capability Reality: Do you have a “Capability Gap Map” identifying the specific skills your team lacks to execute your 12-month plan?

7. The Governance Rhythm: Does your team treat strategy as an “annual event” or as a monthly discipline with structured resets?

8. The Feedback Loop: Do you have “Signposts” in place—data points that tell you when to pivot—before the financial results come in?

9. The Trust Barrier: Can your team engage in “fierce conversations” about strategic failure without it becoming personal or political?

10. The Speed of Correction: How long does it take for a market reality (e.g., a customer loss) to result in a change to your resource allocation?

What Your Score Means

• 0–3 (High Strategy Debt): You are likely firefighting. You need Strategic Clarity.

• 4–7 (Moderate Strategy Debt): You have a plan, but your assumptions are untested. You need Strategic Confidence.

• 8–10 (Low Strategy Debt): You have a system. Your focus is now on Strategic Control.

Next Steps to Clarity, Confidence, and Control

If this audit revealed gaps in your organization’s metabolism, we should move from diagnosis to action.

• The Diagnostic: Book a 1-on-1 Strategy Conversation. We will map your organization against our 5-level maturity model and build your roadmap for the year.

• The Alignment: Most leadership teams aren't misaligned because they disagree; they are misaligned because they aren't speaking the same language. Our PRIME service is a high-velocity, one-day clinical intervention designed to surface those truths, align the team’s vocabulary, and establish an objective, shared logic of reality. Take a closer look at PRIME to see how to calibrate your leadership.

Strategy is a behavior. Let’s start improving yours today.

This is not wordplay. The distinction is practical. Strategy is the act of making choices about where to compete and how to win. Strategic planning is the process of documenting goals, timelines, and activities. One requires difficult tradeoffs. The other organizes work that has already been decided.

When I ask CEOs to show me their strategy, they usually hand me a document. It contains a mission statement, a vision, a list of values, some financial targets, and a set of initiatives with owners and deadlines. This is a plan. It tells me what the company intends to do. It does not tell me what the company has decided not to do, or why its chosen approach will beat the alternatives.

The Test

Here is a simple test. Look at your strategy document and ask: what have we decided to stop doing, or never do, because of this strategy?

If the answer is nothing, you have a plan, not a strategy.

Strategy requires tradeoffs. If you try to serve every customer segment, you serve none of them well. If you compete on price and quality and service and innovation, you spread resources so thin that you lose on all four. A real strategy chooses some customers over others, some capabilities over others, some geographies or channels over others.

Roger Martin, the former dean of the Rotman School of Management, puts it this way: a strategy is a set of choices that positions you to win. If you cannot explain what you’ve chosen and what you’ve chosen against, you do not yet have a strategy.

Why This Matters

Plans fail when conditions change. Strategies adapt.

A plan says: “We will launch three new products, expand into two new markets, and grow revenue 15% next year”. When a recession hits, or a competitor undercuts your pricing, or a key supplier fails, the plan breaks. Leaders scramble to revise timelines and cut budgets, but they have no framework for deciding what to protect and what to sacrifice.

A strategy says: “We win by being the most reliable provider to mid-sized manufacturers in the Midwest who value uptime over price”. When pressure arrives, that clarity guides every decision. You protect reliability investments. You avoid the temptation to chase price-sensitive customers. You double down on the Midwest instead of diluting focus with national expansion.

The strategy does not prevent disruption. It provides a decision-making framework when disruption arrives.

How Companies Confuse the Two

The confusion happens because strategic planning feels like strategy. The process is serious. Leaders gather data, conduct analyses, hold off-site meetings, and produce impressive documents. The work feels strategic.

But the output is often a list of activities, not a set of choices. The plan says what we will do. It does not explain why this approach wins or what alternatives were rejected.

I have seen this pattern repeatedly. A leadership team spends three months building a strategic plan. They emerge with a 40-page document, a balanced scorecard, and a set of initiatives. Everyone feels aligned. Then a new competitor enters the market, or a major customer leaves, or technology shifts the economics of their industry. Within six months, the plan is irrelevant. Not because conditions changed, but because the plan never answered the fundamental question: what is our theory of winning?

The Five Questions

Martin’s framework asks five questions that separate strategy from planning:

1. What is our winning aspiration? Not a vague mission, but a concrete statement of what winning looks like.

2. Where will we play? Which customers, geographies, channels, and product categories will we focus on, and which will we avoid?

3. How will we win? What is our distinctive approach that allows us to beat competitors in our chosen arena?

4. What capabilities must we have? What do we need to be exceptionally good at to deliver on our how-to-win choice?

5. What management systems are required? What processes, structures, and metrics will support and reinforce our choices?

A strategic plan might answer questions four and five. A strategy answers all five, in sequence, with each answer constraining the next.

What to Do About It

If you suspect you have a plan but not a strategy, here is where to start.

First, articulate your theory of winning in one paragraph. Not what you do, but why your approach beats the alternatives. If you cannot write this paragraph, you do not yet have a strategy.

Second, list what you have decided not to do. Which customer segments are you deliberately ignoring? Which product categories will you not enter? Which competitors will you not try to match? If this list is empty, your strategy is not yet sharp enough.

Third, test your choices against pressure. If your largest customer left, would your strategy still make sense? If a competitor cut prices 20%, would you follow, or would your strategy give you a reason to hold? If the answer is “it depends,” your strategy is not doing its job.

Strategy is not a document. It is a way of making decisions. The document exists only to capture and communicate the choices so everyone in the organization can make consistent decisions without checking with the CEO.

The Payoff

Companies with clear strategies move faster. Not because they plan better, but because they waste less time debating choices that have already been made. When a new opportunity appears, leaders can quickly assess whether it fits the strategy or distracts from it. When pressure arrives, they know what to protect and what to sacrifice.

Companies with plans but no strategy move more slowly. Every significant decision becomes a negotiation because there is no shared framework for choosing. Leaders optimize their own functions rather than the whole. Resources are spread across too many priorities, and nothing gets done with excellence.

The distinction between strategy and strategic planning is not academic. It shows up in how fast you make decisions, how aligned your team stays under pressure, and whether your direction survives the first real test.

Most companies need fewer planning processes and more strategic clarity. The plan can come later, once you know what you’re actually trying to win.

About the Author

Mark Haas is the founder of Haas Strategy Solutions (HSS). With decades of experience advising $5M–$100M organizations, he helps CEOs trade “Strategy Debt” for Strategic Control. Through a disciplined focus on Strategic Metabolism, HSS installs the governance and behaviors required to pivot faster than the market.

Ready to find your signal in the noise?

• The Insight: Subscribe to the Strategic Pulse for weekly briefings on retiring Strategy Debt.

• The Diagnostic: Request a Strategy Maturity Session to audit your team’s alignment.

• The Partnership: Explore our Sprint, Build, and System engagements at Haas Strategy Solutions.