Essay
When The Playbook Changes
A disciplined approach to consequential decisions at inflection points
Every organization runs on a playbook. It holds hard-won judgment about where to compete, how to win, and how work actually gets done. Most of the time it works, which is why nobody questions it.
Then it stops working.
Sometimes the cause announces itself. A competitor changes the basis of competition, or a technology resets what customers expect. More often it arrives quietly. Growth flattens. A transformation loses momentum. The operating model strains under demands no one designed it to carry. The old answers still sound right in the room and stop producing results outside it.
These moments are more dangerous than they look. Organizations can hesitate when change is needed, or pour more effort into a course that needs to be reconsidered. Urgency produces motion, and motion can feel like progress. Teams pull data, commission studies, stand up workstreams, and build increasingly polished recommendations. Serious work by capable people can still arrive at a bad decision, because it started from the wrong question or settled on an answer before it had earned one.
Over twenty years running global businesses and leading enterprise transformations, I have seen important decisions come apart in a few different ways. A symptom gets promoted to a problem statement. A preferred solution quietly sets the analysis. Dissent shows up after commitment. The execution constraint that will kill the plan surfaces only after the plan has been chosen.
Here’s an example: one global consumer products company drove a successful playbook so effectively that the entire business became increasingly dependent on a handful of brands, products, markets and channels. Strong results reinforced the established playbook, and the company kept pushing the same sources of growth harder, leaving too little room to examine warning signs. The uncomfortable question was the one that mattered most: what would happen if those sources of growth weakened? When that did happen, revenue and profitability fell sharply. What followed was a disruptive restructuring program and significant changes to the operating model. This experience illustrates why a strategy process must ask the tough questions and challenge the assumptions behind success while there is still time to act.
The Metacta Method℠ was developed through experiences like that one. It exists to help leadership find the right path forward when the established playbook no longer fits the situation.
Why capable teams start in the wrong place
Organizations rarely lack intelligence, effort, or data. What they lack is a structure that turns those things into a better decision.
At an inflection point, the visible issue gets there first and takes the seat. A revenue decline becomes a sales problem. Missed milestones become a project management problem. Margin pressure becomes a cost problem. Each framing is defensible. None of them is necessarily the question leadership needs answered.
Framing decides everything downstream: what evidence gets gathered, who gets asked, which options make the list, which risks are taken seriously. A narrow question does not slow a capable organization down. It sends one in the wrong direction, efficiently.
So the Method starts with a rule. Questions Before Answers means that before any diagnosis begins, we establish what is actually being decided, why it is being decided now, and which assumptions have already been carried into the room. That last one matters most. By the time an inflection point reaches the leadership team, the framing has usually been inherited from whoever escalated it.
A disciplined path from uncertainty to action
The Metacta Method organizes the work into six phases: Frame, Diagnose, Options, Challenge, Decide, and Act. Each does one leadership job and hands off to the next.
The Metacta Method℠ connects six distinct leadership jobs, from framing the question through putting the decision into action.
FRAME
Establish the question that matters most, and the supporting questions required to answer it with confidence. Good framing names the decision, exposes assumptions, and keeps a preferred answer from setting the agenda before the work starts.
DIAGNOSE
Build the clearest available understanding of what sits behind the question: what is happening, what changed, what is driving it, and where evidence stops and belief takes over.
OPTIONS
Develop a small number of genuinely different paths. A real option is a complete direction with its own priorities, investment profile, and operating consequences. Variations on a preferred answer are not options.
CHALLENGE
Test each path against evidence, assumptions, risk, tradeoffs, and execution reality. Challenge has a defined place in the process. It is scheduled, assigned, and owned, which is what makes a serious objection safe to raise before commitment rather than after it.
DECIDE
Make the call. The decision carries its reasoning, the tradeoffs being accepted, the uncertainty leadership is choosing to hold, and the conditions under which it would be revisited.
ACT
Convert the choice into priorities, ownership, resources, and first moves. The decision must now be carried into practice.
The separation is the discipline
The six phases are not hard to understand. Keeping them apart is the hard part, and it is where most of the value sits.
Collapse diagnosis into solution development and the early idea starts selecting the evidence. Collapse options into challenge and the team polishes one favored path while the alternatives receive a courtesy review. Collapse decide into act and implementation detail manufactures the feeling of commitment before anyone has actually chosen.
Separation buys one thing: it delays convergence until convergence has been earned. Clarify the question. Understand the situation. Build the choices. Test them. Choose. Move. The work can run fast, and some of it should, but the logic stays visible at every step, which means it can still be examined later by the leadership team or by a board.
The sequence tolerates iteration, with a condition. Returning to an earlier phase is legitimate when new evidence or a gap in the reasoning calls that phase’s output into question: evidence breaks the framing, challenge exposes an assumption the organization cannot support, early execution reveals that conditions have changed. It is not legitimate because leadership dislikes where the work is heading. Drawing that line in advance is what keeps iteration from becoming avoidance.
Depth should track stakes. A contained decision can move through all six phases in a week. A decision that resets enterprise direction may require broader evidence, harder challenge, and more than one round of leadership judgment. Discipline means doing the thinking a decision actually requires, not applying the same weight to every situation.
What an outside seat contributes
The people closest to a business know things no outsider can reconstruct. They also sit inside a system of history, incentives, relationships, and positions they have already defended in public. That system makes some questions awkward to ask and some alternatives expensive to raise.
An independent seat is useful largely for that reason. It can name an assumption that has become invisible, separate institutional knowledge from institutional habit, and make disagreement affordable for people who would otherwise pay for it.
That perspective gains value when grounded in operating experience. Strategy eventually arrives at an actual organization, with its own people, capacity, economics, systems, customers, and prior commitments. A path that ignores those realities can look compelling on paper and fail in execution. Operating experience puts the constraints on the table while they can still change the decision rather than explain the failure.
Where judgment does the work
Leaders have more data, more analysis, and more computational power available than at any point in my career. Artificial intelligence can analyze large volumes of data quickly, widen the range of options, and expose patterns people would otherwise miss. Leadership remains accountable for the decisions that follow. Turning analysis into a sound decision requires judgment.
At an inflection point the evidence is incomplete, the future is genuinely uncertain, and more than one path can be defensible. The decision often requires giving up something valuable, investing ahead of proof, or accepting a risk that no model resolves.
That is the moment judgment is called for: integrating evidence with context, pattern recognition, and a realistic read of what the organization can absorb. The Method gives that judgment structure, makes the reasoning visible, and creates a place to test it before capital and credibility are committed.
When the Method is the wrong tool
Not every decision deserves this. If a choice is reversible, inexpensive, and sits in territory where the playbook still works, run the playbook. The Method is built for decisions that are costly to unwind, that commit the organization for years, or that are on the table precisely because the old answers have stopped applying. Applying it to everything would be its own failure of judgment.
What the Method is designed to produce
The output is a path leadership understands, can explain, and is prepared to carry forward.
Sometimes that is a full strategy reset. More often it is a targeted change to the operating model, the portfolio, the transformation plan, the organization, or the execution of a strategy that is fundamentally sound. The Method scales to the decision because it starts from the situation and the question rather than from a predetermined type of engagement.
The second output matters as much as the first. A well-run process leaves the organization with a shared account of what is happening, why this direction was chosen, what was traded away, and what has to happen next. That is where conviction comes from, and conviction is what holds execution together when the work gets hard.
This is the architecture. Behind it sit the protocols, tests, and tools that make the Method repeatable. They help sharpen the questions, bring assumptions and alternatives under scrutiny, and make the reasoning behind a decision explicit.
When the playbook changes, the answer does not arrive whole. It starts with the question that matters most, and it has to be earned from there.