Operations Improvements Evidenced (Before/After Metrics)
12 weeks · 4 milestones
Milestone map
Milestone map
3 milestones
Document how you currently manage your responsibilities: the systems you use for tracking work, capturing decisions, managing deadlines, and communicating status. Then spend 1 week logging every interruption, context switch, dropped ball, and late delivery you experience. At the end, produce a 200-word diagnosis of the single biggest gap between your intended system and your actual behaviour — the place where your operating system breaks down most consistently.
Proof required
Submit your operating system map (which tools you use, how you process incoming requests, how you track commitments, how you communicate status) plus your 1-week log of breakdowns (interruptions / context switches / dropped balls / late deliveries with specific dates and brief descriptions) and a 200-word gap analysis naming one specific breakdown pattern.
What gets checked
- Operating system map is specific enough to be actionable — 'I use a to-do list' does not qualify; the map should specify which tool, how items enter, when they are reviewed, and what the failure mode is
- 1-week log contains real events with dates and brief descriptions — not a retrospective summary
- Gap analysis names one specific breakdown pattern (e.g. 'I respond to Slack immediately instead of batching, which causes context switches every 12 minutes on average') with evidence from the log