Skip to content
Recognition, culture and milestones

Peer-to-Peer Recognition on Video: How to Start a Programme

By Ryan Wells 4 min read Updated 2 October 2026

TL;DR — Peer recognition sees things managers miss, but most programmes stall within a few months because nominating takes too long or feels performative. This guide covers how to set one up around short video messages instead of forms, plus a rollout checklist for the first month.

  • Peers notice different things than managers do — the quiet help, not just the visible output.
  • A nomination form adds friction that kills participation; a short video removes most of it.
  • Launch with a narrow scope and a short pilot, not a company-wide rollout on day one.
On this page
01

Why peer recognition matters alongside manager recognition

A manager sees outcomes and meetings. A peer sees the version of someone's work a manager never does: who stayed late to help without being asked, who explained the same thing patiently for the third time, who caught a mistake quietly before it became a problem. None of that shows up in a one-to-one, and all of it shapes how a team actually feels to work in.

The gap is that most peer recognition programmes are built as forms: pick a name from a dropdown, write a sentence, submit. Forms are quick to build and slow to use, and usage is the only thing that matters here.

02

Why video works better than a nomination form

A video message takes about the same time to record as it takes to type a good sentence into a form, but it carries tone a form cannot, and recording it feels less like admin and more like actually telling someone something. Teams that switch from a text-based nomination system to a short video link tend to see more use, not because people suddenly have more to say, but because saying it takes less effort.

03

Rollout checklist for the first month

  • Pick one team or department to pilot with, not the whole company at once.
  • Write one simple prompt: "thank a colleague for something specific they did this week."
  • Share a single link in the team's existing channel — do not ask people to install anything new.
  • Tell people explicitly that messages can be private to the recipient, not just public.
  • Set a loose cadence (weekly reminder, no strict deadline) rather than a quota anyone has to hit.
  • After two to three weeks, ask the pilot group what felt easy and what felt like friction.
  • Fix the friction before expanding to a second team.
  • Share one or two examples (with permission) to show the rest of the company what a good message looks like.
04

Common reasons programmes stall

Most peer recognition efforts die from one of three causes: the process takes too long for how small the moment usually is, leadership stops modelling it after the first month, or every message ends up public and some people stop participating because they would rather keep it private. Address all three up front rather than discovering them after the pilot.

05

Connecting peer recognition to bigger moments

A peer programme also gives a natural source of contributors for bigger occasions — a promotion video, for instance, often works better built from the same peers who already have a habit of sending short recognition messages. See Promotion and Congratulations Videos: Templates for Managers for pulling that together.

In practice

How to do this in Whoosh

Set up a standing recognition link for the pilot team, with a simple prompt and the option to keep a message private to the recipient. No form, no account for the sender to create — just the link and the prompt.

Start free

Frequently asked questions

Should peer recognition be public or private by default?

Give the sender the choice each time rather than forcing one or the other — some recognition is meant to be shared, and some is meant for one person.

How do we stop the programme becoming a popularity contest?

Keep the prompt specific ("what did they do") rather than open ("who do you appreciate") — specificity keeps the focus on actions, not general likeability.

What size team should we pilot with?

A single team of ten to twenty people is usually enough to learn what works before expanding further.

Does leadership need to participate for this to work?

Not to lead every message, but visibly using the system themselves in the first month matters for getting others to try it.

Sources

Related reading

See it in action