How to Write a 30-60-90 Day Plan (With Template and Examples)

A professional mapping out a first-ninety-days plan

A 30-60-90 day plan is a one-page document that turns your first three months into a sequence of visible wins. Most people write one only when an interviewer asks for it, then file it away. The version that actually works is the one you write before your first day and update every two weeks - because the first ninety days are when a new hire is either trusted with real work or quietly parked.

Why the first ninety days decide the hire

A hiring decision is a bet, and the first ninety days are when the bet gets settled. Your manager is not still evaluating whether you are smart - they decided that in the interview. They are watching for something narrower: whether the picture they had of you matches the person who showed up, and whether they can hand you something important without checking on it.

That is why the plan matters more than the output in the first weeks. You are not being measured on what you produce yet. You are being measured on whether you look like someone who will produce, and a written plan is the cheapest way to make that visible.

The reframe: a plan is proof of thinking, not a to-do list

Most 30-60-90 plans fail because they are lists of activities: meet the team, read the docs, shadow a call. Those are things that happen to you. A plan that earns trust is a list of questions you intend to answer and the evidence you will bring back.

The difference is small on paper and enormous in practice. "Meet the team" is a calendar item. "Learn who decides what, and where the work actually gets stuck" is a question with an answer you can present. One of those makes you look busy. The other makes you look like a peer.

The three questions behind every phase

Every strong plan answers the same three questions in order. The phases are just the order in which you are allowed to ask them.

Days 1-30 - What is actually going on here? You are learning the system: the people, the work, the history, and the gap between how things are described and how they run.
Days 31-60 - What should change first? You are picking one thing to improve and shipping it - small enough to finish, visible enough to matter.
Days 61-90 - What do I own? You are converting your learning into a piece of the job that is yours: a number, a process, a relationship, or a deliverable.

Days 1-30: learn the system

The first month is reconnaissance, and the deliverable is a map. Not a report - a map you can draw on one page: who does what, where decisions are made, what the team is measured on, and where the friction is.

Book a short conversation with everyone you will work with, and ask the same three questions: what are you working on, what is slowing you down, and who else should I talk to?
Find the one document everyone points to and read it properly. It is usually out of date, which is itself information.
Ask your manager what success looks like at ninety days, in their words, and write it down exactly as they say it.
Keep a running list of things that surprised you. Surprises are the raw material for the change you will propose in month two.

By day thirty you should be able to explain, in two minutes, how work moves through the team and where it stalls. That explanation is the deliverable. If you cannot give it, you spent the month being introduced instead of learning.

The first week, in order

If you only do five things in your first five days, do these. They are ordered so that each one makes the next one easier.

Day one: confirm what your manager expects from you by the end of the month, and write it down in their words.
Day two: get access to everything you will need - systems, documents, calendars, and the shared drive - before you need it.
Day three: book the conversations. Put every one of them in the calendar now, while you are still new enough that nobody says no.
Day four: read the thing everyone points to, and note the three places it disagrees with reality.
Day five: send your manager a short note - what you have learned so far, what you are still missing, and what you plan to do next week.

That last note is the one people skip, and it is the one that matters. It costs five minutes and it tells your manager, without you saying it, that you are going to be easy to manage.

Days 31-60: change one thing

Month two is where most plans go quiet, because the learning is done and the temptation is to keep meeting people. Resist it. Pick one improvement, small enough to finish inside the month, and ship it.

Choose something you saw in month one that is genuinely broken and cheap to fix - a report nobody reads, a handoff that drops, a meeting that could be a message.
Write the one-paragraph case: what is wrong, what you propose, what it costs, and how you will know it worked.
Get your manager's agreement before you build it. A small win they approved is a win. A small win they did not ask for is a surprise.
Ship it, then say so in one sentence at the next team meeting. Quiet wins do not compound.

The point is not the fix. The point is that by day sixty your manager has watched you find a problem, propose a solution, and finish it - which is the entire job, compressed into a month.

Days 61-90: own a number

The last month is about converting trust into ownership. Ask for the thing you want to be responsible for, and make it specific enough to be measured.

Pick one metric, process, or relationship that will be yours: a weekly number, a recurring deliverable, a set of accounts, a system.
Write down what "good" looks like for it and how often you will report on it.
Agree the handover with whoever holds it now, so ownership moves cleanly instead of being quietly shared.
At the ninety-day mark, present what you learned, what you changed, and what you now own. Three slides, ten minutes.

That presentation is the real deliverable of the whole plan. It closes the loop on the bet your manager made, and it is the moment the conversation shifts from whether you fit to what you should take on next.

The template

Fill this in before your first day and revisit it every two weeks. One page, four columns, three rows.

Phase	The question	Your deliverable	How you know it worked
Days 1-30	What is actually going on here?	A one-page map of the team, the work, and where it stalls	You can explain how work moves in two minutes
Days 31-60	What should change first?	One improvement, shipped and announced	Your manager agreed to it and it is done
Days 61-90	What do I own?	A named metric, process, or relationship	You report on it on a schedule you set

Using the plan in an interview

A 30-60-90 plan is also the strongest answer to the question every interviewer is really asking: what would you actually do here? Most candidates answer with adjectives. A plan answers with a sequence.

