ADR / 018

Retire parallel tools by classification and date, not by mandate

A spreadsheet next to the CRM is often a signal of a missing capability. Inventory each parallel tool, classify it—required temporarily, replaced, integrated or retired—move its legitimate value, then freeze and retire it on a date with an approver for exceptions.

Reference pattern

Independently created. Contains no employer or client implementation detail, internal names or figures.

01Context

Leadership announced twice that only CRM data counted. Both times the spreadsheets survived: the pipeline file served a review the CRM could not support, a margin workbook held cost data the CRM did not have, and a territory analysis was legitimate analytical work. The mandate removed nothing except trust in the next announcement.

02Decision drivers

  1. D01

    Parallel tools often meet real needs

  2. D02

    Some analysis belongs in governed analytics, not in the CRM

  3. D03

    Two sources of truth undermine every review

  4. D04

    Retirement needs an owner and a date, not a reminder

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
Mandate and deadlineTools that are pure habitReal needs move to new filesRejected
Tolerate the toolsShort transitionsTwo operating systems indefinitelyRejected
Inventory, classify, migrate, freeze, retireAny system replacing established workaroundsAn inventory, a migration per tool and bypass monitoringSelected

Every option is right under some premises. The verdict applies to the context above.

04Decision

Discover every parallel tool with its purpose, users and the decision it feeds. Classify each as required temporarily, replaced, integrated or retired, and record what its existence reveals. Move the legitimate value—views, data, routines—into the operating model; move analytical work to governed tools on system data. Freeze each tool read-only on an agreed date, with the business owner approving exceptions, then archive it and monitor bypass signals.

05Consequences

What this choice changes elsewhere in the system.

  1. Capability gaps

    Missing capabilities surface before the retirement date, not after.

  2. Ownership

    Temporary bridges are owned and dated.

  3. Analytics

    Analysis continues on governed data instead of copies.

  4. Governance

    New parallel tools are classified the same way when they appear.

06Revisit when

The decision holds while its context holds. Challenge it when:

01

The tool is the system of record by design, with governed data.

02

The capability gap cannot be closed and the tool becomes a registered extension.

07Where this decision is applied

The decision says why this path was chosen; each case shows how it takes part in a larger architecture.

  1. Adoption case / 01Moving a commercial team from parallel trackers to CRMA CRM that exists but does not run the business: each tracker inventoried and classified, its legitimate value moved into the operating model, the management routines moved in with owners, decision rights set for retirement, definitions and data quality—and a dated freeze, with bypass signals afterwards.Change & AdoptionRevenue OperationsDigital Operating ModelArchitecture case · 11 min

Decisions this one depends on, or constrains.

  1. ADR / 017Measure adoption by process compliance and management use, not loginsLogins measure access. Adoption is measured by whether work moves through the intended process, whether decisions are made from system evidence and whether the parallel way of working has gone—each signal with an owner and an action.Proposed patternAdoption · Measurement · Governance