Adoption case / 01 · Shadow-tool inventory, routines & retirement

Moving a commercial team from parallel trackers to CRM

The CRM is live; the organization’s real operating system is a set of spreadsheets, slides and one legacy tool.

The case in brief

Current reality

The team has a CRM, but daily management still depends on spreadsheet trackers, local customer files, offline forecasts, regional slide packs and manual reporting—and nobody owns the rules that would make the CRM the place the business is run from.

What must become true

The business plans, reviews, forecasts and quotes from the CRM: every management routine has a system view and an owner, every parallel tool has a replacement and a retirement date, data quality and stage definitions have owners, analysis continues on governed data—and bypass is visible and owned.

Design question

What does each tracker do that the CRM does not—and which routines, ownerships and decisions must move before the business operates through one system?

01The reality · current state

How work actually happens today.

A regional commercial organization of account managers, sales managers and a sales operations analyst has had a CRM for a year. The configuration is sound. Opportunities are entered—mostly the day before the weekly review. The review itself runs from a spreadsheet the analyst rebuilds every Monday; the forecast is a separate file with the managers’ adjustments; the monthly performance meeting uses slides per region; account managers keep their own customer lists; a margin workbook checks prices before quoting; one subsidiary still works in its legacy tool. Stage definitions are read differently by each team, and nobody has owned data quality or the CRM’s operating rules since the project closed. Leadership has twice announced that “only CRM data counts”.

  • The weekly review runs from a spreadsheet rebuilt every Monday
  • Forecast adjustments live in a separate file with no history
  • Monthly performance reviews use regional slide packs
  • Account managers keep private customer lists
  • Price checks happen in a workbook outside the quote flow
  • One subsidiary still works in its legacy tool
  • Teams read the stages differently, so reports disagree
  • CRM updates cluster the evening before each review
  • Two announcements changed nothing

02Approach

Not the obvious response—the approach.

Systems and partiesCRMSpreadsheets (retiring)Analytics toolCollaboration tools

The obvious response“Tell users they must use the CRM.”

The trackers exist because they do something the CRM does not. A mandate removes the file, not the need—so the need finds a new file.

  1. 01Identify why the trackers exist

    Inventory every file and tool: purpose, users, the decision it feeds, how often it changes.

    Adoption owner with sales operations
  2. 02Classify missing capabilities

    Separate missing views, missing data, missing routines and habit.

    Process owner
  3. 03Reproduce legitimate value

    Build the review view, forecast overrides and price check where the work happens.

    Platform owner
  4. 04Move the routines in

    Weekly review, forecast call, monthly performance review and account planning run from the CRM—two cycles in parallel, then the CRM only.

    Sales managers
  5. 05Name the owners and rights

    Owners for accounts, opportunities, data quality and stage definitions; who decides a retirement and on what evidence.

    Business owner
  6. 06Set a retirement date

    Freeze each tracker read-only on a date; exceptions need the business owner’s approval.

    Business owner
  7. 07Monitor bypass behaviour

    Watch for new files, offline requests for data and pre-meeting update spikes.

    Adoption owner

What changes beyond the trackers

Retiring the trackers is the visible half. The CRM becomes the environment the business operates through only when these layers change with it.

  1. 01Outcome

    Management decisions made from CRM evidence

  2. 03Process

    One interpretation of stages, with exit criteria

  3. 04Ownership

    Account, opportunity and data-quality owners named

  4. 05Systems

    The CRM as the system of action for every commercial routine

  5. 06Data

    Quality owned at the source by the people who can fix it

  6. 08Governance

    A business owner and a change process for lifecycle definitions

  7. 09Measurement

    Adoption measured by routines run from the system

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
Account managerStage, next step, customer contextPrioritized pipeline; price check inside the quoteThe next commercial actionKeep a private customer list in sync by hand
Sales managerReview decisions, forecast judgement with reasonsA review view that replaces Monday’s spreadsheetWhere the team focuses; which deals escalateAsk the analyst for a rebuilt file
Sales operationsView design, data quality follow-upTime back from weekly rebuildsHow the review view is builtBe the human integration between files
ExecutiveVisible use of the CRM forecastA forecast with recorded judgementTargets and escalationsRequest a separate forecast file

Decision rights the move needs

Retirement is a decision with an owner and evidence—not something that happens by itself. Two further rights keep the moved routines trustworthy.

Decisions: who decides, approves and is consulted, evidence and time limit
DecisionDecidesApprovesConsultedEvidenceWithin
Retire a parallel toolSales leadership—Sales operationsThe replacement view used for two cyclesBy the agreed date
Change a stage definitionCommercial process ownerGlobal governanceSales managers, platform ownerStage ageing and conversionQuarterly
Fix a data-quality issueData owner for the concept—Account ownersQuality measures by source5 working days
Stage definitions and data quality are governed after go-live inOwning and evolving the operating model after go-live

