Working with others

Name everyone behind a shared win

A micro habit for sharing credit in public, so the whole team sees who made the win happen

When shared work lands, post a short note in the team channel naming each person who helped and what they did.

5 minutes
You and your team
Whenever a shared win lands
Quick

Why this can work

Naming each person's specific part in front of the team puts their work where people who didn't see it can. Checking first with anyone who dislikes the spotlight keeps the credit from becoming a burden.

One way to do it

How to give credit to your team in public

You’ll come away with a short team post that says who did what.

Think of everyone who contributed.
Not just the obvious names. Think about who reviewed, tested, unblocked, covered, or answered a question at the right moment.
Check with anyone who might not want the spotlight.
Some people find public praise uncomfortable, and in some teams being singled out is awkward. A quick private message lets them say so.
You“I'd like to thank you by name in the team channel for your part in this. Would you be comfortable with that?”
Post it, one line per person.
Give each person their own line, with what they did and what it made possible. If you led the work, you don't need a line of your own.
To: your team channel
The win is out, and it took a lot of people to get it there.
Name what they did, which what it made possible.
Name what they did, which what it made possible.
Thank you, all of you.
Swap the highlighted parts for your thing. Works on Slack, in email, or said out loud.
Tip: Post it the same day or the next. A thank-you a month later reads as an afterthought.

Good times to repeat it: when a shared project shipsat the end of a quarterafter someone rescues a deadline

Making it work for you

Every workplace is different. Here’s what to think about before you start, and what might get in the way.

Things to think about

People notice who's named first and who gets a full sentence rather than a name in a list. A specific line for each person avoids an accidental ranking.

What might make this harder

Ask someone else on the project to read your list before you post. If you do miss someone, add them in a reply, by name, with their part.

Questions people ask

How do you give credit to your team publicly?

Name each person and the specific thing they did, in the channel your team reads, soon after the win. Check first with anyone who might dislike the attention.

Is it better to praise someone in public or in private?

Both have a place. Private thanks tells someone what their help meant to you; public credit shows everyone else who did the work. Some people prefer private, so it's worth asking.

How do you recognize coworkers without leaving anyone out?

Think through everyone who touched the work, including reviewers and people who unblocked it, and go stage by stage rather than from memory.

The longer read

Why this works, and where it comes from

When something ships, credit flows toward whoever is most visible: the person who announces it, presents it, or leads the team. Usually nobody decides this. It's just where attention goes. Credit follows whoever tells the story, so telling it well is one of the few ways to give credit away.

For the people you name, public credit does something a private thank-you can't. It tells people outside their immediate circle what they're good at, and that can shape who asks them onto the next project or who remembers them at review time. For someone who dislikes the spotlight, the same post can feel like an ordeal, or in some teams cost them a little with their peers. That's why the quick private check comes first.

Giving shout-outs in a team channel is a familiar habit in many workplaces. The small differences here are one line per person, with what each person's part made possible, and asking before you name anyone who'd rather you didn't. A line of names reads like a guest list. A line per person reads like a map of who to go to for what.

Hold the public post back in two situations. If the project ended painfully for someone, a reorganization, a person moved off it, a public celebration can reopen that, so thank people privately instead. A team-wide post can also undersell the person who carried most of the work; for them, say plainly what they did, or tell their manager directly.

Other simple things to consider

Celebrate a small win with your teamFive minutes a week to show your team the ground it covered5 minMake time Make someone's good work visibleTwo minutes that can change how a manager sees their own team5 minConversation

What to do next

Close out a project out loudtie up the loose ends10 minQuick Look back on a project in twenty minuteslearn from how it went20 minConversation

More in Working with others

A few minutes that compound

Do it with Truest and it goes on your permanent record, in a Career Vault your employer doesn’t own.

See how Truest works

Lands in your closeoutFriday's closeout asks for progress, priorities, and proud moments; this is one.
On your recordWhen it's done, it goes on your record with your priorities and progress.
A reminder beforePut it on your calendar and Truest reminds you before it starts.

Read this alongside your role page

Tell Truest what you’re dealing with

We read every one, and we write guides for the things that come up most. Leave your email if you’d like to hear when we do.

An exercise written by Truest, based on our experience. Last updated September 25, 2026. We sell a career membership; where that’s relevant above, we say so.