30-60-90 Day Plan Template for a New Job
Starting a new job is exciting and a little disorienting. You want to prove you were the right hire, but the first weeks are a blur of names, tools, and unwritten rules. A clear 30-60-90 day plan gives you a way to turn that noise into deliberate progress. This guide walks you through a practical template you can adapt to any role, plus how to use it so it actually shapes your first three months.
What’s inside
Why a 30-60-90 day plan is worth your time
How the template is structured
Days 1-30: learn before you leap
Days 31-60: contribute and build trust
Days 61-90: own outcomes and set direction
How to write goals that hold up
Using the plan in your onboarding conversations
Common mistakes to avoid
How Blomma helps you build and use your plan
Why a 30-60-90 day plan is worth your time
A 30-60-90 day plan is a simple document that maps what you’ll learn, do, and deliver in your first three months. It matters for two reasons. First, it forces you to think in phases instead of trying to do everything at once, which is how most new hires burn out or make avoidable mistakes. Second, it signals maturity. When you share even a rough version with your manager in week one, you show that you think in terms of outcomes, not just tasks.
The first 90 days set the tone for how people see you. Early impressions are sticky, and the habits you form now tend to persist. A plan doesn’t lock you into anything rigid, it gives you a starting point you can adjust as you learn. If you tend to freeze at the start of anything big, having a written plan is one of the most reliable ways to build early momentum instead of waiting to feel ready.
How the template is structured
The template splits your first three months into three 30-day phases, each with a different center of gravity: learning, contributing, and owning. For each phase you fill in four fields.
Focus: the one-sentence theme of the phase
Learning goals: what you need to understand (people, product, process)
Performance goals: what you’ll actually do or deliver
Relationships: who you’ll build a working relationship with
Keep it to a single page. The point is clarity, not comprehensiveness. Three or four goals per phase is plenty; more than that and you dilute your attention. Write it in a shared doc so your manager can react to it, and revisit it at the end of each phase to check what’s still true. The template is a living tool, not a form you fill out once and file away.
Days 1-30: learn before you leap
The first month is for absorbing, not proving. Your focus is understanding how things actually work versus how the org chart says they work. Resist the urge to propose big changes; you haven’t earned the context yet.
Learning goals for this phase usually include your team’s goals and metrics, the tools and systems you’ll live in, and the history behind current projects. Book short intro meetings with everyone you’ll work with and ask each person the same few questions: what does success look like for you, what should I know that isn’t written down, and who else should I talk to.
Performance goals should be small and concrete. Ship one tiny thing, complete onboarding tasks, take clean notes you can reference later. On relationships, prioritize your manager and your two or three closest collaborators. Set an expectation early about how you’ll work together, how often you’ll check in, and what a great first 90 days looks like in their eyes. That single conversation prevents a surprising amount of drift.
Days 31-60: contribute and build trust
By month two you should shift from learning to doing. You have enough context to take real work off someone’s plate, and doing so is how trust gets built. Your focus this phase is delivering visible, useful results without overreaching.
Performance goals now get more ambitious. Own a project end to end, even a small one. Volunteer for something slightly outside your comfort zone. The aim is to demonstrate you can be handed something and it will get done well. Keep learning, but let it be pulled by the work rather than done in the abstract.
This is also when you start to understand what earns recognition on your team. It helps to know how leaders actually weigh contribution, because the way execs make promotion decisions is often about consistent, visible impact rather than raw hours. On relationships, widen your circle. Meet people in adjacent teams and start understanding dependencies. A quick mid-point check-in with your manager here is worth its weight, ask what’s going well and what you should adjust.
Days 61-90: own outcomes and set direction
The final month is about ownership and looking forward. You should be operating with real independence now, needing less hand-holding and starting to spot problems before they land on your desk. Your focus is owning outcomes and showing you can set direction, not just follow it.
Performance goals for this phase might include leading a project, proposing an improvement now that you have earned context, or taking over a recurring responsibility. This is where the earlier restraint pays off, your ideas land better because they’re grounded in how things actually work.
Use the end of the 90 days to have an explicit conversation with your manager about performance and the next quarter. Come with a short self-assessment: what you delivered, what you learned, where you want to grow. Treat the whole ramp as a learning project, because staying curious is what separates people who plateau from people who keep compounding. Then reset your goals for the months ahead.
How to write goals that hold up
Vague goals are useless in a plan like this. “Get up to speed” tells you nothing about whether you succeeded. Make each goal specific enough that you and your manager could both agree, at the end of the phase, whether you hit it.
A good format is: verb, object, measure. “Understand the sales pipeline” becomes “Map the full sales pipeline and present it back to my manager by day 25.” “Contribute to the product” becomes “Ship two bug fixes and one small feature by day 55.” The measure doesn’t have to be a hard number, but it should be observable.
Tie each performance goal to something your team already cares about. If you can connect your 30-60-90 goals to your manager’s priorities, you’re building visibility and relevance at the same time. And keep the list short. A plan with four sharp goals per phase beats one with twelve fuzzy ones, because you’ll actually remember it and act on it.
Using the plan in your onboarding conversations
A plan sitting in a private doc does half the job. The real value comes from sharing it. In your first week, tell your manager you’re drafting a 30-60-90 day plan and ask if they’d review it. Most managers will be pleasantly surprised, and their edits are pure gold, they’re telling you exactly what they want to see.
Use the plan as the backbone of your check-ins. Instead of a vague “how am I doing,” you can walk through your phase goals and ask specifically where to adjust. This turns feedback from awkward to concrete. It also protects you: if priorities shift, you’ll catch the change early instead of discovering at day 80 that you optimized for the wrong thing.
Share the relevant slice with close collaborators too. Letting a peer know what you’re focused on this month invites them to flag a landmine or an easy win you’d have missed. A plan you talk about openly ramps you faster than one you keep to yourself.
Common mistakes to avoid
The most common mistake is trying to make a splash too early. Proposing sweeping changes in week two rarely lands, because you don’t yet have the context or the trust to back it up. Learn first.
The second is building a plan and never looking at it again. A 30-60-90 plan is only useful if it’s a living document, revisit it at each 30-day mark and rewrite what’s no longer true. The third is confusing activity with impact. Attending forty meetings isn’t progress; delivering one thing that mattered is.
Another trap is neglecting relationships in favor of tasks. Especially in your first month, who you know and trust determines how fast you can move later. Finally, don’t go it alone. Ask questions early and often, when the cost of not knowing is still low. The new hire who asks smart questions in week two looks far better than the one who guesses and gets it wrong in month two.
How Blomma helps you build and use your plan
A template gets you started, but the hard part is adapting it to your specific role, team, and manager, and then actually using it week to week. That’s where an always-on coach earns its keep. Blomma can help you draft your 30-60-90 day plan, pressure-test whether your goals are specific and realistic, and prep for the onboarding conversations where the plan does its real work.
Because Blomma is available whenever you need it, you can bring the small, in-the-moment questions that shape a good ramp: how to phrase a check-in, whether an idea is too early to raise, how to read feedback you just got. It’s coaching that fits around your actual first 90 days, not a one-off session you forget by week three.
Build your 30-60-90 plan with Blomma free →
Related reading
Starting a new job is exciting and a little disorienting. You want to prove you were the right hire, but the first weeks are a blur of names, tools, and unwritten rules. A clear 30-60-90 day plan gives you a way to turn that noise into deliberate progress. This guide walks you through a practical template you can adapt to any role, plus how to use it so it actually shapes your first three months.
What’s inside
Why a 30-60-90 day plan is worth your time
How the template is structured
Days 1-30: learn before you leap
Days 31-60: contribute and build trust
Days 61-90: own outcomes and set direction
How to write goals that hold up
Using the plan in your onboarding conversations
Common mistakes to avoid
How Blomma helps you build and use your plan
Why a 30-60-90 day plan is worth your time
A 30-60-90 day plan is a simple document that maps what you’ll learn, do, and deliver in your first three months. It matters for two reasons. First, it forces you to think in phases instead of trying to do everything at once, which is how most new hires burn out or make avoidable mistakes. Second, it signals maturity. When you share even a rough version with your manager in week one, you show that you think in terms of outcomes, not just tasks.
The first 90 days set the tone for how people see you. Early impressions are sticky, and the habits you form now tend to persist. A plan doesn’t lock you into anything rigid, it gives you a starting point you can adjust as you learn. If you tend to freeze at the start of anything big, having a written plan is one of the most reliable ways to build early momentum instead of waiting to feel ready.
How the template is structured
The template splits your first three months into three 30-day phases, each with a different center of gravity: learning, contributing, and owning. For each phase you fill in four fields.
Focus: the one-sentence theme of the phase
Learning goals: what you need to understand (people, product, process)
Performance goals: what you’ll actually do or deliver
Relationships: who you’ll build a working relationship with
Keep it to a single page. The point is clarity, not comprehensiveness. Three or four goals per phase is plenty; more than that and you dilute your attention. Write it in a shared doc so your manager can react to it, and revisit it at the end of each phase to check what’s still true. The template is a living tool, not a form you fill out once and file away.
Days 1-30: learn before you leap
The first month is for absorbing, not proving. Your focus is understanding how things actually work versus how the org chart says they work. Resist the urge to propose big changes; you haven’t earned the context yet.
Learning goals for this phase usually include your team’s goals and metrics, the tools and systems you’ll live in, and the history behind current projects. Book short intro meetings with everyone you’ll work with and ask each person the same few questions: what does success look like for you, what should I know that isn’t written down, and who else should I talk to.
Performance goals should be small and concrete. Ship one tiny thing, complete onboarding tasks, take clean notes you can reference later. On relationships, prioritize your manager and your two or three closest collaborators. Set an expectation early about how you’ll work together, how often you’ll check in, and what a great first 90 days looks like in their eyes. That single conversation prevents a surprising amount of drift.
Days 31-60: contribute and build trust
By month two you should shift from learning to doing. You have enough context to take real work off someone’s plate, and doing so is how trust gets built. Your focus this phase is delivering visible, useful results without overreaching.
Performance goals now get more ambitious. Own a project end to end, even a small one. Volunteer for something slightly outside your comfort zone. The aim is to demonstrate you can be handed something and it will get done well. Keep learning, but let it be pulled by the work rather than done in the abstract.
This is also when you start to understand what earns recognition on your team. It helps to know how leaders actually weigh contribution, because the way execs make promotion decisions is often about consistent, visible impact rather than raw hours. On relationships, widen your circle. Meet people in adjacent teams and start understanding dependencies. A quick mid-point check-in with your manager here is worth its weight, ask what’s going well and what you should adjust.
Days 61-90: own outcomes and set direction
The final month is about ownership and looking forward. You should be operating with real independence now, needing less hand-holding and starting to spot problems before they land on your desk. Your focus is owning outcomes and showing you can set direction, not just follow it.
Performance goals for this phase might include leading a project, proposing an improvement now that you have earned context, or taking over a recurring responsibility. This is where the earlier restraint pays off, your ideas land better because they’re grounded in how things actually work.
Use the end of the 90 days to have an explicit conversation with your manager about performance and the next quarter. Come with a short self-assessment: what you delivered, what you learned, where you want to grow. Treat the whole ramp as a learning project, because staying curious is what separates people who plateau from people who keep compounding. Then reset your goals for the months ahead.
How to write goals that hold up
Vague goals are useless in a plan like this. “Get up to speed” tells you nothing about whether you succeeded. Make each goal specific enough that you and your manager could both agree, at the end of the phase, whether you hit it.
A good format is: verb, object, measure. “Understand the sales pipeline” becomes “Map the full sales pipeline and present it back to my manager by day 25.” “Contribute to the product” becomes “Ship two bug fixes and one small feature by day 55.” The measure doesn’t have to be a hard number, but it should be observable.
Tie each performance goal to something your team already cares about. If you can connect your 30-60-90 goals to your manager’s priorities, you’re building visibility and relevance at the same time. And keep the list short. A plan with four sharp goals per phase beats one with twelve fuzzy ones, because you’ll actually remember it and act on it.
Using the plan in your onboarding conversations
A plan sitting in a private doc does half the job. The real value comes from sharing it. In your first week, tell your manager you’re drafting a 30-60-90 day plan and ask if they’d review it. Most managers will be pleasantly surprised, and their edits are pure gold, they’re telling you exactly what they want to see.
Use the plan as the backbone of your check-ins. Instead of a vague “how am I doing,” you can walk through your phase goals and ask specifically where to adjust. This turns feedback from awkward to concrete. It also protects you: if priorities shift, you’ll catch the change early instead of discovering at day 80 that you optimized for the wrong thing.
Share the relevant slice with close collaborators too. Letting a peer know what you’re focused on this month invites them to flag a landmine or an easy win you’d have missed. A plan you talk about openly ramps you faster than one you keep to yourself.
Common mistakes to avoid
The most common mistake is trying to make a splash too early. Proposing sweeping changes in week two rarely lands, because you don’t yet have the context or the trust to back it up. Learn first.
The second is building a plan and never looking at it again. A 30-60-90 plan is only useful if it’s a living document, revisit it at each 30-day mark and rewrite what’s no longer true. The third is confusing activity with impact. Attending forty meetings isn’t progress; delivering one thing that mattered is.
Another trap is neglecting relationships in favor of tasks. Especially in your first month, who you know and trust determines how fast you can move later. Finally, don’t go it alone. Ask questions early and often, when the cost of not knowing is still low. The new hire who asks smart questions in week two looks far better than the one who guesses and gets it wrong in month two.
How Blomma helps you build and use your plan
A template gets you started, but the hard part is adapting it to your specific role, team, and manager, and then actually using it week to week. That’s where an always-on coach earns its keep. Blomma can help you draft your 30-60-90 day plan, pressure-test whether your goals are specific and realistic, and prep for the onboarding conversations where the plan does its real work.
Because Blomma is available whenever you need it, you can bring the small, in-the-moment questions that shape a good ramp: how to phrase a check-in, whether an idea is too early to raise, how to read feedback you just got. It’s coaching that fits around your actual first 90 days, not a one-off session you forget by week three.
Build your 30-60-90 plan with Blomma free →
Related reading
How to start anything
How execs make promo decisions
There is nothing cooler than learning