30-60-90 Day Plan: Template and Examples for New Hires

The first three months in a new job shape how managers perceive you for years afterward. A 30-60-90 day plan turns those months from a vague "settle in and figure things out" into a structured sequence: learn, contribute, then own. These plans help new hires at every level — and bringing one to an interview sets you apart from candidates who only answer questions. This guide explains the framework, gives you a fill-in template, and shows worked examples for common roles.

Key Takeaways

• The framework moves through three phases: learn (days 1-30), contribute (31-60), own and improve (61-90).
• A good plan pairs every goal with a measurable outcome and a deadline.
• Bring a draft plan to interviews to demonstrate initiative — hiring managers remember it.
• Review and revise the plan with your manager at each 30-day mark; it's a conversation tool, not a contract.
• Match goals to your role: an individual contributor's plan differs from a manager's.
• Keep it short — one page beats five.

What a 30-60-90 Day Plan Is

A 30-60-90 day plan is a written outline of what you intend to learn, deliver and improve in your first three months. It exists in two moments of the hiring journey: sometimes as a document you present in interviews to show how you'd approach the role, and more commonly as a personal roadmap you refine with your manager after starting.

The plan's power isn't the document — it's the discipline. Committing to specific outcomes forces you to prioritize, ask better questions and notice early whether you're on track.

The three phases at a glance

Phase	Focus	Typical activities	Success looks like
Days 1-30	Learn	Orientation, systems, people, processes	You know who does what and how work flows
Days 31-60	Contribute	Take on real tasks, apply what you learned	You deliver work that needs minimal rework
Days 61-90	Own	Full responsibilities, improvements, feedback	You run your lane independently and propose one improvement

The weighting shifts by role — a warehouse hire is hands-on in week one, while a policy analyst may spend the first month reading. Adjust the ratio, keep the sequence.

A Fill-In Template

Here is the skeleton. Fill each phase with three to five items.Days 1-30: Learn the landscape

• Goal: [What you need to understand — products, systems, customers, culture]
• Action: [How you'll learn it — shadowing, documentation, meetings]
• Measure: [How you'll know it's done — can complete X unassisted by day 30]

Days 31-60: Contribute meaningfully

• Goal: [First real deliverables and responsibilities]
• Action: [What you'll take ownership of]
• Measure: [Quality bar or volume you'll hit]

Days 61-90: Own and improve

• Goal: [Full independence in core duties]
• Action: [One process improvement or initiative to propose]
• Measure: [Manager-confirmed outcome]

Add a short "resources and support I'll need" note at the bottom — tools, access, introductions — because naming them early prevents month-two stalls.## Worked Examples

Example: customer service representative

• Days 1-30: Complete product training; learn the ticketing system; shadow senior agents; memorize the top 20 customer issues. Measure: handle simple tickets with coaching by day 30.
• Days 31-60: Handle a full queue independently; contribute notes to the knowledge base. Measure: meet team-average ticket volume by day 60.
• Days 61-90: Take on difficult or escalated tickets; review one recurring issue and suggest a fix. Measure: consistently meet quality and satisfaction benchmarks.

Example: marketing coordinator

• Days 1-30: Audit the current calendar, brand guidelines and past campaign results; meet every stakeholder one-on-one; learn the approval workflow. Measure: draft a campaign brief that passes review the first time.
• Days 31-60: Own a small campaign end to end; take over the weekly metrics report. Measure: campaign launches on schedule with no missed approvals.
• Days 61-90: Propose one improvement based on the metrics you've been reporting; mentor the next intake on the workflow. Measure: proposal presented and considered by leadership.

Example: team manager

• Days 1-30: Hold one-on-ones with every direct report and key peer; learn the team's goals, history and pain points; observe before changing anything. Measure: a written team assessment shared with your manager.
• Days 31-60: Establish regular rhythms — team meetings, one-on-one cadence; take on one visible problem the team has named. Measure: team operating rhythm running without prompting.
• Days 61-90: Set or refine team goals; give developmental feedback. Measure: each direct report has a clear goal and knows their next growth step.

Using the Plan in Interviews vs. On the Job

In interviews: Present a concise version (maximum one page) when asked how you'd approach the role — or offer it at the end. Frame it as "here's how I'd think about my first 90 days; I'd refine this with you."

After starting: Rebuild the plan from the real landscape you find — the interview version was based on guesses. Align on it with your manager in week one, then check in at each phase boundary. Those check-ins are where the plan pays for itself: course corrections in month one are painless; discovering a misalignment in month three is not.

Common Mistakes to Avoid

1. Promising outcomes you can't control. "Increase sales 20%" may not be yours alone to deliver in 90 days. Aim for "build and begin executing a qualified outreach plan."
2. Making it about you only. Plans that include learning from colleagues and supporting teammates read better in collaborative workplaces.
3. Too much detail. Five pages of micro-tasks signals busywork, not strategy. One page, three to five goals per phase.
4. Treating it as fixed. Businesses change. Revising at day 30 is judgment, not failure.
5. Skipping the measures. Goals without outcomes are wishes. Every line needs a "how I'll know."

Frequently Asked Questions

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

Share it and invite input, but don't frame it as something requiring approval. The plan is your working document; your manager's role is to correct course and remove obstacles. A 20-minute alignment conversation in week one, then quick check-ins at day 30, 60 and 90, keeps you synchronized.

Does a 30-60-90 plan matter for entry-level jobs?

Yes, scaled down. Even in a first job, showing you've thought about how you'll learn the role signals maturity. Keep it modest: know the menu by day 30, handle a rush section by day 60, train the next new hire on something by day 90.

What if my role changes mid-plan?

Revise the plan to match reality and note what changed. A plan is a navigation instrument, not a pledge. Updating it openly with your manager demonstrates adaptability.

Can I reuse the same plan for different job applications?

Use the template repeatedly, but rewrite the content for each role. Hiring managers spot a recycled plan instantly, and a generic plan cancels the advantage a specific one creates. The customization is where the value lives.

How do I create a plan when I don't know the company yet?

Build it on the role's public facts — the job posting, the company's products, LinkedIn basics — and mark the assumptions you'd verify first. A plan that openly says "I'd validate these in week one" reads as more credible, not less.

Final Thoughts

A 30-60-90 day plan replaces the anxiety of a new job with a sequence you can act on: learn deliberately, contribute early, then take ownership with evidence. Build your one-page draft today using the template above — whether you're preparing for interviews or starting a role next month — and schedule your first review conversation before day 10. The structure does the heavy lifting; you just have to commit it to paper.