Adapted from Ashay Saxena’s Experience Report, IBM Sales Cloud: Transforming the way we sell globally, this case study examines IBM’s global Salesforce rollout through the lens of Closing the Change-Readiness Gap. The change-readiness gap is the distance between an organization’s aspiration to adapt and its capability to realign people, decisions, structures, and work as conditions change. Download the full report.
IBM set out to create one global CRM that would simplify sales work, increase seller time with clients, replace more than 160 tools, and improve reporting. The company set a one-year target for global rollout.
The difficult part was keeping that strategy useful as it moved through eight development teams and numerous groups responsible for architecture, data, compliance, testing, and user enablement. What teams learned about real data, users, and business-unit needs also had to travel back into program decisions.
Closing the change-readiness gap requires a two-way connection between strategy and delivery. Strategic intent must remain clear as it reaches the teams doing the work, while what those teams learn through delivery must travel back to the people shaping priorities and plans. That feedback loop is central to enterprise agility: strategy guides delivery, and delivery helps the organization test and adjust its plans without losing its overall direction.
Four barriers that widen the change-readiness gap
Four common barriers can weaken the connection between strategy and delivery:
| Barrier | What happens |
|---|---|
| Signal loss | Strategic intent loses clarity as it moves through the organization, making it harder for teams to make sound decisions as conditions change. |
| Decision rights | Authority sits too far from where the work is happening, slowing decisions and adaptation. |
| Structural barriers | Dependencies, handoffs, governance, and other organizational structures make it harder for work to respond to changing conditions. |
| Psychological safety | Risks, concerns, and conflicting evidence do not surface early enough because people do not feel able to challenge assumptions or speak candidly. |
The IBM experience does not illustrate all four barriers equally. Two are especially visible in this case: signal loss, as strategic intent lost practical meaning on its way to delivery, and structural barriers, as dependencies and organizational complexity made coordinated delivery harder.
Where the Plan Met Reality
Business architecture was too high-level
Business architecture was presented three months into the program, but it remained too high-level to provide enough guidance for backlog elaboration and solution design.
What this shows: a clear business goal is not enough if teams don’t receive enough context to make sound decisions. This is one form of signal loss: the intent reaches delivery, but some of its practical meaning is lost along the way.
Production exposed a data mismatch
The production territory load was designed around a country-level account hierarchy, while IBM’s trusted territory data was based on city-specific accounts. Sellers saw incorrect accounts in their territories, which also affected dashboard data.
What this shows: enterprise assumptions need to be tested against real operational data and user experience. Production is not simply the end of delivery. It is a source of information about whether the organization’s assumptions were correct.
Standardization did not fit every business unit
IBM began with a standardized sales process, but some business units needed more time to adopt it. The program introduced tactical platform customizations where a uniform approach did not fit operational needs.
What this shows: coherence does not require every part of an organization to work identically. A shared direction can remain intact while different business units respond to their own conditions.
How IBM Adapted the Delivery System
Teams took more end-to-end ownership
According to the original experience report, IBM moved Salesforce into live use at enterprise scale. About 30,000 sellers were using IBM Sales Cloud, and more than 10 million records had been migrated and streamed to downstream applications. The report also noted that development teams recorded just one Severity 1 incident related to delivered features, while seller feedback was described as extremely positive.
The model also pushed more leadership into the teams themselves. IBM described the teams as having enough agile maturity to lead the process, while leadership focused on technical guidance and removing blockers rather than directing how teams worked.
That does not necessarily mean all decision authority moved into the teams. Product and architectural decisions still had defined owners and governance paths. But giving teams broader end-to-end ownership reduced some of the structural barriers that otherwise force work to move repeatedly across specialized groups.
Work and dependencies became more visible
IBM used an Agile application lifecycle management tool as a shared source of information about progress, dependencies, and backlog flow. Scrum of Scrums meetings, cross-squad calls, program reviews, and steering updates gave teams and stakeholders a broader view of the work.
Shared visibility did not remove every dependency, but it made problems and trade-offs easier to see and manage.
Operational learning moved back into program decisions
After the first market went live, business units became more directly involved in initiative and epic elaboration, solutioning, and user feedback.
Production releases also became more frequent, moving from once per iteration to weekly and later to on-demand. This created a stronger feedback loop. Delivery did not simply execute the plan. It produced information that helped IBM change the plan.
What IBM Achieved
IBM moved Salesforce into live use at enterprise scale. About 30,000 sellers were using IBM Sales Cloud, and more than 10 million records were migrated and streamed to downstream applications. Development teams recorded one Severity 1 incident related to delivered features, and seller feedback was described as extremely positive.
What This Case Teaches
- Protect strategic intent from signal loss. A high-level business goal is not enough. Teams need enough context about users, business needs, architecture, and priorities to turn that intent into workable solutions. IBM’s experience with business architecture showed what can happen when that context remains too high-level.
- Reduce structural friction around the work. IBM organized cross-functional teams around CRM workstreams and deliberately reduced dependencies between specialized teams. Giving teams more of the capabilities needed to deliver an increment end-to-end made it easier to move work through the system.
- Use delivery to test assumptions. Production use exposed things that planning had not resolved, including the mismatch between the planned territory hierarchy and IBM’s existing data, as well as business-unit needs that did not fit a standardized approach. IBM responded by increasing business-unit involvement and adapting the implementation.
- Make it possible for problems to surface early. IBM encouraged teams to raise problems, discuss challenges in retrospectives, experiment, learn, and adjust. Feedback loops depend on people being willing and able to say when requirements, assumptions, or solutions are not working.
IBM’s experience shows that change readiness is not created by setting a strategy and asking teams to execute it. Strategic intent has to remain understandable as it reaches delivery, structures have to support the flow of work, and what teams learn through implementation and production use has to influence what happens next.
The IBM case gives especially strong evidence about signal loss, structural barriers, and feedback loops. It also shows practices that helped people surface problems and challenge what was not working. The evidence is less clear about how broadly decision authority itself moved closer to the teams, so that is a question worth exploring rather than assuming.
Read the original Experience Report “IBM Sales Cloud: Transforming the way we sell globally” by Ashay Saxena. Want to explore the issue further? Download the Closing the Change-Readiness Gap report to learn more about where strategy and execution become disconnected, and what leaders and delivery professionals can do about it.
