30-60-90 Day Plan Generator

About the 30-60-90 day plan generator

A 30-60-90 day plan shows how you will spend your first three months in a new role: what you will learn, where you will contribute first, and what you will own by day 90. Hiring managers ask for one in final-round interviews because it reveals how you think about a job before you have it. New hires write one to agree on expectations early instead of guessing.

This free 30-60-90 day plan generator takes the role, your experience level, the company if you know it, and what the job needs to achieve, then drafts a plan with goals, actions, and a measure of success for each phase. Treat it as a structure to fill with what you learn from the job post, your interviews, and your first conversations with your manager.

How to use it

1. 1

   Enter the role and company

   Use the exact job title. Add the company name if you have it so you remember to tailor the plan with what you know about their customers, products, and team.

2. 2

   Set your experience level

   Entry-level plans lean on learning and early wins. Senior and executive plans add stakeholder mapping, team assessment, and a strategy proposal, so pick the level of the role, not your general seniority.

3. 3

   Describe what the role needs to achieve

   Paste priorities from the job post or your interview notes, such as "rebuild the onboarding process" or "grow mid-market pipeline." This field shapes every phase, so be concrete.

4. 4

   Edit the plan with real names and numbers

   Replace placeholders with actual tools, teams, and targets. In an interview, label anything you are unsure about as an assumption you would confirm in week one.

What each phase of a 30-60-90 day plan covers

Each phase has a different job, and each should end with something your manager can see. A plan where all three phases say "learn and build relationships" tells a hiring manager nothing. A plan where each phase ends in a concrete deliverable shows you understand how trust gets built in a new job.

Days 1 to 30 are for learning: the product, the customers, the systems, the people, and how success is measured. Days 31 to 60 are for contributing: take on real work, deliver a first visible win, and start suggesting improvements. Days 61 to 90 are for owning: run your area with less supervision, propose a larger change, and set goals for the next quarter.

• Day 30 deliverable: a short written summary of what you learned, the open questions you still have, and the priorities you agreed on with your manager.
• Day 60 deliverable: one completed piece of work that matters to the team, such as a closed deal, a shipped fix, or a cleaned-up process.
• Day 90 deliverable: a proposal or plan for the next quarter, with goals you will be measured on.

Interview plan vs. first-week working plan

The same structure serves two purposes, and they need different levels of confidence. In an interview, you are working from the outside. Keep the plan to one page or five to seven slides, lean on what the job post and interviewers told you, and phrase proposals as hypotheses: "If onboarding is the main churn driver, I would start by reviewing the last 20 churned accounts." That shows initiative without claiming you already know their business.

Once you start the job, the plan becomes a working agreement. Bring a draft to your first one-on-one, ask your manager what they would change, and revisit it at day 30. Expect it to shift. A plan that survives first contact unchanged usually means you did not listen closely enough in the first month.

How to adjust the plan for your level

The shape stays the same at every level, but the balance between doing, learning, and leading changes. Use these rules when you edit the generated draft.

• Entry level: Spend most of the first month on training, shadowing, and learning tools. Aim for a small, clearly scoped win by day 60, such as handling a full workload independently. Show you can take feedback and improve.
• Mid level: Shorten the learning phase. Take on a real project by week three, deliver a measurable result by day 60, and by day 90 identify one process you would improve and why.
• New people manager: Hold one-on-ones with every direct report in the first two weeks and change nothing structural in month one. Fix one problem the team already complains about by day 60. Propose bigger changes only after you understand why things work the way they do.
• Senior or executive: Map stakeholders across departments, assess the team and budget, and deliver a written strategy with priorities and measures by day 90.

Where to find priorities when you are on the outside

A 30-60-90 plan is only as good as its understanding of what the job is for. Before an interview, pull priorities from every source you can. The job post lists responsibilities in rough order of importance, and repeated phrases usually point at the real problem. Your interview notes matter even more: write down every challenge an interviewer mentions, since those are the goals they will judge your plan against.

Public information fills the gaps. Company press releases, product launches, recent job postings for the same team, and the LinkedIn profiles of people in similar roles all hint at what the team is working on. If you still cannot find a clear priority, say so in the plan and make "confirm top three priorities with my manager" your first goal for week one.

Examples

Frequently asked questions