gtmskills.com

Reference file

RevOps-Specific Change Scenarios

revops-specific-change-scenarios.md

RevOps-Specific Change Scenarios

Detailed playbooks for the four changes RevOps teams run most often. Each applies the same machinery: impact analysis, Traffic Light classification, communication architecture, transition design, and reinforcement. All four are Red changes by default.

Scenario 1: Rolling out a new comp plan

Why it is hard: comp is identity and income. Reps read every change as a threat until proven otherwise.

  • Impact: every AE loses predictability for a quarter; top performers feel most exposed; managers must defend the plan daily.
  • Classification: Red. Written plan, video walkthrough from the CRO, and live Q and A per team.
  • Sequence: Context two to four weeks out (the why, in revenue terms). Vision one to two weeks out (what changes per role). Detail at launch (full mechanics, a personal earnings calculator). Feedback weeks one to four (office hours, a channel). Reinforcement months one to three.
  • Transition: a hold-harmless or minimum-commission guarantee for the first quarter. This costs money and saves your top performers.
  • Watch for: the plan that quietly rewards the old behaviour. Run the Behavioural System Audit before launch.

Scenario 2: Migrating CRMs

Why it is hard: it is simultaneously a system, data, process, and habit change. Four dimensions failing at once.

  • Impact: every rep's daily workflow changes; historical data and reporting continuity are at risk; integrations and automations break.
  • Classification: Red. Plus a named systems owner accountable for data validation.
  • Sequence: announce early, demo often. Detail lands as role-specific quick-start guides, not a 40-page manual.
  • Transition: never go cold turkey. Run parallel for two to four weeks with a hard cutover date. Build and rehearse the rollback plan; having one increases the confidence to move forward. Validate that migrated data reconciles before you trust a single report.
  • Watch for: the productivity dip hitting pipeline hygiene first. Protect the forecast with a bridge view across old and new.

Scenario 3: Changing territories

Why it is hard: the ripple is enormous. Territory touches pipeline, SDR targeting, CS assignments, comp, and live customer relationships.

  • Impact: AEs lose named accounts and relationships; in-flight deals risk disruption; SDR and CS coverage must re-map.
  • Classification: Red. Decisions co-created with the guiding coalition, not handed down.
  • Sequence: explain the rationale (fairness, balance, coverage) before showing maps. Reveal individual assignments in 1:1s, not a spreadsheet drop.
  • Transition: protect in-flight deals with clear credit and split rules. Set a clean cutover for new inbound while existing opportunities follow defined hand-over rules. Milestones, not just a launch date.
  • Watch for: stacking this on top of a comp change in the same quarter. Each carries a dip; stacked, the dip becomes a crater. Sequence them.

Scenario 4: Implementing a new sales methodology

Why it is hard: it is a behaviour change, not a tooling change. The hardest kind to make stick because there is no system to force it.

  • Impact: reps must replace ingrained discovery and qualification habits; managers must coach to the new standard, not just mandate it.
  • Classification: Red. Built as a full enablement programme, not a kickoff event.
  • Sequence: Diagnose (find the reverse salient: the one skill with the most leverage). Design (define the target behaviour as specific and observable). Execute over eight to ten weeks with deep-practice sessions and questions-based coaching. Embed by measuring behaviour change, not attendance.
  • Transition: embed the methodology in the CRM (stage exit criteria, required qualification fields) so the path of least resistance is the new behaviour.
  • Watch for: the one-and-done training event. Methodology dies in a week without spaced reinforcement and a running energy system. Capture the playbook as permanent reference material so new hires learn it as standard.

The common thread

For every scenario: map the impact before communicating, classify honestly, protect earnings and continuity through the transition, plan for the productivity dip out loud, and reinforce for at least three months. The change that sticks is engineered, not announced.