The 30-60-90 Day Plan: How to Build One That Actually Works

To make a 30-60-90 day plan, decide which document you are writing. One is a candidate’s pitch, drafted before an interview from outside the company. The other is an onboarding ramp, written by a manager and a new starter together. Set three review points, weight the first month towards learning, and phrase every item so it can be marked done.

This is employee onboarding, not client onboarding. The reader is a manager writing a ramp for someone starting on Monday, an HR lead standardising the format, or a candidate who has been asked to bring a plan to a second interview. Those are different jobs, and most of the trouble with 30-60-90 plans comes from treating them as one.

What is a 30-60-90 day plan?

A 30-60-90 day plan is a short document setting out what someone will learn, own and deliver across their first three months, with review points at roughly day 30, day 60 and day 90. The format is used for two entirely different purposes, and templates rarely say which one they are.

	Candidate version	Onboarding version
Who writes it	The candidate, before or during interview	The hiring manager and the new starter, jointly
Who reads it	An interview panel	The starter, their manager, the wider team
Information behind it	A job advert and a few conversations	The actual team, backlog and calendar
Judged on	Quality of reasoning	Whether it happened
Typical failure	Confident promises about a business the writer has never seen inside	Vague items nobody can mark done

The candidate version is an argument. The onboarding version is a schedule. Confusing them produces the worst of both: a manager who hands a new starter something that reads like a pitch, full of ambition and empty of dates.

If you are building the wider new-starter process rather than one person’s ramp, the 30-60-90 plan sits inside it. It is one artefact among several, alongside the checklist and the first-week schedule covered in employee onboarding plans.

How to structure a 90 day plan

Structure it as three review points, not three equal workloads. The first month should be weighted heavily towards learning and meeting people, the second towards owning work with a safety net, the third towards owning an outcome outright.

Days 1 to 30, learning. The output of this month is understanding, but understanding only counts if someone can check it. Useful items look like this:

• Can name the five people whose work most affects this role, and what each of them needs from it
• Can explain how the organisation makes its money, or where its funding comes from, without hedging
• Has completed one small piece of real work end to end, however trivial
• Has attended each recurring meeting once and knows what it decides

Days 31 to 60, owning with support. The starter takes a recurring piece of work and runs it, with the manager reviewing rather than doing. One inherited process gets improved. The first real feedback conversation happens here, in both directions, and it is far easier at day 45 than at day 89.

Days 61 to 90, owning outright. By now there should be one thing the person is unambiguously responsible for, with a result attached that someone outside the team would recognise. They should also be able to say what they would change, and be listened to when they say it. A new starter who has no opinion by day 90 was probably never given anything to have an opinion about.

A plan that expects delivery in week two is not a ramp. It is a description of the vacancy, written by someone who needed the headcount three months ago.

How to make a 30-60-90 plan

Build it backwards from what the role is supposed to produce, then work out what the person needs to learn in order to produce it. The sequence below takes about an hour and is best done in the week before the start date.

1. Decide who is writing it, and with whom. The manager drafts. The new starter rewrites it in week one, once they have met the team, and the rewritten version is the real one. A plan handed over unchanged on day one is a plan the starter never agreed to.
2. Start from the outcomes, not the tasks. If nobody has written down what success in this role looks like, do that first. A role scorecard is the document that answers what good actually means in this job, and a 30-60-90 plan without one tends to fill up with activity instead.
3. Turn each outcome into things the person must be able to do unaided. Not “understand the reporting stack” but “can pull last month’s numbers without asking anyone”.
4. Name the person on the other side of every learning item. Someone has to explain how billing works. If no name is written next to that item, it will not happen, because it depends on a colleague finding an hour for a person they have not met.
5. Put the three reviews in the calendar before day one. Thirty minutes each, dated. Reviews that are not diarised do not happen, and day 60 passes in silence.
6. Cut it until it fits on a page. Five to eight items for the first month, fewer for each month after. Leave room, because real work will arrive in week two whatever the plan says.

Step 4 is the one that gets skipped, because it means asking other teams for time rather than typing. The asking is what Projan is for at this step: it puts the questions to the group in Slack or Microsoft Teams, so the finance lead who has to explain the revenue model is in the thread when the commitment is made, and it writes the agreed items out to Asana or Trello with dates attached. However you do it, the commitments should come from the people making them.

How detailed should a 30-60-90 day plan be?

Detailed enough that a third party could mark each item done or not done, and short enough that the new starter reads all of it. Those two constraints do more work than any template.

Detail should decay with distance. Days 1 to 30 can be specific, because you know what exists today. Days 61 to 90 should be directional, because month one will teach both of you things that make month three wrong. Writing precise day-80 deliverables before the person has met the team is confident and useless.

