An appreciation post is a short, specific, public or semi-public message – shared on LinkedIn, Slack, Teams, or email – that recognises an individual or team for a concrete contribution, achievement, or behaviour, with enough detail that the person named and the audience reading it both know exactly what is being recognised and why it matters.
In this guide
- LinkedIn Appreciation Post Templates
- Slack and Teams Shout-Out and Appreciation Examples
- Email Appreciation Messages
- Public Recognition Platform Messages
- What Makes an Appreciation Post Effective?
- How Profit.co Makes Recognition Consistent at Scale
- Frequently Asked Questions
LinkedIn Appreciation Post Templates
Individual Achievement
I want to take a moment to recognise [First Name] [Last Name], [Title] at [Company].
[First Name] [specific achievement – what they did, in one sentence. Quantify where possible: “reduced customer onboarding time by 30%”, “closed our largest enterprise contract of the year”, “shipped a product feature that was 18 months in the making”].
What made this remarkable wasn’t just the outcome – it was [the specific way they worked: the problem-solving approach, how they treated people along the way, the quiet persistence that others didn’t see].
We’re lucky to have you on this team, [First Name].
#EmployeeAppreciation #TeamRecognition #[CompanyName]
Manager Appreciation (Posted by a Team Member)
Not everyone gets to work for a manager who [specific behaviour – e.g., “actually reads your work before feedback meetings”, “goes to bat for the team when it’s uncomfortable”, “credits the team publicly and absorbs blame privately”].
I do. That’s [Manager Name], [Title] at [Company].
This year, [manager’s specific action or decision that made a difference – one to two sentences].
Appreciate you, [First Name]. Thank you for leading the way you do.
#LeadershipAppreciation #ManagementMatters #[CompanyName]
Team Achievement (Posted by Manager or Leader)
Our [Team Name] team just [specific team achievement – “shipped X”, “hit X milestone”, “closed out the quarter at Y% of target”].
What I want the world to see is what it took to get there: [2-3 sentences about the challenge, the effort, the choices the team made that weren’t easy].
This is what great teams look like from the inside. I am proud of every one of you.
[Tag individual contributors if appropriate: @Name1 @Name2 @Name3]
#TeamAppreciation #ProudLeader #[CompanyName]
Peer Appreciation (Individual to Individual)
I’ve worked alongside [First Name] for [X months/years], and I want to say publicly: [what you appreciate about working with them – specific, behavioural, tied to a real moment].
Earlier this [month/quarter], [brief description of a specific moment or contribution].
You make the work better, [First Name]. Thank you.
#PeerRecognition #Gratitude #[CompanyName]
Work Anniversary Appreciation
Today marks [X] years of [First Name] [Last Name] at [Company].
In that time, [First Name] [two to three specific accomplishments or milestones – not a CV summary, real moments].
What [X] years here actually looks like: [one sentence about how the company or team is different because of them].
Here’s to many more.
#WorkAnniversary #EmployeeAppreciation #[CompanyName]
New Employee Welcome Appreciation
Thrilled to officially welcome [First Name] [Last Name] to the [Company] team.
[First Name] joins us as [Title] on the [Team]. [He/She/They] bring[s] [specific background – not a resume bullet, a real skill or experience that’s relevant: “a decade of experience building B2B sales teams from scratch”, “deep expertise in logistics operations across Southeast Asia”].
We asked [First Name] why [Company]. [He/She/They] said: “[Quote – one sentence, real language].”
Welcome, [First Name]. Can’t wait to see what you build with us.
#NewHire #Welcome #[CompanyName]
Farewell Appreciation (When a Colleague Leaves)
Today’s the last day for [First Name] [Last Name] at [Company].
[First Name] [specific contribution or achievement during their tenure – be concrete].
The thing I’ll remember most: [one genuine, humanising observation – a habit, a quality, a moment].
Wherever you land next, [First Name], you’ll make it better. Best of luck.
#Farewell #ThankYou #[CompanyName]
Client Appreciation Post
One of the things that doesn’t show up on the revenue charts: clients who make the work better.
[Client First Name] [Client Last Name] at [Client Company] is one of those.
[2 sentences on what the working relationship looks like – their engagement, their trust, the quality of challenges they bring that push the team to produce better work.]
Thank you for [X years] of partnership, [First Name]. We build better because of you.
#ClientAppreciation #Partnership #[CompanyName]
Volunteer and Community Recognition
Outside of [Company], [First Name] [Last Name] [specific volunteer role or community contribution – e.g., “coaches an under-15 football team”, “runs a coding workshop for teenagers in her neighbourhood”, “volunteers with a food bank every Saturday morning”].
We think who someone is outside of work says something about who they are at work. [First Name]’s commitment to [cause/community] is part of what they bring here.
Thank you for making the world around you a little better, [First Name].
#CommunityImpact #EmployeeAppreciation #[CompanyName]
Values in Action
We talk about [Company Value – e.g., “Ownership” / “Customer First” / “Continuous Improvement”] a lot. [First Name] [Last Name] lives it.
This [month/quarter]: [specific action that exemplifies the value – 2 sentences. What was the situation, what did [First Name] do, and what was the outcome?]
This is what our values look like in practice. Thank you, [First Name].
#[CompanyValue] #EmployeeAppreciation #[CompanyName]
Product Launch Team Recognition
We shipped [Product/Feature Name] last [week/month].
The person who [specific role in the launch – e.g., “held the whole release together”, “rebuilt the backend architecture under a six-week deadline”, “handled every stakeholder question so the team could focus on building”]: [First Name] [Last Name], [Title].
[2 sentences on the specific contribution and why it mattered to the launch.]
Launches like this don’t happen by accident. Thank you, [First Name].
#ProductLaunch #EmployeeRecognition #[CompanyName]
Slack and Teams Shout-Out and Appreciation Examples
Internal recognition moves faster and feels more immediate on Slack and Teams. Keep it short – under 100 words. Tag the person directly.
Standard Kudos Post
Shout out to @[FirstName]
[Specific thing they did – one to two sentences, concrete and real.]
This kind of work doesn’t always get seen. Wanted to make sure it does.
Drop a reaction if you’ve had the pleasure of working with @[FirstName].
Staff Shout-Out Templates
Post these in your #kudos, #recognition, or #shoutouts channel. Keep them under 75 words – specific, warm, and direct.
Staff shout-out: @[FirstName]
[First Name] just [specific thing they did – one sentence. Make it concrete: not “they were helpful” but exactly what they did and why it mattered].
This is the kind of work that makes the whole team better. Thank you, [First Name].
Peer-to-Peer Quick Recognition
Big thank you to @[FirstName] for [specific action – e.g., “stepping in to cover the client call on zero notice”, “staying online until midnight to get the release out”, “writing documentation that actually made sense”].
Really appreciated it.
Manager Recognition of Team Member
@[FirstName] – I want to call out what you did with [specific project/task/situation] this week.
[Two to three sentences: what happened, what [FirstName] did, why it mattered.]
This is exactly the kind of work that makes this team what it is. Thank you.
Kudos to the Team – Group Recognition Post
Want to take 30 seconds to recognise the entire [Team/Project Name] team.
[What they accomplished – specific, one sentence.]
This was a hard thing to pull off. You all made it look easier than it was.
@[Name1] @[Name2] @[Name3] and everyone who touched this – thank you.
Cross-Functional Appreciation
Wanted to cross-post some appreciation for the [Other Team Name] team – specifically @[FirstName] and @[SecondName].
We needed [specific support/deliverable] and they [what they did – made time, moved fast, got it right].
Collaborating with a team this reliable makes everything easier. Thank you both.
Milestone Recognition
Today is @[FirstName]’s [X]-year work anniversary at [Company].
[One thing they’ve contributed that the team would feel if it disappeared tomorrow.]
We’re glad you’re here, [FirstName].
End-of-Sprint Appreciation
Sprint [number] is done.
Before we move on: @[FirstName] – [specific contribution this sprint that might otherwise go unnoticed: e.g., “your retro notes were the clearest we’ve had in months”, “you unblocked the [feature] integration at exactly the right time”, “you reviewed three PRs while shipping your own work”].
Sprint wins are team wins. This one has your fingerprints on it. Thank you.
Email Appreciation Messages
Email appreciation works best for formal milestones, large-team recognition, or when you want a permanent record of the recognition.
Employee of the Month Email (HR/People Team Send)
Subject: [Company] Employee Recognition – [Month] Spotlight: [First Name] [Last Name]
Hi team,
Each month, we recognise a team member whose contribution stands out.
This [month]’s recognition goes to [First Name] [Last Name], [Title] on the [Team] team.
What [First Name] did:
[Specific achievement – 3-4 sentences. Use real project names. Include a number or outcome where possible.]
In [First Name]’s own words:
“[Employee quote – sourced directly, not paraphrased. Should sound like a person, not a press release.]”
Congratulations, [First Name]. Thank you for the standard you set.
– [HR / People Team / CEO Name]
Manager Appreciation Email (Individual to Manager)
Subject: Thank you – [specific project or period, e.g., “Q2 product launch” / “my first year here”]
[Manager Name],
I’ve been meaning to say this properly: thank you for [specific thing – how you handled X, what you did during Y, the conversation you had with me about Z].
[Two to three sentences about the specific impact it had on the writer’s work, confidence, or direction.]
I don’t say this enough. Wanted to say it now.
[Your name]
Year-End Team Appreciation Email
Subject: The [Team Name] team – a note before the year closes
Team,
Before [Year] closes, I want to be specific about what this year was.
[3-5 concrete things the team accomplished – one sentence each. Not “great collaboration.” Real outputs: “We shipped X”, “We grew Y by Z%”, “We navigated [specific challenge] without losing a single client”.]
What made this year different was [one honest observation about how the team worked – the trust, the decision-making, the way people stepped up in hard moments].
Thank you – genuinely – for the year you brought.
[Your name/signature]
Peer-Nominated Recognition Email (HR/People Team Send)
Subject: A nomination came in for [First Name] – here’s what their colleague said
Hi team,
This month’s recognition started with a nomination from one of [First Name]’s colleagues. Here’s what they wrote:
“[Verbatim or near-verbatim peer nomination – 3-5 sentences. Keep the original voice. Do not edit for polish. Peer-sourced recognition is credible precisely because it sounds like a person, not an announcement.]”
We don’t think we can say it better than that.
Congratulations, [First Name] [Last Name] – [Title], [Team].
Want to nominate a colleague? [Nomination form link]
– [HR / People Team]
Promotion Announcement with Recognition
Subject: [First Name] has been promoted to [New Title]
Hi all,
I’m glad to share that [First Name] [Last Name] has been promoted to [New Title], effective [date].
[First Name] joined [Company] as [original title] [X years ago]. In that time, [2-3 sentences on concrete contributions – what they built, what they led, what changed because of their work. Use real project names, not tenure language].
This promotion reflects what we want to reward: [the specific quality or behaviour that made it clear – not seniority, but the thing they consistently did].
Congratulations, [First Name].
[Sender name / Title]
Team Milestone All-Staff Email
Subject: The [Team Name] team hit [Milestone] – here’s what it took
Hi [Company/Team],
On [date], the [Team Name] team hit [specific milestone – “$1M ARR”, “100 enterprise accounts”, “1,000 onboarded customers”, “Q3 target at 112%”].
What got them there:
- [Specific initiative or decision – one sentence]
- [Specific obstacle they overcame – one sentence]
- [One thing the team did that wasn’t obvious from the outside – one sentence]
[Final line: one honest sentence about what this milestone means – not “exciting times ahead” but what it actually unlocks or proves.]
Thank you to the [Team Name] team. You earned this.
[Sender name / Title]
Public Recognition Platform Messages
For Profit.co’s recognition module or similar platforms, keep messages under 150 words and always tie to a value or OKR category. Profit.co’s employee engagement module lets you tag recognition by company value and link it to the key result the employee owns – so kudos given today are visible as evidence in the next performance review. See how Profit.co connects recognition to goal performance.
Value-Tied Recognition
Recognised for: [Company Value – e.g., “Customer First” / “Ownership” / “Collaboration”]
@[FirstName] – what you did with [specific project] this [week/month] exemplifies exactly what [Company Value] means in practice.
[Two to three sentences on the specific action and its impact.]
Thank you for setting the standard.
OKR-Linked Recognition
@[FirstName] just hit [specific milestone on their key result – e.g., “85% complete on the API documentation project”, “closed the 10th enterprise account this quarter”].
This directly moves our [Objective name]. Big moment.
Well done.
Peer-to-Peer Platform Recognition
Peer Recognition
@[FirstName] – I want to put this on record, not just say it in passing.
[2-3 sentences on the specific thing they did and its impact. Use real project names and real outcomes where possible.]
Thank you for making this team better at what it does.
Manager-to-Report Platform Recognition
Manager Recognition
@[FirstName] – logging this here so it exists somewhere more permanent than a Slack message.
This [week/month], you [specific achievement or behaviour – one concrete sentence with a real outcome].
That’s the standard. Thank you for setting it.
Cross-Functional Platform Shout-Out
Cross-Functional Shout-Out
For anyone who doesn’t work directly with @[FirstName] on the [Team] team: they [specific thing they did that crossed team lines – solved a problem for another team, unblocked a critical dependency, shared a resource or skill that helped a project land].
Cross-functional support this good is easy to miss. Didn’t want to miss it.
Public Milestone Celebration
Milestone Moment
@[FirstName] just hit [specific milestone – “1 year at [Company]”, “closed their 50th deal”, “shipped their 100th PR”, “trained their 25th new hire”].
One of those milestones that’s easy to pass without noticing. We noticed.
Here’s to the next one.
What Makes an Appreciation Post Effective?
The key word in any appreciation post is specific: a post that names what someone did – not just that they “did great work” – is the one that lands, gets shared, and makes the recipient feel genuinely seen rather than managed. Before the templates: one rule that separates recognition that resonates from recognition that feels performative.
Specificity is everything. “Great work this quarter!” is noise. “James built our entire API documentation from scratch in three weeks so the customer success team could onboard enterprise accounts without engineering support” is recognition.
An effective appreciation post answers:
- Who is being recognised
- What specifically they did
- Why it mattered – to the team, the customer, or the company
- Optional: one humanising detail or direct quote
Keep it under 200 words for social. Under 100 words for internal channels.
Weak vs. Strong Appreciation Post – At a Glance
| Dimension | Weak Appreciation Post | Strong Appreciation Post |
|---|---|---|
| Specificity | “Great job this quarter!” | “Kavya closed the company’s largest enterprise deal – $180K ARR – in her second month on the team.” |
| What | Vague (“she was really helpful”) | Specific action (“stepped in to rebuild the QA process two days before launch”) |
| Why it mattered | Not mentioned | Included (“which meant the release shipped clean and the client renewed on time”) |
| Length | Over 300 words or under 20 | 80-200 words for LinkedIn; 30-80 words for Slack |
| Tone | Corporate (“We are pleased to recognise…”) | Human (“You made the hard thing look easy.”) |
| Timing | Weeks or months after the achievement | Within 1-2 weeks of the moment |
How Profit.co Makes Recognition Consistent at Scale
The problem with appreciation posts is not that people don’t want to give recognition – it is that when recognition is informal and untracked, it defaults to the loudest voices, the most visible roles, and the most recent wins. Quieter contributors, cross-functional supporters, and long-tenured employees get overlooked.
Profit.co’s recognition tools connect appreciation directly to the OKR and performance system:
- Tie recognition to key results – see who is contributing to which objectives, and recognise based on real progress
- Log peer and manager kudos in the same platform as performance check-ins, so recognition history is visible at review time
- Set recognition cadences – weekly, bi-weekly, or monthly prompts to ensure recognition doesn’t only happen when someone thinks to do it
- Company value tags – categorise every recognition post against the company value it exemplifies, so patterns are visible in aggregate
Make Recognition Consistent at Scale with Profit.co
Frequently Asked Questions
An appreciation post is a short, specific, public or semi-public message shared on LinkedIn, Slack, Teams, or email that recognises an individual or team for a concrete contribution, achievement, or behaviour. The distinguishing characteristic is specificity: an effective appreciation post names exactly what the person did and why it mattered, rather than offering generic praise like “great work this quarter.”
Every effective appreciation post answers four questions: who is being recognised (name, role, team), what specifically they did (a concrete action, not a general description), why it mattered (the impact on the team, customer, or company), and optionally one humanising detail or direct quote. Posts that skip the “what” and “why” read as performative rather than genuine, and are less likely to be shared or remembered by the recipient.
It depends on the audience and the occasion. LinkedIn is strongest for employer branding and external visibility (promotions, milestones, new hires, client appreciation). Slack or Teams is better for immediate, in-the-moment recognition that reaches the team directly. Email works best for formal milestones, large-team recognition, or when a permanent record matters. Public recognition platforms like Profit.co’s engagement module are best when you want recognition tied directly to goals and visible at performance review time.
For LinkedIn, 80-200 words is the effective range – long enough to include a specific achievement and why it mattered, short enough to be read in full. For Slack and Teams, 30-80 words. For email, 150-300 words depending on the occasion. Posts over 300 words on social tend to lose readers before the key point lands; posts under 20 words typically lack the specificity that makes recognition meaningful.
An appreciation post recognises a specific achievement or moment – it is reactive, triggered by something the person did, and can be written and posted in minutes. An employee spotlight is a structured, scheduled piece of content that profiles a team member comprehensively (their role, background, a recent win, and a humanising detail) as part of a recurring program. Appreciation posts are immediate and occasion-driven; spotlights are planned and program-driven. Most teams benefit from doing both.
Consistency requires structure, not just intention. Without a system, recognition defaults to the loudest voices, the most visible roles, and the most recent wins – leaving quieter contributors, cross-functional supporters, and long-tenured employees overlooked. The fixes are: set a recognition cadence (weekly or bi-weekly prompts), tie recognition to OKR progress so it is grounded in real work, use a platform that logs kudos and makes recognition history visible at review time, and rotate who is recognised to ensure every team and level gets visibility across the year.
Related reading: Employee Shout Out Examples: 50+ Messages for Every Occasion
Related reading: Employee Spotlight Social Media Templates: LinkedIn, Slack and Email
Related reading: Employee Appreciation Week: Ideas, Messages and Planning Guide