Direct answer
Technology Strategy produces a roadmap the business recognises, a portfolio governed on value, and a run cost that can be defended line by line. Vision, portfolio, delivery discipline and FinOps are held together, because a roadmap without a cost model is a wish and a cost model without a roadmap is a cut.
What the mandate produces
- A two-to-three-year investment roadmap with named owners and decision gates
- Portfolio governance that arbitrates on value, not on volume
- Delivery discipline and the PMO that holds it
- Sourcing and vendor management against the target state
- A run cost broken down and defensible line by line
Six sub-capabilities, six proven
- IT vision and roadmap
- IT governance
- Portfolio and value management
- Delivery and PMO
- Sourcing and vendor management
- FinOps
What it is not
It is not enterprise and solution architecture. Technology Strategy decides — what is invested in, in what order, at what cost. Enterprise and solution architecture structures what has been decided, and lives in the Engineering expertise. Neither page crosses into the other's vocabulary.
How the mandate runs
Four workstreams that only make sense together. The estate as it is, costed. The ambition, expressed as a target architecture rather than as a list of technologies. The portfolio that moves from one to the other. And the governance that keeps arbitrating it after the roadmap is written.
The costing comes first and is usually the uncomfortable part. Most estates cannot attribute their run cost to the products and teams that cause it, which means every prioritisation conversation is held without the one number that should inform it.
The roadmap is built in waves with decision gates rather than as a two-year plan, because a plan that cannot absorb a changed assumption is abandoned at the first one. Each wave names an owner and the value it is accountable for.
What is handed over is a roadmap the business recognises as its own, a portfolio governed on value rather than on volume, and a cost model the finance function can audit without ARCHITEKT in the room.
What the estate usually reveals
Three findings recur across mandates, and they are worth naming because they change what the roadmap has to contain.
The first is that the portfolio is governed on volume rather than on value: projects are prioritised by how loudly they are requested and how far along they already are, which is a ranking of sunk cost. Replacing it requires a value expression each initiative can be held to, and that is harder than the ranking itself.
The second is a run cost nobody owns. Cloud and licence spend accumulates against services whose original requester has left, and the finance function receives a single number it can only cut proportionally. Attribution is the fix, and it is unglamorous work that pays for the rest of the mandate.
The third is a delivery function judged on activity. Throughput reported without reference to outcome produces roadmaps that are always on track and never done. The strategy names what each wave is accountable for so that the question can be asked at all.
What it is not
It is not enterprise architecture. Technology Strategy decides — what is invested in, in what order, at what cost. Enterprise and solution architecture structures the decision, and it lives in the Engineering expertise. Neither page borrows the other's vocabulary, because a buyer searching for one and landing on the other has been misled about what they are buying.
It is not a tooling selection exercise. A vendor choice made before the portfolio governance exists is a decision that will be revisited, and revisiting it is more expensive than sequencing it properly.
How it ends
With a named owner inside the organisation who holds the roadmap and the portfolio governance after ARCHITEKT leaves. Where no such owner exists yet, the seat is held on an interim basis until one does — a strategy handed to nobody is a document, and documents do not survive a budget round.
Who it is bought by
A chief executive facing a technology budget they cannot interrogate, a new technology leader who needs an evidence baseline before committing to a roadmap, or an investor whose thesis depends on a run cost coming down. The signal is the same in all three: a number nobody can defend line by line.
Exit
A roadmap the business recognises, a portfolio governed on value, and a cost model the finance function can audit without ARCHITEKT in the room.
Questions
- What does a technology strategy mandate deliver?
- A target architecture ambition translated into a two-to-three-year investment roadmap with named owners and decision gates, the portfolio governance that arbitrates it, and the cost model that makes it defensible.
- Does it include FinOps?
- Yes. FinOps is a sub-capability of the strategy, not a separate engagement: a roadmap that does not carry its run cost has not been costed. Where FinOps is the whole of the need, it is bought as an expertise instead.
- How is this different from enterprise architecture?
- Technology Strategy decides. Enterprise and solution architecture structures the decision. The first is an Advisory mandate; the second is a specialty of the Engineering expertise.
- Who holds it after the mandate?
- A named owner inside the organisation, identified during the mandate. Where no such owner exists yet, the seat is held on an interim basis until one does.