An end-of-year exchange with no shopping, no spending limit and no secret. Everyone brings one genuinely useful thing they learned this year — a technique, a shortcut, a mistake worth not repeating — and gives it to a randomly assigned colleague, who then has to use it.
What it is good for
- RecognitionMaking good work visible to people other than the manager.
- Trust & safetyLowering the cost of admitting a mistake or asking for help.
- Cross-team networkingConnecting people who would otherwise never share a meeting.
- InclusionDesigning participation so the loudest voice does not set the pace.
What you need
- A shared document or a pile of cards
The run sheet
Ask for the thing a week ahead (prep)
One paragraph, written down. Specific and usable: 'how I stopped losing track of follow-ups' beats 'be more organised'.
Assign recipients randomly (prep)
Each person's contribution is assigned to one colleague. Send it to them privately before the session so they arrive having read it.
Recipients present, not authors (20 min)
The recipient explains what they were given and who gave it. This is the twist that makes it work — it forces people to actually read and understand it, and it is far easier to praise someone else's idea than your own.
Authors add one sentence (10 min)
The author gets one sentence of correction or addition. One. It keeps them honest and keeps it moving.
Collect them all into one document (5 min)
The whole set, published. For most teams this is the most-read internal document of the quarter.
Facilitator notes
- This is the one to reach for when you want an end-of-year thing that does not assume a holiday, a budget, or anyone's beliefs.
- Recipients-present is the critical design choice. Reverse it and you get a round of people underselling their own ideas.
- Ask people to commit to actually trying the thing they were given, and check back in a month. About a third will have.
Debrief questions
Ask these immediately afterwards, not next week. Fifteen minutes of these is what turns the activity into something the team refers back to — see the debrief guide.
- What were you given that you will genuinely use?
- Was anything given that more of us should know?
Variations
Mistake edition
The thing you learned must come from something that went wrong. Harder, better, and only for teams with the trust to carry it.
Cross-team edition
Assignments cross team boundaries entirely. Slower to present, much better for breaking down 'what do they even do over there'.
Access and inclusion
Written contributions submitted in advance mean nobody has to improvise, and the published document makes the whole session available to anyone who could not attend.
Running it remotely
Entirely remote-native. Collect in a form, assign by script, present on a call with the document shared.