Most people think of onboarding as something a company does to you. You turn up, someone hands you a laptop and a week of welcome sessions tells you how things work. For a lot of new hires, it doesn’t go that way. Gallup finds that only 12% of employees strongly agree their organization does a great job onboarding new employees. So if your first week was mostly logins and forms, you’re far from alone and you haven’t done anything wrong.
This post is for individual contributors, meaning people whose job is their own work rather than running a team. It shows you how to run your own onboarding in your first 30 days. You’ll agree a target with your manager in week one and send it back in writing, then work out how work really gets done, finish one small thing and meet the people you need to learn from. All of it works when the company’s onboarding is thin, and it still helps when the onboarding is good.
Why do you have to run your own onboarding?
Company onboarding usually covers the things a company can hand out in bulk. That means accounts, forms, the org chart and a few introductions. Those matter, but they aren’t what you need to do the job. The job itself needs you to know what your role is for, what good looks like and how decisions get made here. These are the parts that rarely get written down, because they live in people’s heads.
Research on new employees points the same way. A meta-analysis led by Talya Bauer pulled together 70 samples of newcomers to see why some people settle into a new job better than others. Three things stood out: people did better when they knew what their role was, felt able to do it and felt accepted by the people around them. Seeking out information was one of the ways newcomers got there. The review shows a link rather than proof that asking questions causes success, but it does tell you where to aim.
An earlier study by Susan Ashford and Stewart Black looked at the moves newcomers make on their own, which included asking for information and feedback and building a relationship with the boss. So a new hire who goes looking for answers is following a well-documented pattern, and that isn’t pushy or a personality quirk.
If your main problem right now is feeling behind or out of place, start with our guide to imposter syndrome at a new job. This post is about the work itself. If you manage people, the 90-day leadership plan for new managers will fit you better. For the bigger picture of building a career on your own work, see our guide to growing your career without becoming a manager.
What should you settle with your manager in the first week?
Your manager is the one person whose idea of good decides how your first months are judged. You may never see that idea written down, but it’s there and your work will be measured against it. So the most useful thing you can do in week one is find out what it is.
New hires often skip this conversation, either because they assume the answer is obvious or because they worry that asking will make them look unprepared. Your manager hired you for a reason, so they usually have a picture of what they want, even if it’s rough. Asking about it shows you’re taking the job seriously, and it gives you the role clarity that Bauer’s review tied to settling in well. Getting this conversation right is a skill of its own, usually called expectation setting.
What to cover
Start with what the role is for. Every job exists to solve some problem, and it helps to know which one. Ask why the job was opened now, too. A role created because a team is drowning in requests is different from one created for a new project, even when the job description reads the same. The answer tells you which work counts most when everything looks urgent.
Next, ask what good looks like at day 30 and at day 90. You want your manager’s picture here, not a template you fill in alone, because their idea of a successful first month is what you’ll be judged against at the end of it. Ask for something concrete enough that you could both tell whether it happened. “Getting up to speed” is hard to check, while “running the weekly report without help” is easy.
The third topic is how they like updates. Some managers want a short written note every Friday, while others would rather hear it live in a weekly meeting. Some want every detail and some only want to know when something is off track. Treat this as a preference to learn rather than a deal to negotiate, since you’re finding out how this person takes in information so that your updates actually get read.
The fourth topic is scope. Ask which decisions you can make on your own, which ones you should check first and which ones belong to someone else entirely. New people tend to get this wrong in both directions: some ask permission for everything, and others change things that weren’t theirs to change. Knowing where the lines sit lets you move quickly inside them. Our post on knowing how far to go without being asked covers how to judge that over time.
Last, ask who else needs to be consulted or kept informed about your work. Almost every role has someone whose agreement matters even though they aren’t your boss, such as a team lead next door or a finance partner who signs off spending. If your manager names them in week one, you won’t find out the hard way in week five.
Why you send it back in writing
A conversation feels clear while you’re having it, but a week later each of you remembers it a little differently. A short written note fixes that, because it turns the conversation into a record you can both look at, and it brings out differences while they’re still cheap to sort out. Say your manager meant the day-30 goal to be about clearing a backlog, but you heard “build a dashboard.” The note shows that now instead of at the end of the month.
Keep the note short, with a few lines on each of the five topics in your own words, and send it the same day or the next while the conversation is fresh. Ask your manager to correct anything you got wrong rather than asking them to approve it. Approval feels like a formal sign-off, so busy managers put it off. A correction takes them thirty seconds.
If nothing comes back, send one short follow-up a few days later. If that gets no reply either, carry on and say so. A line like “I’ll work from this unless you tell me otherwise” is enough. Keep the note somewhere you can find it, because you’ll need it again at the end of the month.
A note that was only half answered
“What would you need to see from me by the end of the month to know this is working?” Dana asked her manager that on her third day as a data analyst at a logistics company. Dana is an illustrative example, not a real person.
Her manager had a quick answer for day 30: he wanted her to take over the weekly on-time delivery report from a colleague who was leaving, and to be running it without help by the end of the month. That was specific, so Dana put it in her note and he confirmed it the next morning.
Day 90 was harder. He talked about “getting more out of the data” and maybe a forecasting model, but he couldn’t say who the model was for or when it was needed. Dana wrote down what he’d said and marked it as open, because she didn’t want to invent a target just to make the note look complete. So at the end of her first month, only half of the note had a clear answer. The report was running and her manager knew it. The day-90 line was still a question, and it became the main item for her day-30 check-in.
When your manager says to just settle in first
The most common obstacle is time. Your manager may say they’re slammed this week, or tell you to just get settled in first. That’s usually meant kindly, but it leaves you guessing. You don’t need one long meeting to cover all five topics. Ask one or two at the end of a meeting you’re already in and another in a chat message, then send the note anyway with the gaps marked so they can fill them in when they have a minute. A written note asks less of a busy person than a meeting does. Our guide to managing up picks up the relationship from there.
How do you find out how work actually gets done here?
Every company has an official way of getting work done and a real one. The org chart and the wiki show you the official version, but you have to work out the real one by watching. The table below is our own method for doing that, not a research finding.
| What to find out | How to find out | Sign it’s stale or unwritten |
|---|---|---|
| Who actually decides | Watch whose view ends a discussion. Ask who would need to be happy with a piece of work. | The approver on paper signs whatever one other person has already agreed. |
| Which docs and tools are real | Notice what colleagues link to in chat when someone asks a question. Check last-edited dates. | The official page hasn’t been touched in a year and nobody links to it. |
| The unwritten rules | Watch how fast people reply and where decisions land. Notice how people disagree and who gets copied in. | People follow the rule but can’t point to it anywhere. |
| How work moves from start to done | Follow one piece of work from the first request to the finished result. | Steps happen that aren’t in any process document. |
Watch more than you change for the first two weeks. You’ll see things that look slow or odd. Some of them really are odd, but others exist for a reason nobody has told you yet. The only way to tell them apart is to wait.
Keep private running notes as you go, writing down who answered which question, which documents people actually opened and anything that surprised you. The notes are only for you, so be honest in them.
Also find one peer you trust and ask what a new person wouldn’t know to ask. It’s easier to answer than “what should I know?” because it points at gaps rather than at everything. This is the kind of information seeking that both Bauer’s review and Ashford and Black describe, though neither of them tested this particular method.
You’ll learn the most when your own work has to pass through the real process, which is one reason the first deliverable matters as much as it does.
What makes a good first deliverable at a new job?
A good first deliverable is small and real. Small means you can finish it in a few days or a couple of weeks. Real means it goes through the same approvals and tools as everyone else’s work, so you learn the route by walking it. It should be agreed with your manager as part of the week-one note so you both know it’s what you’re aiming at, and it should be visible to at least one person beyond your manager. Ideally it depends on someone else’s input as well, which gives you a working reason to meet them.
We didn’t find any study that tests whether a small first deliverable improves how a new job goes, so the case for it is practitioner craft. Our reasoning is simple. An ambitious first project often fails before you know how things work here, and when it does you can’t tell whether the idea was wrong or you just didn’t know the process. A small project that finishes teaches you the process and leaves you with something done.
Here are a few illustrative examples. A finance analyst might rebuild one recurring report and write down its steps along the way. A marketer might change one existing web page and take it through the real review route. Someone in support could rewrite one outdated help article that customers keep asking about. Each one is modest but shows you who signs off, where the files live and how long things really take.
When you hand the work over, say what it changed rather than just what you did. Our guide on how to communicate your impact at work covers how to word that.
Who should you meet in your first month, and what should you ask each?
Most advice about meeting people in a new job is about being liked. That’s no bad thing, but it isn’t the best way to decide who to meet first. Choose by what you need to learn instead, so each meeting has a question it’s there to answer.
Start with the person whose decisions shape your work most, if that isn’t your manager. It might be a product lead who sets priorities or a director who approves budgets. Learn what they’re trying to achieve this year, and ask what they wish the person in your role did more of.
Next, meet the people on either side of your work. One hands you your inputs and another receives what you produce. Ask the second person what tends to go wrong when the work reaches them, because their answer often tells you more about what quality means here than any guide does.
A peer in a similar role can show you the practical side, so ask how they plan their week and which meetings they’d skip if they could. Someone who joined one or two years ago is useful in a different way, because they still remember being new and know what has changed since. Ask what they wish they’d known in their first month.
Finally, find someone outside your team who sees the work from another side. That might be a customer-facing colleague or someone in a function that depends on yours. Ask what your team is known for, both good and bad.
At the end of each meeting, ask who else you should talk to. Keep a simple list of who you met, what you learned and anything you promised to send. These meetings run on curiosity more than charm, because the questions are what make them useful.
There’s a good reason to be deliberate about this. A study by Yu, Yang, Lindley and Wan followed more than 10,000 people who joined one large technology company in early 2022. Their networks kept growing through the first six months. Even so, at the end of that time they still looked different from the networks of long-serving colleagues. People in roles that didn’t need much contact with others were at a disadvantage. That was one company during the pandemic, in a remote and hybrid workplace. But it suggests that a network doesn’t build itself just because you’ve been somewhere a while.
When does this not work?
Some managers can’t or won’t define day 30 or day 90, either because they are new themselves or because the role was opened before anyone decided what it was for. If that happens, draft your own version and send it as the note. If they don’t correct it, treat that as soft agreement and keep the note as your record. This is a second best. A target your manager never really agreed to can be swapped out later, and you may not get much warning.
Sometimes what you hear doesn’t add up. Your manager says the role is about one thing, the team acts as if it’s about another and the job description says a third. That tells you something about the job itself, so write down what each person said and take it to the day-30 check-in.
Remote and hybrid work make watching slower. You can’t see how a decision got made if it happened on a call you weren’t on. The Yu study looked at exactly that kind of setting, so plan to ask more direct questions because watching won’t show you as much.
Not every proactive move pays off, either. Ashford and Black found that only some of the tactics newcomers used were linked to better performance and satisfaction, and their data came from people reporting on themselves. So the honest claim is that this approach leaves you better informed. It can’t promise a better outcome.
No study has tested this four-part method as a whole. Each part rests on qualitative research or on practitioner craft, and we’ve said which is which. If by day 30 nobody can tell you what your role is for, nothing in this post will fix that.
What should the day-30 check-in cover?
Book the day-30 check-in when you send the week-one note, so it’s in the calendar before the month fills up. Bring the note with you, because the meeting runs on it.
Go through what you agreed in week one and compare it with what happened. Bring the deliverable or a link to it and say briefly what it changed. Share what you’ve learned about how work gets done here, keeping it to processes and patterns rather than people so it doesn’t sound like gossip. Finally, ask what should change for day 90 and update the note with the answer.
A check-in without the note tends to become a chat about how you’re settling in, with both of you relying on memory. The note gives you a written target to hold the month up against. Dana’s open day-90 line shows how that works. She had marked it as open in week one, so she knew exactly what to ask at the check-in.
After day 30 the note becomes a working document between you and your manager. Keeping that going is the ongoing work of managing up, which is a bigger subject than your first month.
Can an AI coach help you through the first month?
Some of this is easier to rehearse than to make up on the spot. Merlin, Risely’s AI coach, runs natively in Slack and Microsoft Teams. If your new job runs on either one, you can practice inside the tools you already use there. Before the week-one conversation, tell Merlin what you know about the role and ask it to play a busy manager. You’ll see which of your five topics gets the vaguest answer.
You can also use it to work out who to meet and what to ask each person, and near the end of the month it can help you debrief what you’ve learned before the check-in. Merlin doesn’t know your company, your manager or your role. What you get out depends on what you tell it.
Risely users see an average 26% skill improvement in 12 weeks. If your first proper conversation with your new manager is this week, rehearse it with Merlin first.