Target capability
What the organisation needs to be able to do, expressed in business terms rather than technologies.
Independent advisory / Services
Technology Strategy
An independent technology strategy connecting business priorities, architecture, capability, investment and a credible delivery roadmap.
Decisions, not ambition
A strategy is a set of decisions about what not to do.
A useful technology strategy names the trade-offs it accepts, the capability it assumes and the constraints it is willing to live with. Without those, it is a set of intentions rather than a plan.
From priorities to a credible roadmap
Fewer inputs, clearer decisions.
Priorities, constraints, capability and evidence converge on a small number of decisions that then shape investment, roadmap and ownership.
What the strategy must settle
If a decision is not made here, it is made by default.
Each of these has a consequence whether or not it is addressed deliberately.
Architecture direction
The structural choices that either enable or obstruct those capabilities over the next few years.
Investment profile
Where money goes, what it buys and what is explicitly not being funded.
Sequencing
What must happen before what, and which enabling moves unblock the most value.
Ownership and capacity
Who is accountable for delivery and whether the organisation has the capability it assumes.
Measures of progress
Signals that show whether the strategy is working before the next planning cycle.
Independent of the vendor answer
No platform to sell.
Strategy shaped by preference rather than constraint is expensive to unwind.
We are not aligned to a platform, product or delivery model. Recommendations follow from the outcome, the estate and the organisation's capacity to operate what is chosen.
- No platform agenda
- Evidence over fashion
- Options preserved
- Trade-offs explicit
Trade-offs stated openly
The tensions every strategy has to resolve.
| Theme | The tension | How we decide |
|---|---|---|
| Accelerate or stabilise | Delivery pressure against the resilience of the estate. | Named risk owners and an explicit ceiling on accepted fragility. |
| Standardise or federate | Consistency against the autonomy teams need to move. | Scale of the organisation and the maturity of its engineering practice. |
| Build or buy | Control and differentiation against speed and operating burden. | The cost of exit, integration and long-term dependency. |
| Invest now or defer | Current cost against future constraint. | Whether deferral increases the eventual cost or genuinely preserves options. |
| Modernise or consolidate | Reducing technical constraint against reducing duplication. | Which removes the binding constraint rather than the visible one. |
Stating the tension makes the strategy testable. A direction that claims to resolve every tension is not a direction.
When to engage
Moments when strategy matters most.
Reset
A strategy that needs to be rebuilt
Where previous plans did not survive contact with delivery or the business.
Budget
An investment cycle approaching
Where technology spending needs to be defended against outcomes rather than activity.
Pressures
Competing technology pressures
Several urgent demands with no agreed basis for sequencing them.
Leadership
New technology leadership
Where an independent view of the estate and its options is needed quickly.
Divergence
Business and technology priorities diverging
Where the roadmap no longer reflects what the organisation is trying to achieve.
Assurance
A strategy that needs independent testing
Where significant commitment rests on assumptions that have not been examined.
What the engagement can produce
A direction that survives delivery.
Strategy is written to be used by engineering, finance and leadership together, not to be admired as a document.
- 01Technology strategy and direction
- 02Capability and gap assessment
- 03Architecture direction and principles
- 04Investment and funding profile
- 05Sequencing and dependency view
- 06Ownership and operating implications
- 07Measures of progress
- 08Decision records for the trade-offs accepted
Engagement enquiries
Discuss the strategy requirement.
Bring the priorities, the constraints and the decisions that need to be made. We will be clear about what can be established and what depends on your own data.
Useful links
Recommendations are independent of any platform, product or delivery partner.