A CEO once told me, “Our strategy is solid. We just need to execute.”
I asked, “What could stop you from executing?”
He didn’t hesitate. “People. Systems. Time.”
That’s not a bad answer. It’s honest. But it’s also a signal that the strategy is still sitting on top of a shaky foundation—because what he was really saying was, “Our bet depends on capabilities we’re not sure we have.”
And that’s how most strategies fail in a very predictable way.
They assume conditions that aren’t true yet. They assume behaviors will magically change because the slide looks convincing. They assume the organization can deliver a promise it has never delivered consistently.
So yes, you can call it a Must-Be-True list.
But the real point is bigger than a list.
This is a capability check—the step that turns Bold Bets from a confident declaration into a grounded commitment.
It’s also the step most planning sessions skip, because it forces leaders to face reality before they announce victory.
The quiet danger: strategies that sound right
Some strategies are obviously unrealistic. Everyone can feel it.
But the most dangerous strategies are the ones that sound reasonable. They sound so reasonable that teams rush to planning. They build initiatives. They assign owners. They add KPIs. The machine starts moving.
And then execution slows down.
Not because people aren’t trying.
Because the strategy required a level of capability the system can’t deliver.
So the team compensates with heroics. More overtime. More follow-ups. More escalations. More meetings. More pressure. For a while, it works—until it breaks.
Bold Bets isn’t supposed to run on heroics.
Bold Bets is supposed to run on capability.
That’s why this step matters.
What this step really is
A Must-Be-True list sounds like paperwork. A capability check sounds like leadership.
Here’s the real question you’re answering:
If this Bold Bet is going to earn Obvious Choice—and deserve Only Choice—what capabilities must exist inside our organization for that to be true?
Notice what changes. You’re not just listing assumptions. You’re naming the muscles that must be built. You’re translating “how we win” into what the organization must be able to do repeatedly—especially under pressure.
If your advantage depends on speed, then speed must be operationally possible. If your advantage depends on trust, trust must be consistently earned through frontline behavior. If your advantage depends on specialization, expertise must be developed and protected, not merely claimed.
This step makes those dependencies visible.
And once they’re visible, leaders can no longer hide behind “We just need discipline.”
Why most teams skip it
They skip it for three reasons, and all three feel reasonable—until Monday arrives.
First, it feels like slowing down. Leaders want momentum. The team wants to “move forward.” A capability check feels like asking hard questions when everyone wants a plan. But a plan built on missing capability is not momentum. It’s motion.
Second, it creates uncomfortable truth. You might discover that your Bold Bet requires capabilities you don’t have, and that’s not the vibe people want during a planning workshop. But avoiding the truth doesn’t make it disappear. It just makes it expensive later.
Third, it demands investment. Once you name a missing capability, you can’t pretend execution is just “effort.” You have to build something: training, systems, process redesign, decision rights, incentives, staffing. That’s real work.
But it’s also the work that makes Only Choice possible.
How to do the capability check without turning it into a long document
You don’t need forty statements.
You need enough clarity to expose what will break.
Start where you should always start: your Bold Bet—your “how we win.”
Step 1: Start with your “How we win” and translate it into capabilities
Take your advantage statement and ask:
If we’re going to win this way, what must we be capable of doing—repeatedly, reliably, without heroics?
Write short, testable statements. Not vague virtues.
Not “We must be excellent.”
But “Our turnaround time must stay under 48 hours for 90% of requests.”
Not “We must have great leaders.”
But “Frontline supervisors must be trained and authorized to resolve complaints without escalation.”
The more testable the statement, the more useful it becomes—because it stops being a wish and starts becoming a build target.
Step 2: Use the four capability zones so you don’t blame “people” for everything
Most capability gaps fall into four zones:
People — skills, leadership, behavior, staffing
Process — workflows, handoffs, standards, decision-making
Systems — tools, data, reporting, infrastructure
Offer — product/service design, pricing, packaging, delivery model
This matters because teams love to over-focus on People. “We need more discipline.” “We need better accountability.” Sometimes that’s true.
But often the real issue is Process and Systems. Handoffs are broken. Decision rights are unclear. Data is unreliable. Tools are outdated. The frontline is expected to deliver a premium promise with budget tools and unclear rules.
A capability check corrects that. It stops you from scapegoating effort when the system is the problem.
Step 3: Keep only what the strategy depends on
If it’s not necessary for the bet to work, remove it.
This is not an improvement wishlist.
This is a dependency map.
If this capability is missing, the bet weakens. If it’s built, the bet strengthens. That’s the standard.
A short example you can feel
Let’s say your Bold Bet is:
“We will win by being the fastest and most reliable provider for a premium niche.”
That sounds strong. Now translate it into capabilities:
To win on speed and reliability, these capabilities must exist:
Your service process must be standardized across teams, not reinvented per supervisor. Turnaround time must be predictable, not heroic. Escalations must be resolved within 24 hours. Frontline leaders must have authority to decide in the moment. Delays must be tracked in real time and acted on weekly. And your premium promise must be priced to fund the capability.
Then ask the only question that matters:
Which of these capabilities are currently weak, missing, or unreliable?
That answer becomes your real work.
Not nineteen priorities.
Not “improve operations.”
Real capability moves.
The power move: name what’s not true yet
This is where leadership grows up.
Because the point of this exercise is not to produce a neat list. It’s to admit the gap between your Bold Bet and your current reality—without shame, without drama, and without pretending.
A CEO once read the capability statements and said, quietly, “Okay… half of this isn’t true today.”
That could have been discouraging.
But it was actually liberating.
Because now the team stopped pretending. They stopped blaming execution. They stopped demanding heroics. They started building capability on purpose.
And the moment a team begins building capability, strategy stops being aspirational and becomes achievable.
Only Choice isn’t a claim.
It’s a consequence.
How it connects to your game plan and your rhythm
This capability check is the bridge between strategy and planning.
Once you identify the gaps, you design your next 90-day moves around them. Instead of random initiatives, you focus on what your Bold Bet depends on. And instead of drowning in activity, you build the few capabilities that make Obvious Choice inevitable.
Then your rhythm keeps it alive.
A good monthly strategy review doesn’t just ask, “Are we hitting targets?”
It asks, “Are we building the capabilities that make this bet real?”
That question changes everything, because it keeps leaders focused on capability, not just activity.
A practical push
In your next strategy meeting, add this one line before planning:
“Before we assign owners and timelines, let’s name the capabilities this Bold Bet depends on—and admit what we can’t do consistently yet.”
If your team can do that, you’ll avoid the most common failure of traditional planning: executing a strategy your organization can’t actually support.
If you paste the next article, I’ll sharpen it the same way—and yes, I’ll keep it prose-first, story-forward, and consistent with the Bold Bets brand.
