Strategy is a Rhythm, Not a Waterfall
Stop planning strategy once or twice a year. Run it like your heartbeat.
It’s 11pm and you’re looking at a slide deck that explains why the quarter missed.
Not reading it — you wrote most of it. You’re looking at the space between the slides. The section that says “people” when you were expecting “pipeline.” The chart showing the team executing harder into territory that wasn’t working six months ago and isn’t working now.
The deck has an answer. The answer is wrong.
You already know what you’ll do. Change the person running sales. Bring in a consultant to audit the process. Schedule an offsite, get everyone realigned. These are the moves that are supposed to work. Some of them will work, briefly. The quarter after the change will look better. Then it will flatten again.
Here’s what almost never happens: you stop before acting and ask which element is the constraint.
Not “what’s wrong.”
Not “what should we change.”
Which element in the system broke first?
Until you can name the element, you’re fixing symptoms downstream without getting to the source. Adding process to a prioritization problem. Retraining people around a positioning failure. Moving faster in a direction that was already off.
The cash register isn't ringing. You redesign the store.
The Discipline That Makes You Rigid
Picture the moment the strategy becomes official.
The moment the leadership team nods, the deck gets filed, and the initiative list gets turned into a roadmap.
In that moment, something happens that no one names: the model freezes.
You've hired against them. Budgeted against them. Aligned the team to them. The cost of being wrong compounds from that moment — invisibly, because every week of execution makes the model harder to change.
That’s waterfall. Big planning before building. Review before action. It feels like discipline.
It’s also a trap.
Waterfall pushes uncertainty to the start, then takes away your ability to respond once you’re moving.
You’re investing in research, but research captures stated problems, not where people are headed. Customers can tell you what annoys them. They can’t map the future they’re trying to reach. Research gives you the surface. The thing they’re reaching for shows up only when you build, ship, and watch what they do. Instead, you compress the unknown into one bet, then you lock execution.
So you drive by the rearview mirror.
The measurement problem makes it worse. Planning cycles run on lagging averages: quarterly revenue, survey scores, aggregate churn. That data tells you what happened. It can’t tell you what’s about to happen. Strategy is a bet on what comes next.
By the time the lagging data tells you the bet is wrong, the plan is already six months into execution. You've hired for the bet. Allocated budget for the bet. Aligned the team to the bet. The cost of adjustment climbs with every week you're in motion.
The rigor that felt like discipline becomes the reason you snap.
You don’t see it because the model isn’t a diagram on a wall. It’s the cadence you inherited: the annual offsite that anchors the year, the business review rhythm every team has built around. It doesn’t feel like a choice. It feels like “how we work.”
You call it conviction. It’s a blind spot with a louder voice.
Courage Is a Data Problem
It’s 2am. You’ve been turning the same question over for an hour.
You know what you want to do. The logic holds. But there’s a gap between what the data supports and what you’re about to commit to, and it feels heavy. People who look decisive in moments like this have always seemed like a different species—less bothered by that gap, more willing to move without the certainty you can’t quite get.
You’ve probably called that difference courage.
That frame doesn’t help.
At 2am, the uncertainty is real. You don’t have enough signal to feel steady. When the signal is thin, every action feels like it carries more of you with it. The “courage” you think you need scales with the gap: the farther the jump from what you can see to what you’re signing up for, the braver the move looks. It’s not personality. It’s what happens when you try to decide with blurry numbers.
So the fix isn’t to pump yourself up. It’s to see more clearly.
Quarterly reports are averages. They sand down the edges, flatten the weird stuff, and leave you with a clean story after the fact.
What closes the gap is behavior in motion: what a specific set of customers is doing right now, not what the “average segment” did last quarter. Early patterns that show up before the outcome. Outliers that point somewhere new.
This isn’t a stats argument. It’s a direction problem. The customers at the edge are often the first to move. When you average them away, you lose the clue you needed.
The best early-stage teams didn’t solve this by being braver. They solved it by shortening the loop.
Early-stage teams don’t carry more courage than ones at enterprise. They start with less certainty and change course more often. They learn faster, so the distance between what they know and what they’re betting on stays small. The bet stays close to the signal. The need to “be brave” shrinks.
Not more conviction. Just a shorter learning loop.”
The Harder Discipline
Thursday at 3pm, an early-stage team finishes a customer call with an unexpected signal — not a complaint, not a feature request, but a different framing of the problem. By 5pm, they’ve changed the sales story. By Monday, they’re checking whether it changed anything.
Another team hears the same thing. It lands in a survey. It gets rolled into a quarterly pull. It gets summarized in a deck. It becomes an action item, handed to a workstream, reviewed at the next cycle. By the time it reaches a decision, the early-stage team has already tried two versions and knows which one moved.
The difference isn’t headcount. It’s thestructure of the loop.
Teams running the loop aren't better at strategy because they're smarter. They’re running a system you can actually run. They take a working view of reality, act on it, watch what happens, update, and act again.
Starting with less certainty is what keeps your ability to change. Moving before feeling certain isn’t reckless. You’re keeping ability to respond to what you learn. Waiting for certainty has already hardened the bet. Every week of waiting raises the price of changing course.
And planning events get mistaken for discipline.
The annual offsite. The business review. These are events. They feel strict because they’re structured, because they demand prep, because they pull the exec team into the same room. But an event isn’t a loop. The loop is the discipline.
Not the planning meeting. Not the strategy doc. Not the frozen list of priorities. The loop: run, learn, adjust, run again—often enough that you don’t need to wait for the next event to change.
Rigor lives inside the loop, not in how much you do before you start.
The hard part is knowing what to keep fixed and what to change.
It’s easy to treat flexibility like a mood: stay open, respond to what you learn. True, but vague. It doesn’t tell you what must not move.
Keep the “what” fixed. Your positioning: the change you own for the customer, the job they’re trying to get done, why your approach belongs there. Your priorities turn that into choices. The closer you get to the real problem—beneath the stated one—the more precise your positioning becomes. That precision isn’t optional.
Change the “how.” Process is the how. The how is where you move.
On Thursday, the team didn’t switch problems. They changed how they talked about the problem. Same what. New how. That’s the loop working.
The default is to get this backwards. Stay fuzzy on the what—positioning stays loose, the change you claim stays unnamed—and they clamp down on the how. The process becomes sacred. The playbook can’t move. Fuzzy what, fixed how. That’s waterfall in miniature: executing a process for a bet you can’t say out loud.
A plan is easy. It’s static. You can finish it, present it, approve it, file it.
A learning loop stays in motion. It asks for a different kind of leadership: hold the what steady enough to execute, keep the how loose enough to learn.
At the same time.
That tension is the work. Lock both what and how and you get a plan that can’t change. Stay vague on both and you get a team that can’t act. This only works when the what stays firm and the how stays open.
One question drives everything from here:
Which part is slipping?
The Flywheel Diagnoses Where Strategy Fractured
Here’s what it looks like when positioning breaks.
Sales explains the product one way to one buyer and a different way to the next. Product ships features that serve three conflicting stories. Marketing writes copy that could fit any competitor. The leadership team agrees in the room, then splinters the moment everyone walks out.
Everyone is busy. Nothing compounds.
The reflex is to fix execution: tighten the process, retrain the team, rewrite the messaging. Those are visible moves, so they feel like progress. But they’re downstream. The break is upstream.
You probably don’t need a brand-new strategy. You need to know what snapped.
The Strategy Flywheel is a diagnostic for locating where it broke.
Five elements, each resting on the one above it:
Positioning → Prioritization → Process → Performance → People
The flywheel runs in order. Positioning is the customer change you own. Prioritization is what deserves focus given that change Process is how you deliver the change, on purpose, repeatedly. Performance is how you tell if the change is sticking. People shows who has to act, and whether they can say the why without a script.
Clarity flows from the top. When positioning is clear, priorities stop fighting each other. When priorities are narrow, process can be designed around them. When process is coherent, measures start to mean something. When measures mean something, teams can move without constant executive rescue.
Break the chain anywhere and you’ll see symptoms below it.
This is why the reflex to “fix people” so often fails. The symptoms look like a people problem—slow execution, mixed messages, constant re-explaining. But the cause is usually higher up: fuzzy positioning or scattered priorities showing up at the bottom.
Positioning is the most misread element.
It’s often seen as a messaging problem. The language is off. The pitch needs work. The brand voice isn’t landing. So messaging gets fixed, and six months later the same misalignment reappears.
Because positioning isn’t a messaging problem. It’s a territory problem.
Territory means: what customer change you own, who it’s for, and why you—not anyone else—gets to claim it. That decision sets the boundaries for what you build, what you say, and what you measure.
If you polish the words without choosing the territory, you end up with a clean surface on top of a crooked frame.
Hold the Frame
A team is three weeks into Q2 when the head of sales notices a pattern — not a trend, just three accounts responding differently to the same pitch. She brings it to the Monday sync. By Wednesday, the team has changed what they’re testing. The next planning event is eleven weeks away.
That’s the loop running.
You saw the other version two sections back: the same signal arriving via satisfaction survey, quarterly data pull, QBR deck, action item, workstream, next planning cycle. By the time it reaches a decision, that team has run the experiment twice and knows whether it worked.
That gap is learning velocity — how fast the model improves because it’s in motion.
Your role in that loop isn’t to generate the strategy. It’s to hold the frame — steady enough for execution, loose enough for learning — so the cycle can run without waiting for the next event to authorize adjustment.
The team who gets this right becomes a different kind of bottleneck — not depending on the leader for answers, but the one holding the tension that keeps the model alive.
The plan doesn’t compound. The rhythm does.
Which element in your Flywheel is the constraint?
For the forward view — how to build the Flywheel from Positioning through People — start here: The Strategy Flywheel: How Strategic Clarity Compounds Into Momentum