The 30-60-90 Day Plan, Without the LinkedIn Polish
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.
Most 30-60-90 day plans on the internet are written for the person presenting them in an interview, not the person living through them. They sound impressive and do nothing for you on Tuesday morning of week 6.
The version that actually helps is shorter, less polished, and shared with one person: your manager.
Three pages, not thirty
A working plan fits on three pages. Page one is days 1-30. Page two is days 31-60. Page three is days 61-90. Each page has the same three sections: what you will learn, who you will talk to, what you will produce. That is it.
Resist the urge to fill page one with deliverables. Days 1-30 are for learning. Producing in the first month means you are guessing in public, and the team has not yet earned the right to your guesses.
The one shared section
Each page has a shared section your manager updates with you in 1:1s. Two prompts: "what are you not seeing?" and "what would you change if you ran my desk?" Most managers will give better answers to the second one. They are flattered by the question and instinctively reveal what they actually care about.
The unwritten rule
Your plan is not graded. It is a working tool. Crossing things out, swapping priorities, and discovering that week 4's project was wrong are signs the plan works, not signs it failed. The version of the plan you ship at day 90 should look almost nothing like the one you wrote at day 5.
The exception: the milestones in the plan are sticky. Your 30-day note exists. Your 60-day calibration happens. Your 90-day review is on the calendar. The content moves; the rhythm holds.
What goes in the shared doc
Three sections per phase. Keep each to 5 lines maximum.
Learn: the 5 things you will know cold by day 30. Not "the codebase," but specific files, specific people, specific docs. "Familiar with the auth flow" is fluff. "Read auth/session.go and paired with Priya on a token refresh bug" is signal.
Talk to: the 8-12 people you will have 1:1s with by day 30. Names, not roles. Schedule them in week 1 even if the actual conversation happens week 3.
Produce: the one or two visible artifacts. A document. A small fix. A customer email. Things you can point at when someone asks "what have you been working on?"
Three pages, three phases, one shared doc. That is the entire framework. Everything else is a podcast.