2 min lesson
Underneath all three horizons is one scorecard and it isn't artifacts
Give the practical answer to "What's the strongest way to frame Day 90 success in this loop and what's the trap to avoid?" Then name the detail that supports it.
Step 1 of 2
Day 60 turns the wedge into a shipped system with a feedback loop attached. Day 90 is the proof you build primitives, not one-offs: the same workflow or its abstraction, gets adopted by a second team or extended to a new segment without you rebuilding it.
Underneath all three horizons is one scorecard and it isn't artifacts. The unit you're measured on is impact: human hours removed, manual steps eliminated, programs that now run without you in the loop.
- Toil removed
- Hours of manual work eliminated per week, not 'a workflow built.'
- Reuse
- Programs or teams now running on a primitive you shipped once.
- Reliability
- Workflows that survive production unattended - fewer fire-drills.
- Self-sufficiency
- Teams that run programs without filing a ticket to you.
If your plan front-loads a long listening tour with nothing shipped, you've signaled the wrong altitude for this team. Cursor hires for agency and bias to ship. Map and learn while you ship something small in week one. A plan whose first milestone is a deliverable, not a doc, reads as senior here.
Week one I'd ship a small fix to prove I can operate in the stack. By day 30 I'd have the GTM plumbing mapped and the highest-toil workflow named with hours attached. By day 60 I'd have automated it as a reusable workflow with a feedback loop. By day 90 the proof would be a second team running on that same primitive - the scorecard is human hours removed, not dashboards built.