Why I Hate the Word "Strategy"

I'll say something that might be unpopular coming from a consultant:
๐โ๐บ ๐ป๐ผ๐ ๐ฎ ๐ณ๐ฎ๐ป ๐ผ๐ณ ๐๐ต๐ฒ ๐๐ผ๐ฟ๐ฑ "๐๐๐ฟ๐ฎ๐๐ฒ๐ด๐" โ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐, ๐ ๐ง๐๐๐ก๐ก๐ฎ ๐ฑ๐ถ๐๐น๐ถ๐ธ๐ฒ ๐ถ๐.
Not because strategy doesn't matter โ it does. But because in most organizations, "strategy" has become a way to sound important without saying anything actionable.
Leaders craft vision statements. Decks get built. Terms like "transformation," "alignment," and "efficiency" get thrown around in all-hands meetings. And then everyone goes back to their desks and asks the same question they were asking before:
๐๐ฐ... ๐ธ๐ฉ๐ข๐ต ๐ฅ๐ฐ ๐ ๐ข๐ค๐ต๐ถ๐ข๐ญ๐ญ๐บ ๐ฅ๐ฐ ๐ฅ๐ช๐ง๐ง๐ฆ๐ณ๐ฆ๐ฏ๐ต๐ญ๐บ ๐ฐ๐ฏ ๐๐ฐ๐ฏ๐ฅ๐ข๐บ?
Here's what I've come to believe: ๐๐๐ฟ๐ฎ๐๐ฒ๐ด๐ ๐ถ๐ ๐ผ๐ป๐น๐ ๐๐๐ฒ๐ณ๐๐น ๐ฎ๐ ๐ฎ ๐๐๐ฎ๐ฟ๐๐ถ๐ป๐ด ๐ฝ๐ผ๐ถ๐ป๐. It tells us why we are doing what we are doing, but the real work โ the stuff that actually moves things โ happens in the sentence that follows.
"๐ข๐๐ฟ ๐๐๐ฟ๐ฎ๐๐ฒ๐ด๐ ๐ถ๐ ๐ซ, ๐ฉ๐๐๐ง๐๐๐ค๐ง๐...:"ย
โ E.g., These three teams need to restructure by Q3.ย
โ E.g., This process needs an owner, a deadline, and a weekly check-in.ย
โ E.g.,ย This initiative gets funded. These two don't.
The "therefore" is where strategy becomes real. It's where you find out whether the bold words in the deck can survive contact with actual organizational complexity โ budgets, headcount, competing priorities, and people who weren't in the room when the strategy was decided.
In my experience, the gap between a good strategy and a good outcome isn't vision. It's the willingness to get specific about what needs to happen next, who owns it, and by when.
WHO. WHAT. WHEN.
Three words. No framework required.



Comments