Updated 2026-08-26
Every step, against how long it usually takes
People are only named to you once a step is twelve days late, because you are the one who can unblock a department head.
The books connect
1 days, and this step usually takes 5on timeTheir IT or security review
1 days — someone else sets this timetableon their clock, not oursRuns on the reviewer's clock, not ours. The watch does not fire here.
Everyone finishes the wizard
0 days, and this step usually takes 5on timeHeads answer their expectation card
3 days, and this step usually takes 7on timeHeads agree after the founder's answer
1 days, and this step usually takes 3on timeGoals agreed by whoever agrees them
1 days, and this step usually takes 5on timeManagers read their people's goals
1 days, and this step usually takes 5on timeProduction released by its head
0 days, and this step usually takes 3on timeEveryone's conversation
2 days, and this step usually takes 7on timeHeads read the findings about their department
0 days, and this step usually takes 4on time
How Corto decides something is late
Four stages, and one case where Corto stays quiet
- Day 3. Only the person doing it is told, and nobody else. If they ignore it three times Corto stops showing it and raises it with someone else instead, rather than nagging.
- Day 7. The person running the rollout sees how many are outstanding. They can see who, because chasing is their job, but it is shown as a total rather than as a complaint about one person.
- Day 12. The founder is told and the people are named, because he is the only person who can unblock a department head. Nothing can be configured to hide this from him.
- Day 20. Corto says plainly that this is not working right now and offers to pause. Nothing is wrong with the business — the timing is wrong.
- Some steps are not ours to hurry. A legal negotiation, an IT security review or a contract with their lawyers runs on someone else's timetable. Corto never marks those late.