- Why "digital transformation" is overused and what it actually means when applied rigorously
- The difference between digitisation, digitalisation, and transformation — and which one most Salesforce programmes actually deliver
- Why technology implementation alone does not produce transformation and what the missing ingredients are
- The conditions that must exist for a Salesforce programme to be genuinely transformative
- How to honestly position a Salesforce programme — and why honesty about scope protects the programme
The Language Problem
Every Salesforce implementation deck includes the phrase "digital transformation." It appears in the business case, the programme charter, the executive briefings, and the go-live communications. It is used so ubiquitously that it has become meaningless — and its meaninglessness is actively harmful to programme success.
When a programme is labelled as transformation without being designed as transformation, three things reliably happen. First, expectations are set that the programme cannot meet — users expect their work to feel fundamentally different, executives expect a step-change in performance, and neither happens from a CRM implementation that replicates existing processes in a new platform. Second, the real work of transformation — process redesign, operating model change, cultural shift — is omitted from scope because the technology implementation alone is assumed to be sufficient. Third, when the programme delivers a working CRM but not the promised transformation, it is deemed a failure against expectations it was never designed to meet.
Digitisation: converting paper-based or manual processes to digital (a CRM replacing spreadsheets). Digitalisation: using digital technology to improve or change existing processes (automating lead qualification that was previously manual). Transformation: fundamentally changing how the business operates, creates value, and engages with customers — enabled by but not caused by technology. Most Salesforce implementations are digitisation or digitalisation. Very few are transformation.
What Transformation Actually Requires
Genuine business transformation through Salesforce requires four things that technology alone cannot provide:
Operating model change. Transformation changes how work is organised, not just how it is done. A transformed sales organisation does not just use Salesforce to log calls — it has restructured territory management, account ownership, compensation models, and manager cadences around the data and automation capabilities of the platform. This requires HR, finance, and business leadership involvement — not just IT and the Salesforce team.
Process redesign, not process replication. The most common failure in "transformation" programmes is implementing existing processes in Salesforce rather than redesigning them. If the legacy CRM had a 12-step opportunity process, implementing the same 12-step process in Salesforce is digitisation, not transformation. Transformation asks: given the capabilities of Salesforce, what should this process look like if we designed it today? That question is harder to answer and requires more business engagement — but it is the only path to genuine transformation.
Data strategy. Transformation is impossible without trustworthy data. An organisation that transforms its customer engagement model on a foundation of poor data quality will make wrong decisions faster — which is worse than making wrong decisions slowly. Data quality assessment, data governance, and master data management must be components of any programme that genuinely aspires to transform the business.
Cultural and behavioural change. Technology changes what is possible. Culture determines what actually happens. A sales team that does not believe in data-driven management will work around the pipeline discipline that Salesforce is supposed to enable. A service team that does not trust the Knowledge Base will continue to solve problems independently rather than sharing solutions. Transformation requires sustained behavioural change — supported by management, measured, and held accountable.
The Transformation Readiness Test
Before labelling a Salesforce programme as transformation, test it against five readiness questions:
1. Has the operating model been redesigned? If the org chart, role definitions, and management structure are unchanged, the programme is not transformational. Transformation changes how the business is organised, not just what tools it uses.
2. Have processes been redesigned from first principles? If the Salesforce configuration maps directly to the legacy system's processes, the programme is digitising the past. Transformation requires asking what processes should be, not what they were.
3. Is there a data quality programme? Transformation that runs on poor data is not transformation — it is automated confusion. A programme without a data quality workstream is not designed for transformation.
4. Is there genuine executive sponsorship? Transformation requires leaders who will make decisions about process redesign, operating model change, and cultural expectation. A programme sponsored by IT but not by the business leadership of the affected functions cannot transform the business.
5. Are change management and adoption outcomes in the programme success criteria? If success is defined entirely by technical delivery milestones (go-live date, features delivered, zero P1 defects), the programme is not designed for transformation. Transformation measures behaviour change and business outcomes.
Honest Positioning — Why It Protects the Programme
There is a strong temptation to use transformation language because it justifies larger budgets, higher executive attention, and stronger sponsorship. The short-term benefit of the label rarely outweighs the long-term cost.
A programme honestly positioned as "implementing Salesforce to improve our sales process efficiency and data quality, with a target to reduce average sales cycle by 15%" sets expectations it can meet. A programme positioned as "transforming our customer engagement model" sets expectations it almost certainly cannot meet from a CRM implementation alone.
Programmes that meet their stated objectives get funded for the next phase. Programmes that fail against unrealistic expectations built on transformation rhetoric rarely get the investment needed to realise the potential of the platform they have just built.
The most successful transformation journeys position the Salesforce implementation as Phase 1 (foundation) and genuine transformation as Phase 2 (enabled by the foundation). This is honest, achievable, and builds credibility for the larger investment. Phase 1 delivers the platform. Phase 2, built on clean data and adoption in Phase 1, delivers the transformation. This sequencing works far better than promising transformation and delivering CRM.
When Salesforce Genuinely Enables Transformation
Dismissing all "digital transformation" language as hype would be wrong. Salesforce can genuinely enable transformation — when the conditions are right. The cases where transformation is real share common characteristics:
The business was genuinely constrained by its previous technology. Replacing a system that made Customer 360 impossible with one that makes it possible is transformative — if the business actually changes how it uses the customer insight. The legacy constraint was a genuine barrier, and removing it enables genuinely new behaviours.
The programme was designed as transformation from the start. Process redesign, operating model change, and change management were in scope from the business case. The technology implementation was one workstream among several — not the entire programme.
Leadership drove the change. The transformation was owned by business leaders who were accountable for the business outcome, not just IT leaders accountable for the technology delivery. The CTO was the enabler, not the driver.
Key Takeaways
- Most Salesforce implementations are digitisation or digitalisation — implementing existing processes in a better platform. Very few meet the definition of genuine transformation
- Transformation requires operating model change, process redesign, data quality investment, and cultural and behavioural change — technology alone cannot provide any of these
- Labelling a programme as transformation when it is not sets expectations it cannot meet, typically producing a "failed" programme that delivered a working CRM
- Test transformation readiness: operating model redesign, process redesign, data quality programme, genuine executive sponsorship, and behaviour-change success criteria
- Honest programme positioning protects long-term investment — programmes that meet their stated objectives get funded; programmes that fail against transformation rhetoric rarely do
- Genuine transformation is achievable with Salesforce — but only when designed as transformation from the outset, not retrofitted as a label onto an implementation
Checkpoint: Test Your Understanding
1. A Salesforce programme replicates the existing 14-step opportunity management process from the legacy CRM into Sales Cloud, with the same field names and approval steps. How should this be characterised?
2. Why does using "transformation" language to justify a Salesforce implementation create long-term risk for the programme?
3. What is the most important factor that distinguishes a Salesforce programme that genuinely enables transformation from one that merely implements CRM?
Discussion & Feedback