Week one onboarding
Help a new joiner feel welcome and productive, or make your own first week count.
Case study: The laptop and the silence
Harsha joined a Bengaluru team as a frontend developer. On day one he got a laptop, a Confluence link with 140 pages, and a buddy who said "ping me if you need anything" and then went to a client workshop for three days. Afraid to look slow, Harsha didn't ask, spent a week fighting a VPN setting, and pushed his first PR in week three. His friend Isha joined a team in Singapore the same month. Her buddy booked fifteen minutes every morning, introduced her to five people by name, and gave her a tiny real bug to fix on day two. She shipped it on day three.
Takeaway: A good first week is designed, not hoped for. Buddies should schedule it, and new joiners should ask early.
New joiners from Indian teams often avoid asking questions so they don't seem incapable, and buddies wait to be asked. Global teams expect lots of questions in week one, and a buddy who reaches out first.
Onboarding as buddy
Goal: Make Liam feel welcome, connected and productive, with a first small win by the end of week one.
Step by step
- Welcome and map. A warm hello and a simple plan for the week.
- Connect people. Introduce him by name to the five people he'll work with most.
- Give a first win. A small, real task he can ship in the first few days.
- Check in daily. A short, scheduled check in, not "ping me anytime".
- Normalize questions. Say clearly that questions are expected and welcome.
Say this, not that
| Welcome to the team, Liam! I'm your buddy for the first month, so I'm your shortcut for everything. | Ping me if you need anything. | New joiners rarely ping. Reach out first. |
| Here's the plan for this week: setup today, meet the team tomorrow, and a small bug to fix by Thursday. | ||
| Let me introduce you to Nisha. She owns the design system, so she's who you'll talk to most. | ||
| There are no silly questions this month. If you're stuck for more than thirty minutes, just ask me. | A clear rule removes the fear of asking. | |
| Let's do fifteen minutes every morning this week to check how it's going. | Let me know if you face any issues. | A fixed time is easier than asking for help. |
Model conversation
- You
- Welcome to the team, Liam! I'm your onboarding buddy for the first month. How was the laptop setup this morning?
- Liam
- Long, but good! Thanks. I'm excited, and a bit overwhelmed, to be honest.
- You
- Totally normal. Here's the plan: setup today, meet the team tomorrow, and a small bug for you by Thursday.
- Liam
- That sounds great. Who should I talk to about the design system?
- You
- Nisha. I'll introduce you at lunch. She's lovely and she knows every component.
- Liam
- Perfect. And is it okay to ask lots of basic questions?
- You
- Please do. If you're stuck for more than thirty minutes, ask me. That's the rule.
- Liam
- Love that. Thanks, this makes it much easier.
Being the new joiner
Goal: Get set up fast, build a few real relationships, and ship something small in your first week.
Step by step
- Ask early. Questions are cheapest in week one. Ask them now.
- Clarify expectations. Ask what success looks like in thirty, sixty and ninety days.
- Meet people. Ask for short intro calls with key people, and ask about their work.
- Show progress. Share what you've done and what you're stuck on, briefly.
Say this, not that
| Thanks for being my buddy. Could you tell me what a good first month looks like here? | ||
| I've been stuck on the VPN setup for about thirty minutes. Could you point me in the right direction? | Sorry to disturb, small doubt. | No need to apologize. Be specific about what you tried. |
| Who are the three or four people I should get to know first? | ||
| Would you have fifteen minutes this week for a quick intro? I'd love to understand what your team works on. | I'll just observe for some weeks. | Relationships built early make everything easier later. |
| Quick update: my environment is set up, and I've started on the date picker bug. | Visible progress builds trust fast. |
Model conversation
- Wei Ling
- Hi! Welcome. I'm Wei Ling, I'll be your buddy. How's day one going?
- You
- Thanks, Wei Ling! It's going well. Could you tell me what a good first month looks like here?
- Wei Ling
- Sure. Get set up, ship a couple of small fixes, and get to know the team. No pressure on big features yet.
- You
- That's helpful. I've been stuck on the VPN setup for about thirty minutes. I tried the wiki steps but the certificate fails.
- Wei Ling
- Ah, that wiki is outdated. You need the new certificate from IT. I'll send you the link.
- You
- Thank you! Also, who are the three or four people I should get to know first?
- Wei Ling
- Raj for the backend APIs, Hana in product, and Chris in QA. I'll set up intros.
- You
- That would be great. I'll send you a quick update tomorrow on how the setup goes.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.