How to Write a 30-60-90 Day Plan

A 30-60-90 day plan is a short document setting out what you intend to do in your first three months. It shows up in two places: as something you present at final-stage interview to win the job, and as something you write in your first week to run the job well.

Most examples of them are bad in a specific and predictable way — they are full of confident action in month one, written by someone who has not seen the business. That is precisely the thing experienced managers are watching for, because a new hire who arrives certain about what needs fixing is a risk rather than an asset.

Why month one is for listening

Every organisation has processes that look stupid from outside and exist for a reason. The reason is usually a customer, a regulator, an incident three years ago, or a personality. A new hire who eliminates one of these in week two learns why it existed at considerable cost, and spends the rest of the year rebuilding the trust.

The related risk is signalling. Arriving with a plan to restructure the team tells everyone that you have already judged their work without looking at it. People remember that far longer than they remember your first improvement.

So month one is deliberately weighted toward learning. That is not passivity — specific, structured learning is work, and it is visible.

The first 30 days

People

• Meet everyone you will work with, one to one, for half an hour. Your team, your peers, your manager, your main internal customers, and the people upstream and downstream of your work.
• Ask the same four questions in every conversation, so the answers are comparable:
  • What does your work involve day to day?
  • What do you need from my role that you are not getting?
  • What is working well that I should not change?
  • If you could fix one thing, what would it be?
• Write the answers down. When the same frustration appears in six unrelated conversations, you have found the real problem rather than the loudest one.

The work

• Learn the systems, tools, and processes properly rather than superficially.
• Do the actual job for a while — take tickets, run a shift, sit with the team — even at manager level. It is the fastest way to understand where the friction is.
• Find out what is measured, how, and whether anyone trusts the numbers.
• Read the last two quarters of reporting and any post-incident reviews.

Expectations

In week one, ask your manager directly: “What does good look like at ninety days? And what would make you think this hire had gone wrong?” The second question is the more useful of the two and almost nobody asks it.

One early, visible, small win

Not a restructure. Something small, obviously useful, and entirely within your own control — a report nobody had time to build, a piece of documentation that did not exist, a recurring meeting made shorter. It establishes that you deliver, without claiming to know better than the people already there.

Days 31–60

Now you have context, so you can act on it.

• Take full ownership of your core responsibilities. By day 60 you should not need supervision on routine work.
• Pilot one change. Small, reversible, and measured. Run it alongside the existing process rather than replacing it, so people can see the output matches before they have to trust it.
• Test your diagnosis. Take what you think the main problem is to two or three people who know the area and ask what you have missed. You usually have missed something, and finding out now is cheap.
• Build one relationship outside your immediate team — whoever you depend on most.
• Ask for feedback explicitly, around day 45. “What should I be doing differently?” Early correction is much easier than correction at six months.

Days 61–90

• Deliver something measurable. The pilot rolled out, the process changed, the backlog cleared. Something you can point at.
• Propose the larger piece of work — now with evidence from your own months here rather than assumptions from your last job.
• Review against the plan with your manager. What worked, what you got wrong, what you now understand differently.
• Set the next horizon. What months four to six look like.

Presenting one at interview

If you are asked for a plan at final stage — increasingly common for management and senior roles — the assessment is not really about the plan. It is about whether you understand the problem, whether you are appropriately humble about what you do not know, and how you think.

Structure for a presented plan

1. What I understand the role to be about — two or three sentences, in their words, drawn from the interviews
2. Days 1–30 — what I would learn, who from, and what I would want to be able to answer by day 30
3. Days 31–60 — where I would expect to start contributing, and the first thing I would test
4. Days 61–90 — what I would aim to have delivered, and what I would be proposing next
5. What I would need from you — access, introductions, decisions
6. What I do not yet know — the assumptions this plan depends on

That last section is the one that distinguishes a strong plan from a generic one. Naming your own assumptions demonstrates exactly the judgement the role requires.

What gets marked down

• Specific fixes proposed for problems you have only heard described in an interview
• Restructuring the team in month one
• Targets you have no basis for — “increase conversion by 25% in 90 days”
• Generic language that could apply to any role at any company
• No mention of the people you would need to work with

A worked example

Using it once you have the job

Write your own in week one even if nobody asks for it, and share it with your manager. It does three useful things: it forces you to decide what matters, it gives your manager visibility without them having to chase, and it creates a written record of what you were told the priorities were — which is valuable if the priorities change and nobody tells you.

Review it at 30, 60, and 90 days and change it out loud. A plan revised because you learned something is working correctly; a plan followed rigidly after the facts changed is not.