Refactoring

Refactoring

Good Strategy / Bad Strategy ๐Ÿ“—

Summary and review of the most influential work by Richard Rumelt.

Luca Rossi's avatar
Luca Rossi
Aug 17, 2023
โˆ™ Paid
37
3
5
Share
Upgrade to paid to play voiceover

Hey there, as some of you already know, we started a Book Club ๐Ÿ“—ย in the Refactoring community!

Every two months we read some famous book in the engineering/management space, and we review it together in a live event at the end of the period.

This works on many levels: the cadence forces all of us to read more books, the conversation improves our understanding, and the whole ceremony creates bonding in the community.

We had a lot of fun discussing the book in a community call.

We started by reading Good Strategy / Bad Strategy, by Richard Rumelt, as it won the popular vote!

This article is dedicated to it, and should work on two levels:

  • ๐Ÿ“‹ Summary โ€” explain the main themes, frameworks, and ideas included in the book. So if you are low on time, you can just read this instead of the whole thing!

  • ๐ŸŒŸ Review โ€” illustrate our take on such ideas, how they relate to our work, and what we liked and disliked.

Letโ€™s go!


The book club and the community are exclusive to paid subscribers. If you want to get access you can subscribe below ๐Ÿ‘‡


โš–๏ธ Good and Bad

At the very beginning of the book, Richard Rumelt says that strategy seems to be everywhere these days.

It was 2011 when he wrote this, and, I swear, it is even more true today. Every day we are bombarded with threads, Linkedin posts, presentations, and ebooks by people who seem to have strategies about pretty much anything.

But then, Rumelt argues, truly good strategy is rare. This is a core theme of the book, which, as the name implies, spends almost the same time talking about good strategy, as it does talking about bad strategy.

And thatโ€™s what caught my attention โ€” as a fellow writer.

Whenever I read something, I canโ€™t help but think about how I would have written about that topic, in terms of structure, tone of voice, and actual content. Itโ€™s like a process that runs all the time in the back of my mind.

So, what struck me is that this book is not called โ€œHow to create a good strategyโ€ โ€” or some catchy variation on that. It is called Good Strategy / Bad Strategy.

In fact, the book hits you with a one-two punch:

  • First, it hits you with inversion โ€” it shows you whatโ€™s bad. Since bad strategy is incredibly common, chances are this is going to hit you hard: โ€œbeen there, done thatโ€.

  • Second, it shows you what good strategy looks like. And at this point your mind has been primed to hear what the author has to say.

This is so effective that we will follow the same pattern for this review. Here is what we will cover:

  • โŒ Bad Strategy โ€” what it looks like, and why it happens.

  • ๐Ÿ”ฎ Good Strategy โ€” what strategy is really about, and how to create it by following Rumeltโ€™s three-step framework.

  • ๐Ÿ’ช Sources of Power โ€” the key elements to consider from which you can draw good strategy.

  • โš”๏ธ Competition โ€” putting the bookโ€™s key lessons in context with digital products.

  • ๐Ÿ“ฃ How to be heard โ€” how you can contribute to your company strategy and communicate effectively.

  • ๐Ÿ“Œ Bottom line โ€” final thoughts and takeaways.

Letโ€™s dive in!


This post is for paid subscribers

Already a paid subscriber? Sign in
ยฉ 2025 Refactoring ETS
Privacy โˆ™ Terms โˆ™ Collection notice
Start writingGet the app
Substack is the home for great culture