Bring it to a final-round interview, and keep it to one page. Offer to walk through it rather than handing it over.
Build it from public information: the job description, the company's own announcements, and what you learned in earlier rounds.
Say plainly that the first thirty days are for learning, and name the questions you would ask. Guessing at solutions before you have seen the system is the mistake the plan is designed to avoid.
End by asking whether your read of the priorities matches theirs. That question turns a presentation into a conversation.

The plan does not have to be right. It has to be specific, and it has to show that you think in phases rather than in enthusiasm.

If nobody asks for a plan

Some managers never ask for a 30-60-90 plan, and that is not a reason to skip it. Write it anyway, for yourself, and use it as the agenda for your one-on-ones. A plan you bring to a check-in turns a status update into a conversation about direction, which is the conversation that actually shapes your first year.

The same page works in the other direction. If you are the one hiring, a plan is the fastest way to tell whether a candidate has thought about the job or only about getting it. Ask for one page, not a presentation, and read the first thirty days closely - that is where the guessing shows.

The one-page template

Fill this in before your first day and revisit it every two weeks. One page, four columns, three rows - a 30-60-90 day plan is proof of thinking, not a to-do list.

Phase	The question	Your deliverable	How you know it worked
Days 1-30	What is actually going on here?	A one-page map of the team, the work, and where it stalls	You can explain how work moves in two minutes
Days 31-60	What should change first?	One improvement, shipped and announced	Your manager agreed to it and it is done
Days 61-90	What do I own?	A named metric, process, or relationship	You report on it on a schedule you set

The first-week checklist

Day one: your manager's definition of success at ninety days is written down in their words.
Day two: you have access to every system, document, and calendar you will need.
Day three: every introductory conversation is booked in the calendar.
Day four: the document everyone points to has been read, and its three gaps noted.
Day five: a short note to your manager - what you learned, what is missing, what is next.
The plan is one page and lives somewhere you will actually open it.
The first thirty days are questions, not answers.

Where people get stuck

Stuck because the plan feels like homework nobody asked for. Write it for yourself and use it as your one-on-one agenda. A plan you bring to a check-in turns a status update into a conversation about direction - and that is the conversation that shapes your first year.

Stuck because month two arrived and nothing has changed. Pick the smallest broken thing you saw in month one and ship it this month. The point is not the fix; it is that your manager watches you find a problem, propose a solution, and finish it.

Stuck because you are guessing at solutions before you have seen the system. That is the mistake the plan is designed to prevent. Keep the first thirty days for learning, name the questions you would ask, and let the answers choose the change.

Common mistakes

Writing a list of activities instead of a list of questions and deliverables.
Making the plan so ambitious that month one is already behind by week two.
Skipping the interview use case, then scrambling to build one the night before.
Treating the plan as private. A plan nobody sees cannot build trust.
Stopping at day thirty because the learning phase felt productive.
Proposing a big change in month two, before you understand why the current process exists.
Never revisiting it. A plan you do not update is a document, not a plan.

What good looks like

One page, three phases, one deliverable each.
The first month is questions, not answers.
One improvement shipped by day sixty, with your manager's agreement.
One thing you own by day ninety, with a number attached.
The plan was shown to someone - a manager, a mentor, or an interviewer.
It was updated at least twice.
You can explain the whole thing in two minutes.

Where this fits

A 30-60-90 plan is the bridge between getting the role and doing it well. If you are still building the case for the role, the career plan guide and the career goals examples are the place to start. If the plan is for an interview, pair it with company research and the four-part answer to tell me about yourself. And if the goal is to be trusted with more, the guide to building the case before you ask for a promotion picks up exactly where day ninety ends.

None of this requires a perfect first quarter. It requires a page, three questions, and the discipline to update it. Write the first version before your first day, and the rest of the plan gets easier every week.

Quick answers

Short answers to the questions this piece gets asked most.

What is a 30-60-90 day plan?
A one-page document that sets out what you will learn, change, and own in your first three months. Each phase has one deliverable: a map of how the work moves, one improvement shipped, and one thing you own by day ninety.

Should I bring a 30-60-90 day plan to an interview?
Yes, for a final round. Keep it to one page, offer to walk through it rather than handing it over, and say plainly that the first thirty days are for learning. The plan does not have to be right - it has to be specific.

What if my manager never asks for a plan?
Write it anyway and use it as the agenda for your one-on-ones. A plan you bring to a check-in turns a status update into a conversation about direction, which is the conversation that shapes your first year.

How long should a 30-60-90 day plan be?
One page. Three phases, one deliverable each, and a line on how you will know it worked. If it does not fit on a page, it is a project plan, not a first-ninety-days plan.

Read next:I Spent 10 Years in the Wrong Career. Here's How I Fixed It — A first-hand method for figuring out what you actually want to do next.They Offered You More Money to Stay. What Happens Next? — What really happens after you accept a counteroffer, and how to decide.The Experience Paradox Is a Lie. Here's How to Break In — How to break in without years of experience, and what entry level really means.

LaunchPath Careers tool: want to build this with structure instead of guesswork? LaunchPath Careers has a Job Search Roadmap and a Resume & Applications Roadmap. Start at LaunchPathCareers.com.

LaunchPath Careers by UFO Chaser® helps job seekers build a strategy-first job search. Learn more at LaunchPathCareers.com.

Search This Blog

Cosmo's Career Strategy Blog