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

Three things: getting clear on what your role actually requires, building enough confidence to do the work without checking every step, and getting to know the colleagues your work depends on. Onboarding research treats these three, role clarity, self-efficacy and social acceptance, as the core of a newcomer's adjustment. Early contributions matter too, but they come more easily once the three are in place.

How do I ask questions in a new job without looking incompetent?

Ask specific questions with context. Say what you are trying to do, what you already tried, and what you need. A question like that shows you have done your part. Asking early is also easier than asking late: in your first weeks people expect questions, and a question in month four about something basic is harder to ask.

When should I ask for feedback in a new job?

Within the first few weeks, and well before any formal review. Pick a specific piece of work, ask the person who saw it closely, and ask a specific question about it. Waiting to be told means small misreadings can turn into habits before anyone mentions them.

Do I need a 30-60-90 day plan?

A short one helps, as long as you agree it with your manager. Keep it to one page: for each month, what you will deliver, what you will learn and which relationship you will build. Treat it as a practical tool that you adjust as you learn, not a promise carved in stone.

How is a mentor different from my manager during onboarding?

Your manager sets your priorities and evaluates your work. A mentor sits outside your reporting line, so you can ask the basic questions, test your reading of the culture and prepare difficult conversations. A mentor cannot change your manager's expectations or your probation outcome; they help you understand and meet them.

Your First 90 Days in a New Job: A Guide for New Hires and Mentors

Your first 90 days in a new job are the period in which you work out what the role really requires.

You also become confident you can do it, and become part of the group of people you work with.

Much of what decides how well those months go is not in the onboarding pack.

It is in your manager’s head, in the habits of your team and in the relationships you build or do not build.

This guide is for new hires and for the mentors who support them.

It covers expectations, people, feedback and a simple 30-60-90 day plan.

It ends with three worked examples and how to use it all in mentoring meetings.

What actually changes in your first 90 days?

Research on newcomers describes settling in as adjustment.

A large review of that research by Talya Bauer and colleagues groups it into three parts:

Role clarity. You know what you are supposed to do, what matters most and how your work is judged.
Self-efficacy. You feel confident that you can do the job well, even if you are not there yet.
Social acceptance. You feel accepted by your colleagues, and you know who to go to.

The same review links adjustment to later outcomes that organizations and newcomers both care about:

job satisfaction
commitment to the organization
performance
the intention to stay
actual turnover

It also found that newcomers’ own information seeking was part of that picture.

In other words, part of a good start is in your hands.

Bauer’s practical guidelines for onboarding describe four levels:

compliance (rules, policies, systems access)
clarification (what your job requires)
culture (how things are really done here)
connection (the relationships you need)

Compliance is the level formal onboarding most easily writes down.

Clarification, culture and connection depend more on people.

That is where a manager, colleagues and a mentor can help.

How do you find out what your role really requires?

Start by separating three kinds of knowledge:

Written down: the job description, team goals, documented processes.
Said out loud: what your manager told you, what came up in onboarding meetings.
Simply expected: what everyone assumes you know. Examples are how fast to reply, how polished a draft should be, or whether you raise problems in the meeting or afterward.

The third kind causes most newcomer mistakes, because nobody thinks to mention it.

A practical first step is to list your three most important priorities in order.

Next to each one, note how you know it.

If most of your answers are “I inferred it”, you need a conversation with your manager.

Ask for 30 minutes specifically about expectations, and bring questions such as:

If my first six months go really well, what will you have seen me do?
Of the things on my plate, which matters most to you right now?
How will you judge whether my work is good: speed, quality, numbers, feedback from others?
What do people new to this role often get wrong?
How would you like me to raise a problem or a disagreement with you?

Write down the answers, as close to your manager’s words as you can.

Then check the unwritten rules with one or two colleagues and, if you have one, a mentor.

Ask how decisions get made, which channels get a quick response and how disagreement is expressed.

Who should you meet, and how do you ask for help without looking lost?

Much of what you need to know in a new job sits in people’s heads.

A useful way to decide who to meet is to map your work:

Whose work does yours depend on?
Whose work depends on yours?
Who has been here a long time and knows why things are the way they are?
Who is also new, in another team?

Pick three to five people from that map and ask each for a short conversation.

A simple opening works: “I have just joined the X team and my work feeds into yours. Could we take 20 minutes so I understand what you need from us?”

Follow up with a brief thank-you and, if possible, something useful in return.

When you need help, ask specific questions with context.

Say what you are trying to do, what you have already tried, and what you need.

Compare “How does reporting work here?” with “I am preparing the monthly report and found two templates. Which one does finance use?”

The second question is just as basic.

But it shows that you have done your part.

Quiet newcomers do not need to become networkers.

Three good one-to-one conversations do more than a crowded social event you dread.

How do you ask for feedback before anyone offers it?

Susan Ashford and L.L. Cummings introduced the idea of feedback seeking.

People do not only receive feedback; they actively go and get it.

Later research by Ashford and J. Stewart Black looked at people entering organizations.

It described several proactive moves newcomers make:

seeking information
seeking feedback
building relationships
negotiating changes to their job
framing situations positively

