How do you recognise work that nobody sees?

Describe the problem that did not happen and connect it to the person who prevented it. Behind-the-scenes work has no launch to celebrate, so the message has to name the outage that never occurred or the review that found nothing, and say whose work that was.

Why does behind-the-scenes work go unrecognised?

Because success looks like nothing. A renewed certificate, a fixed flaky test and a sorted queue are all invisible when they work. Recognition follows visible events, so the people doing invisible work wait a long time for it.

Should behind-the-scenes recognition be public?

Always. The problem with this kind of work is exactly that nobody saw it, and a private thank you leaves that unchanged. A public message tells the team the work exists and that it counts.

What kinds of work count as behind the scenes?

Maintenance, preparation, prevention and administration: dependency upgrades, meeting prep, expiring certificates renewed early, vendor contracts renegotiated. Anything whose success is measured by what did not happen.

How often should you recognise it?

Whenever you notice a problem you have stopped having. That is usually the trace behind-the-scenes work leaves, and it is worth asking who made it disappear.

Recognition messages

Recognising Behind-the-Scenes Work: 10 Messages

The best work in most companies is invisible because it worked. Recognising it means describing the problem that never arrived.

Success looks like nothing

A certificate renewed on a Sunday, one flaky test fixed in April, the inbound queue that arrives sorted every morning. All of it worked, so none of it produced an event, and recognition follows events.

The people doing this work are usually aware of the gap. They can see the launch announcements for things that broke twice, and the silence around the thing that never broke.

Describe the problem that never arrived

Prevention cannot be recognised the way a launch can, because there is nothing to point at. The message has to supply the event: the outage that did not happen, a review with nothing to say, an hour a week everybody got back.

Then say whose work that was, in a channel where the people who benefited can read it.

10 messages you can send

Thank you for the dependency upgrades, Ravi. Nobody noticed, which is the point, and the security review had nothing to say for the first time in three years.
Manager, on maintenance
Uses the absence of findings as the evidence.
Thanks for prepping the board deck data every quarter. The meeting runs on numbers that are simply correct, and nobody in the room knows how much work that word covers.
Leader, on preparation
Names the gap between what the audience sees and what it took.
You rewrote the onboarding docs in your own time and the last three new starters were productive in week one. Nobody connected those two things, so I am.
Manager, on documentation
Draws the causal line the rest of the team missed.
Thank you for the flaky test you fixed in April. I checked: the pipeline has not failed for a false reason since. That saved every one of us an hour a week.
Peer, on a fix
A checked fact and a quantified effect.
Thanks for the pre-meeting messages you send to make sure everyone arrives knowing the decision to be made. Our meetings are half the length of other teams’ and this is why.
Peer, on facilitation
Recognises an invisible habit by naming its measurable result.
You spotted the certificate expiring on a Sunday and renewed it before anybody was paged. The outage that did not happen was ours to thank you for.
Manager, on prevention
Describes the incident that never occurred, which is the only way prevention can be recognised.
Thank you for triaging the inbound queue every morning before standup. The rest of us start the day with a sorted list and had assumed it arrived that way.
Peer, on routine
Admits the assumption, which is the honest part.
Thanks for keeping the staging environment working. It is the least visible job on the team and every demo this quarter depended on it.
Manager, on infrastructure
States the dependency plainly.
You spent a week making the export faster and the customer who complained about it has stopped writing to us. That silence was expensive to buy and worth it.
Peer, on a quiet result
Frames silence as the outcome.
Thank you for the vendor renewals you handled in the background this year. The contract we did not overpay for is the one you renegotiated in the summer.
Leader, on administration
Recognises an administrative save with the specific example.

What makes one land

Describe the problem that never happened. Prevention has no event to point at, so the message has to supply one: the outage that did not occur, the review that had nothing to say.
Check a fact before you send. “The pipeline has not failed for a false reason since April” is a claim the reader can verify, and that is what separates it from a nice thought.
Name the dependency. Demos, board meetings and clean pipelines all rest on somebody’s unseen work, and saying so out loud is the recognition.
Admit what you had assumed. “I thought the queue arrived sorted” is a small confession that makes the thank you honest.
Say it in public, because the whole problem is that nobody saw it. A private thank you leaves the work exactly as invisible as it was.

Questions people ask

How do you recognise work that nobody sees?: Describe the problem that did not happen and connect it to the person who prevented it. Behind-the-scenes work has no launch to celebrate, so the message has to name the outage that never occurred or the review that found nothing, and say whose work that was.
Why does behind-the-scenes work go unrecognised?: Because success looks like nothing. A renewed certificate, a fixed flaky test and a sorted queue are all invisible when they work. Recognition follows visible events, so the people doing invisible work wait a long time for it.
Should behind-the-scenes recognition be public?: Always. The problem with this kind of work is exactly that nobody saw it, and a private thank you leaves that unchanged. A public message tells the team the work exists and that it counts.
What kinds of work count as behind the scenes?: Maintenance, preparation, prevention and administration: dependency upgrades, meeting prep, expiring certificates renewed early, vendor contracts renegotiated. Anything whose success is measured by what did not happen.
How often should you recognise it?: Whenever you notice a problem you have stopped having. That is usually the trace behind-the-scenes work leaves, and it is worth asking who made it disappear.