OCI DOMAIN TWO
Technology strategy
Very few environments are badly designed. Most are the accumulated result of decisions that were sound at the time and were never revisited. Technology strategy is the domain that asks whether the reasoning behind your current estate still holds, and whether anyone in the organisation owns that question.
Does any of this sound familiar?
A platform decision made three years ago is still in place. The problem it was chosen to solve no longer exists in the same form.
Renewals arrive, get approved, and the underlying question of whether you still need what you are renewing is never formally asked.
Your roadmap and your primary vendor's roadmap have become difficult to tell apart.
You could not say what it would cost or take to move off your current core platform, because nobody has modelled it.
Technical debt is acknowledged in conversation and appears in no document that anyone reports against.
What this domain examines
Decision ownership
Whether a named person is accountable for revisiting architectural choices, or whether they persist by default.
Licensing and renewal strategy
Whether renewals are evaluated against current need or approved on the basis of prior commitment.
Business alignment
Whether infrastructure decisions are made against where the organisation is going rather than where it has been.
Technical debt visibility
Whether known compromises are recorded, quantified, and reported, or held informally by the engineering team.
Exit options and lock in
Whether you have modelled the cost, time, and dependency involved in changing direction.
Enterprise agreement exposure
Whether large multi year agreements have been assessed for what happens at renewal rather than at signature.
Why this goes unnoticed
Nothing breaks when a technology decision stops being the right one. The system carries on working. The cost of a decision that has quietly outlived its reasoning is paid in renewal fees, in the operational complexity your team absorbs, and in the options it removes, none of which generate an alert.
The people best placed to tell you whether your architecture still makes sense are usually the people who sold it to you. That is not dishonesty on their part. It is structural. A vendor's account team is measured on retention and expansion, so the advice they give will be accurate within their own product line and silent about everything outside it.
Enterprise agreements make this sharper. A multi year commitment signed on favourable terms can become a significant liability at renewal, particularly where licensing models have changed underneath it. The exposure is created at signature and discovered years later, usually with very little time to respond.
How Technology Strategy is scored
Every domain in the Operational Confidence Index is scored 6 to 18. A higher score means lower operational confidence, so the highest scoring domain in your result is the one to start with.
What we usually hear
“We completed a strategy refresh recently.”
Then this should score well, and the index will show that in five minutes. The more useful question is who wrote the refresh and what they were selling, if anything.
“Our vendor advises us on this.”
Vendor advice is accurate about the vendor's own products. What it cannot do is tell you when the right answer sits outside their catalogue, because nobody is compensated for that conversation.
“We are mid project. We cannot revisit decisions now.”
Assessing does not mean reversing. Knowing where an in flight project has created long term exposure is more useful before it completes than afterwards.
“This is really a procurement question.”
Procurement can tell you what you are paying. It cannot usually tell you whether the architecture underneath it still fits the direction of the business, because that requires technical judgement rather than commercial comparison.
Questions about this domain
How is technology strategy scored in the OCI?
The Operational Confidence Index uses six questions, each scored 0 to 3, giving a domain range of 6 to 18. A higher score means lower operational confidence, so a high score here indicates this is where to start.
Do I need to prepare anything before answering?
No. The questions are answerable from what you already know. Where you do not know, that is a valid answer and it is reflected in the score.
Will this tell me which products to buy?
No. The index identifies where risk and cost concentrate. It does not recommend manufacturers, and Rullan Scott holds no reseller relationships.
We are a midmarket organisation. Is this aimed at us?
Yes. The index is built for organisations from around fifty staff upwards, where infrastructure has grown faster than the governance around it.
What happens after I complete it?
You receive a score, a breakdown by domain, and a report. If you want to talk it through, you can book thirty minutes with a cofounder. There is no follow up unless you ask for one.
The other three domains
Find out how your technology strategy scores.
Twenty four questions across four domains, five minutes, and an evidence based read on where your assumptions have drifted.
Run the OCI Diagnostic