A roadmap is not a strategy, and a busy delivery team is not proof of either.
- Strategy is direction: the challenge you face, the approach you will take, and what you will deliberately not do.
- The roadmap is sequence: what comes first, what depends on what, and what is realistic now.
- Execution is delivery: the daily trade-offs and course corrections that turn the sequence into outcomes.
Test each layer
When a technology plan lists twelve projects for the year and calls itself a strategy, ask what challenge the list responds to. If nobody can say, a roadmap is standing in for choices. Check that people can state the approach in two sentences, that each roadmap item traces back to it, and that what delivery learns flows back into the roadmap. Richard Rumelt’s warning is that many documents called strategy are goals and slogans without a diagnosis.
Tell it upward
Technical leaders often brief executives the way they brief engineers: context first and the ask last. Executives need the decision first. Gregor Hohpe frames executive impact as logic times stakes, so zero on either side means zero impact.
To ask for funding to replace a fragile integration, write the big idea in one sentence, as Sumeet Moghe suggests: our order flow depends on a component that fails regularly, and replacing it this quarter removes the risk of a week-long outage. Then give the options, your recommendation and the cost of waiting. Cap the takeaways at three, and keep the evidence ready for questions.