How to write a 30-60-90 day plan
- Start from the job description. The responsibilities listed there are what your manager will judge you on.
- Learn first. The first 30 days are for people, tools and context. Big changes can wait.
- Contribute next.By day 60, own a first project and share what you've learned.
- Lead by day 90. Deliver, work independently, and propose goals for the next quarter.
- Agree it with your manager. Share the plan in your first week and review it at each stage.
Starting remotely? Pick the starter goals about overlap hours, written decisions and onboarding notes: they cover what an office would teach you without asking.
30-60-90 day plan examples by role
Example plans for common kinds of roles. Copy the goals that fit into the builder above.
When to use it: Software, data and other technical roles, where the first weeks go into the codebase and the deploy process.
First 30 days: Learn
- Set up the development environment and ship a first small change
- Read the architecture docs and the last few incident reviews
- Pair with a teammate on a code review each week
Days 31 to 60: Contribute
- Own a feature or bug-fix area end to end
- Join the on-call or support rotation, if the team has one
- Write down one gap in the documentation and fix it
Days 61 to 90: Lead
- Deliver a project from design to release
- Propose one technical improvement with a short written plan
- Help onboard the next engineer who joins
When to use it: Account executives and business development, where pipeline and product knowledge come first.
First 30 days: Learn
- Learn the product, pricing and main competitors
- Listen to recorded calls and shadow live demos
- Get set up in the CRM and learn the sales process
Days 31 to 60: Contribute
- Run my own discovery calls and demos
- Build a pipeline in my territory or segment
- Agree my quota and ramp targets with my manager
Days 61 to 90: Lead
- Close my first deals
- Share what I've heard from prospects with product and marketing
- Review pipeline and win rate with my manager
When to use it: Support and customer success roles, where the help center and ticket tools are the first things to learn.
First 30 days: Learn
- Learn the ticketing tool and the help center
- Shadow teammates on live tickets and calls
- Answer my first tickets with a review from a teammate
Days 31 to 60: Contribute
- Handle a full queue on my own within the team's response times
- Update help articles I found unclear
- Learn the escalation path to product and engineering
Days 61 to 90: Lead
- Own a topic area or a set of accounts
- Spot one recurring issue and propose a fix
- Review my quality and satisfaction scores with my manager
When to use it: Content, growth and product marketing, where you need the audience, the channels and the numbers first.
First 30 days: Learn
- Learn the audience, positioning and current campaigns
- Get access to analytics and review last quarter's results
- Meet sales and product to hear what customers ask about
Days 31 to 60: Contribute
- Launch a first campaign or piece of content
- Set up reporting for the channels I own
- Agree targets for my channels with my manager
Days 61 to 90: Lead
- Report on results and what I'd change
- Propose next quarter's plan for my area
- Document the playbook for my channels
When to use it: A first or new management role, where trust and context matter more than quick changes.
First 30 days: Learn
- Have a one-on-one with each person on the team
- Learn the team's goals, projects and how work is tracked
- Meet my peers and my manager's other reports
Days 31 to 60: Contribute
- Set up regular one-on-ones and a team rhythm that works across time zones
- Agree priorities for the next quarter with my manager
- Address one quick win the team raised in one-on-ones
Days 61 to 90: Lead
- Share a written plan for the team's next two quarters
- Give each person clear goals and feedback
- Review hiring needs and team structure
What each phase is for
Meet people, set up tools, and agree what success looks like.
Own a first project, share early ideas, ask for feedback.
Deliver results, work on your own, and set next quarter's goals.
Before your first day
Still interviewing? Prepare with the questions to ask the interviewer, and accept the offer in writing with the job offer response emails. At your first review, the self-evaluation phrases help you look back on the plan.