30-60-90 Day Plan: How to Succeed in Your First 90 Days

A 30-60-90 day plan is not a task list. It is a structured way to learn an organisation, establish credibility, understand what is expected of you, identify the real priorities and progressively create measurable value. Used well, it is the difference between arriving in a new role and actually taking ownership of it.

This guide explains what a 30-60-90 day plan is, what belongs in each phase, what good looks like at senior level, and how to build one for your own role.

What is a 30-60-90 day plan?

A 30-60-90 day plan is a written plan for your first three months in a new role. It splits the transition into three phases: days 1 to 30 for learning and diagnosis, days 31 to 60 for alignment and prioritisation, and days 61 to 90 for execution and visible impact.

It exists because a new role has two workloads running at once. There is the job itself, and there is the parallel job of understanding the organisation well enough to do the job properly. Without a plan, the second workload gets crowded out by the first, and you end up making decisions on assumptions you never tested.

Anyone entering a new role benefits from one, but it matters most for experienced professionals, managers and functional leaders. The higher the role, the more of your value depends on judgement, and judgement depends on context you do not have yet.

The three phases differ because the question changes. In the first month the question is what is actually true here. In the second it is what matters most and who agrees. In the third it is what has demonstrably changed because you are in the role.

Why the first 90 days in a new job matter

In the first quarter you move from outsider to credible contributor, and organisations form a view of new people quickly. That view is assembled from a small number of visible moments: how you handled your first disagreement, whether your first commitment landed on time, whether your questions were useful or performative. Once formed, it takes more evidence to change than it took to create.

Five things have to happen inside this window.

Learning before changing. Every organisation carries decisions that look irrational from outside and sensible from inside. Changing something before you understand why it exists is the most common way new hires spend credibility they have not yet earned.

Understanding expectations. The role you were hired for and the role your manager is now judged on are not always identical. The gap is usually discovered in month four unless you ask about it in month one.

Building stakeholder trust. Trust here is specific: people need to know what you will do, whether you will do it, and whether you will tell them when you cannot. Reliability establishes faster than brilliance.

Reading organisational context. Decision rights, informal influence, funding cycles and history determine what is possible. The formal structure only tells you part of it.

Creating early evidence of value. Not a transformation. Evidence that your presence changed something concrete, visible and attributable.

The 30-60-90 day plan framework

The framework below is the shape of the plan, not a schedule to follow rigidly. Role, seniority, company size and whether the organisation is stable or in difficulty all move the boundaries. A leader inheriting a crisis compresses the diagnosis. A leader inheriting a well run function often needs longer before changing anything.

Days 1 to 30: learn before you change

The output of the first month is understanding, written down. Aim for a diagnosis you could defend, not a list of impressions.

Priorities for this phase:

• Clarify expectations with your manager. Ask directly what success looks like at 90 days and at one year, and what would count as a disappointing start. Write the answers down and confirm them.
• Understand the business objectives. Know what the organisation is trying to achieve commercially, and how your function contributes to or constrains that.
• Map key stakeholders. For each one: what they are judged on, what they need from you, and what is currently going wrong for them.
• Understand how decisions are made. Which decisions are yours, which need alignment, which are made elsewhere and simply communicated to you.
• Learn the operating model. How work enters the function, how it is prioritised, where it stalls.
• Review the performance metrics. What is measured, how reliable the data is, and which numbers people actually act on.
• Identify the cultural norms. How disagreement is expressed, how much detail is expected, what is decided in meetings and what is decided before them.
• Separate symptoms from underlying problems. Missed deadlines, escalations and rework are usually symptoms. The underlying cause is normally structural, in capability, ownership or prioritisation.

Questions to answer in your first 30 days

1. What does success in this role actually look like, in the words of the person who decides?
2. Which two or three outcomes matter most to the business this year?
3. Where are the biggest dependencies outside my control?
4. Which decisions require alignment, and with whom?
5. What has already been tried here, and why did it not work?
6. Who holds informal influence, regardless of title?
7. Which of the current problems are inherited and which are structural?
8. What would my predecessor say is the hardest part of this role?

