The Telecom CTO Is Becoming a Business Strategist
The technology leader's job used to be keeping the network running and the programmes on budget. In a business where the network is the product, that job is now inseparable from strategy, capital allocation and growth.
For most of telecom's history, the technology function had a clear brief: build the network, run it reliably, and deliver the programme portfolio on time and within budget. Strategy was set elsewhere, and technology executed it. That division of labour is breaking down, and the operators that recognise it early will allocate capital better than those that do not.
Why the brief has changed
Three shifts have pulled technology leadership towards the centre of business strategy.
- The network has become software. Decisions about platforms, cloud and automation now shape the cost structure and speed to market as much as any commercial decision.
- Capital intensity has not gone away, but the mix has changed. Choosing between building, buying and partnering is now a strategic call with a long tail, not a procurement exercise.
- Customer experience is increasingly produced by operations. How quickly the network detects, diagnoses and resolves problems is part of what customers are paying for.
When the product, the cost base and the customer experience are all shaped by technology choices, the person making those choices is making strategy, whether or not the organisation chart says so.
What changes in the role
From technology owner to business strategist
The traditional brief
- Deliver the programme portfolio on time and on budget
- Keep the network stable
- Report progress in technical milestones
The emerging brief
- Allocate capital across a portfolio against business outcomes
- Shape the operating model the technology runs inside
- Report in the board's language: margin, growth, risk and customer experience
The practical difference shows up in the questions a technology leader brings to the executive table. Not “is the programme on track?” but “is this still the best use of the capital?” Not “what does the platform need?” but “what will the business be able to do in two years that it cannot do today?”
The skills that matter now
Technical depth remains necessary. A technology leader who cannot tell a sound architecture from a fashionable one will allocate capital badly. But depth is no longer sufficient. The role also requires fluency in financial trade-offs, the judgement to stop programmes that have stopped earning their budget, the ability to redesign an operating model rather than add to it, and enough commercial awareness to see where the network can support growth as well as lower cost.
When technology shapes the product, the cost base and the customer experience, the technology leader is already a strategist. The only question is whether the organisation treats them as one.
What CEOs should ask for
The implication for chief executives is straightforward. Hold the technology function to business outcomes, and give it a seat where those outcomes are decided. Ask for the portfolio to be presented as capital allocation, not as a project list. And expect the technology leader to argue for what the business should stop doing, not only for what it should build next.
Enterprise Technology Executive
Anurag Kumar Mishra
I lead large-scale transformation across telecom and enterprise technology, connecting technology strategy, operating models and capital allocation to measurable business outcomes.
LinkedIn