13. Failure modes of strategy

§The question: where does this go wrong, and what does it look like from inside?

§Rumelt listed the hallmarks of bad strategy: fluff, failure to face the problem, mistaking goals for strategy, bad objectives. At one to five people the list is shorter and more specific, because the failures that matter are the ones that consume a quarter of runway. Six of them, each with its tell.

§ 13.1Limbo#

§What it looks like. The evidence framework shows mixed signals. The team decides neither to iterate nor to pivot and waits for the picture to clarify. It does not. Months pass. Why it happens. Both moves feel like losses. Iterating admits the current version failed; pivoting admits the direction did. Waiting feels like neither, and Annie Duke's research on quitting explains why people choose it: the cost of waiting is invisible and the cost of moving is not. The tell. The same grid, read three months apart, with the same colors. The defense. A date on the decision, set when the grid is filled. Paul Graham's question, default alive or default dead, asked out loud. Chapter 14 tells the case.

§ 13.2Pain number one shipped as version one#

§What it looks like. The loudest problem in the room becomes the first thing built, and the roadmap is constructed backwards from it. Why it happens. Loudness is mistaken for priority, and the ladder is skipped. Nobody asks which bet the loud problem depends on. The tell. The first version contains the feature the team argued about most, and no goal above it that the evidence supports. The defense. The sequence of bets by dependency. In the field sprint, payments was pain number one and depended on a check-in that had failed six of six. The ladder put it in month twelve. A vote would have put it in month one.

§ 13.3Three frameworks and no decision#

§What it looks like. A strategy canvas, then a positioning map, then a bets grid, then a prioritization matrix. Four documents, each coherent, and no sentence beginning "we will not." Why it happens. Frameworks feel like progress and defer the part that hurts. The team is choosing among tools instead of among directions. The tell. The strategy folder is full and the exclusion list is empty. The defense. One method for prioritization, one ladder for strategy, and a rule that the strategy row is not complete until the "we will not" list has at least three entries a competitor would reject.

§ 13.4A vision so broad it excludes nothing#

§What it looks like. "To transform hospitality through technology." Every product serves it. Nothing is forbidden by it. Why it happens. Breadth feels safe and inspiring. It is also unfalsifiable, which is why it feels safe. The tell. You cannot name a plausible product this company might build that the vision would rule out. The defense. The vision from three seats, on a Tuesday, in sentences a stranger could check. If the sentences could describe any company in the category, they describe none.

§ 13.5Goals set before bets#

§What it looks like. "Ten thousand users by the third quarter." A roadmap reverse-engineered to produce it. No bet the number would validate. Why it happens. Numbers feel like rigor, and investors ask for them. The tell. When the number is missed, nobody can say which belief was wrong. The defense. Every goal has a parent bet with a critical question. A goal that cannot be traced upward is a metric that has started to set the strategy, and the first whitepaper said what happens then.

§ 13.6The strategy that was never written#

§What it looks like. The team agrees, in conversation, on a direction. It is not written down. Three weeks later it is three directions. Why it happens. Writing feels bureaucratic at five people. The conversation felt clear. The tell. Two team members describe the strategy differently to the same customer. The defense. The decision document from chapter 3 and the four documents from chapter 12. Short, dated, confirmed in writing.

§ 13.7The root#

§Rumelt's word for the common cause is the one this whitepaper has used from its first page: bad strategy fails to choose. Every failure above is a failure to exclude. Limbo excludes no direction. Pain number one excludes no sequence. Three frameworks exclude no option. The broad vision excludes no product. Goals before bets exclude no belief. The unwritten strategy excludes no interpretation.

§ 13.8What comes out#

§The six, pinned next to the ladder. Read before the strategy conversation and again when the first goal is read. Every team finds itself in at least one. The ladder is built so that finding it costs a conversation rather than a quarter.