1 min lesson
Top three risks and mitigations
Respond to "Why front-load the security review in days 0 to 30 instead of starting it once the pilot shows results?" Name the reason and the detail behind it.
Step 1 of 2
Top three risks and mitigationsName them before the sponsor does
- Risk
- Security review stalls the timeline
- Why it bites on Meridian
- No org-wide rollout until it closes; it can drag for weeks
- Mitigation
- Run the gate in parallel from day 0 and name a security contact
- Risk
- Pilot activates but stays shallow
- Why it bites on Meridian
- Logins without Agent depth won't move retention or expansion
- Mitigation
- Track depth, not just WAU; office hours target real tasks; seed a strong starter rule in
.cursor/rules/
- Risk
- Champion burns out as the lone driver
- Why it bites on Meridian
- One platform lead can't enable 600 engineers
- Mitigation
- Build a repeatable enablement kit; recruit a second champion per BU before widening the wave
| Risk | Why it bites on Meridian | Mitigation |
|---|---|---|
| Security review stalls the timeline | No org-wide rollout until it closes; it can drag for weeks | Run the gate in parallel from day 0 and name a security contact |
| Pilot activates but stays shallow | Logins without Agent depth won't move retention or expansion | Track depth, not just WAU; office hours target real tasks; seed a strong starter rule in .cursor/rules/ |
| Champion burns out as the lone driver | One platform lead can't enable 600 engineers | Build a repeatable enablement kit; recruit a second champion per BU before widening the wave |
Self-score
Read your plan line by line and ask of each: does this ladder to activation, adoption or retention and expansion? Cross out anything that is just motion. If a phase has no leading indicator, you can't course-correct it, so add one or cut it.
Learn more
Optional practice
Test yourself on Top three risks and mitigations
QIt's week 5 of the Meridian pilot. Which pairing is a leading indicator that days 30 to 60 are on track?