Sample 30-60-90 day plans: what good actually looks like

The internet is full of 30-60-90 day plan templates that all say the same thing: day 30 is for learning, day 60 is for contributing, day 90 is for leading. That framing is fine as scaffolding. It’s useless as a plan, because it applies equally to every job and therefore applies to none of them.

A plan that says “in the first 30 days I will learn the business” tells your manager and your future self nothing. The plan that lands is the one specific to your role, your team’s actual situation, and the one or two things that genuinely matter most in your particular ramp.

The anatomy of a useful sample plan

Before looking at examples: a useful 30-60-90 has three qualities. It names goals, not activities. “Understand the product roadmap” is an activity. “Identify the two biggest roadmap gaps and understand why they’re open” is a goal. Second, it has success signals, not metrics. You often can’t define a hard metric in week one. You can define how you’ll know you’ve landed each phase. Third, it’s short enough to be read in 90 seconds. A plan that requires a table of contents won’t be used.

Sample plan: new analyst, operations

Day 30: orientation

• Goal: understand the current operating rhythm and where the breaks are
• Key relationships: direct manager, two team leads, the analyst who had this role before me
• Questions: what’s the biggest recurring bottleneck in the weekly ops cycle? What does a strong vs. weak analyst output look like here?
• Success signal: I can explain the full ops cycle to someone new without consulting my notes

Day 60: contribution

• Goal: have a first project contribution reviewed and improved
• Working on: [specific workstream from manager briefing]
• Gaps to close: the BI tool this team uses, the reporting convention they expect
• Success signal: I’ve submitted at least one analysis that passed review with minimal revision

Day 90: ownership

• Goal: own the weekly [report type] end-to-end, without supervision
• Driving: [specific report or process from manager scoping conversation]
• Relationships: my counterpart on the finance team knows my work and can confirm it
• Success signal: my manager is no longer checking the report before it goes out

Sample plan: new marketing coordinator

Day 30: orientation

• Goal: understand the current campaign calendar and who owns what
• Key relationships: campaign leads, design team liaison, one external agency contact
• Questions: what’s the current approval bottleneck for campaigns? What’s the biggest thing that went wrong in the last launch?
• Success signal: I can brief a new vendor on our brand guidelines without help

Day 60: contribution

• Goal: own one end-to-end deliverable for an active campaign
• Working on: [asset type or channel from manager brief]
• Gaps to close: the campaign management tool, the internal review process
• Success signal: I’ve shipped one campaign asset that needed only light revision

Day 90: ownership

• Goal: be the coordinator of record on a specific campaign from briefing to launch
• Driving: [specific campaign or channel from manager]
• Relationships: agency contact and design lead know my style and can anticipate my asks
• Success signal: campaign launches on time with my name on the internal brief

Sample plan: new product or strategy hire

Day 30: orientation

• Goal: understand the product’s three biggest open bets and the evidence behind each
• Key relationships: the PM or lead who’s been here longest, one engineer, one customer-facing person
• Questions: what’s the hypothesis behind [biggest current initiative]? What would make us pivot?
• Success signal: I can articulate the product strategy in one paragraph without sounding like I’m reading from the deck

Day 60: contribution

• Goal: have contributed meaningfully to one live problem, not just an orientation exercise
• Working on: [from manager brief, a specific problem space or quarter’s work]
• Gaps to close: user interview access, data access, context on the last three major decisions
• Success signal: I’ve given feedback on an in-progress project that the team incorporated

Day 90: ownership

• Goal: be driving at least one clearly defined project or problem space end-to-end
• Driving: [from manager brief or proposed during week 3 check-in]
• Relationships: my key cross-functional stakeholders know my work
• Success signal: I’m the person others come to with questions about [my domain]

What to do with the samples

Take whichever one is closest to your role and adapt it. Change the goals to match your actual context, based on the conversations you’ve had in week one. Fill in the [bracketed fields] from your manager brief and your own onboarding conversations.

Then share it with your manager in week two. Not as a finished plan, as a starting point: “Here’s my current thinking, does this match what you’d want to see?” That conversation is usually shorter than you expect and more useful than any orientation document HR hands you on day one.

Further reading

• The 30-60-90 day plan for new roles
• First 90 days boot sequence
• The early win playbook: credibility without overpromising