How do you recognise remote employees?

In writing and in public. In an office a good deal of recognition happens by being overheard, and remotely that channel does not exist, so anything not deliberately written down reaches nobody.

Why is recognition more important for remote teams?

Because the ambient signals are gone. Somebody working hard in an office is visible by being there. Remotely the only evidence of effort is output plus whatever people say about it, which makes silence read as invisibility.

What remote work goes unnoticed most often?

Social maintenance and timezone cost. The person who keeps the weekly call going, or who always takes the 7am one so somebody else does not have to, is doing something real that appears nowhere.

Should remote recognition be public?

Almost always. A DM reaches the recipient; the same message in a channel also tells everyone else what gets noticed here, and in a distributed team that is one of the few culture signals available.

How do you spot work worth recognising when you cannot see people?

Look at what is written. Clear updates, decisions recorded with reasoning, answers given in public channels and handovers that work across timezones are all visible in the artefacts, and all of them are choices.

Recognition messages

Recognising Remote Employees: 10 Message Examples

In an office, half of recognition is overheard. Remotely nothing is overheard, so anything unsaid stays unknown.

Nothing is overheard

An office leaks information. Somebody handles a difficult call within earshot. It is obvious who stayed late. A colleague explains something patiently for the third time and two people hear it.

Remotely none of that reaches anyone. The only things visible are the artefacts and whatever people deliberately say, which means recognition stops being a courtesy and becomes the primary mechanism by which effort is known about.

Write it in a channel

A DM does one job. The same sentence in a public channel does two: it thanks the person, and it tells a distributed team what this company notices.

For a team that never shares a room, that second job is one of the only culture signals available.

10 messages you can send

Thank you for the written updates. I know exactly what happened this week without having asked, which is not true of everyone.
Manager, on writing
Comparative without naming anyone.
You answer questions in the channel rather than in DMs, which means four other people learn the answer too. That is a deliberate choice and I noticed it.
Peer, on working in the open
Explains the mechanism, so it can be copied.
Thanks for turning the meeting into a document. Three timezones read it properly instead of one timezone attending it badly.
Manager, async
Concrete about the benefit.
Ines has been the first reply to every new starter’s question in #general this quarter. Remotely that is the difference between settling in and floundering.
Manager, onboarding
Says why it matters more remotely.
Thank you for the loom instead of the meeting. I watched it at 1.5x at a time that suited me and understood it fine.
Peer, dry
Small joke, real point.
You noticed I had gone quiet and checked in. That is much harder to spot remotely and you spotted it.
Peer, on attention
Credits difficulty explicitly.
Thanks for writing decisions down with the reasoning. Six months later I could tell why we did it, which almost never survives a remote team.
Manager, on decision records
A durable benefit, dated.
Marek keeps the handover notes so tight that Europe picks up from Australia without a call. Neither half sees the other work.
Manager, follow-the-sun
Describes the invisible interface.
Thank you for saying in the standup that you were stuck. It is easier to hide remotely and you did not.
Peer, on visibility
Recognises honesty that is easy to avoid.
You have run the same fifteen-minute weekly call for a year and it is the only reason this team feels like a team.
Manager, on ritual
Credits maintenance of something social.

What makes one land

Write it down. Remote recognition that happens in a call is heard by whoever attended and nobody else.
Put it in a public channel. A DM reaches one person; the same words in a channel tell everybody else what the team values.
Recognise working in the open. Answering in a channel rather than a DM costs nothing and teaches four other people, and it is a deliberate habit.
Notice the social maintenance. Somebody keeping a remote team feeling like a team is doing real work that appears on no plan.
Be specific about timezone cost. Somebody taking the awkward call every week is absorbing something the rest of the team is not.

Questions people ask

How do you recognise remote employees?: In writing and in public. In an office a good deal of recognition happens by being overheard, and remotely that channel does not exist, so anything not deliberately written down reaches nobody.
Why is recognition more important for remote teams?: Because the ambient signals are gone. Somebody working hard in an office is visible by being there. Remotely the only evidence of effort is output plus whatever people say about it, which makes silence read as invisibility.
What remote work goes unnoticed most often?: Social maintenance and timezone cost. The person who keeps the weekly call going, or who always takes the 7am one so somebody else does not have to, is doing something real that appears nowhere.
Should remote recognition be public?: Almost always. A DM reaches the recipient; the same message in a channel also tells everyone else what gets noticed here, and in a distributed team that is one of the few culture signals available.
How do you spot work worth recognising when you cannot see people?: Look at what is written. Clear updates, decisions recorded with reasoning, answers given in public channels and handovers that work across timezones are all visible in the artefacts, and all of them are choices.