Why the best technology strategy is the one that can be executed

There is a version of technology strategy that is intellectually satisfying and practically useless. It involves comprehensive capability assessments, sophisticated market analyses, and well-reasoned prioritization frameworks. The output is a document that is correct in its analysis and inert in its effect. The organization knows what it should do. It has no idea how to do it.

We have seen this document in more organizations than we can count. It usually arrives with a presentation. There is a roadmap slide. The roadmap has phases. The phases have names. Nobody can tell you what the first initiative actually requires, how long it will take, who will do it, or how it will be funded.

The gap between strategy and execution

Technology strategy fails at the same place every time: the translation from direction to action. The strategy identifies what should be built. It does not identify who will build it, what it will cost, how it connects to adjacent systems, what needs to change in the organization to make it work, or what the first sprint looks like.

This gap is not accidental. It is structural. Strategy consultants are not incentivized to produce executable plans. They are incentivized to produce defensible recommendations. Defensibility comes from breadth and rigor. Executability comes from depth and specificity. The two are in tension.

The result is a generation of enterprise technology strategies that are broad, rigorous, defensible, and unexecutable.

What executable strategy looks like

An executable technology strategy has a different structure than a traditional strategy document. It is not organized by capability area or technology domain. It is organized by initiative.

Each initiative has: a clear problem statement that the initiative solves; a defined scope that can be delivered by a team of known size in a known timeframe; a dependency map that identifies what needs to be true before the initiative can start; an effort and cost estimate that the finance function can evaluate; and a success definition that the business can verify.

The initiatives are sequenced. The sequencing is driven by dependencies and business value, not by technology elegance. The first initiatives create the foundation for the later ones. The later ones deliver the outcomes the strategy is designed to achieve.

The role of the strategist

This kind of strategy requires the strategist to do things that traditional strategy does not require: understanding implementation constraints well enough to assess feasibility; being specific enough about scope that the estimate is defensible; and having enough conviction about the sequencing to recommend a starting point, not a menu of options.

It also requires the client to do something that strategy projects do not traditionally ask: to commit. Not to the full roadmap — to the first two initiatives, with the understanding that the rest of the roadmap is subject to revision as those initiatives produce information.

The best technology strategy is not the most comprehensive one. It is not the one with the most sophisticated analysis. It is the one that ends with an organization knowing exactly what it is doing next, why it is doing it, and how it will know when it is done.