What is a 30-60-90 day plan?

Why the first thirty days are deliberately quiet

The temptation on both sides is to show value early, and it is almost always the wrong instinct. A new starter dropped into live delivery in week one learns the shape of one account and nothing about the organisation around it, which costs the business the next two years of judgement. The learning phase should be specific enough to be checked: fifteen named people met, four customer calls listened to, the pricing model explained back without help, the incident process walked through once. Those are all verifiable, which is what separates a plan from a welcome note. The other thing this phase buys is a record of what the organisation was unable to explain. A new starter's questions in the first month are the cheapest audit of internal documentation anybody will ever run, and they stop being asked at about week six.

The middle phase is where plans usually fail

Days thirty one to sixty are the hardest to write because contributing inside somebody else's work leaves no obvious artefact. The fix is to name the work, not the behaviour. Support the Q3 renewal for two named accounts is checkable; become more involved with the team is not. It also needs a named colleague whose work the new person is joining, because contribution without a host turns into shadowing for another month. Expect this phase to expose any gap between the role that was advertised and the role that exists. If the middle phase keeps getting rewritten, the problem is usually the job description rather than the plan, and that is worth saying out loud at the sixty day mark rather than at the end of probation.

Ownership has to come with authority

The last phase is where the plan earns its keep, and where managers most often hand over responsibility without the decision rights that make it real. Owning onboarding for new customers means nothing if every email template still needs sign off. Write the authority into the plan in the same sentence as the outcome: owns the onboarding sequence, may change templates and timing without approval, escalates only pricing changes. The proposal element matters too. Asking a new starter to write one page on what should change in the next quarter produces the most useful document of the whole process, because it captures an outsider's view at the last moment they still have one.

Using it in a probation review

A plan agreed in week one makes the probation conversation straightforward, and that cuts both ways. If the outcomes were met, the discussion is about the next quarter. If they were not, the plan shows whether the cause was the person, the work or the support, because each phase names who was responsible for what. Keep the reviews short and on the dates written, rather than letting them slide into a single conversation at ninety days. Two things to avoid: scoring the plan like a performance rating, which turns an onboarding tool into an assessment instrument, and revising the targets quietly when they slip. Note the change and why, in the document, so the record stays honest.

Building the plan as a document

A 30-60-90 plan is a short structured document, usually two to four pages, and it reads best as three sections with a table of outcomes under each. A timeline block suits the meeting schedule for the first fortnight. Tables carry the checkpoints and owners. A cover is only added to a document a reader would expect one on and never under three pages, so a two page plan carries none, while a fuller version for a senior hire can take one of the seven cover layouts. Documents have no input fields, so a checkpoint that will be ticked later is written as content and the signed copy is kept as a version.

Questions people ask