1 min lesson
Deliverable 1: the 30/60/90 rollout plan
Say what this means in practice. "Build the full 30/60/90 plan as if you're presenting it to the VP Eng next week."
Step 1 of 2
Build the full 30/60/90 plan as if you're presenting it to the VP Eng next week: in days 0–30, clear security and provision the pilot; in days 30–60, drive weekly use and Agent depth while comparing Copilot openly; in days 60–90, package the workflow proof and earn approval for the next wave. Give yourself 25 minutes, open each phase with the metric it moves and name the risks that could stop it.
The trap in a 30/60/90 is listing activities that sound busy. A strong plan ties every phase to an outcome: days 0 to 30 clear security and provision the pilot; days 30 to 60 drive weekly use and Agent depth; days 60 to 90 package proof and earn approval for the next wave. On Meridian, phase one is gated by the security review, so the first 30 days are as much about pre-empting the blocker as starting the pilot.
Learn more
Full explanation
The First 90 Days as a Pipeline
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
The security review is a gate, not a step - clear it in parallel or the whole wave stalls behind it.