We've lost count of how many technology transformation discussions begin with a solution. It is understandable. Technology is tangible. Vendors can demonstrate it, teams can budget for it, and executives can put a milestone against it. By contrast, the business problem is often harder to agree upon. Is the real constraint a slow workflow, a poor operating model, fragmented data, weak decision rights or a product proposition that no longer meets customer needs?
Choosing the technology first gives an illusion of momentum. It can also make the organisation exceptionally efficient at implementing something it never needed.
Start with the decision, not the platform
Technology strategy should begin by identifying the decisions, services and outcomes the organisation needs to improve. Take a trading business that wants a new operating platform. Is the objective to enter new markets, cut operational risk, make a fragmented workflow coherent, reduce total cost of ownership or help traders make better decisions? Those aims may overlap, but they lead to different investment priorities.
A cloud migration might reduce infrastructure friction without resolving fragmented ownership. An AI assistant might shorten searches without fixing unreliable data. A platform replacement might modernise screens while preserving unnecessary hand-offs. Each can still be valuable. None should be treated as the objective itself.
One useful test is brutally simple. If the preferred vendor or technology disappeared from the conversation, could the sponsors still describe success? If not, there may not yet be a strategy.
Follow the consequences
The next step is to trace the outcome through processes, information, people, controls and architecture. Who makes the decision? What do they need to know? Where does that information originate? Which controls matter? What is the cost of delay, failure or an incorrect decision?
Only then can you assess the competing options properly. Some problems need a new product. Others need to retire redundant systems, improve ownership, simplify integrations or change how teams work. Good advice is not always the advice that results in the largest programme.
Make investment decisions reversible
Technology strategy is also about managing uncertainty. Big, irreversible commitments based on weak assumptions are not signs of conviction. They are expensive experiments conducted without an exit plan.
Sequence investments to test the riskiest assumptions early. Define meaningful checkpoints. Establish what evidence would justify continuing, changing direction or stopping. And be clear about ownership of the outcomes after the project team leaves.
The questions worth asking before authorising the next transformation are these:
What must change?
Who benefits?
How will we know? What could invalidate our assumptions?
What are we willing to stop doing?
Technology can change what is possible. But when the tool becomes the strategy, the organisation has already surrendered the most important decision.
