Your first 90 days at a new job, week by week.
Interactive 30-60-90 day plan. 73 tasks across 12 weeks, tagged by role. Save progress in your browser. No account, no email gate. Built on the learn-contribute-deliver framework that actually holds up after the honeymoon ends.
Week 1Land softlyLearn0 / 12 done+
- Confirm laptop, IDE, VPN, SSO, and password manager all work.Core
- Read your offer letter and role description in full once more.Core
- Get added to Slack/Teams channels for your team and adjacent teams.Core
- Schedule a 30-min 1:1 with your manager for week 2.Core
- Write down 3 questions you do not want to ask twice. Ask them this week.Core
- Find your team's source of truth: wiki, Notion, Confluence, or Drive.Core
- Pull the repo, run it locally, and commit a no-op README typo fix.Core
- Get added to your team's CI/CD, monitoring, and on-call rotations as observer.Core
- Test your home setup: lighting, mic, camera, async hours overlap.Core
- Read the last 3 months of board updates and team OKRs.Core
- Shadow 2 customer calls with senior reps before pitching anything.Core
- Open the design system in Figma. Star the canonical components page.Core
Week 2Map the territoryLearn0 / 8 done+
- Draw the team org chart on paper, including who actually decides things.
- List the top 5 metrics your team is measured on. Ask if you are unsure.Core
- Schedule a 1:1 with one peer outside your direct team.
- Find the runbook for last on-call incident. Read what broke and how it got fixed.
- Build the project from a clean clone; document any setup friction in a doc.
- Map the customer journey end-to-end with one Loom or whiteboard sketch.
- Write a working assumptions doc: what you think the role looks like at day 30, 60, 90.Core
- Identify your async-vs-sync ratio with the team. Mirror it.Core
Week 3Listen tourLearn0 / 7 done+
- Run 5 listening 1:1s. Same 4 questions every time.Core
- Take notes on patterns, not anecdotes. What gets repeated?Core
- Find the team's recurring frustration. The one nobody fixes because nobody owns it.
- Pair-program with two engineers on different areas of the codebase.Core
- Skip-level 1:1 with your manager's manager.
- Sit in on 3 product/design critiques. Take notes, do not present yet.
- Listen to 5 sales calls (recorded). Note every objection you hear twice.Core
Week 430-day debriefLearn0 / 5 done+
- Write a 1-page 30-day note: what you learned, what surprised you, what you will focus on next 30 days.Core
- Share the note in your next 1:1. Ask one direct question: 'Am I focused on the right things?'Core
- Ship one small visible win: a doc, a fix, a customer email, a design polish.Core
- Update your LinkedIn and internal profile to reflect the new role.
- Sanity-check: are you sleeping, eating, exercising? First month is exhausting.
Week 5Pick your first real betContribute0 / 6 done+
- Propose 2 candidate projects to your manager. Let them pick one.Core
- Write a short spec: problem, success metric, scope cuts you would make.Core
- Identify the top risk to delivery. Address it in week 1, not week 5.
- Find the senior reviewer for your work. Get their early read on the spec.
- Run your first manager 1:1 where you set the agenda.
- Run your first solo customer call. Bring a peer for backup.Core
Week 6Show progress visiblyContribute0 / 5 done+
- Write a weekly status update. 3 lines: shipped, learned, blocked.Core
- Demo your in-progress work in the team meeting. Even ugly, even partial.Core
- Open a PR or design draft early. Reviewing 200 lines beats reviewing 2000.Core
- Have one meaningful disagreement, in public, with curiosity not heat.
- If remote: post a short video update once this week instead of typing it.
Week 7Build trust on a hard callContribute0 / 5 done+
- Make one decision your gut says is right but you cannot fully prove yet.Core
- Push back on one piece of work that you think is misallocated.
- Ask for feedback in writing. 'What would you change about how I worked this week?'Core
- Run a postmortem (or retro) on a small mistake out loud.
- Send your first cold email or first close-attempt of the cycle.Core
Week 860-day calibrationContribute0 / 5 done+
- Update the 30-day note into a 60-day note. Same 1 page, same 3 sections.Core
- Ask your manager: 'If you had to score me right now out of 10, what is it?'Core
- Identify the one thing you would do differently if you started this role today.
- Take one full unplugged day. Energy debt compounds.Core
- Promote one peer's work in a Slack channel. Specific, public, sincere.
Week 9Drive the spec to doneDeliver0 / 5 done+
- Cut scope hard. What is the smallest version that proves the bet?Core
- Set an explicit ship-by date. Tell at least one person.Core
- Run one dry-run demo to a friendly audience before the real one.
- Triage your inbox. Reply to 5 things that have been waiting on you.
- Find your first deal in late-stage. Pre-mortem the closing call.Core
Week 10Ship and write it upDeliver0 / 5 done+
- Ship the project. Even if it is rough.Core
- Write a launch note: what shipped, why, what is next, what you learned.Core
- Tag everyone who helped. By name. With specifics.Core
- Capture metrics before/after. Even rough numbers beat no numbers.
- Close one deal or hand off one warm pipeline.
Week 11Plan quarter twoDeliver0 / 5 done+
- Propose 2 areas you want to own in the next quarter to your manager.Core
- Identify one thing that you and only you can do at this company.
- Identify one habit from this 90 days you want to keep forever.
- Identify one team norm you want to gently change.
- If managing: lock 1:1 cadence and growth conversation rhythm with each report.Core
Week 1290-day reviewDeliver0 / 5 done+
- Write the 90-day review: shipped, scope, scale of impact, gaps, next bets.Core
- Have the formal 90-day check-in with your manager. Ask for written confirmation of expectations met.Core
- Update your brag doc. Keep it as a private file, forever.Core
- Send three thank-you messages to people who made the first 90 easier.
- Plan a real break before quarter two. Even a long weekend.Core
Pick your role track
Each track filters the checklist to the items that matter for that role and adds three watch-outs the maker wishes someone had said in week one.
First quarter for software engineers. Land a real PR by week 4, ship a real feature by week 10. Code review fluency over hero work.
First quarter for new managers. Listen first, decide second, hire third. The team you inherit is not the team you will have.
First quarter as a remote hire. Async by default, video on demand. Visibility is a written-output problem, not a webcam problem.
First quarter for new account executives. Shadow before pitching, write the objection list, close one small deal before quarter end.
First quarter for product designers. Learn the system before extending it, sit in critiques before presenting, ship one polished surface by week 10.
Playbooks for the awkward moments
First-day jitters, manager 1:1s you led too late, the 60-day check-in nobody warned you about. Short reads on the parts of onboarding that do not show up on the org chart.
What to do, what to avoid, and the one thing nobody warns you about on day one.
Three questions, two to skip, the one to never wait until week 6 for.
Three sections, one question, under 200 words. Sent the day before your week-4 1:1.
Four habits that move trust signals from body language to written output. Built for the first 90 days of any remote role.
Compare
Same phases, different bars. What changes when your output stops being your own work.
What changes, what stays. The four habits that decide whether remote works.
Same template, different deliverables. What seniority changes about the bar at day 90.
Why the standard quarter beats the executive 100-day frame for most roles.
Reading list
A few writeups for when the checklist is not the whole answer.
What an honest 30-60-90 day plan looks like for a real person, not a panel speaker. Three pages, three phases, one shared doc.
Five things to do, three things to avoid, one question to ask. Day-by-day for the first 5 working days at any new job.
Three questions to ask, two to skip, and the one to never wait until week 6 to bring up.
What changes when nobody can read your body language. The four habits that decide whether remote onboarding works.
Why halfway through your first quarter is the right time to renegotiate, and the script that makes it normal.
What to put in the one-page note you give your manager at the end of month one. Three sections, one decision they make, written under 200 words.
FAQ
What is a 30-60-90 day plan?+
A 30-60-90 day plan is a structured personal roadmap for the first three months in a new role. The first 30 days are for learning the team, product, and culture. Days 31-60 are for contributing on focused work without rebuilding everything. Days 61-90 are for delivering a visible result and resetting expectations for the next quarter. It is not a performance review document. It is a working tool you and your manager refer to in 1:1s.
How is this different from the templates Asana or Monday give you?+
Generic templates list tasks. This is an interactive checklist you save and revisit. It runs entirely in your browser, no account, no email. Tasks are tagged by role (engineer, manager, sales, designer, remote) so you can filter to what actually applies. Progress saves to your device. The structure follows Michael Watkins's First 90 Days framework: learn, contribute, deliver.
Should I share my 30-60-90 day plan with my manager?+
Yes. Share a short version, not the whole checklist. One page. Three sections: what you learned, what you will focus on next, where you need help. Ask one direct question, like 'am I focused on the right things?' Most managers do not get clear progress signals from new hires. A short note in week 4 buys a lot of trust.
What if my company already has an onboarding program?+
Use both. Company onboarding handles compliance, tools, and team intros, the floor. This checklist covers the social, cognitive, and political work, the parts no HR system tracks. The two do not compete. Most company onboarding ends at day 14, exactly when you actually start working.
Is the first 90 days really make-or-break?+
It is not make-or-break for keeping the job. It is make-or-break for building trust. The default at 90 days is 'I am still figuring this person out.' If you treat the first 90 days as a writing-things-down exercise, you usually graduate to 'this person is solid' by month 4. Skip the writing, and the verdict slides to month 9 or never.
What if I am working remotely?+
The remote track inside this checklist exists exactly for this. Working hours, async expectations, written-update cadence, and an early on-camera demo move from optional to load-bearing when nobody can read your body language. Visibility is a written-output problem when you are remote, not a webcam problem.
What if I am a new manager who used to be on this team?+
Run the manager track but be extra careful with weeks 1-4. The hardest part is shifting from peer to manager with people who watched the change happen. Hold off on reorgs and big calls until day 30 minimum. Do every skip-level 1:1 your manager offers, you need outside-the-team perspective right now more than usual.
Is there a 30-60-90 day plan for senior or staff roles?+
The phases are the same: learn, contribute, deliver. The bar moves. A senior IC ships a project by week 12 that a junior would ship by week 24. A staff or principal hire is expected to influence direction, not just delivery, by day 90. The IC track in this tool is written for mid-level engineers and reasonable for senior. For principal, treat the tasks as floor not ceiling.
Do I need to do every task?+
No. The checklist has 73 tasks across 12 weeks. Filter by role and focus on the core-priority items first. Skipping a task is fine, missing the milestone for the week is the signal that matters.
Does this work for non-tech roles?+
The framework is industry-agnostic. The specific tasks lean toward tech because that is the default audience. Sales and Designer tracks broaden coverage. For finance, ops, marketing, or other roles, use the IC or Manager track and translate task language to your context. The cadence (learn-contribute-deliver) holds in any white-collar role.
Can I print this checklist?+
Yes. Use your browser's print function (Cmd+P or Ctrl+P). The page is print-styled to one section per page break. Best for offline use or sharing with a manager who prefers paper.
Where does my progress save?+
In your browser's local storage on this device. Nothing leaves your machine. If you switch devices, you start fresh, by design. Your data is never sent to a server, no account, no tracking attached to a user identity. Standard analytics apply (page views) but nothing tied to your specific tasks.
Is the framework backed by research?+
The 30-60-90 structure originated in management literature, popularized by Michael Watkins's 2003 book The First 90 Days. The phases (learn, contribute, deliver) and tactics (listening tour, early wins, scope cuts) are drawn from that body of work plus career advice from Andy Grove, First Round Review, and HBS alumni resources. Specific task wording and ordering is our own.
What if I started a new job 6 weeks ago, am I behind?+
No. Start at the current week and work forward. Optionally backfill the high-priority tasks from earlier weeks (Listening tour, 30-day note). The exact day count matters less than the rhythm of learning, then shipping, then resetting expectations.
Why is this tool free?+
It is part of Choppy Toast, a small portfolio of free tools the maker uses to learn what people need. No account, no email gate, no upsell. Ads in the corners pay for the domain. If it helped you land your first 90 days well, share it with one person who is starting a new job soon.