A 30-60-90 day plan divides your first three months into three different jobs: learn how the place actually works, contribute something visible, then lead work nobody assigned you. Answer four questions and get a plan built for your role, whether you start Monday or you are bringing it to a final-round interview.
Generic plans fail in the first week because "familiarize yourself with the culture" is not an action anyone can do on a Tuesday. The builder above asks what role you are starting, whether you manage anyone, and how much your manager has actually told you, then writes the three phases with actions specific to that job and milestones a manager could verify. Here is the shape it builds toward.
The 30-60-90 template is not three equal boxes; each phase exists because of a resource that expires. In your first 30 days you hold a license nobody else on the team has: you can ask basic questions without looking incompetent, and people will explain how things really work, including the parts that contradict the wiki. That license expires around week four or five. Spend it deliberately: calls, documents, and one honest conversation with everyone your work touches.
Days 31 to 60 exist because trust is bought with visible output, not with insight. The move is to pick one contribution someone on the team already wants, small enough to finish, public enough to be noticed, and ship it. Not your best idea; your most finishable one. And days 61 to 90 are for the thing that separates a hire who worked out from a hire who was worth it: proposing work that was not on anyone's list, built on a pattern your fresh eyes caught before they stopped being fresh.
This is also why writing the phases out of order fails. A day-10 initiative gets politely ignored because nobody trusts it yet, and a day-80 basic question quietly costs you credibility. The plan is less a to-do list than a promise to do things in the order the organization can accept them.
Managing changes the plan's arithmetic, because from day one your output is the team's output, and the team formed its opinions about you before you arrived. The first 30 days become a listening tour: a one-on-one with every report, asking the same few questions (what should I keep, what should I change, what do you wish the last manager had asked) and changing nothing yet. The discipline to not fix things in month one is the hardest and highest-yield line in the whole plan, because every process you inherit is load-bearing for someone.
By day 60 the goal is one fixed friction the team already hated, chosen from what the one-on-ones surfaced, because trust is bought fastest with an item from their list. By day 90 you make your first structural change, and it lands, because you can propose it in the team's own words. If you are inheriting a team of more than eight, stretch the listening tour and shrink the day-60 fix; the tour is the work at that size.
Hiring managers sometimes ask for a 30-60-90 outright, especially in sales, customer success, and leadership roles. Even unasked, bringing one to a final round is one of the few moves that visibly separates candidates, because it changes what the meeting is. The other candidates answer questions about themselves; you and the interviewer spend twenty minutes working on their team's next quarter.
The craft is in the humility of it. You do not know their org yet, and pretending otherwise reads as arrogance. So the plan is one page, not ten. The day-30 bar is learning, not results. And every assumption is framed as a question: "By day 30 I would want to run eight customer calls; is that realistic given the current book?" You are not being graded on whether the plan is correct. You are being graded on how you think when you do not have enough information, which is exactly the condition the job will hand you.
Run the generator above with the role you are interviewing for and "I am building this plan to find out" as the expectations answer; that setting writes the day-30 milestone around turning ambiguity into agreed goals, which is the honest position of someone who does not work there yet. It pairs well with the other final-round staple, your answer to tell me about yourself.
This is a real run of the builder above, inputs included, so you can judge the output before you use it. Read the milestones especially: each one is an artifact or a state a manager could check, which is what separates a plan from a wish.
Inputs: Customer success manager, mid-market SaaS · individual contributor · broad direction but nothing measurable · small team of 2 to 8
Learn how customers actually use the product and where your accounts stand, before forming a single opinion.
ActionsSit in on 8 to 10 customer calls across segments and keep verbatim notes on what customers ask for. Read the last two quarters of churn post-mortems and renewal notes for your book of accounts. Meet everyone your accounts touch, sales, support, and product, and ask each person where handoffs break.
MilestoneBy day 30, a one-page map of your accounts ranked by renewal risk, reviewed with your manager, plus the measurable goals this plan was missing.
Convert what you learned into one visible win someone on the team already wants.
ActionsTake over the full call load for your book and run your first business reviews solo. Fix the one onboarding friction every post-mortem mentioned, and document the fix so it survives you. Flag your two highest-risk renewals early and bring your manager a save plan for each.
MilestoneBy day 60, one at-risk account moved to stable, and a fix shipped that another teammate has already reused.
Propose something that was not on anyone's list, built on a pattern only fresh eyes could see.
ActionsTurn your call notes into a proposal: the top three reasons customers stall in month one, with a fix for each. Pitch one initiative you would own next quarter, sized small enough to ship. Ask your manager for the feedback conversation the 90-day mark has earned.
MilestoneBy day 90, an initiative with your name on it approved for next quarter, and a book of accounts you can forecast without checking.
Notice the day-30 milestone doing double duty: because the inputs said the manager gave only broad direction, the plan's first deliverable is the measurable goals themselves. The plan repairs its own brief, which is what you would want a real hire to do.
What is a 30-60-90 day plan?
A 30-60-90 day plan is a one-page outline of your first three months in a new role, split into three phases with different jobs: days 1 to 30 for learning how the organization actually works, days 31 to 60 for contributing one visible win, and days 61 to 90 for leading work nobody assigned you. Each phase ends in a milestone a manager could verify.
How do I write a 30-60-90 day plan?
Start from the role's actual work, not a generic template. For each phase write one focus sentence, about three actions specific to the job (the calls, systems, and people it touches), and one checkable milestone. Keep learning in the first phase, output in the second, and initiatives in the third; the order matters because questions are only free early, and trust is only spendable late.
Should I bring a 30-60-90 day plan to an interview?
For final rounds in sales, customer success, and leadership roles, yes; elsewhere it rarely hurts and often separates you. Keep it to one page, set the day-30 bar at learning rather than results, and frame every assumption as a question for the interviewer. You are demonstrating how you think without enough information, which is the actual job condition, and the meeting turns into a working session.
What should be in the first 30 days of a plan?
Inputs, almost exclusively. Meetings with everyone your work touches, the recent history of the thing you now own (past reports, post-mortems, tickets), and real exposure to customers or users. The first month is the only time you can ask basic questions for free, so the plan should spend that license deliberately. The milestone: you can explain how things really work, and your goals are now measurable.
What does a 30-60-90 day plan look like for a new manager?
The first 30 days become a listening tour: a one-on-one with every report, and no changes yet, because every inherited process is load-bearing for someone. By day 60, fix one friction the team already hates, chosen from what the tour surfaced. By day 90, make your first structural change, proposed in the team's own words. Managers who reverse this order pay for it all year.
Is a 30-60-90 day plan the same as an onboarding plan?
No, and the difference is the owner. An onboarding plan is the company's checklist for you: accounts, training, compliance. A 30-60-90 day plan is yours: what you intend to learn, contribute, and start, with milestones you set. Companies with excellent onboarding still cannot write it for you, because its whole value is that it contains your read of the role.
A 30-60-90 day plan tells you what order to do things in. Which initiatives you should be the one to propose comes from knowing what you are best at, and Coached's free career read measures that from just your LinkedIn.
Get your free career read »
"My free resume review was truly eye-opening. I found out why I wasn't getting interviews and exactly what to add to get past resume screeners. I've already had way more callbacks since I used it. I recommend it to all my friends who are job searching."
"Probably the best thing I've done this year. Showed me what my strengths were and the jobs and industries I should be focusing on. The most impactful part though was how it identified this spiral I'd been doing subconsciously - yikes, freakishly accurate."
Thank you for the checklist! I realized I was making so many mistakes on my resume that I've now fixed. I'm much more confident in my resume now.