30 60 90 Day Plan: Template, Example and How to Present It at Interview

What a 30 60 90 day plan is, when UK employers ask for one, what goes in each phase, a template you can copy and a worked example for a new team leader.

By Tony Musso on

A 30 60 90 day plan sets out what you intend to do in your first three months in a new job, split into three stages of roughly a month each. It shows an employer that you have thought about the role in practical terms: how you will learn the business, when you will start adding value, and what you hope to have achieved by the end of month three.

UK employers ask for one most often at interview for management, sales and senior roles. Some managers also ask new starters to write one in their first week. This guide explains what goes in each phase, gives a template you can copy, works through an example for a new team leader, and covers how to present it without overpromising.

When UK employers ask for a 30 60 90 day plan

You are most likely to be asked for a plan in these situations:

  • Interviews for management and team leader roles, where the employer wants to see how you would take over a team.
  • Sales roles, especially business development and account management, where they want to know how you would build a pipeline.
  • Senior and head-of roles, where the first three months shape how the rest of the job goes.
  • Second or final-stage interviews, often as a presentation task with a few days' notice.
  • Starting a new job, where your manager asks you to agree a plan for your first three months.

The 90-day timescale lines up neatly with probation. Many UK jobs start with a probation period, and a clear plan gives you and your manager something concrete to review at the end of it.

What goes in each phase

The most common structure is learn, contribute, lead. The labels vary, but the logic is the same: you cannot improve something you do not yet understand.

Days 1 to 30: learn

The first month is about listening and getting set up. Typical goals:

  • Meet your manager, team and key colleagues one to one
  • Understand how the team is measured, and how it is performing now
  • Learn the systems, processes, policies and any mandatory training
  • Find out what customers, or internal customers, think is working and what is not
  • Identify one or two small, low-risk improvements you could make

Days 31 to 60: contribute

In the second month, you start using what you have learned. Typical goals:

  • Take full ownership of your core responsibilities
  • Deliver the first quick improvements you identified
  • Start building relationships with other teams you depend on
  • Agree priorities for the rest of the quarter with your manager
  • Ask for feedback on how you are settling in

Days 61 to 90: lead

By the third month, you should be looking further ahead. Typical goals:

  • Propose a larger improvement, backed by what you have seen
  • Set goals with your team, or for your own pipeline or project
  • Review progress against the plan with your manager
  • Agree what success looks like for the next six to twelve months

A 30 60 90 day plan template

Copy this structure and fill it in for the role you are applying for. Keep each cell to a few short points.

Days 1-30: LearnDays 31-60: ContributeDays 61-90: Lead
Main focusUnderstand the role, team and businessDeliver in the core role and make early improvementsPlan ahead and take on bigger goals
PeopleOne-to-ones with manager, team and key colleaguesBuild links with other teams and stakeholdersSet goals with the team; give and ask for feedback
LearningSystems, processes, policies, mandatory trainingDeeper knowledge of customers, products or servicesGaps in your own skills to work on next
DeliveryOne or two quick, low-risk winsOwn core responsibilities fullyPropose and start a larger improvement
How you will measure itTraining complete; meetings held; current performance understoodQuick wins delivered; feedback gatheredPlan reviewed with manager; next six months agreed

If you want to turn the "Learning" row into something longer term, our guide to writing a personal development plan shows how to set goals beyond the first three months.

Example: a new team leader in a customer service centre

Here is how the template might look for someone applying to lead a team of customer service advisers. The details are illustrative; your own plan should use what you learn about the employer from the job description, the website and the interview.

Days 1 to 30: learn

  • Hold a one-to-one with each adviser to understand their experience, what they enjoy and what gets in their way
  • Sit in on calls and live chats across different shifts to see the work first hand
  • Learn the main performance measures, such as call quality scores, customer satisfaction and response times, and where the team stands now
  • Complete system training and read the complaints and quality procedures
  • Agree with my manager what a good first 90 days would look like for them

