A structured first-90-days plan you can fill in and hand to a new hire before day one, plus a conversation script for walking them through it. Copy either piece on its own, or both.
Fill in the blanks with your own team's details before sending it. A plan with real names and real dates lands completely differently than a generic welcome email.
Here's how your first 90 days are structured, a mix of self-directed learning and working closely with the team, so you're picking up real context from the people who already have it, not just reading docs alone. We'll check in at a few set points along the way, not to grade you, just to make sure we're aligned on goals and progress and that nothing's slipping through the cracks. Your questions and feedback are part of how this gets better, ask them.
| When | What happens |
|---|---|
| Day One | Start the onboarding plan, get familiar with your surroundings, plan your week ahead. |
| Week One | Establish goals for the next 30 and 90 days, together. |
| 30-Day | [fill in] |
| 90-Day | [fill in] |
[Goal 1]
[Goal 2]
You'll be paired with an onboarding buddy, [Name]. They're your go-to partner for anything related to [company] as you navigate your first few days, weeks, months, or quarters. Between me and [Name], you've got someone to ask no matter what the question is.
| Week | Person | Role | Topics |
|---|---|---|---|
| 1 | |||
| 1 | |||
| 1 | |||
| 2 | |||
| 2 |
| Day | Schedule |
|---|---|
| Monday | 9:00 to 12:00 computer setup and account access. 12:00 team launch meeting. |
| Tuesday | Meet the team: 1:1s scheduled with key people, e.g. 9:30 and 10:00. |
| Wednesday | [fill in] |
| Thursday | [fill in] |
| Friday | 1:00 to 5:00 review materials and on-demand training. |
Knowledge base · Company goals · How the company started · Go-to tools ([e.g. project tracker, docs, intranet, HR system])
Use this as a starting point, not something to read verbatim. Say it in your own words, but keep the order and the directness.
"I'm really glad you're here. Before you touch anything, let's walk through what your first week looks like, who you'll meet, and what we actually expect from you right now. Nothing here is a test, it's just so you're not guessing."
Say this before they open a single tool or ticket. A new hire's first hour sets the tone for the whole first month, if it starts with a login screen and a task list, that's the message they absorb. If it starts with a person taking the time to orient them, that's a different message entirely.
"For your first two weeks, your only job is to learn, not to produce. That means asking more questions than feels comfortable, if something seems obvious and you're still not sure, ask anyway. Week one is about getting oriented: computer setup, meeting the team, understanding how we work. By the end of week one, we'll sit down and set your 30 and 90 day goals together, so nothing about what's expected of you is a guess."
Removes the pressure to perform before they have context. Most new hires quietly assume they should already be contributing by day three, and that pressure is what keeps them from asking the question that would've saved them an hour of confusion.
"You'll be paired with an onboarding buddy, [Name]. They're your go-to for anything that feels too small to bring to me, where's the good coffee, what does this acronym mean, is it normal that this meeting runs long. Between me and [Name], you've got someone to ask no matter what the question is. You'll also be meeting a handful of other people over the first two weeks, I'll walk you through who and why, so every meeting has a purpose instead of just being another name on the calendar."
New hires ask peers things they won't ask managers. That's not a flaw in the system, it's the reason the system needs both. Name the buddy specifically, don't just gesture at "the team."
"We'll check in at a few key points, day one, end of week one, 30 days, and 90 days. At each one, we're making sure we're aligned on your goals and progress, and giving you support along the way. None of these are pass or fail moments, they're just built-in points to make sure nothing's slipping through the cracks, for either of us."
Lay out the shape of the first 90 days so they're not wondering when the next evaluation is coming. Naming the checkpoints up front turns them from something to dread into something expected.
"Let's plan on a quick Friday check-in for your first month, just what's clicking, what's confusing, what you need more of. If you show up with a list of things you're still unsure about, that's not a bad sign, that's exactly what these are for."
Normalizes confusion as expected, not a failure. Without this, a new hire's instinct is to hide what they don't understand until it becomes a real problem. With it, confusion becomes something they bring to you on schedule, before it turns into something bigger.
Their onboarding buddy's name, confirmed in advance, not decided on the spot. The week-one schedule, who they're meeting and why, so you can explain the purpose behind each name on the calendar. A 30- and 90-day goal framework, even in rough form, so week one's goal-setting conversation isn't starting from a blank page. Team goals, so they understand what they're stepping into, not just their individual role. Where the resources live, knowledge base, company goals, key tools, so you're pointing them somewhere real instead of promising to send a link later.