30-60-90 Day Plan Template: IC vs Manager Versions

Sep 10, 2026 | Blog, First 90 Days

You start with a blank doc titled “30-60-90.” Week one, it fills with meeting notes and tool links. Week four, it’s a graveyard of half-finished goals. Week eight, you’re still “ramping” while your calendar looks like you already own half the company. The plan didn’t fail because you lack ambition. It failed because it never forced you to stop collecting and start owning.

A useful 30 60 90 day plan template does three jobs: it names what you’re learning, what you’re delivering, and what you’re quitting once that phase ends. That last part is the one most templates skip. Keep reading for fillable IC and manager tables, labeled samples, and the questions to run with your manager at day 0, 30, 60, and 90.

For the wider ramp playbook, see The First 90 Days at Work and the New Hire hub.

What belongs in a 30-60-90 (and what doesn’t)

Put in the plan
– Role outcomes your manager would recognize as success at each checkpoint
– A short learning list tied to those outcomes (systems, customers, decision rights)
– Two to four measurable 30 60 90 day goals per phase, written so a peer could score them
– Named stakeholders and the conversations you’ll have with them
– A start-doing list and a stop-doing list for each phase
– How you’ll show evidence (doc links, shipped work, demos, written recaps)

Leave out
– Vague vibes (“be a culture fit,” “build presence,” “add value everywhere”)
– A full year of OKRs disguised as onboarding
– Fake-precise metrics you can’t measure yet (“lift NPS 12 points by day 45”)
– Every meeting invite as a “goal”
– Promises about promotion, title, or retention (the plan is a ramp tool, not a contract)

Think of this as an onboarding plan template for the first quarter, not a career manifesto.

IC vs manager: same skeleton, different job

Both versions use learn → contribute → own. The object of attention changes.

	IC focus	Manager focus
Days 1–30	Map the work system, standards, and handoffs	Diagnose the team: goals, capacity, friction, informal power
Days 31–60	Ship scoped contributions inside the existing system	Improve one ritual, unblock delivery, clarify ownership
Days 61–90	Own a defined slice end to end	Own a team outcome with the people, not instead of them

ICs earn trust by finishing clean work. Managers earn trust by learning before swinging the axe. If you’re new to managing, resist a surprise reorg in month one. If you’re an IC who has done this craft before, still map this company’s tools and politics. Speed up the observer phase; don’t skip it.

How to write a 30 60 90 day plan without fluff

Co-create, don’t solo-hero. Draft 70% alone so you’re not waiting for perfect clarity. Bring it to your manager and ask what to cut, raise, or postpone. Your manager owns constraints and priorities; you own the draft and the evidence.

Make goals measurable without fake precision. Prefer “done / not done + artifact” over invented decimals. Good: “Publish a one-page map of campaign handoffs and review it with Ops by day 28.” Weak: “Fully understand marketing.” Good: “Close three support-adjacent bugs with peer review by day 50.” Weak: “Become a top performer.”

Learning goals without soft padding. Pair every learn item with a prove-it artifact. “Learn the billing funnel” becomes “Shadow two billing escalations and write a half-page ‘where tickets stall’ note for my manager.” Learning that never produces a shareable artifact turns into endless shadowing.

Day 30 vs day 90. Day 30 success looks like a clear map: you can explain the team’s purpose, customers, workflow, and what “good” means in your lane. Day 90 success looks like ownership evidence: a finished outcome with links, lessons, and a next-bet list. Don’t judge day 30 with day 90 standards.

The “stop doing” rule most plans miss

Write each phase with a start doing list and a stop doing list. Most failed new hire 30 60 90 plans die the same way: people keep collecting information and attending every meeting long after they should have narrowed to a few owned outcomes.

Examples of healthy stops:
– After day 30: stop joining every optional sync “just to learn”
– After day 60: stop treating shadowing as the main job
– After day 75: stop holding three candidate projects; pick one finish line

If your calendar still looks like day 10 on day 55, the plan isn’t a plan. It’s a diary.

Fillable IC 30-60-90 day plan template

Copy this table into a doc. Keep each cell short.

Phase	Learn (with artifact)	Contribute / Own	Start doing	Stop doing	Evidence by checkpoint
Days 1–30		Map + small reliable tasks
Days 31–60		Scoped deliveries
Days 61–90		One owned outcome

IC prompts to fill the blanks
– Who are my customers (internal or external)?
– What work enters, moves, and finishes on this team?
– What two contributions would my manager notice by day 60?
– What single outcome can I own by day 90 without boiling the ocean?

Fillable manager 30-60-90 day plan template

Managers need four tracks: team diagnosis, relationships, operating cadence, and a first owned initiative.

Phase	Team diagnosis	Relationships	Operating cadence	First owned initiative	Start / Stop
Days 1–30	Listening tour notes; goals & capacity sketch	1:1s with reports; peer managers; key partners	Observe rituals; note what wastes time	Candidate initiatives list (no big swings yet)	Start: listen & map / Stop: reorg talk
Days 31–60	Top 3 friction themes with evidence	Trust check-ins; skip-levels if useful	Fix one ritual (agenda, decision log, standup)	Scope one team-visible initiative	Start: clarify ownership / Stop: attending everything
Days 61–90	Written “how we work” update	Stakeholder recap of team direction	Cadence that sticks without you heroing	Ship the initiative with team ownership	Start: coach & close / Stop: doing ICs’ work

First 90 days plan example (fictional, labeled)

These are examples only, written for illustration. They are not real company results and include no fake metrics.

Example: Marketing IC (content / campaigns)

Days 1–30 (learn)
– Learn: campaign brief → creative → launch → retro path; artifact: one-page handoff map reviewed with manager
– Contribute: rewrite one stale FAQ and ship a small landing-page copy tweak under review
– Start: weekly “what I learned / still unclear” note to manager
– Stop: accepting every “can you just jump on this call?” invite after week 3

