Skip to content

Saying thank you at work: a simple routine for recognising good work in a small team

6 min read
Operations
Saying thank you at work: a simple routine for recognising good work in a small team

Key Takeaways

  • 1In a small team, recognition happens by accident, so it reaches the same visible people and misses quiet, steady work
  • 2A routine needs one owner, one fixed weekly slot of five minutes and a place where it is written down
  • 3Good thanks names the specific thing done and the effect it had, not just 'great job'
  • 4One line per thank-you in a shared note shows who has not been mentioned for months
  • 5Say it to the person first and in public only if they are comfortable with that

A colleague stays late to fix a delivery that was about to go wrong. The customer is happy, the manager is relieved, and everybody moves on to the next job. Nobody says anything. A month later the same colleague quietly starts looking at other offers, and the manager is surprised.

In a team of five to fifteen people this is the usual pattern. Nobody decides to withhold thanks. It simply depends on someone remembering at the right moment, and in a busy week nobody does. This article describes a very small routine that makes recognition regular without turning it into an HR programme.

Why it goes wrong without a routine

Recognition left to chance has three predictable problems:

  • It follows visibility. The person who closed the big deal gets thanked. The person who kept the invoices correct or answered the same customer question patiently for the tenth time does not, because nobody sees that work.
  • It follows the manager's memory. What happened on Monday is forgotten by Friday. What happened last month is gone.
  • It is vague. "Thanks for your help" is pleasant but tells the person nothing about what to repeat.

None of this needs a bonus scheme. It needs a habit that does not rely on good intentions.

The routine in four parts

1. One owner

Pick one person who is responsible for the routine, usually the owner or team lead. The owner does not have to do all the thanking; they make sure it happens. If it is everybody's job, it is nobody's. Name a deputy for holidays.

2. One fixed slot

Put five minutes in the calendar once a week, for example Friday at 15:00 or at the end of the weekly team meeting (see a thirty-minute weekly team meeting). In the slot the owner asks one question: "Who did something this week that made our work easier or better for a customer?"

Everyone can answer, not only the owner. Colleagues often see good work the manager misses, especially work between two people, such as a handover that went smoothly.

3. Specific words

Good thanks has three pieces, and it fits in two sentences:

  1. What the person did. "You called the customer before the deadline and told them about the delay."
  2. What it changed. "They were not surprised, and they agreed to the new date without complaint."
  3. Optionally, what you want to see again. "Please keep doing that."

Compare this with "good job on the customer thing". The first version tells the person that their judgement was noticed. The second only tells them that you were in a good mood.

Say the thanks directly to the person, in person or in a short personal message. Mention it in front of the team only if you know the person is comfortable with it. Some people are happy to be named; others find it embarrassing. Ask once, when you start, and remember the answer.

4. One line of record

After the slot, the owner writes one line per thank-you in a shared note: date, person, what they did. For example: "23 Oct, Anna, warned the customer about the delay before the deadline."

This takes a minute and gives you two things. First, you can see at a glance who has not been mentioned for two or three months, which usually means their work is invisible rather than absent. Second, the note is useful material for one-to-one meetings and for the retrospective after a project, where you can refer to concrete things instead of general impressions.

What to avoid

  • Thanking only results. If you only recognise outcomes, people learn to hide risks and take credit. Also thank the person who found a problem early, or who said "I am not sure this will work".
  • Rotating a fake "employee of the month". In a small team everybody knows the rotation is artificial, and it feels worse than saying nothing.
  • Mixing thanks with criticism. Do not use "great, but" in the same sentence. Give the correction separately, at another time.
  • Tying thanks to money by default. A bonus is a separate decision. A sincere, specific sentence costs nothing and is often remembered longer.
  • Overdoing it. If the same phrase is used for everything, it stops meaning anything. It is better to thank two things a week properly than ten things in passing.

Where AI can help, and where it should not

An AI assistant can help the owner with the boring part: it can turn your rough notes from the week into a tidy list or remind you who has not been mentioned recently. It should not write the thanks itself. People notice quickly when a message is generic, and the entire value comes from the fact that someone paid attention. Keep the observation human; use tools only for the record.

What to do this week

  1. Choose the owner and a deputy, and put a five-minute slot in the calendar.
  2. Create a shared note with three columns: date, person, what they did.
  3. In the first slot, ask the question and write down every answer, even small ones.
  4. Thank at least two people directly, with the three pieces: what, effect, and what to keep doing.
  5. After a month, look at the note. If someone has no lines, ask yourself what they have been doing, and then ask them.

If after a month the routine feels forced, shorten it, but keep the note. The note is what makes the habit survive a busy week.

Share this article

Need expert guidance?

Let's discuss how our experience can help solve your biggest challenges.