Question five is the one most people skip, and it is the one that prevents you from confidently proposing something that already failed twice.

If you are still weighing whether this role is the right move at all, that is a different question from how to start well. Check your career direction first before building a plan around it.

Days 31 to 60: align and prioritise

The second month is where you shift from learning to judgement. You now have enough context to form a view, and the task is to test that view with the people who will have to live with it.

• Validate your diagnosis. Take your written diagnosis to three or four people who see the function differently. What survives that conversation is probably real.
• Agree priorities, do not announce them. A priority your manager and peers have argued with and accepted survives resource pressure. One you declared alone does not.
• Build stakeholder alignment. Confirm with each significant stakeholder what they will get, what they will not get, and by when.
• Choose quick wins carefully. A quick win is only useful if it is genuinely painful to someone senior, solvable inside four to six weeks, measurable without argument and not dependent on a political fight you cannot yet win.
• Clarify the trade-offs. Making the cost of a priority explicit, in time, money or capacity, is what turns a wish list into a plan.
• Establish an operating rhythm. The meetings, reporting and review cadence that make progress visible without constant escalation.
• Start deciding inside your mandate. Deferring every decision past day 60 reads as caution, then as weakness.

By day 60 you should be able to point to a written diagnosis that others recognise, a short list of agreed priorities, a stakeholder map that includes informal influence, and at least one commitment you made and met.

Days 61 to 90: execute and demonstrate impact

The third month converts alignment into evidence.

• Turn priorities into action. Named owners, dates and a definition of done for each.
• Deliver visible progress. Visible does not mean loud. It means the people who care about the outcome can see the movement without asking.
• Establish accountability. Who is responsible for what, and what happens when it slips.
• Make the decisions you have been holding. Some of them will be imperfect. Unmade decisions are usually more expensive than imperfect ones.
• Communicate progress. A short written update at the end of the quarter covering what you found, what you delivered and what you propose next. Very few people write one, and it disproportionately shapes how the first year is remembered.
• Build repeatable mechanisms. Anything you fixed manually will break again unless the way of working changed with it.
• Define what happens after day 90. The plan should end with the next two quarters sketched, not with a full stop.

Impact at 90 days does not mean a completed transformation. For senior roles, credible direction, alignment across stakeholders and the quality of the decisions taken usually matter more than a visible quick win. A Director who has correctly diagnosed a structural problem and secured agreement to fix it has delivered more than one who shipped three cosmetic improvements.

30-60-90 day plan example

The example below is a fictional operations manager joining a mid sized manufacturer with a delivery reliability problem. It shows the shape of a plan rather than a template to copy, because the content of a good plan is specific to the role.

Notice what the example does not contain: a long list of activities. Each phase has one objective and the evidence that would prove it.

30-60-90 day plan for managers and leaders

The plan changes materially when you manage people or enter a role with broader scope. The main difference is that your output is now other people's output, so any change you make to the team costs you time before it returns anything.

• Do not restructure immediately. A restructure in month one signals that you formed a judgement without evidence, and it removes the people who could have explained the context to you.
• Understand capability before judging individuals. Underperformance is frequently a symptom of unclear ownership, poor inputs or an impossible remit rather than of the person holding it.
• Identify informal influence. In most teams one or two people set the tone regardless of the organisation chart. Ignoring them slows every change you attempt.
• Assess decision rights honestly. Establish which decisions you can take alone, which need your manager, and which are genuinely owned by another function.
• Map cross functional dependencies. At Director level and above, most of what constrains you sits outside your own team.
• Clarify performance expectations early. People adapt quickly to a clear standard and slowly to an implied one.
• Distinguish inherited problems from structural ones. Inherited problems can be worked through. Structural problems need a decision from above you, and the sooner that conversation is framed with evidence the better.
• Avoid promising transformation before diagnosis. Enthusiasm in week one is understandable. An unmet commitment in month four is not recoverable at the same price.

