90-Day Sales Methodology Rollout Playbook

Week-by-week. Four phases, each with a deliverable — not a vague "training happens sometime in Q2."

Phase 1 — Foundation (Weeks 1–2)

Week 1

• Executive sponsor states the "why now" in one paragraph, communicated to the full team (not "we're adopting a new methodology," but the specific business problem it fixes: forecast accuracy, ramp time, win rate)
• Methodology (or blend) selected — use the Sales Methodology Selection Decision Tree if undecided
• Adoption metrics defined up front and tied to the CRM Compliance Scorecard fields, so "adoption" has a number attached from day one
• Internal champions/certified trainers identified (senior reps or managers, not just the enablement team)
• Explicit "what we are NOT changing" list published (comp plan structure, territories, tools) — reduces anxiety surface before training starts

Week 2

• CRM fields built or modified, mapped to methodology elements (see Compliance Scorecard field map)
• Reporting dashboard built so adoption is visible from week one, even at zero
• Training curriculum and role-play Scenario Bank finalized
• Pilot cohort selected — 10–20% of the team, a deliberate mix of top and mid performers, not just volunteers

Phase 2 — Pilot (Weeks 3–6)

Week 3 — Pilot cohort completes live training on the core framework; terminology quiz administered.

Week 4 — Pilot cohort completes role-play certification against the standard rubric; friction points and real objections from the field are logged.

Week 5 — Training materials revised based on pilot feedback; pilot cohort's managers trained on the Deal Review question bank.

Week 6 — Pilot cohort begins applying the methodology to live deals with manager co-review; 10 real, anonymized deal examples captured for use in full rollout training.

Phase 3 — Full Rollout (Weeks 7–9)

Week 7 — All-hands training kickoff using the refined curriculum plus the pilot's real deal examples; all managers trained on the Deal Review structure.

Week 8 — Full-team role-play certification, staggered by team over 2–3 days each; non-certified reps get a named remediation plan and date.

Week 9 — CRM go-live: legacy free-text fields deprecated or hidden; new structured fields become mandatory at stage-gate; certification becomes a prerequisite for running live, unsupervised discovery calls (ties directly to the Ramp Checklist).

Phase 4 — Enforcement & Reinforcement (Weeks 10–13 / Day 90)

Week 10 — First full-team Deal Reviews run on the new question bank; managers apply the red-flag list; Pipeline Hygiene Scorecard baseline captured.

Week 11 — First CRM Compliance Scorecard run org-wide; adoption % published by rep and team, no shaming — a target-setting conversation for anyone under 70%.

Week 12 — Recognition pass: spotlight reps hitting both compliance and pipeline hygiene targets; certified reps present a real deal to the full team (peer teach-back).

Week 13 (Day 90) — Executive readout: adoption %, pipeline hygiene trend, forecast accuracy trend if measurable yet, lessons learned. Lock in ongoing cadence (monthly compliance audit, quarterly re-certification). Ownership transitions from the rollout project team to frontline managers — the rollout is now just "how we run pipeline."

Change-fatigue guardrails

• Never run more than one major adoption initiative at a time.
• Cap new process asks to one new CRM field group and one new meeting ritual per rollout — piling on more guarantees rejection.
• Tie adoption to recognition (and, ideally, a comp/spiff mechanism) so it isn't unrewarded extra work layered onto quota.
• Track only 2–3 leading indicators for the full 90 days: certification %, CRM field compliance %, pipeline hygiene score. Resist adding more dashboards mid-rollout.
• Publish the "what we're NOT changing" list in Week 1 and refer back to it — most rollout anxiety is about unstated scope, not the methodology itself.

RACI

(R = Responsible, A = Accountable, C = Consulted, I = Informed)