What to Do in the First 90 Days of a New Job

The first 90 days of a new job are not a test of how quickly you can do everything. They are a chance to learn how the organization works, build useful relationships, and make a few well-chosen contributions that show sound judgment.

The strongest start is usually quieter than people expect. Listen closely, clarify priorities, document what you learn, and avoid making promises before you understand the work.

This 30-60-90 day plan gives you a practical way to do that.

Before day one: prepare a small starting file

You do not need an elaborate system. Create one document with four sections:

• People you need to meet.
• Questions about the role, team, customers, or process.
• Terms, tools, and decisions you need to understand.
• Priorities and follow-ups agreed with your manager.

Bring it to onboarding sessions and one-on-ones. This makes it easier to spot patterns and prevents important questions from disappearing after a busy week.

Days 1 to 30: learn the work and the people

Your first month is for context. You are learning what success means, how decisions get made, where work gets stuck, and which relationships shape the role.

Clarify expectations with your manager

In your first conversations, ask direct questions:

• What should be true by the end of my first 30, 60, and 90 days?
• Which responsibilities need my attention first?
• What should I understand before I recommend changes?
• How do you prefer to receive updates or questions?
• Which partners or customers should I meet early?

Write down the answers. If expectations change, update your notes and confirm the new priority rather than assuming.

Meet the people around the work

Schedule short conversations with teammates and close partners. Ask what they own, what they need from your role, what a smooth handoff looks like, and what they wish new people understood sooner.

These are not networking calls for their own sake. They help you see the operating reality around the job.

Observe before you overhaul

New employees often notice friction quickly. That fresh perspective can be valuable, but the first explanation is rarely the full explanation. Before proposing a change, find out what constraint, history, customer need, or compliance requirement shaped the current process.

Days 31 to 60: contribute in a focused way

Once you understand the basics, choose work that is useful, visible to the right people, and realistic for your level of context.

Pick one or two clear priorities

Do not create a long list of “quick wins.” Pick a small number of deliverables that connect to the priorities you and your manager discussed.

For example, a new operations coordinator might:

• Document a recurring intake process that is currently spread across chat messages.
• Build a simple tracker for a shared project.
• Clarify handoffs between two teams that repeatedly lose information.

The goal is not to make the work look dramatic. It is to make the work easier to understand and complete.

Ask for feedback while there is time to adjust

Use regular check-ins to ask whether you are spending time on the right things. A useful question is: “Based on what you have seen so far, what should I continue, stop, or learn next?”

Feedback becomes more useful when it is attached to actual work. Bring a short update, name the decision you need help with, and be ready to adjust.

Communicate progress simply

Keep status updates short and concrete:

This week I completed the onboarding documentation draft, met with support and sales to confirm handoffs, and identified two open decisions for the intake workflow. Next, I will revise the draft based on their input and confirm ownership with my manager.

This shows progress without overstating it.

Days 61 to 90: build ownership with context

By the third month, you should have enough context to take clearer ownership of a responsibility, project, or recurring process. That does not mean you know everything. It means you can connect your work to the team’s goals and make informed recommendations.

Share a practical point of view

If you see an opportunity to improve something, present the context first. Explain the current goal, the friction you observed, the options you considered, and the tradeoff involved.

For example:

I noticed that incomplete requests slow the weekly reporting process. The team needs a reliable intake step, but the current form asks for details many requesters do not have. I recommend a shorter required form with an optional follow-up field, then a two-week review of the results.

That is more useful than saying, “This process does not work.”

Prepare a 90-day conversation

Before the end of the period, summarize what you learned, what you delivered, and what you recommend prioritizing next. Ask your manager to confirm where you are meeting expectations and where you need to build more depth.

Your note can be brief:

• Key relationships and workflows you now understand.
• Work completed or moved forward.
• Decisions or risks that still need attention.
• Two or three priorities for the next quarter.

This creates a shared record of your start and gives you a better basis for the next phase of the role.

Avoid these first-90-days mistakes

• Trying to fix everything immediately: Learn the reason behind the process before changing it.
• Waiting too long to clarify priorities: Ask early when expectations are unclear.
• Treating relationships as optional: Good work often depends on knowing who owns what and how they prefer to work.
• Overpromising: Commit to what you can deliver with the context and authority you actually have.
• Keeping progress invisible: Share concise updates so your manager understands what you are learning and moving forward.

Keep a record you can use later

The notes you take in a new role can later become strong resume material. Save specific examples of projects, scope, tools, people involved, and results once they are clear. Good resume bullets are easier to write when you capture the evidence while the work is fresh.

When it is time to update your job-search materials, start with a format that keeps your experience organized and easy to tailor. Resume Genesis templates give you a clean structure for turning real work into a focused resume.

Browse Resume Templates →

Frequently asked questions

What should I focus on in my first 30 days at a new job?

Focus on learning how the team works, meeting key partners, understanding expectations, and collecting the context you need before making broad changes.

What is a 30-60-90 day plan?

A 30-60-90 day plan divides the first three months into phases: learning and relationship-building, focused contribution, and clearer ownership of priorities or projects.

How often should I meet with my manager in the first 90 days?

Use the meeting rhythm your manager prefers, but ask for regular check-ins early enough to confirm priorities, ask focused questions, and adjust before misunderstandings grow.

When should I suggest improvements at a new job?

Start by learning the context behind existing processes. Share observations after you understand the goal, the constraints, and the people affected, then frame suggestions as practical options rather than quick judgments.

How can I track progress during my first 90 days?

Keep a simple weekly record of people you met, decisions you learned, work delivered, open questions, and agreed priorities. It helps you prepare for check-ins and identify what to clarify next.