Why it matters
In many teams only the presenter gets public credit, which quietly teaches that visibility matters more than contribution. Naming a specific action and the person it helped makes the less visible work — the fix, the handover, the quiet support — part of the team’s shared story.
How to run it
- Use an existing moment. A few minutes at a weekly meeting, at the same point each time.
- Name the action. One person describes something specific a colleague did — not "great job", but what they actually did.
- Name who it helped. A customer, a colleague, another team — and why it mattered.
- Rotate the storyteller so recognition comes from different voices.
- Watch the range. The Keeper notes which kinds of work get named; if it's always the same people or the same kind of work, widen the lens.
From the free playbook: Operationalising Rituals Using the Büdaya Framework — with the canvas, pilot plan and review signals to run it well.
Watch out for
- The same people get recognised — deliberately look for less visible contributions
- Vague praise — always name the specific action and why it mattered
When not to use it
Don’t tie participation or being named to performance ratings or promotion — it turns appreciation into a competition.
