Nobody remembers their 47th week at a job. Everybody remembers their first. The first week is when a new hire decides — mostly subconsciously — whether they joined a team that notices people or a company that processes them. That's why finding real ways to recognize new hires in their first week isn't onboarding fluff; it's the opening move of your entire retention strategy.
The stakes are bigger than a warm fuzzy. Gallup and Workhuman found that employees who don't feel adequately recognized are about twice as likely to say they'll quit within a year — and week one is precisely when "adequately recognized" starts getting defined. Deloitte's research ties strong recognition cultures to up to 31% lower voluntary turnover, and cultures are built one first impression at a time. So here are 20 concrete, mostly-free ways to make a new hire's first five days feel like a welcome party instead of a paperwork gauntlet. (And when the confetti settles, the same playbook extends across their whole first 90 days.)
Day One: Make the Arrival Loud
1. The public welcome post
Before their laptop finishes updating, post a welcome in your team's main channel: name, role, one fun fact, and a genuine "we fought hard to hire this person." Tag them so their first Slack notification is a pile of wave emoji, not a compliance training reminder.
2. A welcome thread everyone actually replies to
A welcome post with zero replies is worse than no post. Ask three or four teammates ahead of time to jump in with a specific hello — "I saw your talk on caching, excited to nerd out" beats a lone thumbs-up every time.
3. Recognition from the top, in writing
A two-line DM from a senior leader — "We're genuinely glad you're here, and here's why your role matters" — takes ninety seconds to send and gets screenshotted for posterity. Founders and VPs: this is the highest-ROI ninety seconds of your week.
4. The desk (or DM) surprise
Swag is fine, but personal beats expensive. A handwritten note referencing something from their interviews — "still thinking about your answer on incident retros" — proves the team was listening before day one.
5. Introduce them by their wins, not just their title
When introducing a new hire in meetings, skip "this is Sam, new backend engineer" and try "this is Sam, who scaled payments at their last gig and asked the single best question in our system design interview." You've just given recognition for things they did before they even started.
First Contributions: Catch Them Doing Something Right
6. The first-PR shoutout
The first merged pull request — even a typo fix — deserves a public cheer. It marks the moment they became a contributor instead of a guest. Same idea for first ticket closed, first support reply, first sales call, first design comment.
7. Celebrate the first great question
New hires are terrified of looking clueless. When one asks a question that exposes a gap in your docs or your thinking, say so publicly: "This is exactly the question nobody's asked in two years — fresh eyes for the win." You've just made curiosity safe for every future hire too.
8. Recognize the docs feedback
Week-one confusion is a gift: it's the only time anyone reads your onboarding docs with honest eyes. When a new hire flags something broken or fixes a stale README, thank them loudly. That's real work with compounding value.
9. Shout out the small unblocking moments
Did they sit in on a call and catch a detail everyone missed? Spot a bug while shadowing? Tiny contributions in week one feel enormous to the person making them — match your recognition to their perception, not the diff size.
10. The end-of-week "first wins" recap
On Friday, have their manager post a short list of everything the new hire actually accomplished — shipped, learned, fixed, asked. New hires consistently underestimate their own first week; a public receipt resets the story they tell themselves over the weekend.
Peer Power: Recognition That Doesn't Come From the Boss
11. Buddy props — in both directions
If you run a buddy system, make recognition part of the job: the buddy publicly recognizes the new hire's first wins, and the manager publicly recognizes the buddy for great onboarding. Buddies who get celebrated keep volunteering; buddy programs that run on guilt quietly die.
12. Have peers send the first kudos
Recognition from a manager reads as encouragement. Recognition from a peer reads as acceptance — and acceptance is what week one is really about. Nudge one or two teammates to send the new hire a specific thank-you by Wednesday. (There's a whole art to it: here's how to give kudos in Slack without it feeling forced.)
13. Give them props to give
Here's the sneaky-good one: invite the new hire to give recognition in week one, not just receive it. "Who helped you most this week? Tell them publicly." It teaches your recognition culture by participation, and it hands them a low-stakes way to make their first public post.
14. Cross-team hellos with substance
Ask adjacent teams to send one specific welcome each: "Your team is why our launch didn't slip last quarter — glad you're joining them." The new hire learns the org map through appreciation instead of an org chart PDF.
15. The recognition feed tour
If you have a public recognition channel, make scrolling it part of onboarding. Ten minutes of reading real, specific praise between real teammates teaches your values faster than any culture deck — because it's evidence, not aspiration.
Rituals and Manager Moves
16. The one-on-one that opens with recognition
First one-on-one, first agenda item: something specific they did well this week. Not "how's it going?" — that's a status check. Managers set the tone here more than anyone; Gallup pegs about 70% of the variance in team engagement to the manager, and that variance starts accruing on day one.
17. Celebrate the milestone, not just the merge
"You survived week one" deserves an actual moment — a team lunch, a goofy certificate, a dedicated shoutout. Marking small milestones early establishes that this is a team that celebrates things, which makes every later celebration feel normal instead of weird.
18. Name the courage, not just the output
Week one is full of invisible bravery: introducing yourself to strangers, admitting you don't know the acronyms, pushing code to an unfamiliar repo. Recognizing effort and courage — not just results — tells new hires what actually gets valued here.
19. Recognize the onboarding crew
The IT person who had the laptop ready, the teammate who rewrote the setup guide at 9pm, the buddy who blocked their calendar all week — recognize them publicly during the new hire's first week. It shows the newcomer that behind-the-scenes work gets seen, and it keeps your onboarding machine willingly staffed.
20. Ask them how they like to be recognized
Some people glow in public shoutouts; others want a quiet DM and would rather perish than be tagged in front of 200 people. One question — "how do you like to be appreciated?" — makes every future gesture land twice as hard. File the answer somewhere the whole team can see it.
Making It Stick Past Friday
Twenty ideas is a menu, not a mandate — pick five and do them every single time. The real risk isn't doing too little in week one; it's doing a spectacular week one and then going silent. A new hire who gets a confetti cannon on Monday and nothing for the next two months learns that the warmth was a script. Consistency is the whole game, which is why the first 90 days matter more than the first five.
The easiest way to make it consistent is to lower the cost of each gesture to near zero. That's the case for putting recognition where work already happens — and yes, full disclosure, this is the part where we mention that Propsly is ours. Propsly lives in Slack: anyone can type /props to recognize a teammate in seconds, every give lands in a public recognition feed, and the free tier covers unlimited users with 200 props per person per month. First-PR shoutouts, buddy props, and "welcome aboard" recognition all become five-second habits instead of calendar reminders. If you want the messaging itself to hit harder, steal from our peer recognition message examples.
However you do it — tool or no tool — the principle holds: the first week is when new hires learn whether being noticed is how this place works. Make sure the answer is yes, loudly, twenty different ways.