04Key dimension · Shadow-tool inventory, routines & retirement

Every tracker classified—and every routine it carried moved in

The inventory records what each tool does, who relies on it, which decision depends on it, what its existence reveals—and what happens to it. Beside it, the routines that move into the CRM, each with a system view and an owner.

Tools that move out

Parallel-tool inventory: purpose, users, decision, what it reveals and what happens to it
ToolPurposeUsed byDecision it feedsWhat it revealsVerdict
Monday pipeline spreadsheetWeekly reviewSales managers, analystWhich deals need helpNo CRM view fits the reviewReplacedFrozen after two parallel reviews
Forecast adjustments fileMonthly forecastManagers, leadershipCommitted forecastOverrides have no place in the CRMReplacedRetired at the next quarter start
Regional slide packsMonthly performance reviewSales managers, sales operationsWhich accounts and plans need attentionNo performance view per account and planReplacedRetired after two monthly cycles in parallel
Margin workbookPrice check before quotingAccount managersWhether a price needs approvalCost data missing in the quote flowRequired temporarilyRead-only until cost data is integrated
Territory analysis workbookAccount prioritizationSales operationsTerritory focusLegitimate analysis, not a process gapIntegratedMoved to the analytics tool on CRM data
Private customer listsContacts and visit notesAccount managersWho to visit nextHabit—plus one missing visit-type fieldRetiredArchived after the field is added
Legacy tool in one subsidiaryThe subsidiary’s whole pipelineLocal sales teamLocal pipeline and forecastLocal rules never registered as variationsReplacedRetired at the subsidiary’s go-live, with registered variations

Routines that move in

Management routines moved into the CRM
RoutineBeforeAfterOwner
Weekly pipeline reviewExported spreadsheet, rebuilt every MondayTeam pipeline view with stage changes and stale dealsSales manager
Monthly performance reviewSlides per regionPerformance view by account and recovery planSales operations
Account planningSlides per accountAccount plan record linked to opportunitiesAccount owner
Forecast submissionEmail with a totalForecast view with recorded judgementSales leader

Three of the seven trackers revealed missing capabilities; banning them would have removed the files and kept the gaps. A parallel tool without a retirement date is the real system of record—so retirement is a decision with an owner, taken when the routine it carried runs from the CRM.

05Adoption signals

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

Adoption signals: level, owner, meaning and action
SignalLevelOwnerMeaningAction
Weekly review run from the CRM viewL3 · Management adoptionSales managerThe review has movedRetire the Monday spreadsheet after two parallel cycles
Updates clustered before the reviewL1 · UsageAdoption ownerThe CRM is updated for the meeting, not for the workShow each rep their own prioritized view daily
Forecast overrides recorded with a reasonL3 · Management adoptionSales leadershipJudgement is in the systemReview override accuracy each quarter
Parallel tools past their retirement dateL4 · Operating-model adoptionBusiness ownerA retirement decision was not carried outDecide: retire now, or record an exception with a new date
New files requested or sharedL4 · Operating-model adoptionAdoption ownerA need is not metClassify it like the original inventory

06The trade-offs

Credible options, judged against these premises.

Rejected

Mandate and deadline

Trackers that are pure habit

Cost: Legitimate needs move to new files
Rejected

More training and mandatory fields

Teams that already manage from the CRM

Cost: Compliance without use
Rejected

Rebuild the CRM

A broken configuration

Cost: The same result if the routines do not move
Rejected

Leave the trackers; improve the CRM first

A CRM missing core capabilities

Cost: Two operating systems indefinitely
Selected

Classify, move routines and owners in, retire on a date

A sound CRM the business does not operate through

Cost: An inventory, parallel cycles, named decision rights—and managers changing how they run meetings

Design decision

Treat every tracker as a signal first and adoption as an operating-model change: find what each tracker does, move its legitimate value and the management routine it carried into the CRM with an owner, give retirement, definitions and data quality named decision rights—then freeze and retire each tracker on a date, with an approver for exceptions.

07The second layer

Questions that change the design.

Purpose

  1. What purpose does each spreadsheet serve?
  2. Which capability is missing?
  3. Who uses it, and how often?

Routines & owners

  1. Which management routine moves first—and who owns it?
  2. Which decision depends on each tracker?
  3. Who owns data quality and stage definitions once the routines have moved?

Retirement

  1. When should each tool be frozen?
  2. Who decides a retirement—and who approves exceptions?
  3. How will we see it coming back?

08Decisions & outputs

What the work produces.

  1. 01Shadow-tool inventory
  2. 02Classification and migration plan
  3. 03Routine migration plan with owners
  4. 04Ownership model and decision rights
  5. 05Freeze and retirement register
  6. 06Adoption signals with owners