30-60-90 day plan vs the first 72 hours
Published Friday 13 November 2026 by 3D CODED LIMITED
A 30-60-90 day plan and a 72-hour plan answer different questions. One asks where the person should be in three months. The other asks whether the basics happened this week. They work best together.
What a 30-60-90 day plan does
A 30-60-90 day plan sets goals for the end of the first, second and third months: typically learning the role in the first 30 days, contributing in the next 30 and working more independently by day 90. It is a direction-setting document, reviewed at monthly intervals.
Because its checkpoints are a month apart, it says little about the first few days, and a slow start can go unnoticed until the first review.
What a 72-hour plan does
A 72-hour plan covers only the first three days, in three phases with a checkpoint at the end of each: orientation and system access, first deliverable assignment, and output validation. Each phase is pass or fail.
It is an operating check rather than a goal-setting document. It shows whether the things the team controls (accounts, a buddy, a real task with clear checks) were actually in place.
Side by side
- Time span: 30-60-90 covers about three months; the 72-hour plan covers the first three days.
- Question answered: “Where should they be?” versus “Did the basics happen?”
- Checkpoints: monthly reviews versus three checkpoints a day apart.
- Result: progress against goals versus pass or fail for each phase.
- Owner: usually the line manager for both; the 72-hour plan also names a buddy and the person who checks the first output.
How they fit together
Write the 72-hour plan first, because it depends on preparation that has to happen before the start date. Then let its first deliverable feed the first 30 days: if the first piece of work passed, the 30-day goals can build on it; if it failed, the record shows where (access, briefing or the work itself).