Building a Technology Strategy That Survives Contact With Reality
There’s a saying in military planning: no plan survives first contact with the enemy. Technology strategy has a similar problem. The strategy that looks elegant on slides often falls apart the moment it meets the reality of legacy systems, constrained budgets, shifting priorities, and teams that are already stretched thin.
The answer isn’t to stop making strategy. It’s to build strategy that’s designed for reality from the start.
Why strategies fail
Most technology strategies fail for predictable reasons:
They’re disconnected from business priorities. A strategy built around technology trends rather than business needs will always struggle for investment and support. If the strategy doesn’t map to revenue, cost, risk, or capability, it won’t survive the next budget cycle.
They assume a clean slate. Target architectures that ignore the current state are aspirational at best and damaging at worst. Real strategy works with what exists and charts a practical path forward.
They’re too abstract. A strategy that says “we will adopt a microservices architecture” without addressing migration sequencing, team capability, operational readiness, and integration complexity isn’t a strategy — it’s a wish.
They don’t account for change. Business priorities shift. Markets move. Key people leave. A strategy that can’t adapt to changing conditions is brittle by design.
What a practical strategy looks like
A technology strategy that survives contact with reality has several characteristics:
It starts with business context
The first question isn’t “what technology should we use?” — it’s “what does the business need to achieve in the next one, three, and five years, and what role does technology play?”
This means understanding growth plans, competitive pressures, operational constraints, and risk appetite. Technology strategy is a supporting function, not an end in itself.
It’s honest about the current state
Every strategy needs a credible baseline. This means an honest assessment of the current technology landscape: what works, what doesn’t, what’s at risk, and where the debt lies.
Skipping this step is one of the most common mistakes. Without a realistic current-state picture, the gap between where you are and where you want to be is invisible — and so are the risks of getting there.
It makes trade-offs explicit
Good strategy is about choices. Every decision to invest in one area means not investing in another. A practical strategy makes these trade-offs visible so that leadership can make informed decisions.
This is where many strategies fall short. They present a wish list of initiatives without ranking them, without sizing them, and without acknowledging that not everything can happen at once.
It’s sequenced for value delivery
A strategy that requires two years of investment before delivering any value is politically fragile. Practical strategies are sequenced so that each phase delivers measurable value while building toward the target state.
This doesn’t mean compromising on the end goal. It means finding the sequence of moves that delivers the most value soonest while keeping the long-term direction intact.
It includes governance without bureaucracy
Strategy without governance is just a document. But governance doesn’t have to mean heavy processes and approval committees. Lightweight governance — clear decision rights, regular architecture reviews, and explicit principles — is often enough.
The goal is to make it easy to make decisions that align with the strategy and hard to make decisions that contradict it, without slowing teams down.
The role of leadership
Technology strategy doesn’t happen in a vacuum. It requires active sponsorship from business leadership and genuine collaboration between business and technology teams.
This means technology leadership needs a seat at the table — not just to report on projects, but to contribute to business strategy. And business leadership needs to understand that technology decisions have strategic implications that go far beyond IT budgets.
Keeping the strategy alive
A strategy document that sits in a shared drive collecting dust isn’t a strategy. It’s an artefact. Living strategy requires:
- Regular review — at least quarterly, aligned with business planning cycles
- Clear ownership — someone must be accountable for the strategy, not just for its creation
- Visible connection to execution — teams should be able to see how their work connects to the strategy
- Willingness to adapt — when conditions change, the strategy should change too
Getting started
If your organisation doesn’t have a technology strategy, or if the existing strategy has lost relevance, the path forward is simpler than you might think.
Start with a clear-eyed assessment of where you are. Connect it to where the business needs to go. Identify the biggest gaps and the most impactful moves. Sequence the work for value delivery. And build just enough governance to keep things on track.
The result won’t be a perfect plan. But it will be a practical one — and that’s what makes the difference between strategy that lives and strategy that stays on a slide.