Adoption case / 02 · Readiness, waves & champions

Designing adoption for a multi-subsidiary CRM rollout

One global standard, several very different starting points.

The case in brief

Current reality

A global CRM is deployed across subsidiaries with different maturity, roles, historical processes, data quality, local tools and management habits.

What must become true

Each subsidiary goes live when it is ready, with role-based enablement, a named champion, dated tool retirement and first-weeks support—and adoption is compared by level, read in local context.

Design question

How do we balance the global standard with local readiness—so each subsidiary adopts the same model without the rollout ignoring where it starts?

01The reality · current state

How work actually happens today.

A multi-subsidiary organization is rolling out one CRM and one commercial lifecycle to its subsidiaries. Some already manage from a CRM; others run on local trackers and email. Data quality, ERP integration status and management habits differ. The original plan deployed every subsidiary within one quarter, with the same training for everyone.

  • One go-live date for subsidiaries with very different readiness
  • The same screen-based training for every role in every country
  • Local trackers expected to “disappear” at go-live
  • No local support beyond a central ticket queue
  • Adoption compared by logins across very different units

02Approach

Not the obvious response—the approach.

Systems and partiesGlobal CRMLocal ERPsLocal trackers (retiring)Data platform

The obvious response“Deploy everywhere at once with the same training.”

Readiness differs. The least ready units fail visibly, and the failure is blamed on the system—not on the sequencing.

  1. 01Assess

    Score each subsidiary on seven readiness factors.

    Adoption owner
  2. 02Prepare

    Targeted preparation on partial factors; blockers resolved first.

    Local business owner
  3. 03Configure variation

    Only registered, approved local differences.

    Global governance
  4. 04Enable

    Role-based scenarios; champions trained on interpretation, not only screens.

    Adoption owner with champions
  5. 05Launch

    One wave at a time; the project team present in the pilot.

    Programme lead
  6. 06Stabilize

    Local support for the first weeks; bridges frozen.

    Local champion
  7. 07Measure

    Adoption level per unit, reviewed with local context.

    Adoption owner
  8. 08Improve

    Friction from every wave feeds one global backlog.

    Process owner

03Role value

What each role gives, gets and decides.

What each role gives, gets, decides and should not have to do
RoleGivesGetsDecidesShould not have to
Local sales directorSponsorship, local review cadenceThe same view of the business as global leadershipWhen local readiness gaps are closedKeep a local tracker “until things settle”
Local championFeedback, first-line support, local contextTime allocated and a direct route to ownersWhat to escalateDecide process or system changes
Sales repOpportunity state, customer contextEnablement on their own scenariosNext commercial actionsAttend training on screens they will never use
Global process ownerThe core process, variation decisionsComparable adoption and friction per unitCore changes and variationPush a date on a unit that is not ready

04Key dimension · Readiness, waves & champions

Readiness decides the wave—not the calendar

Seven factors per subsidiary. A blocker stops the date; partial factors get targeted preparation; ready units pilot or deploy.

Select a unit to see its readiness by factor, its wave and the action it needs.

PilotSubsidiary North

Process
Ready
Data
Ready
Sponsorship
Ready
Users
Ready
Variation
Ready
Integration
Ready
Support
Partial
Wave
Pilot
Action
Pilot with the project team present

Wave 1Subsidiary West

Process
Ready
Data
Ready
Sponsorship
Ready
Users
Partial
Variation
Ready
Integration
Ready
Support
Ready
Wave
Wave 1
Action
Extra scenarios for new reps

Wave 2Subsidiary South

Process
Ready
Data
Partial
Sponsorship
Ready
Users
Partial
Variation
Partial
Integration
Ready
Support
Ready
Wave
Wave 2
Action
Data cleansing; decide the open variation

HoldSubsidiary East

Process
Partial
Data
Partial
Sponsorship
Not ready
Users
Partial
Variation
Ready
Integration
Not ready
Support
Partial
Wave
Hold
Action
Test the ERP integration; secure local sponsorship

Compare all 4 in one table
Readiness by subsidiary and factor, with the resulting wave and action
UnitProcessDataSponsorshipUsersVariationIntegrationSupportWaveAction
Subsidiary NorthReadyReadyReadyReadyReadyReadyPartialPilotPilot with the project team present
Subsidiary WestReadyReadyReadyPartialReadyReadyReadyWave 1Extra scenarios for new reps
Subsidiary SouthReadyPartialReadyPartialPartialReadyReadyWave 2Data cleansing; decide the open variation
Subsidiary EastPartialPartialNot readyPartialReadyNot readyPartialHoldTest the ERP integration; secure local sponsorship

Holding one subsidiary protected the rollout: its first weeks would have been the evidence every sceptic quoted.

05Adoption signals

How we know it is working—each signal with an owner.

Adoption signals: level, owner, meaning and action
SignalLevelOwnerMeaningAction
Adoption level reached per unitL3 · Management adoptionAdoption ownerWhere each subsidiary stands, comparablyReview with the local champion before comparing
Local trackers still in use after freezeL4 · Operating-model adoptionLocal business ownerA local need or habit remainsClassify; add a registered variation or retire
Friction items per waveL5 · ImprovementProcess ownerWhat the core design gets wrongFix in the core before the next wave
Local reviews run from the CRML3 · Management adoptionLocal sales directorManagement has movedRetire the local review file

06The trade-offs

Credible options, judged against these premises.

Rejected

Big bang across all subsidiaries

Homogeneous, ready units

Cost: The least ready fail visibly; no learning between waves
Rejected

Each subsidiary picks its own date and model

Independent businesses

Cost: No global standard; comparability lost
Selected

Global core, readiness-sequenced waves, controlled learning

One model, different starting points

Cost: A longer programme and a readiness assessment per unit

Design decision

Sequence waves by assessed readiness rather than by calendar, keep the global core fixed, and give each subsidiary a champion with allocated time—escalating process and system decisions to named global owners.

07The second layer

Questions that change the design.

Readiness

  1. Which subsidiaries are ready?
  2. What blocks readiness?
  3. Who decides that a blocker is resolved?

Enablement

  1. How does enablement differ by role?
  2. Who is the local champion—and how much time do they have?
  3. Who supports the first weeks?

Adoption

  1. Which parallel tools must disappear, and when?
  2. How is adoption compared without ignoring local context?
  3. What changes in the core between waves?

08Decisions & outputs

What the work produces.

  1. 01Readiness model
  2. 02Rollout waves
  3. 03Role-based enablement
  4. 04Champion network
  5. 05Adoption scorecard by level
  6. 06Global friction backlog