Skip to lesson
Exit
Enterprise Rollout & Adoption Playbook1 / 2

2 min lesson

Phase the rollout to match enablement capacity

Compare two rows from "Phase the rollout to match enablement capacity", then say when each one fits.

Step 1 of 2

Phase the rollout to match enablement capacitypace provisioning to onboarding, not to enthusiasm

Phase
Pilot
Who
1 representative team
Goal
Prove value, build the readout
Gate to advance
Success criteria met, security cleared
Phase
Beachhead
Who
2–4 teams around the champion
Goal
Standardize the playbook, train co-champions
Gate to advance
Each team weekly-active above target
Phase
Wave rollout
Who
Department by department
Goal
Scale the repeatable motion
Gate to advance
Enablement keeps pace with activation
Phase
Org-wide
Who
Remaining seats
Goal
Reach saturation, hand off to champions
Gate to advance
Self-sustaining usage, low support load

Advance on activation health, not on the calendar. A wave that outruns enablement leaves dead seats behind it.

Each phase has a gate. You don't open the next wave because a month passed; you open it because the current cohort is genuinely active and your enablement bandwidth is free. That discipline is what keeps the health score climbing instead of inflating with dark seats.

Start narrow, prove ROI, then scale - the canonical pattern

This phasing isn't a Cursor-specific invention; it's the rollout pattern Cursor's own field team recommends. Don't roll out to everyone at once: pick a repo, a few tasks and a few engineers; after measurable impact, expand to a couple more teams, share the results up, and only scale org-wide once you see strong ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. on specific tasks. And frame staying current as part of the job - it's easy to keep using the predictable toolset you already know, so leveraging new agent capabilities is an ongoing responsibility, not optional.