When Strategy Needs to Change starts with a simple test: does this make the work more decidable, or does it only make the work easier to describe? When Strategy Needs to Change: in product strategy, teams often mistake fluency for progress. When Strategy Needs to Change: they can explain the issue, name the stakeholders, and produce a tidy artifact while the actual product choice remains untouched.

When Strategy Needs to Change matters because operating systems decay when decisions stay implied. When Strategy Needs to Change: the company keeps moving, but each team carries a different version of the truth. When Strategy Needs to Change: one group thinks the bet is strategic. When Strategy Needs to Change: another treats it as optional. When Strategy Needs to Change: a third waits for a signal that nobody has agreed to produce. When Strategy Needs to Change: the surface looks aligned until execution exposes the disagreement.

When Strategy Needs to Change is the part of the series that shows when changing course is a sign of contact with reality, not inconsistency. When Strategy Needs to Change: the post should therefore leave the reader with something more useful than a principle. When Strategy Needs to Change: it should leave a sharper question, a better artifact, and a way to inspect whether the work changed.

Where the work breaks

When Strategy Needs to Change breaks when the team keeps the conversation abstract. When Strategy Needs to Change: abstract language lets everyone nod because nobody has to give anything up. When Strategy Needs to Change: a real decision has a cost. When Strategy Needs to Change: it changes priority, sequence, ownership, scope, customer contact, or follow-through. When Strategy Needs to Change: if none of those things changes, the team may have had a good conversation, but it has not changed the operating system.

When Strategy Needs to Change also breaks when teams use process as a substitute for judgment. When Strategy Needs to Change: a meeting can collect updates without creating insight. When Strategy Needs to Change: a memo can summarize context without recommending a choice. When Strategy Needs to Change: a dashboard can show movement without showing whether the movement matters. When Strategy Needs to Change: the repair is not more ceremony. When Strategy Needs to Change: the repair is a clearer relationship between evidence and action.

When Strategy Needs to Change has another failure mode: people protect optionality until the decision window closes. When Strategy Needs to Change: optionality feels responsible because it avoids premature commitment. When Strategy Needs to Change: past a certain point, though, optionality becomes a tax. When Strategy Needs to Change: teams keep weak work alive, delay learning, spread attention thin, and make every downstream handoff harder.

What good looks like

When Strategy Needs to Change is healthy when a team can say what changed after the conversation. When Strategy Needs to Change: the change might be small: a narrower customer segment, a stopped feature, a clearer launch owner, a better research question, a different account plan, or a new review date. When Strategy Needs to Change: small changes count when they remove ambiguity and create forward motion.

When Strategy Needs to Change should make disagreement more useful. When Strategy Needs to Change: good disagreement is not noise. When Strategy Needs to Change: it is information about assumptions, risk, incentives, and evidence quality. When Strategy Needs to Change: the operating move is to capture the disagreement in a form the team can test. When Strategy Needs to Change: if the disagreement cannot be tested, it should at least be named as a judgment call instead of hidden as consensus.

When Strategy Needs to Change should also protect the team from false completeness. When Strategy Needs to Change: complete-looking artifacts can still avoid the most important question. When Strategy Needs to Change: the test is whether a new person could read the artifact and understand the decision, the evidence, the tradeoff, the owner, and the next inspection point without reconstructing the whole history.

The useful artifact

When Strategy Needs to Change needs an artifact that is small enough to survive normal work. When Strategy Needs to Change: a useful artifact has five parts: the decision, the evidence, the tradeoff, the owner, and the review trigger. When Strategy Needs to Change: anything beyond that should earn its place.

When Strategy Needs to Change should name the decision in plain language. When Strategy Needs to Change: if the decision is actually three decisions, split it. When Strategy Needs to Change: if the decision has already been made, say that and use the artifact to clarify execution. When Strategy Needs to Change: if the decision is still open, make the options visible enough that people can argue about the real choice.

When Strategy Needs to Change should treat evidence with respect without worshiping it. Evidence has shape. When Strategy Needs to Change: a customer quote, usage trend, sales objection, churn pattern, or support signal can matter a lot, but each proves a different thing. When Strategy Needs to Change: the artifact should say what the evidence supports, what it does not support, and what would be strong enough to change the next move.

When Strategy Needs to Change should make the tradeoff impossible to miss. When Strategy Needs to Change: tradeoff language is the difference between a strategy document and an aspiration document. When Strategy Needs to Change: the team should know what receives less capacity, what waits, what gets cut, what risk is accepted, and which stakeholder will feel the cost.

How to inspect it

When Strategy Needs to Change can be inspected with four questions. What are we choosing? What are we refusing? When Strategy Needs to Change: what evidence would change our mind? When Strategy Needs to Change: what happens before the next review? When Strategy Needs to Change: if a team cannot answer those questions, the work is not yet ready for more process. When Strategy Needs to Change: it needs clearer judgment.

When Strategy Needs to Change should show up in the calendar. When Strategy Needs to Change: if the decision matters, it deserves a checkpoint. When Strategy Needs to Change: that checkpoint does not need to be heavy. When Strategy Needs to Change: it needs a defined signal, a real owner, and permission to change course. When Strategy Needs to Change: without that, the team will keep carrying the decision as background anxiety.

When Strategy Needs to Change should reduce the need for executive translation. When Strategy Needs to Change: a senior leader should be able to inspect the work without redoing the thinking. When Strategy Needs to Change: if the leader has to infer the customer, rebuild the evidence, guess the tradeoff, or identify the owner, the artifact is not doing enough operating work.

Field test

When Strategy Needs to Change can be tested on one live piece of work this week. When Strategy Needs to Change: pick something already consuming attention. When Strategy Needs to Change: rewrite it as a decision, not a status update. When Strategy Needs to Change: name the owner, the evidence, the tradeoff, and the review trigger. When Strategy Needs to Change: then ask what changed because the artifact exists.

When Strategy Needs to Change passes the test when the next action becomes more specific. When Strategy Needs to Change: the next action may be a customer call, a killed initiative, a narrower scope, a pricing review, a product bet, a launch decision, or a management conversation. When Strategy Needs to Change: the important part is that the work leaves the realm of explanation and re-enters contact with reality.

Evidence note: This is an operator-judgment essay grounded in Antoine's local source pack for Product Strategy That Actually Makes Choices and adjacent series context, including https://www.antoinebuteau.com/gtm-strategy-series-index/.

This is part 9 of 10 in Product Strategy That Actually Makes Choices.