1 min lesson
Metrics and leading indicators per phase
Pick two rows from the table in "Metrics and leading indicators per phase" and explain the choice each one supports.
Step 1 of 3
Metrics and leading indicators per phaseMake every phase measurable
- Phase
- 0-30
- Target metric (lagging)
- Security review closed; pilot team provisioned
- Leading indicator you watch weekly
- SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. test passed; security questions answered; pilot seats activated within 5 days
- Phase
- 30-60
- Target metric (lagging)
- 70%+ of pilot seats active weekly; Agent used by majority
- Leading indicator you watch weekly
- Daily Tab acceptance trend; first Agent task per engineer; office-hours attendance
- Phase
- 60-90
- Target metric (lagging)
- Pilot WAU/MAU stickiness holding; next wave approved
- Leading indicator you watch weekly
- Depth-of-use climbing (Agent, context, rules); champion running a session solo
| Phase | Target metric (lagging) | Leading indicator you watch weekly |
|---|---|---|
| 0-30 | Security review closed; pilot team provisioned | SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. test passed; security questions answered; pilot seats activated within 5 days |
| 30-60 | 70%+ of pilot seats active weekly; Agent used by majority | Daily Tab acceptance trend; first Agent task per engineer; office-hours attendance |
| 60-90 | Pilot WAU/MAU stickiness holding; next wave approved | Depth-of-use climbing (Agent, context, rules); champion running a session solo |
Lagging metrics prove the phase; leading indicators tell you a week early whether it's working.
Learn more
Full explanation
The Copilot narrative
The Copilot narrativeCoexist, then earn the switch
Do not open by trashing Copilot. Skeptical engineers have muscle memory there and an attack reads as insecurity. Run them side by side in the pilot and let the depth difference show: Cursor's codebase-aware context, Agent doing multi-file work, .cursor/rules/ encoding the team's conventions. The switch is something the pilot data earns, not something you assert.
"Keep Copilot on for the pilot. I'd rather your engineers feel the difference on their own repos than take my word for it. We'll look at acceptance and depth of use across both after four weeks and you decide where Cursor earns the seat."