How the emphasis shifts by level:

If you are stepping into people leadership for the first time, the shift in what the job actually is deserves separate attention. See what a people manager role really involves.

Common 30-60-90 day plan mistakes

Treating the plan as a task list. A list of activities proves you were busy. The plan should be organised around what you will learn, agree and change, with evidence attached to each phase.

Trying to prove yourself too quickly. Four half finished improvements read as scattered. One closed problem reads as effective.

Changing things before understanding context. Nearly every strange process was a reasonable answer to a problem you have not encountered yet. Ask what it was before removing it.

Confusing activity with impact. Meetings held, documents written and workshops run are inputs. What changed for the business is the output.

Ignoring stakeholder expectations. If your priorities and your manager's priorities have drifted apart by day 60, the quality of your delivery will not save the assessment.

Setting goals you do not control. A 90 day goal that depends entirely on another function is a hope, not a commitment. Set the goal on what you own, and manage the dependency explicitly.

Treating day 90 as the finish line. The first quarter buys you the right to a wider conversation about scope, resources and direction. Plan for that conversation rather than stopping at it.

How to create your own 30-60-90 day plan

1. Define what success looks like. In the words of the person who evaluates you, at 90 days and at one year.
2. Identify what you need to learn. List the specific unknowns that would change your decisions, not general background.
3. Map the critical stakeholders. What each is judged on, what they need from you, how much influence they hold.
4. Separate learning, alignment and execution. Assign each phase one primary objective. Resist putting execution in month one.
5. Define the evidence for each phase. What you would be able to show at day 30, 60 and 90 that proves the phase worked.
6. Identify the transition risks. Where the role is most likely to go wrong for someone with your background, and what you will do about it early.
7. Review the plan with your manager. This converts the plan from your private intention into a shared expectation, which is where most of its value comes from.
8. Adapt it as evidence arrives. A plan that survives the first month unchanged usually means you were not paying attention.

What should be different after 90 days?

If most of those have not shifted, the issue is usually that the first month was spent producing rather than diagnosing.

30-60-90 day plan: quick answers

What is a 30-60-90 day plan?

A written plan for the first three months in a new role, split into learning and diagnosis in days 1 to 30, alignment and prioritisation in days 31 to 60, and execution and demonstrated impact in days 61 to 90. It sets the objective and the expected evidence for each phase rather than listing tasks.

What should I do in my first 30 days at a new job?

Clarify what success looks like with your manager, map the stakeholders and how decisions are made, learn the operating model and the metrics, and write down a diagnosis of what is actually going wrong. Avoid changing anything significant before you understand why it exists.

What should happen in the first 60 days of a new role?

Test your diagnosis with people who see the function differently, agree a short list of priorities rather than announcing them, make the trade-offs explicit, establish an operating rhythm and start taking the decisions that sit inside your mandate.

What should I achieve in my first 90 days?

Visible progress on one or two agreed priorities, decisions taken and communicated, accountability in place, and a plan for the next two quarters. A short written summary of what you found, delivered and propose next is worth more than it costs.

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

Detailed enough to be specific about objectives and evidence, short enough that you will actually use it. One or two pages is usually right. Depth belongs in the questions you plan to answer, not in the number of activities listed.

Should I show my 30-60-90 day plan to my manager?

Yes. Most of the plan's value comes from turning your assumptions into a shared expectation. Review it in the first two weeks and again around day 30, once your diagnosis has replaced your assumptions.

What is a 30-60-90 day plan for a manager?

The same three phases, with the emphasis on the team. Understand capability and ownership before changing structure, identify informal influence, clarify performance expectations, and stabilise delivery before attempting redesign.

What should a Director focus on in the first 90 days?

Structural diagnosis and stakeholder alignment rather than quick wins. At Director level, credibility is built on the quality of your judgement, the decisions you take and the cross functional agreement you can secure, not on visible early activity.

Related reading

• Interviewing one level up: what changes
• Choosing between two offers
• Leadership philosophy examples that hold up under questioning