Mark Nicholls, Chief Operating Officer, Cerillion, explains why telecom operators must rethink their approach to BSS/OSS modernisation, arguing that business ownership, executive accountability and clearly defined commercial outcomes are more important than technology selection.
Telecom operators have invested billions in modernising billing, ordering and customer management systems. Yet programmes disappoint, raising an uncomfortable question: what if the problem starts before the technology is selected?
Boston Consulting Group estimates that more than 70% of transformation projects miss their objectives. McKinsey found organisations captured a median 31% of expected revenue benefits and 25% of anticipated cost benefits from Digital Transformation.
Mark Nicholls, Chief Operating Officer, Cerillion, argues that unclear commercial goals, weak ownership and inadequate executive accountability can undermine even technically successful projects.
Q: Why do telecom transformation programmes fail to deliver?
Many programmes begin without a sufficiently clear understanding of what the business wants to achieve. Operators spend time evaluating platforms and integration requirements, but replacing software is not the same as transforming operations.
Legacy systems create difficulties, yet technology is often blamed for problems rooted in organisational decisions. If leaders have not agreed which processes must change, who owns the outcomes and how improvements will be measured, a successful deployment can disappoint commercially.
Transformation needs a business case that goes beyond installing a new platform.
Q: What should operators decide before issuing an RFP?
They must establish what kind of business they want to become. Which customer experiences need improvement? Which processes should disappear rather than be automated? Which products and activities no longer justify their complexity?
These decisions belong to the operator, not the supplier. If they are postponed, procurement begins defining the transformation by default. Teams select technology against functional requirements without knowing whether those functions support commercial priorities.
A clear strategy makes vendor evaluation meaningful. It also provides a basis for rejecting capabilities that do not advance the business objectives.
Q: Why should IT not lead transformation alone?
IT is essential, but BSS and OSS modernisation changes product design, customer journeys, order fulfilment and responsibilities. Technical teams cannot set commercial priorities or redesign how the organisation operates.
A programme can meet its technical targets while preserving inefficient processes and fragmented customer experiences. Delivering software on time and within budget does not necessarily mean customers receive better service or employees work more efficiently.
Business leaders must own the outcomes, with IT providing the expertise and systems needed to achieve them. Shared delivery responsibility matters, but commercial accountability cannot be delegated to technology teams.
Q: How much does executive sponsorship matter?
There is a difference between naming a sponsor and maintaining executive leadership. Initial enthusiasm is insufficient when implementation requires difficult decisions about budgets, processes and departmental responsibilities.
Effective sponsors resolve competing priorities, remove barriers and remain accountable for the promised benefits. Prosci research found that projects with extremely ineffective sponsors had a 27% likelihood of meeting objectives, compared with 79% for those with extremely effective sponsors.
Sponsorship must therefore be visible and sustained. Without it, unresolved disagreements accumulate and the programme drifts away from its original business case.
Q: Are smaller projects preferable to major transformations?
Not necessarily. Operators can retain ambitious objectives while organising delivery into stages that produce measurable business value. The distinction is between incremental transformation and simply splitting a large software rollout into smaller technical releases.
Milestones should represent improved capabilities, such as faster onboarding, simpler products or less effort launching services. Each stage needs an operational or commercial measure of success.
This allows leaders to test assumptions, identify disappointing results early and change direction before migration decisions become entrenched. It also gives sponsors evidence of progress beyond completed technical tasks.
Q: What does Telstra’s T22 programme demonstrate?
Telstra’s T22 transformation showed the importance of removing complexity rather than transferring it into replacement systems. The operator reduced its consumer and small-business product portfolio from 1,800 products to 20.
The lesson is that historical complexity should not automatically survive modernisation. Every obsolete product, exception and cumbersome process recreated in new software adds cost and makes future change harder.
Operators should challenge what needs preserving. Simplification before or alongside deployment can reduce implementation risks and create a more efficient operating model. Technology then supports a cleaner business rather than digitising decades of accumulated compromises.
Q: How should operators measure success?
Governance must connect workstreams to commercial outcomes. That requires clear ownership, defined measures and authority to challenge decisions that undermine the wider strategy.
Budgets, deadlines and deployment milestones remain important, but they cannot be the only indicators. Leaders should ask whether onboarding has accelerated, service delivery has improved, operating costs have fallen or product launches have become easier.
Complex programmes involve multiple suppliers and departments, each with its own priorities. Without common measures, teams can optimise their performance while weakening the overall business case.
Regular reviews should test benefits against expectations and trigger corrective action. The question is not how much technology has been delivered, but what has materially improved for customers and the business.
Q: What is your advice before BSS/OSS transformation?
Define the business outcome and establish ownership before selecting technology. Business leaders must specify the changes required and remain accountable. Executive sponsors must resolve obstacles. Governance must keep delivery aligned with the objectives.
Operators should be able to answer three questions: who owns the transformation, what outcome are they responsible for and how will success be demonstrated?
Once those answers are clear, technology selection becomes disciplined. The chosen platform should enable the transformation the organisation has defined, rather than determine its direction.
Software alone cannot compensate for a programme without clear commercial purpose.