Not all of these moves were linked to better performance or satisfaction.

So it is worth trying them deliberately and noticing which work in your setting.

To make feedback seeking practical:

Pick a specific piece of work, ideally from the last few days.
Pick the person who saw it closely, not just the most senior person available.
Ask a specific question. “Any feedback?” usually gets “All good.” “In yesterday’s client call, was my summary at the end too long?” gets something you can use.
Listen, thank them and decide what to change. You do not have to agree with everything. But arguing on the spot makes people less likely to be candid next time.

Ask your manager too, on a regular rhythm rather than only at review time.

“Is there anything you would like me to do differently in the next month?” is a fair question in week four.

What does a simple 30-60-90 day plan look like?

Michael Watkins’ book The First 90 Days is a practitioner framework for role transitions, not a research study.

Two of its ideas are useful for any new hire.

First, deliberately speed up your learning about the organization.

Second, secure a few early wins that matter to the people whose support you need.

A one-page plan can be as simple as this:

By day 30: deliver one small, finished piece of work. Learn how your team’s main process runs end to end. Meet the people your work depends on.
By day 60: take on a piece of work with less checking. Learn the numbers or measures your manager watches. Build one relationship outside your team.
By day 90: own something visible that others rely on. Know where you can add most in the next six months. Have asked your manager how your first three months looked to them.

Under each month, write one or two things to deliver, one thing to learn and one relationship to build.

Then share the plan with your manager and ask what they would change.

A good early contribution is usually small, useful and finished.

Big changes proposed in the first weeks often run into reasons that newcomers have not yet heard.

What does this look like in practice?

Three illustrative examples, composites rather than real people or case studies.

A software engineer joining from another company.

In week three she realizes she has been polishing code for days before opening a pull request.

Her team, meanwhile, ships small changes several times a day.

Nobody told her; she inferred the standard from her old job.

In the expectations conversation her manager says speed of feedback matters more than polish here.

She asks a senior colleague to review a small change the same day.

Her first contribution is a fix to a flaky test that has annoyed the team for months.

A sales representative in a hybrid team.

He hardly sees colleagues outside his own team.

Deals stall because he does not know who in legal and product to ask.

With his mentor he maps who his deals depend on.

He asks two people in legal and one in product for 20-minute calls.

He learns which contract questions legal wants in writing and which it prefers to discuss.

His 60-day goal becomes closing a deal without a legal delay, with the people he met as the route.

An internal transfer into a new team.

She has been with the company for five years but has just moved from operations into a strategy role.

She assumes she knows the culture and skips the clarifying questions.

By week six she finds the new team judges work on written analysis, not on the fast operational fixes she was praised for before.

Her mentor suggests treating the move as a new job.

She asks her new manager what a strong first analysis looks like. She also requests feedback on a draft before it goes wider.

In each case the turning point was an explicit question: to the manager, to a colleague or to a mentor.

How do you use this with your mentor?

A mentor outside your reporting line is useful in the first months.

That is precisely because they have no say in your evaluation.

You can ask the basic questions, test your reading of the culture and rehearse conversations before you have them.

A practical way to work through the first months together:

First meeting: describe your first weeks honestly. Rate, roughly, how clear your role is, how confident you feel and how connected you feel. Agree how you will work together; see how to set goals with your mentor.
Expectations: bring your list of priorities and how you know each one. Use the mentor to draft questions for your manager, then have the conversation yourself.
Network: bring your work map. Ask your mentor who you should meet and whether they can introduce you.
Feedback: bring one piece of work and the question you plan to ask about it. Rehearse it.
Plan: bring a draft 30-60-90 day plan and ask which early contribution would actually be noticed.
Review: compare your ratings with the first meeting. Decide which habits you will keep on your own.

Before each meeting, spend ten minutes on what happened since the last one and the one situation you want to work on.

How to prepare for a mentoring meeting covers this in more detail.

Questions to ask a mentor gives you more to work with.

If your organization also gives new hires a peer buddy, the onboarding buddy guide explains how the two roles differ.

Be clear about limits.

A mentor can explain how things work, open doors and help you think.

A mentor cannot change your manager’s priorities, settle a dispute about your role or decide your probation.

Use the mentor to prepare those conversations, and have them yourself.

Sources

Bauer, T. N., Bodner, T., Erdogan, B., Truxillo, D. M., & Tucker, J. S. (2007). Newcomer adjustment during organizational socialization: A meta-analytic review of antecedents, outcomes, and methods. Journal of Applied Psychology, 92(3), 707-721.
Bauer, T. N. (2010). Onboarding New Employees: Maximizing Success. SHRM Foundation Effective Practice Guidelines.
Ashford, S. J., & Cummings, L. L. (1983). Feedback as an individual resource: Personal strategies of creating information. Organizational Behavior and Human Performance, 32(3), 370-398.
Ashford, S. J., & Black, J. S. (1996). Proactivity during organizational entry: The role of desire for control. Journal of Applied Psychology, 81(2), 199-214.
Watkins, M. (2003). The First 90 Days: Critical Success Strategies for New Leaders at All Levels. Harvard Business School Press. Practice framework (practitioner book, not peer-reviewed).