I've got nothing against a 100-page strategy document.
I've written plenty of strategy.
I've read plenty more.
The problem isn't the number of pages. The problem is what happens after page 100.
Too often, the strategy gets delivered, admired, discussed in a leadership meeting, saved to a shared drive and slowly becomes an expensive historical document.
Meanwhile, Monday morning arrives.
People still have to decide what to do.
That's the part I care about.
A strategy is supposed to change decisions. It should help an organization decide where to focus, what to stop doing, what to invest in, what to measure and how to move forward.
If it doesn't do that, it may be a very good piece of analysis.
It just isn't doing the job of strategy.
This is why I built the Elevaate Strategic Sprint around a relatively simple set of questions:
Where are we?
What's changing?
What's the opportunity?
What should we do?
What should we stop doing?
What will success look like?
How do we execute?
Those questions aren't revolutionary. That's precisely why I like them.
They force the conversation back to the organization instead of the document.
And what if you already have the 100-page strategy?
Good.
Don't write another one.
You've already paid for the research. You've debated the recommendations. You've probably highlighted the pages you agree with and quietly ignored the pages you don't.
Now let's make the thing useful.
That might mean translating recommendations into a handful of strategic priorities. It might mean identifying the decisions leadership actually needs to make. It might mean assigning ownership. It might mean sequencing the work so the organization doesn't try to do twelve things at once.
It might even mean admitting that part of the strategy no longer fits because the world changed.
That's not failure.
That's management.
Strategy shouldn't be a monument to the thinking that happened six months ago.
It should be a tool for the decisions you have to make now.
So here's my confession:
I don't particularly enjoy writing 100-page strategic plans. But I do enjoy figuring out what to do with them.
There is a missing step between “Here is the strategy” and “Go execute.”
That's where a lot of the value gets lost.
And that's also where I like to work.
Because strategy should survive contact with Monday morning.
There is nothing wrong with detail when detail is necessary. The problem is detail without hierarchy. Leaders don't need to remember every finding. They need to know which findings change the decision. Teams don't need to memorize every recommendation. They need to know which priorities change their work. A useful strategy creates hierarchy: here is what matters, here is why, here is what changes, and here is what happens next. If a document can do that in 30 pages, great. If it takes 100, fine. Page count isn't the point. Usefulness is.