The CIO was facing a difficult Board meeting.
Her organisation had invested more than $20 million in a new CRM platform. It was meant to underpin an ambitious strategy to grow and consolidate operations across Europe: one common platform, one standard way of working, and the foundations for expansion.
Two years in, the expected benefits had not materialised. Delivery was slipping, costs were mounting and confidence in the transformation was draining away.
The Chief Sales Officer was furious. He pointed directly at one of the technology vendors, demanded accountability and wanted the investment recovered. The CIO was left defending a programme that was getting harder to justify every month.
The problem nobody had addressed
The fundamental problem wasn't the technology. The organisation had tried to implement a Europe-wide CRM platform without first agreeing how its European business should operate.
When an independent review was commissioned, the underlying issue surfaced quickly.
The organisation had no consistently documented sales processes, even within individual countries, let alone a common operating model across Europe. There was no agreed approach to managing customers, opportunities, processes or responsibilities across markets.
In short, the business expected the CRM platform to provide the operating model rather than enable it.
More concerning still, the original project initiation documents had explicitly listed the target operating model as a prerequisite. As the programme progressed, that dependency slipped, was deprioritised and eventually dropped out of management attention. Along the way, the expectation quietly shifted. The business stopped owning how it would operate, and the IT programme was left to deliver the operating model through the system it was configuring.
The tail was wagging the dog.
The CIO now faced a choice: keep defending the existing programme, or change how the transformation was being led. She chose the latter.
Five moves that turned the programme around
1. She stopped defending the programme and named the real problem
Her first move was to change the conversation with the Board. Instead of another revised delivery plan, or a list of the vendor's shortcomings, she acknowledged that the organisation had approached a business transformation as a technology implementation.
She separated three issues that had been conflated: technology delivery, business readiness and vendor performance. The vendor might have missed some contractual obligations. The technology might have limitations. But neither explained why the business had tried to deploy a common European platform without defining common European processes.
Naming the root cause moved the conversation from who was to blame to what needed to change.
2. She established what could be recovered before spending more
Next, she regained control of spend and delivery. She paused discretionary rollout activity and commissioned an independent assessment built around five questions:
- What had actually been delivered for the $20 million?
- Which technology components and capabilities could be retained?
- What were the underlying causes of the delivery difficulties?
- What business value, if any, had already been realised?
- What would it take to recover the transformation?
In parallel, the organisation reviewed the vendor's contractual obligations and performance. But the CIO resisted pressure to make the vendor dispute the centrepiece of the recovery. Replacing a supplier might fix specific delivery failures; it would not fix the absence of a common operating model.
The assessment gave a factual basis for deciding what to keep, what to change and whether further investment was justified. The objective was no longer to protect the $20 million already spent. It was to protect the value of every dollar spent next.
3. She put the operating model ahead of the technology
This was the most significant change. The CIO worked with the Chief Sales Officer and country leadership to establish a common European target operating model.
Instead of asking how the CRM platform should be configured, the organisation started with more fundamental questions. How should sales opportunities be managed across Europe? Which processes should be standardised, and where were local variations genuinely necessary? Who owned customer data? Which decisions should be made centrally, and which should stay with individual countries?
These were business decisions, not technology decisions. The principle adopted was standardisation wherever practical, with local variation only where genuine commercial or regulatory requirements justified it.
Rather than designing every detail upfront, the recovery focused on a minimum viable operating model, validated in one geography before being replicated elsewhere. For the first time, the operating model was an input to technology delivery rather than an output of it.
4. She made the transformation a shared executive responsibility
The review had exposed another weakness. The programme was meant to deliver commercial growth and operational consolidation, yet accountability had become concentrated in IT. The CIO was defending delivery while the Chief Sales Officer was attacking the vendor. Neither position reflected the shared ownership a business transformation needs.
So the CIO reset the governance model:
- Chief Sales Officer: accountable for defining the business processes, driving adoption and delivering commercial outcomes.
- Country leaders: responsible for local business readiness and implementation.
- CIO: accountable for the technology platform, integration, architecture and technical delivery.
- CFO: investment oversight and benefits governance.
- CEO: sponsor of the cross-business decisions needed to achieve European standardisation.
Crucially, the programme introduced explicit business readiness gates. No further country would go live without agreed processes, clear ownership, acceptable data quality and demonstrated operational readiness. Independent delivery assurance was added to give an objective view of progress, risk and readiness.
The transformation was no longer something IT delivered to the business. It was something the business and IT were accountable for delivering together.
5. She rebuilt the roadmap around business outcomes, not technology milestones
Finally, the CIO challenged the programme's definition of success. Progress had been measured through technology milestones: functionality delivered, integrations completed, systems configured, countries scheduled. None of them showed whether the investment was achieving its strategic purpose.
The recovery roadmap was rebuilt around the outcomes the business had set out to achieve: better visibility of the European sales pipeline, lower cost to serve, higher sales productivity and faster expansion into new markets.
The rollout strategy changed too. Instead of a broad European deployment, the organisation moved to three phases:
- Prove: establish the operating model and show the technology supports it in one geography.
- Replicate: extend the model into a second market, confirming it scales without extensive redesign.
- Scale: expand across Europe using proven processes, configurations and deployment methods.
Each phase needed evidence of business readiness, measurable value and a credible investment case before the next could start. The focus had shifted from delivering a CRM system to enabling a European growth strategy.
The bigger failure wasn't the missing operating model
The lesson here goes beyond CRM.
The original project documentation had identified the target operating model as a critical dependency. It wasn't an unforeseen issue discovered halfway through delivery. The organisation knew it needed an operating model before implementation began. Yet that dependency quietly fell off the programme's priorities while investment and delivery carried on.
The real governance failure was allowing a critical prerequisite to stay unresolved without triggering executive intervention.
Effective programme governance does more than track milestones, budgets and risks. It keeps testing whether the conditions for success are still in place:
- Are the original business assumptions still valid?
- Have critical dependencies been delivered?
- Is the business ready to adopt the change?
- Does the investment case remain credible?
Had those questions been asked, and acted on, earlier, the organisation might have avoided much of the cost and disruption that followed.
What other CIOs can learn
The lesson is not that CRM implementations are inherently difficult, or that technology vendors can't be trusted. It is that technology cannot compensate for an organisation that hasn't agreed how it wants to operate.
Three principles stand out.
Business transformation must be led by the business. Technology can enable new ways of working. It cannot resolve fundamental disagreements about processes, responsibilities and operating models.
Critical dependencies must stay visible throughout delivery. Identifying them at initiation is not enough. They need active management, clear ownership and consequences when they aren't delivered.
Independent assurance should challenge the conditions for success, not just report progress. A programme can look on track against its technology plan while drifting further from the outcomes it was set up to achieve.
For this CIO, recovery began when she stopped defending the implementation and started addressing the transformation. That is often the difference between continuing to fund a troubled programme and creating a credible path to business value.
Performance Radar provides independent delivery assurance for technology leaders running complex programmes. To discuss your situation, schedule a 15-minute introduction.