The planning room is not the final test of strategy. The test comes the next working day, when two reasonable options compete and people must decide which one the organization will protect.
Your strategy may sound clear until someone must choose
A strategy often feels convincing inside the planning room.
The choices appear connected. The presentation shows a clear direction. Leaders agree on the win, the chosen field, the way to win, and the priorities that deserve concentration.
Then the next working day begins.
A customer asks for something outside the chosen offer. A manager must decide whether to protect the strategic work or respond to an urgent request. A department proposes a useful project that does not support the chosen direction. A salesperson finds an opportunity that could bring revenue but pull the organization into another market.
The strategy now faces its real test.
People cannot return to the planning room every time two reasonable options compete. They need to know what the strategy asks them to choose while the work is moving.
A strategy becomes useful when it helps people make the next decision differently.
The test is not whether people can repeat the strategy. It is whether they can use it before familiar habits, urgent demands, and local targets take over.
The next decision reveals the real strategy
Organizations often judge strategy through annual results.
Did revenue grow? Did market share increase? Did the company reach its targets?
These results matter, but they appear after many decisions have already been made.
The strategy becomes real much earlier.
It appears when leaders choose which customer deserves attention. It appears when a manager allocates the team’s limited time. It appears when a project receives funding, when an exception is approved, or when a familiar activity is finally stopped.
Everyday decisions either strengthen the strategy or quietly rebuild the old game.
Suppose an organization says it will win by helping a selected customer group solve one important problem. The next day, sales accepts work from several unrelated markets because the opportunities promise immediate revenue.
The organization has returned to the familiar game: take any work that can be sold.
Suppose leaders say routine decisions should move to the lowest responsible level. The next day, a supervisor brings the decision back to the department head because that is how risk has always been managed.
The old game survives again.
The strategy may remain unchanged on paper, but daily decisions are carrying the organization somewhere else.
Strategy should settle a real conflict
A strategy is most useful when two attractive options cannot both receive full support.
Imagine a service company that has chosen to win through complete customer resolution. One visible owner should remain accountable even when several departments must contribute.
Then a manager faces a difficult choice.
The team can close the transaction quickly by transferring the customer to another department. Or it can retain ownership, coordinate the work, and remain involved until the result is complete.
Speed and ownership both matter.
The strategy must explain which one carries the game when they conflict.
If the organization’s way to win is complete resolution, the manager should protect ownership. Leaders may still look for ways to reduce delay, but they should not reward a quick transfer that leaves the customer to manage the next step.
That is what a strategic choice does. It settles a conflict that general values cannot settle on their own.
“Serve the customer” is too broad. Both options can be defended as service.
“Retain one visible owner until complete resolution” gives the manager a basis for choosing.
The one-page game plan should enter the decision
The one-page game plan gives the organization’s central choices a visible home.
But the page earns its value only when people bring it into real decisions.
A manager considering a new request should be able to examine the win, chosen field, way to win, trade-offs, capabilities, and current strategic moves.
The page should help answer:
Does this request serve the win?
Does it belong in the chosen field?
Does it reinforce how we intend to win?
Does it build a capability the strategy depends on?
What will receive less if we say yes?
These questions are not a substitute for judgment. They improve the quality of judgment.
The page does not make every decision automatic. It makes the strategic logic available before people fall back on personal preference, departmental pressure, or habit.
Test the strategy with a customer request
Customer requests expose whether the organization has made real choices.
A customer may ask for a lower price, a customized feature, a new service, a faster deadline, or an exception to the normal process.
Leaders often treat responsiveness as the obvious answer. They do not want to appear inflexible or lose the business.
But not every customer request should shape the organization.
Suppose a consultancy has chosen to help new supervisors turn strategic priorities into clear direction, delegated wins, and daily follow-through. A client then asks for a general motivational program unrelated to that movement.
The engagement may produce income. The client may value it. The consultancy may even know how to deliver it.
The strategic question is whether accepting the work builds the chosen game.
Will it strengthen the consultancy’s expertise, methods, evidence, and reputation in the field it has selected? Or will it pull attention toward another market and another promise?
The answer does not always have to be no.
The work may be accepted for financial or relationship reasons. But leaders should name the decision accurately. It is an exception, not evidence that the chosen field has expanded.
Without that clarity, repeated exceptions become the real strategy.
Test the strategy with a new initiative
Organizations rarely lack ideas.
Someone proposes an academy, platform, campaign, summit, transformation program, partnership, or digital tool. The proposal has benefits and supporters.
The easiest response is to add it.
The more strategic response is to ask what choice the initiative advances.
Suppose the organization has decided to move managers from answering every problem to building decision ownership in the team.
A proposed leadership conference may attract participation and create energy. But does it change how decisions are made during work?
Perhaps the stronger move is not a large conference. It may be a focused practice system in which managers clarify decision boundaries, employees present options, and teams review the reasoning behind actual decisions.
The conference can still contribute, but it should not be mistaken for the strategic movement.
The initiative is a vehicle.
The strategy determines whether the vehicle belongs, how it should be designed, and what result it must help create.
Test the strategy with a resource decision
Budgets reveal what leaders truly protect.
An organization may say that a strategic capability matters while continuing to fund activities built for the previous game.
Suppose leaders want decisions to move closer to customers.
That shift may require timely information, clearer authority, manager coaching, and review routines that help teams improve judgment.
But the budget continues funding additional approval systems, detailed escalation reporting, and layers of supervisory control.
The resource decisions contradict the strategy.
The same problem appears with leadership attention.
Executives may announce a new priority, then spend nearly every meeting reviewing short-term operating numbers. Managers learn that the strategic movement matters only after immediate targets are satisfied.
The strategy becomes work people should pursue in their remaining time.
A real priority changes the allocation.
Money moves. Capable people move. Measures change. Meetings change. Some existing work receives less.
A strategy that does not influence resource decisions remains an intention.
Test the strategy with a difficult exception
Exceptions are unavoidable.
A valued customer may require unusual support. A regulatory change may demand immediate attention. A crisis may force leaders to act outside the normal plan.
The issue is not whether exceptions occur. The issue is what the organization learns from them.
Some exceptions reveal that the strategy is too rigid. Others reveal that leaders have not built the capabilities needed to carry it. Many simply reveal that someone powerful wanted a different answer.
Ask what the exception means.
Does it expose a customer need the chosen field failed to recognize?
Does it challenge an assumption behind the way to win?
Does it reveal a missing capability?
Or are leaders abandoning the choice because the trade-off has become uncomfortable?
An exception should not quietly rewrite the strategy.
Name it. Explain why it is being made. Decide whether it is temporary. Examine what it teaches.
When exceptions accumulate, review the strategic logic. The organization may be learning that the choice needs revision. Or it may be discovering that leaders have never truly protected it.
Familiar measures can defeat a new strategy
People respond to what the organization counts, reviews, and rewards.
A company may introduce a strategy based on complete customer resolution while continuing to reward transaction speed.
A leadership team may want sound decisions near the work while managers are judged by whether problems are escalated early.
A company may choose a focused market while sales incentives reward any revenue from any customer.
The new strategy and the old measures then compete.
Under pressure, the measures usually win.
Employees know what affects their performance review, budget, promotion, and standing with senior leaders. They may support the strategic message, but they will protect the result the system makes consequential.
Testing strategy against daily decisions therefore requires a close look at measures.
What behavior does the measure encourage?
What decision will a reasonable employee make to protect it?
Does that decision reinforce the strategy?
What happens when two measures conflict?
A measure may have served the previous operating model. It should not remain untouchable simply because the organization already knows how to report it.
Leaders must explain the rule behind the decision
Employees learn strategy by watching what leaders choose.
Suppose a senior leader declines an attractive project because it does not serve the chosen field.
The decision teaches something.
But the lesson becomes stronger when the leader explains the rule:
“This project could create value, but it requires capabilities that do not support the game we have chosen. We will protect the current strategic moves.”
The explanation allows others to apply the same reasoning later.
Without it, people may interpret the decision as a personal preference, budget problem, or political conflict.
The same principle applies when leaders approve an exception.
They should explain why the decision differs from the normal choice and what conditions make the exception legitimate.
Leaders translate strategy through these moments.
A presentation tells people what the organization intends. A visible decision shows what the intention means.
This is why leaders who move work must do more than communicate priorities. They must use strategy when they give direction, allocate resources, resolve conflicts, and decide what the team will protect.
Move decisions to the right level
Senior leaders cannot make every strategic decision.
If all uncertainty travels upward, the organization becomes slow and dependent. Managers wait. Employees learn that strategy belongs to executives.
The goal is to move decisions to the lowest responsible level while preserving the strategic logic.
People closer to the work often have more current information. They can see customer conditions, operational constraints, and emerging problems earlier.
But they need boundaries.
What kinds of decisions may they make?
Which trade-offs are already settled?
When should they recommend options?
What evidence should they consider?
When must the decision move upward?
For example, a salesperson may be allowed to adapt the offer within the chosen customer field but may not create a new service category without review.
A service team may make exceptions needed for complete resolution within an agreed cost or risk boundary.
A supervisor may delegate routine operating decisions but escalate issues that change policy, legal exposure, or the strategic promise.
Clear boundaries allow the organization to combine speed with coherence.
The strategy stops being an executive possession and becomes a shared basis for judgment.
Use a five-question decision test
When a decision could affect the strategy, pause and ask five questions.
1. What win does this decision serve?
Name the result that should move. Do not accept a general answer such as growth, service, or efficiency without explaining the specific contribution.
2. Does it belong in our chosen field?
Identify the customer, problem, offer, channel, or part of the journey the decision supports.
3. Does it reinforce how we intend to win?
Examine whether it strengthens the organization’s distinct value or pulls it toward a familiar industry practice.
4. What will receive less because we choose this?
Make the trade-off visible. If nothing loses time, money, attention, or capacity, leaders may be pretending the choice is free.
5. What evidence will tell us whether the decision worked?
Name what should become visible before the organization declares success or expands the commitment.
The test should not turn every decision into a long meeting.
Use it for choices with strategic consequences: investments, customer exceptions, new initiatives, capability commitments, changes in measures, and opportunities that may shift the field.
With repeated use, the questions become part of how people think.
Do not expect perfect consistency
A strategy enters an organization that already has customers, commitments, habits, measures, systems, and political realities.
Daily decisions will not become perfectly aligned at once.
A department may still follow an old process. A leader may approve a contradictory exception. A measure may continue rewarding the familiar behavior because the replacement is not yet ready.
These contradictions matter, but they also provide useful information.
They show where the strategy has not yet entered the system.
The goal is not to punish every inconsistency. It is to make the inconsistency visible and decide what to do about it.
Ask:
Why did the old decision make sense to the people involved?
Which rule, measure, or constraint supported it?
What must change so the strategic response becomes easier next time?
This is where strategy connects with daily execution. People need more than instructions. They need practical plays, supportive systems, decision authority, and feedback that help the new response survive normal pressure.
Review decisions, not only results
Strategy reviews often begin with numbers.
Revenue, cost, customer ratings, project milestones, and completion percentages fill the agenda.
These indicators show what happened. They do not always explain the choices that produced the result.
Review selected decisions.
What did people choose when priorities competed?
Which customer requests were accepted or refused?
Where did leaders protect the chosen field?
What exceptions were made?
Which resource decisions strengthened or weakened the way to win?
What did the organization learn?
Richard Rumelt describes strategy as a response to an important challenge through a guiding policy and coherent action. Reviewing decisions allows leaders to see whether the organization’s actions remain coherent with the policy it has chosen.
A poor result does not automatically mean the decision was poor. A favorable result does not automatically prove that the choice was sound.
Leaders need to examine both the result and the reasoning.
Use the strategy before the decision is final
A strategy is most useful before commitment.
Once the contract is signed, the budget approved, the system purchased, or the team assigned, leaders become attached to the path.
It becomes harder to reconsider.
Bring the strategic choices into the conversation early.
Before developing a full proposal, ask whether the opportunity belongs.
Before building the detailed business case, ask which strategic choice it advances.
Before assigning a team, ask which existing commitment will lose capacity.
Before announcing the project, ask what proof would justify further investment.
This prevents the organization from using strategy only to explain decisions that have already been made.
The purpose is not to find language that makes every proposal appear aligned.
It is to improve the choice while the organization still has options.
Follow patterns across several decisions
One inconsistent decision may be an exception.
A repeated pattern reveals the actual game.
If the organization keeps accepting customers outside the chosen field, the field may not be truly chosen.
If managers repeatedly take decisions back from employees, the organization may not trust the boundaries it has established.
If leaders continue approving unrelated initiatives, the strategic priorities may not be protected.
If every difficult trade-off is postponed, the organization may prefer optionality over focus.
Follow the pattern.
Do not look only at what leaders say. Look at what the organization repeatedly chooses when money, time, customers, and reputation are involved.
This is part of Strategic Learning. The pattern provides evidence. Leaders can use it to clarify the choice, redesign the system, build a missing capability, or reconsider an assumption.
Daily decisions do not merely execute strategy. They teach leaders whether the strategy can live in the organization they actually have.
Test one decision now
Choose a decision your organization must make within the next few days.
It may involve a customer request, project proposal, hiring decision, investment, partnership, deadline, or exception.
Do not begin by asking whether the proposal is useful.
Ask what strategic choice it advances.
Then apply the five questions.
What win does it serve?
Does it belong in the chosen field?
Does it reinforce the way to win?
What will receive less?
What proof should appear?
Write the answer before the decision is final.
You may discover that the proposal does not belong. You may redesign it so that it serves the strategy. You may accept it as a deliberate exception. Or you may recognize that your strategy does not yet provide enough guidance.
Each result is useful.
The strategy has entered the decision.
Make the next decision part of the game
The strategy does not become real because the planning document is complete.
It becomes real when people begin choosing differently.
A manager protects the customer result instead of the old measure. A leader refuses an attractive project that pulls the organization away from its chosen field. A team moves a decision closer to the work. A budget begins building the capability the way to win requires.
These decisions may look small compared with the annual plan.
Together, they create the organization’s direction.
The next article, choose the first bet, will show how to turn the strategic choices into one meaningful move that can produce action, evidence, and learning without requiring the organization to launch everything at once.
Recommended reading
Richard P. Rumelt, Good Strategy/Bad Strategy. Rumelt’s framework of diagnosis, guiding policy, and coherent action helps leaders examine whether everyday choices respond to the central strategic challenge or pull the organization in another direction.
A.G. Lafley and Roger L. Martin, Playing to Win: How Strategy Really Works. Their integrated choice cascade provides a practical test for decisions involving the win, chosen field, way to win, capabilities, and management systems.