Aibrary Logo
Podcast thumbnail

Good Strategy / Bad Strategy

9 min

The Difference and Why It Matters

Introduction

Narrator: Imagine being in a grand hotel ballroom, surrounded by two hundred of your company’s top managers. The CEO takes the stage, backed by a slickly produced film showcasing the firm's products. He declares the company’s new "strategy": to achieve global leadership, drive growth, and deliver high shareholder returns. The presentation ends, balloons drop from the ceiling, and everyone feels energized. But as the excitement fades, a nagging question emerges: what are we actually supposed to do? This scene, a real event described by author Richard Rumelt, captures a pervasive and dangerous problem in the modern world: the complete misunderstanding of what strategy truly is.

In his seminal work, Good Strategy / Bad Strategy: The Difference and Why It Matters, Rumelt dissects this confusion with surgical precision. He argues that most of what passes for strategy today isn't strategy at all. It’s a mix of ambitious goals, motivational fluff, and wishful thinking. Real strategy, he explains, is a rare and powerful tool for overcoming critical challenges, and learning to distinguish it from its bad counterpart is an essential skill for any leader.

The Four Hallmarks of Bad Strategy

Key Insight 1

Narrator: Before one can build a good strategy, one must learn to recognize a bad one. Rumelt identifies four tell-tale signs that a strategy is fundamentally flawed. The first is fluff: the use of buzzwords and needlessly complex language to create an illusion of high-level thinking. For example, a major bank's strategy memo declared its goal was "customer-centric intermediation." When stripped of the jargon, this simply meant "being a bank," a statement so obvious it provided no guidance whatsoever.

The second hallmark is the failure to face the challenge. A strategy is a way to overcome an obstacle. If it doesn't identify the nature of the challenge, it's not a strategy. The third is mistaking goals for strategy. A document that lists ambitious targets, like "20 percent annual revenue growth," is not a strategy; it's a wish list. It describes a destination without providing a map. Finally, the fourth hallmark is bad strategic objectives. These are objectives that are either impractical or fail to address the critical issues at hand. A long list of "action steps" that are disconnected and unfocused is a classic example of a "dog's dinner" of objectives, not a coherent plan.

The Kernel of Good Strategy: Diagnosis, Guiding Policy, and Coherent Action

Key Insight 2

Narrator: In contrast to the formless nature of bad strategy, Rumelt argues that all good strategies share a core structure he calls the "kernel." This kernel has three essential components. The first is a diagnosis. A good diagnosis simplifies a complex reality by identifying the crucial aspects of the challenge. It defines what is happening and why it matters.

When Lou Gerstner took over a struggling IBM in 1993, the common diagnosis was that the company was too integrated and needed to be broken up. Gerstner, however, offered a different diagnosis. He argued that in a fragmenting industry, IBM's integrated knowledge was its unique strength; the problem was that it was failing to use it.

This diagnosis led to the second part of the kernel: a guiding policy. This is the overall approach to overcoming the obstacles identified in the diagnosis. Gerstner's guiding policy was to transform IBM from a hardware seller into a services company that offered customers tailored solutions to their complex IT problems.

Finally, the kernel requires coherent actions. These are the specific, coordinated steps, resource commitments, and policy changes that carry out the guiding policy. For IBM, this meant reorganizing its sales force, shifting its focus from hardware to software and consulting, and leveraging its brand to sell integrated solutions. A good strategy, therefore, is not just a single idea but a logical, coherent structure that links diagnosis, policy, and action.

The Power of a Proximate Objective

Key Insight 3

Narrator: A common failure of bad strategy is setting "blue-sky" objectives that are so distant and abstract they are paralyzing. Good strategy, conversely, often gains its power by establishing a proximate objective—a target that is close enough to be feasible. A leader's greatest responsibility is to absorb the ambiguity of a situation and present the organization with a solvable problem.

A powerful historical example is President John F. Kennedy's 1961 declaration to land a man on the moon by the end of the decade. At the time, this goal was audacious, but it was also proximate. It was a concrete, understandable, and achievable objective. It wasn't a vague call to "lead in space exploration." Instead, it was a clear engineering problem that focused the efforts of thousands of scientists and engineers, galvanizing the nation and ultimately demonstrating American technological prowess. By setting a clear, proximate goal, Kennedy turned a complex geopolitical challenge into a manageable, though monumental, task.

Discovering Power by Reframing the Challenge

Key Insight 4

Narrator: Good strategy often arises from a fresh perspective that discovers new sources of strength and weakness. It challenges conventional wisdom and reframes the competitive landscape. For decades, the retail industry believed that a full-line discount store needed a population base of at least 100,000 people to be viable. This was the accepted truth.

Sam Walton, the founder of Wal-Mart, saw things differently. He didn't see a store as a standalone unit; he saw it as part of a network. By building a cluster of stores in small towns, supported by a central distribution center and a sophisticated satellite-based logistics system, he completely changed the economics of retail. While competitors like Kmart were focused on expanding internationally, Wal-Mart was quietly building an unassailable advantage in a market others had dismissed. Walton's insight was to redefine the fundamental concept of a "store," discovering a hidden source of power that his rivals failed to see until it was too late.

Strategy as Design, Not Just Decision

Key Insight 5

Narrator: Many people think of strategy as making a choice from a list of alternatives. But Rumelt argues that the most powerful strategies are not chosen, they are designed. They are an adroit configuration of resources and actions, premeditated and coordinated to achieve a specific effect.

One of the most famous examples of strategic design is Hannibal's victory at the Battle of Cannae in 216 B.C. Facing a much larger and more aggressive Roman army, Hannibal didn't simply choose a standard tactic. He designed a trap. He anticipated the Romans' tendency to charge the center of his line. He purposefully placed his weaker troops there, instructing them to slowly give way, bowing inward. As the Roman legions pushed forward, they were funneled into a kill zone. Hannibal’s superior cavalry, positioned on the flanks, defeated their Roman counterparts and then wheeled around to attack the Roman infantry from behind. The Roman army, despite its numerical superiority, was encircled and annihilated. This was not a simple decision; it was a masterful design of coordinated actions, built on a deep understanding of his opponent's predictable behavior.

Conclusion

Narrator: The single most important takeaway from Good Strategy / Bad Strategy is that strategy is not a list of ambitions, a vision statement, or a set of financial goals. It is a coherent, problem-solving discipline. It begins with an honest diagnosis of a critical challenge, establishes a guiding policy for dealing with that challenge, and is executed through a set of focused, coordinated actions. It is fundamentally about making hard choices and concentrating power, not trying to do everything at once.

The book's most challenging idea is that the biggest obstacle to good strategy is often not a lack of intelligence or resources, but the unwillingness to choose. Leaders often prefer the comfort of vague goals and universal buy-in over the difficult work of setting priorities and saying "no." So, the ultimate question Rumelt leaves us with is this: when you look at the strategy of your own organization, do you see a fluffy wish list, or do you see the clear, sharp kernel of a diagnosis, a guiding policy, and coherent action? The answer to that question may determine your future.

00:00/00:00