Days 31–60 (contribute)
– Own a scoped campaign module (email sequence or landing section) end to end inside the existing process
– Sit with Sales once to capture objection language; turn it into a short messaging addendum
– Start: proposing one process fix with evidence
– Stop: treating Slack reactivity as the measure of helpfulness

Days 61–90 (own)
– Own a defined outcome: ship one campaign slice, run the retro, and document what to reuse next quarter
– Share a progress packet: links, lessons, open risks, next bets
– Start: protecting deep work blocks for owned work
– Stop: collecting more “inspiration decks” instead of finishing

Example: New engineering manager

Days 1–30 (diagnose)
– Listening tour with every direct report; note goals, blockers, and career worries (private notes, not a public scorecard)
– Meet peer managers in product and design; learn decision rights for roadmap changes
– Observe standup, planning, and incident rituals; write “what I saw” not “what I’ll change”
– Start: psychological safety in 1:1s / Stop: announcing a reorg or tool migration

Days 31–60 (contribute)
– Clarify ownership on one sticky cross-team dependency
– Improve one ritual (for example: decision log in planning, or tighter incident handoff)
– Scope a first team initiative with the team’s input (tech debt slice, reliability bar, or hiring loop fix)
– Start: coaching on one recurring delivery friction / Stop: rewriting every PR yourself

Days 61–90 (own)
– Ship the team initiative with clear success criteria the team agrees on
– Give your manager a written team health + delivery summary (facts, not vibes)
– Start: succession and coverage thinking for key paths / Stop: being the bottleneck for routine decisions

Remote and hybrid adaptations

If you’re remote or hybrid, the template stays the same; the artifacts get more explicit.
– Replace hallway learning with scheduled “work-with-me” sessions (45 minutes, screen share, real tickets).
– Write decisions down. Ambiguity multiplies over chat.
– Book stakeholder time early; remote ramps stall when intros stay “someday.”
– Use a shared doc as the source of truth for your 30 60 90 day goals so timezone gaps don’t erase them.
– For hybrid: treat office days as relationship and ambiguity days, not as catch-up email days.

Review cadence and who else sees the plan

With your manager: co-review at day 0 (or week 1), then at 30, 60, and 90. A light mid-phase check in 1:1s is enough; you don’t need a new ceremony every Friday.

Beyond your manager: share a short version with your onboarding buddy and one or two critical partners (the people whose handoffs can sink you). Don’t broadcast a five-page plan to the whole org. Stakeholders need “what I’m owning and when I’ll need you,” not your full learning diary.

Internal transfers: yes, use the same template when you switch teams inside the company. You already know the employer; you don’t know this team’s customers, norms, or landmines. Compress days 1–30 if tribal knowledge overlaps, but still write stop-doing items so you don’t drag old-meeting habits into the new role.

Manager co-review questions (day 0 / 30 / 60 / 90)

Day 0 / week 1
1. What does good look like at day 30, 60, and 90 in this role?
2. What should I not touch in the first month?
3. Who must I meet early, and will you make warm intros?
4. How do you want updates (doc, Slack, 1:1 narrative)?

Day 30
1. Does my map of the work match reality?
2. Which learning items can we retire so I can contribute more?
3. What should I stop attending?
4. What’s the best contribution target for days 31–60?

Day 60
1. Which contributions landed, and which missed the mark?
2. Is my candidate day-90 outcome scoped right?
3. Where am I still acting like an observer?
4. What risk should I surface to stakeholders now?

Day 90
1. What evidence shows ownership, not just activity?
2. What should continue next quarter vs. stop?
3. How should we talk about this ramp in the first performance conversation?
4. What support do I need now that I’m past “new”?

Using the plan in your first performance conversation

Bring a one-page progress packet, not the whole living doc: goals by phase, links to evidence, what you stopped doing, and what you want next. Frame it as “here’s how I ramped and what I own now,” not “please validate my anxiety.” If your company has no formal 90-day review, this packet still gives you and your manager a shared story. The plan won’t guarantee a rating. It will make the conversation concrete.

Simple progress tracking (no new tool)

Use one doc with three headings (30 / 60 / 90). Under each, keep:
– Goals (checkbox)
– Evidence links
– Start / stop lists
– Open questions for your manager

Update it for 10 minutes before each checkpoint 1:1. Green / yellow / red on each goal is enough. If you need a project tracker to manage your onboarding plan, the plan is too big.

A practical way to start this week

Open a blank page. Write the three phases. Add one learn artifact, one contribution, and one stop-doing item for the phase you’re in. Send the draft to your manager with: “Here’s my working 30-60-90. What would you change?” Then protect time on the calendar that matches the phase you’re actually in.

A 90 day plan template free of fluff isn’t motivational wallpaper. It’s a narrowing device. Start wide, then cut. Keep the stops as honest as the starts.

FAQ

How long should a 30-60-90 document be?

One to two pages for the living plan, plus links. If it needs a table of contents, you’ve written a handbook.

What if my manager won’t co-create the plan?

Send a draft with clear asks and default dates. “I’ll assume these day-30 outcomes unless you edit by Friday.” Written defaults beat silent confusion.

Should I include stretch goals?

One stretch max, labeled as stretch. Don’t let aspirational work crowd out the must-hit outcomes that define a healthy ramp.

Can I reuse this as a 90 day plan template for contractors or interns?

Yes, with shorter ownership scope and clearer supervision checkpoints. Keep the stop-doing lists; contractors drown in optional meetings too.

Does completing a 30-60-90 guarantee I’m succeeding?

No. It creates shared expectations and evidence. Success still depends on judgment, delivery quality, and team context.