Governance and adoption.

Most frameworks do not fail in the model; they fail because nobody owns the rules. This chapter installs the ownership, change control, and phased rollout that keep one framework from fragmenting into unofficial versions.

The rule: one framework, many users

Central teams own definitions, scoring logic, the state model, and major changes. Local teams own execution, local context, and learning. Local teams can adapt tactics, but never core definitions or scoring, without formal approval.

Who decides what

• Insight and Analytics: own signals, scoring, confidence rules, state logic, the monthly review, and the change log.
• CRM and Loyalty: own state journeys, contact and suppression rules.
• CX, Operations and Service: own root-cause fixes and high-touch recovery.
• Data and BI: own pipelines, identity matching, and freshness.
• Privacy and Compliance: own consent and data-use controls for trust-sensitive signals.
• Leadership: owns prioritisation, resource, escalation, and major rule changes.

Change control

Every core component is versioned Major.Minor. A change moves through proposal, impact review, approval (minor by the Insight lead, major at quarterly steering), release and communication, then a post-change check after one cycle. No evidence, no change.

The phased rollout

• Phase 0, Mobilise: lock ownership, scope, and the v1 freeze.
• Phase 1, Instrument and validate: connect sources, validate identity matching, run first scores, baseline confidence.
• Phase 2, Dry run and train: one dry-run review, all eight cards tested with owners, SLAs validated.
• Phase 3, Live pilot: state-based actions live, weekly huddles and monthly reviews running, 30/60/90 outcomes tracked.
• Phase 4, Scale and standardise: more teams and properties, central definitions intact, thresholds adapted by cohort evidence.

Exit criteria, not dates

Each phase ends with evidence, not a date. Phase 0 ends when ownership is named, the pilot scope is approved, and the v1 rules are frozen. Phase 1 ends when identity matching is validated and first scores with confidence baselines exist. Phase 2 ends when a dry-run review has happened and every card has been tested by its owner. Phase 3 ends when 30, 60, and 90-day outcomes exist for at least two playbooks. Phase 4 ends when framework language is common across the portfolio, the review rhythm is stable without heroics, and leadership accepts the value proof.

Expected exceptions

Six situations will happen and each needs a standing rule rather than a debate: a data outage, an identity-resolution failure, a major service incident, a seasonality spike, a pricing distortion, and a new brand onboarding. The rule is the same shape every time: label affected states Provisional, flag the period in the review, never compare flagged periods without saying so, and run a post-event correction.

How to measure adoption

• Leading: percent of the base classified, percent Firm, review attendance by owner group, card-action completion, and SLA adherence on L4 and L7.
• Quality: assignment consistency across sites, confidence trend by dimension, and contact-rule compliance.
• Outcome-linked: L3 to L2 or L1 movement, L4 recovery rate, L5 conversion, and L1 retention and advocacy.

Training and enablement

Role-based tracks, not one all-hands: leadership 60 minutes, CRM and Loyalty 90, CX and Service 90, Insight and Data 120. Six artefacts ship with the rollout: a one-page summary, an L1 to L8 cheat sheet, the review guide, a card quick reference, the escalation matrix, and the change-request form. No team goes live without its track and artefacts.

The six anti-patterns

The single-score comeback, CRM-only ownership, treating Provisional as Firm, threshold drift by team, snapshot obsession, and tech-first implementation that buys tools before locking signals, states, and ownership.

What good looks like after six months

The review runs consistently, state assignment is repeatable, confidence is visible and improving, at least two playbooks show proven movement and value, and changes are versioned and controlled.

Chapter checklist

• Name the framework owner and the executive sponsor.
• Agree decision rights with each owning team.
• Plan Phases 0 to 2 with dates before any tooling decision.