Days 31 to 60: contribute

  • Run regular one-to-ones and start giving structured feedback on quality
  • Fix one quick problem raised by advisers, such as an unclear script or a slow handover between teams
  • Meet the team leaders on other shifts so that handovers and standards are consistent
  • Build a simple weekly summary of team performance to share with the team

Days 61 to 90: lead

  • Set individual development goals with each adviser
  • Propose one larger change based on what I have seen, with a clear reason and a way to measure it
  • Review the plan with my manager and agree priorities for the next six months

Notice that the plan does not promise a specific improvement in figures. You cannot know the right target until you have seen the team's data. Saying how you would measure progress is more credible than inventing a number.

Adapting it for a sales role

For a sales manager or business development role, the same three stages apply, but the content shifts:

  • Learn: products, pricing, the CRM, existing accounts and the current pipeline; shadow experienced colleagues on calls and meetings.
  • Contribute: start prospecting and taking ownership of accounts; aim for first meetings and proposals.
  • Lead: build a pipeline review routine, agree targets with your manager and refine your approach based on what has worked.

How to present your plan at interview

Keep it short. One page, or three or four slides if it is a presentation, is usually enough. If the employer gives a time limit, stay comfortably within it.

Research before you write. Use the job description, the company website, recent news and anything said at earlier interviews. Refer to the employer's own priorities where you can.

Show your thinking, not just a list. For each phase, say briefly why it comes in that order. Interviewers are often more interested in your reasoning than in the specific tasks.

Admit what you do not know yet. Phrases such as "I would want to check this once I have seen the data" show good judgement, not weakness.

Bring copies. If you present in person, a printed one-page version is helpful for the panel to annotate.

Be ready for questions. Expect "What would you do if the team resisted that change?" or "Which of these matters most?". Our guide to common interview questions and answers covers how to handle follow-ups calmly, and you can use your plan to frame good questions to ask at the end of the interview, such as how the employer measures success in the first three months.

If the plan helps you secure an offer, the same thinking is useful in salary negotiation: it gives you specific examples of the value you expect to bring.

Common mistakes to avoid

  • Changing everything in month one. Proposing major changes before you understand the team suggests you will not listen.
  • Promising figures you cannot back up. A target without data looks like guesswork. Say how you would set targets instead.
  • Making it generic. A plan that could apply to any company shows little research. Use the employer's language and priorities.
  • Forgetting people. Plans full of systems and processes, with no mention of building relationships, miss the most important part of a new role, especially a leadership one.
  • Too much detail. Twenty bullet points per phase is hard to follow. Pick the few things that matter most.
  • Treating it as fixed. Say you would review the plan with your manager and adjust it. That is what good managers expect.

Know how you naturally work before you plan your first 90 days Work Personality shows your working style, how you prefer to build relationships and make decisions, so your plan plays to your strengths.

Take Work Personality

Frequently asked questions

What is a 30 60 90 day plan?

It is a short plan setting out what you will do in your first 30, 60 and 90 days in a new job. The usual structure is learn, contribute and lead. Employers use it to see how you think about a new role and how you would settle in.

How long should a 30 60 90 day plan be?

For an interview, one page or three or four slides is usually enough. Keep each phase to a handful of clear goals, and check whether the employer has given a time limit for presenting it.

Do I need a 30 60 90 day plan for every interview?

No. They are most often requested for management, sales and senior roles. If one is not requested, you can still prepare a short version to help answer questions like "What would you do in your first few months?".

Should I include targets in my plan?

Include how you would measure progress, but be careful with specific figures. Without access to the team's data, it is usually more credible to say you would agree targets with your manager once you have seen current performance.

Can I use a 30 60 90 day plan after I start a new job?

Yes. Many people write one in their first week and agree it with their manager. It gives you both a clear way to review progress, and it fits well with the end of a probation period.

Related reading

If you are weighing up options, our guide to choosing a career test explains what a good one tells you and what it cannot.