An organisation without a roadmap is not undirected. It is directed by whatever is shouting loudest at any given moment.
The strategic vacuum does not feel like a vacuum from the inside. There is plenty of activity. Decisions are being made. Projects are being funded. Vendors are being selected. The organisation appears to be moving.
What is missing is a way to test whether any of it is moving in the right direction.
Free · 4 minutes
Do you know where AI is already being used in your business — and what it can see?
Fourteen questions on shadow AI, data exposure, oversight, and governance debt — the gap between how fast AI is arriving and how much control you have over it. Banded finding on screen, full sheet by email.
The reactionary default
Without a stated direction, technology decisions get made on other grounds. Vendor relationships, departmental pressure, calendar mechanics, end-of-year budgets, personal preference, what worked last time, what the competitor announced last week.
Each decision is justifiable in its own terms. The CRM project was needed. The reporting platform was overdue. The new website looked dated. The integration was promised to a key account. None of these are wrong individually. What is wrong is that none of them are being tested against a shared destination, because there is no shared destination to test them against.
The result is an organisation that is busy, expensive, and reactive. Activity is high. Progress is harder to identify. Money is spent. Strategic position changes very little.
The most consistent symptom is fatigue. Senior people feel they are constantly responding to demands rather than building toward anything. The technology team feels its work is unrewarded, because nobody can articulate what successful delivery would look like beyond “the project shipped.” The business feels stuck despite obvious investment.
This is not a discipline problem. It is a navigation problem. An organisation that does not know where it is going cannot tell whether it is making progress.
What a roadmap actually provides
A roadmap is not a project list. It is a direction.
It states what the organisation is trying to become — over the next year, the next three, the next five — in terms specific enough to be tested against. The kind of customers it serves. The capabilities it must develop. The markets it intends to enter or leave. The size and shape of the organisation that will deliver those things.
This sounds obvious. It is frequently absent. Many organisations operate with a strategy that exists in the founder’s head, the CEO’s email, or the last off-site presentation deck — none of which is accessible to the people making weekly technology decisions.
A roadmap that is not written down, shared, and used to evaluate decisions is not a roadmap. It is an intention. The difference between the two is whether the organisation can use it.
KPIs as the measurement layer
A roadmap states direction. KPIs measure whether the organisation is moving in that direction.
The number does not have to be large. Five KPIs at the business level, well chosen and consistently measured, will do more for clarity than fifty that nobody trusts. The discipline is in the selection: which numbers, when they move, indicate that the strategy is working — and which numbers, when they fail to move, indicate that the strategy is not.
Most organisations do not lack data. They lack a small set of measures that are agreed at the top and used to evaluate everything else. The reports proliferate. The dashboards multiply. The number of meetings in which numbers are discussed grows. But the question “is the business succeeding by its own definition” rarely has a confident answer.
KPIs without a roadmap measure nothing. They report on activity. A roadmap without KPIs is rhetoric. The two together create the conditions under which decisions can be tested.
The decision test
When the roadmap and KPIs exist, every technology decision can be evaluated against a simple question: how does this decision move the relevant KPI in the direction the roadmap requires?
A new CRM might support a sales growth KPI by reducing time-to-quote. A reporting platform might support a margin KPI by surfacing cost data that is currently invisible. A warehouse system might support a customer retention KPI by reducing fulfilment errors. Each is a defensible decision, anchored to a measurable outcome that contributes to a stated direction.
A new platform that cannot be located on the roadmap, or shown to contribute to a stated KPI, should not be funded. This sounds harsh. It is much less harsh than continuing to fund decisions that produce no measurable contribution to the organisation’s direction.
This test does not eliminate disagreement. Reasonable people can debate which KPI a decision serves, or how much it will move the number. The debate itself is the value. It forces the decision to be justified in terms the organisation has already agreed are important — rather than in terms of who wanted it, who promised it, or which budget line had funds available.
Why this is a technology problem
Strategy is a business question. KPIs are a board question. Why is this on a technology consultant’s blog?
Because the absence of these things is most visible — and most expensive — in technology decisions. Every IT investment is an opportunity to test whether the organisation is moving toward a stated goal. Every IT investment without that test is an opportunity to drift.
Technology is also where the reactionary pattern produces the most lasting damage. A poor marketing decision can be reversed in a quarter. A poor technology decision becomes embedded in the architecture, the data, the operational practices, and the budgets of subsequent years. The cost of strategic vacuum at the technology layer compounds for much longer than at other layers.
Senior technical leadership has a role here that is not always visible. Part of the job is to refuse decisions that cannot be justified against the roadmap. Part of the job is to surface the absence of a roadmap when it becomes clear that one does not exist. Neither role is comfortable. Both are necessary.
A few rules
A roadmap that is not written down is not a roadmap. It is a private intention. The organisation cannot use it. Write it down. Share it. Use it.
Five KPIs at the top, well chosen, beat fifty that nobody trusts. The discipline is in the selection. Each one should be a number that, when it moves, indicates whether the strategy is working.
Every funded decision should pass the test. How does this contribute to the KPI? If the answer is unclear, the decision is reactionary. If the answer is clear but the contribution is small, the decision is competing with better uses of the same budget.
The absence of a roadmap is its own diagnostic. When decisions feel arbitrary, when senior people feel constantly reactive, when investment produces activity but not progress — the cause is usually that there is nothing to navigate by.
Strategic vacuum is most expensive at the technology layer. Other decisions are reversible in a quarter. Technology decisions become embedded for years. Apply the test most rigorously where the consequences last longest.
Richard King is CTO at Sixteen Pillars — technical leadership, architecture, and governance for organisations that need it without the overhead of a full-time hire.
Most technology problems are not technology problems. They are control problems.
The systems exist. The investment has been made. The question is whether leadership can understand, direct, evidence, and sustain what those systems produce. Find out where control exists — and where it only appears to.