Recognition That Lands: Telling Colleagues' Stories

Recognition at work lands when it is specific, true and told as a story: what the person did, what it took, and what changed because of it. A named moment, shared in a way the person is comfortable with, does more for connection than any generic "great job" or monthly award.

Why so much recognition slides past people

Leaders often tell me, with some frustration, that they do recognise their people. There are awards. There are shout-outs in the town hall. There is a thank-you channel. And still, when I sit with teams, I hear the same quiet sentence: "Nobody really sees what I do." I hear it from teams in Abu Dhabi, who work with me online, as much as from the teams I sit with in person in Dubai.

Both things are true. The recognition exists, and it is not landing. Usually for one of these reasons:

• It is generic. "Thanks for all your hard work" could be said to anyone, so it feels as if it was said to no one.
• It praises the result only. The number is celebrated. The person behind the number stays invisible.
• It follows visibility. The people who present get thanked. The people who prepared, checked and fixed do not.
• It arrives late and in a batch. By the end of the quarter, the moment has gone cold.

Here is a simple test. If your message could be copied and sent to a different colleague without changing a word, it is not recognition yet. It is politeness.

What a story does that a thank-you cannot

A story has a person in it, a moment, a difficulty and a change. When you tell a colleague's story, you prove that you were paying attention. That proof is the real gift.

Stories also do three things that a thank-you cannot:

• They travel. People repeat a good story at lunch. Nobody repeats "well done, team".
• They teach. A story shows what this team values in practice, far more clearly than a list of values on a wall.
• They give people words. Many colleagues, especially the quieter ones, struggle to describe what they are good at. Hearing it described by someone else gives them language they can keep.

And a story honours the whole person, not only their output. It says: I saw the choice you made, not just the file you sent.

The four parts of a recognition story

You do not need to be a natural storyteller. You need four short parts, and most stories take under a minute to tell.

1. The moment. When and where did this happen? Name the day, the meeting, the project.
2. The choice. What did the person do that they did not have to do?
3. The cost. What did it take from them? Effort, courage, time, a difficult conversation.
4. The ripple. What changed for someone else because of it?

To see the shape, compare two versions of the same thanks. The first: "Thanks to the finance team for closing the month." The second, as an illustration: "On Thursday, when the supplier file arrived full of errors, Sara went through it line by line and rang the supplier herself instead of sending it back. It meant operations could release payments on time, and our smaller vendors were paid before the weekend."

The second version takes twenty seconds longer. It is the one the person will remember, and the one the rest of the room will learn from.

Where to find the stories

The hard part is not telling. It is noticing. Most of the best work in a team happens where nobody is looking, so you have to go and look.

• Ask better questions. In one-to-ones, ask "Who made your week easier?" and "What nearly went wrong, and who caught it?"
• Keep a running note. A simple list on your phone with a name, a date and one line. Memory fades within days. Notes do not.
• Look at the invisible work. Onboarding a new joiner, staying calm on a tense call, translating between two departments that do not understand each other, tidying a shared file so the next person can use it.
• Invite colleagues to bring them. Peers see things managers never will. A story told by a colleague often means more than one told by the boss.

Once you start collecting, you will be surprised at how many stories there are, and at who appears in them.

Recognition at work in a multicultural team

In Dubai and across the region, a single team may bring together many nationalities, languages and ideas about what respectful praise looks like. One colleague glows when thanked in front of the whole company. Another would rather disappear under the table.

So the story is only half of the work. The other half is how you deliver it.

• Ask first. "I would like to share what you did on Thursday with the team. Are you comfortable with that?" The question itself is a form of recognition.
• Offer more than one stage. A private note, a small team huddle, a wider meeting. Let the person choose.
• Keep personal details theirs. If the story touches on family or life outside the office, it belongs to them. Share only what they have agreed to.
• Use plain language. When English is a second or third language for many in the room, simple words carry the feeling better than clever ones.
• Share the credit accurately. In many cultures, being singled out above the group is uncomfortable. Name the others who contributed.

Small rituals that keep the stories coming

One beautiful story at the annual gathering changes very little. A small, steady habit changes the feel of a team.

• One story to open the weekly meeting. A single minute, and a different person tells it each week.
• The written note. Four sentences, one for each part of the story. People keep these for years.
• The story log. A shared page where anyone can add a line about a colleague, read out once a month.
• Leaders go first. When senior people tell specific stories about junior colleagues, everyone else learns that this is how things are done here.

Choose one ritual, not four. Keep it small enough that it survives a busy month.

Four mistakes that make it feel hollow

• Exaggerating. If the story is bigger than the truth, the person feels embarrassed and the team stops trusting the stories.
• Telling the same people's stories. Check your note every month. Who has not appeared yet?
• Attaching a request. Praise followed at once by "so could you also take on" is not recognition. It is negotiation.
• Glorifying overwork. If every story is about late nights and cancelled weekends, you teach the team that exhaustion is the price of being seen. Tell stories about judgement, care and craft instead.

Start with one story this week

Teams in Abu Dhabi and across the region join this work with me online, and the in-person sessions are held in Dubai.

Think of one colleague whose work you have quietly relied on this month. Write the four parts, ask how they would like to hear it, and tell it. Then notice what shifts in the room. If you would like to build this kind of attention into the way your whole organisation connects, explore Unmute, my corporate wellness work on emotional connection inside teams, and see whether it fits your people.