A practical test: read each item and ask who says whether it happened. “Build relationships with key stakeholders” has no such person. “Has had a one-to-one with each of the four team leads” has four of them. Items that fail this test are not motivational, they are decorative, and they are the reason so many plans quietly stop being referenced after week three.

Writing a 30-60-90 day plan for an interview

A candidate’s 30-60-90 plan is judged on how you think, not on whether you are right. You are writing about a company you have seen from the outside, using a job advert and two conversations, so accuracy is not available to you and pretending otherwise is the trap.

The strongest version asks more than it asserts. Structure it as what you would want to find out, what you would expect to be true, and what you would do differently depending on the answer. “In the first month I would want to know how support tickets are currently triaged and who decides priority. If it turns out that engineering triages directly, the first thing I would look at is…” That shows a panel your reasoning and gives them something to react to.

The weak version commits to numbers. Promising to increase pipeline by twenty per cent in ninety days, based on a job advert, reads as naive to anyone who has run the function. An experienced interviewer hears a candidate who has not yet realised how much they do not know. Keep the commitments conditional, state your assumptions plainly, and keep it to a page unless you were explicitly asked for a presentation.

What is the 30-60-90 rule in leadership?

Applied to a new leader, it means diagnosing before changing anything, on the grounds that the credibility to make changes is earned in the first month rather than granted at the offer stage. The content shifts from systems and tools to relationships, decision rights and inherited commitments.

Michael Watkins’s The First 90 Days is the book most managers are half-remembering when they use this language. Its argument is that a transition strategy should be matched to the situation being inherited, since taking over a turnaround is a different job from taking over something that already works. The three-month framing itself is older and more generic than any single book, so treat 30-60-90 as a convenient rhythm rather than a method with an owner.

The specific failure for new leaders is the week-three reorganisation. It is usually a signal that someone arrived with a plan formed before they had met anyone, which is exactly what the first thirty days are supposed to prevent.

What are common mistakes in a 30-60-90 day plan?

The most common mistake is writing items nobody can mark done. Every other failure on this list follows from something similar: a plan that looks reasonable on paper and cannot be checked in practice.

• Unfalsifiable items. “Immerse yourself in the culture” cannot be completed, so it is never completed.
• Delivery expected in the first fortnight. The person is still working out who to ask about the staging environment.
• Written by one person and handed over. Authorship is what turns a plan into a commitment. A document received is a document ignored.
• Straight from a template. Generic plans contain items belonging to a role nobody at your organisation holds.
• Learning goals with no named teacher. Every learning item is a request for someone else’s time, whether or not you asked them.
• No diarised reviews. Day 60 arrives and nobody notices.
• Ninety days of detail written before day one. Month three is a guess. Write it as a guess.
• A plan created because there is already a problem. That is a different document with different rules, and calling it a 30-60-90 plan helps no one.

That last point needs care. A 30-60-90 plan is a development tool, and it changes character the moment it is used as evidence about someone’s suitability. Probation terms come from the employment contract, and the rules around notice and dismissal vary considerably by jurisdiction, so take that path through your own HR or legal advice rather than through the ramp document. Keep genuine performance concerns in the process built for them, such as a properly planned review cycle, where both sides know what the conversation is.

Frequently asked questions

What is the 30-60-90 onboarding rule? It is a convention rather than a rule. Someone decided that three review points a month apart was a sensible rhythm for a new starter, and the name stuck. Nothing breaks if your checkpoints land at four, ten and fourteen weeks instead. The useful part is having fixed dates at all, not the specific numbers.

How many pages should a 30-60-90 plan be? One page for an onboarding ramp, two at the outside. A candidate version for an interview should be one page or a handful of slides, and building a twenty-slide deck for a job you have not been offered signals the wrong thing. If it runs longer, you have written a job description with dates on it.

Can a 30-60-90 day plan be used personally? Yes, for a career change or a side project, though it loses the thing that makes it work at a job. Nobody else marks your items done. If you use one personally, borrow that mechanism back: name a real person who will ask you at day 30, and pick items they could verify without taking your word for it.

What happens if the day 30 items are not met? You find out why before you draw any conclusion about the person. The common cause is organisational: access was not granted, the named expert was on leave, the small first task never materialised. Rewrite the plan around what actually happened. A missed item is information about the ramp as often as it is information about the hire.

Do 30-60-90 day plans work for internal promotions? They work well, and they get skipped because the person already knows the systems. What they do not know is the new authority: which decisions are now theirs, who expects to be consulted, what they must stop doing. An internal 30-60-90 plan should be almost entirely about relationships and decision rights rather than tools and logins.

A 30-60-90 day plan is worth having only if someone can tell whether it happened. Write it with the person it belongs to, name whoever owes them an hour of explanation, and book the three reviews before the first day rather than after the first problem.