Who owns when?
A chalkboard lesson on the timeline nobody owns cleanly.
The seven notes
The Product Manager: What and why
Priority has business data behind it: market windows, sales cycles, the school year your customers plan around.
The Staff engineer: How
Dependencies are technical facts. This genuinely cannot ship until that other thing exists.
The Engineering Manager: The people
Their workload, their wellbeing, their capacity to actually deliver.
Capacity is the only input with give in it. It can be defended, compressed, or quietly absorbed.
PM and Staff: Scope
What is the thinnest thing worth shipping that can be built in time?
The full assessments feature wasn’t going to make the exam revision window. A timer was, and that window’s engagement was the best yet.
Staff and EM: Approach
Same people, same date: what can we do differently to get there?
For the curriculum cutover nobody could add engineers or move the date, so the team shipped without tests and wrote them afterwards.
PM and EM: Pace
How hard to lean on the team for a window that matters, and what that costs next time.
All three: When?
Nobody owns it cleanly. “When” is what you get when you try to synthesise priority, dependencies and capacity under pressure.