How do you recognise attention to detail?

Describe what was caught and what would have happened otherwise. Precision produces a non-event, so the message has to supply the version where nobody noticed. A number helps more than an adjective.

Why does this kind of work go unrecognised?

Because it succeeds by producing nothing. A bug caught in review leaves no incident, no customer complaint and no ticket, so the only trace it leaves is whatever somebody chooses to write about it.

Is “great attention to detail” a good thing to say?

It is review language, and it is interchangeable between people. The specific catch, and what it would have cost, does the same job and could only have been written about one person.

How do you recognise quality work that nobody owns?

Name the lack of ownership. Translations, error copy and accessibility usually sit outside anybody’s remit, and the person maintaining them is volunteering, which is worth saying out loud.

Should you recognise someone who was right when you were wrong?

It is the most credible version of this message. Conceding a specific disagreement proves the praise is about the work rather than about being encouraging.

Recognition messages

Recognising Attention to Detail: 10 Messages

Catching a mistake before it ships produces nothing to point at, which is why the people who do it most often hear about it least.

A catch leaves no evidence

A bug found in review produces no incident. Catching a typo before send means there is no apology email, and spotting a contradiction in a spec saves a month nobody will ever count.

All of that is success, and all of it is indistinguishable from nothing having happened. The only record is a person deciding to describe it.

Say what would have shipped

The difference between a forgettable thank-you and one people remember is usually the counterfactual.

“Thanks for the careful review” is polite. “You checked the unsubscribe link before we sent to forty thousand people, and it was broken” is a story somebody will retell.

10 messages you can send

You caught the off-by-one in the invoice rounding. Across a year that was about eleven thousand pounds, in the customer’s favour and then ours.
Manager, with a number
Quantifying it makes the catch undeniable.
Thanks for reading the contract properly. The auto-renewal clause was not what we had been told it was.
Peer, on diligence
Specific document, specific finding.
Sofia found the typo in the migration that would have dropped a column. It was one character.
Manager, near miss
The scale contrast is the whole message.
Thank you for checking the numbers in my deck before I presented them. One of them was wrong and it was the one on the title slide.
Peer, saved from embarrassment
Honest about the personal stake.
You are the reason the German translations are not embarrassing. Nobody else was checking them.
Manager, on unowned quality
Names work with no owner.
Thanks for noticing the alt text was missing on the new pages. Twelve of them. You just fixed them rather than filing tickets.
Peer, on accessibility
The second sentence is the compliment.
Tom read the whole spec and found the paragraph that contradicted the one before it. We would have built both.
Manager, on reading properly
Describes the concrete consequence avoided.
Thank you for the pixel-level review. I disagreed with three of your points and you were right about all three.
Peer, on design detail
The concession makes the praise real.
You checked the unsubscribe link before we sent to forty thousand people. It was broken.
Manager, near miss
One sentence, no adjectives needed.
Thanks for asking what happens if the list is empty. It was the only case we had not handled and it was going to happen on day one.
Peer, on edge cases
Precise about which case and why it mattered.

What makes one land

Quantify the catch where you can. “About eleven thousand pounds” turns a proofreading note into a business outcome.
Name the near miss plainly. A message that says what would have shipped is more memorable than one praising thoroughness.
Thank the fix as well as the find. Somebody who corrects twelve pages rather than filing twelve tickets has done the harder half.
Recognise unowned quality. Translations, alt text and error messages usually belong to nobody, and the person maintaining them chose to.
Avoid making it sound like a job description. “Great attention to detail” is review language; describing the specific catch is not.

Questions people ask

How do you recognise attention to detail?: Describe what was caught and what would have happened otherwise. Precision produces a non-event, so the message has to supply the version where nobody noticed. A number helps more than an adjective.
Why does this kind of work go unrecognised?: Because it succeeds by producing nothing. A bug caught in review leaves no incident, no customer complaint and no ticket, so the only trace it leaves is whatever somebody chooses to write about it.
Is “great attention to detail” a good thing to say?: It is review language, and it is interchangeable between people. The specific catch, and what it would have cost, does the same job and could only have been written about one person.
How do you recognise quality work that nobody owns?: Name the lack of ownership. Translations, error copy and accessibility usually sit outside anybody’s remit, and the person maintaining them is volunteering, which is worth saying out loud.
Should you recognise someone who was right when you were wrong?: It is the most credible version of this message. Conceding a specific disagreement proves the praise is about the work rather than about being encouraging.