Blog

All articles

How to Review a Recognition Feed for Under-Recognized Work

Review the recognition feed for what it misses, not just what it celebrates. Build a repeatable routine that surfaces quiet contributors, checks the signal behind the praise, and turns gaps into specific action.

How to Review a Recognition Feed for Under-Recognized Work

Review the feed like a transcript, not a scoreboard

A recognition feed is chronological by design. It shows who was thanked, for what, and against which value. That makes it useful. It does not make it complete. Under-recognized work is usually quiet, repetitive, and easy to absorb into "that's just how the team runs." The review is where you make it visible.

In Wudd, every Recognition Feed entry is tagged to a Company Value and carries a weight and timestamp. Those structured details give you something to review beyond the message text. Read the feed as a record of what your team noticed, then ask what it missed.

Define under-recognized before you look

Under-recognized does not mean never recognized. It means valuable work that appears less often than its impact warrants. A single missed thank-you is not a pattern. Four to six weeks of quiet contribution is.

Look for work that is:

  • Essential but unglamorous: maintenance, testing, documentation, scheduling, cleanup.
  • Coordinating rather than owning: handoffs, unblocking, cross-team follow-up.
  • Invisible by role or shift: support, operations, remote colleagues, people who work outside the main meeting hours.
  • Successful because nothing went wrong: risk prevention, quality checks, calm fixes.

Set a fixed review rhythm

Put the review on the calendar. Twenty minutes every two weeks is enough for many teams; a smaller team may need less. Before you open the feed, have three things ready: your team roster, the current priorities, and the actions from the last review. Then read the feed from oldest to newest and take notes. Do not start with the loudest entries.

1. Check coverage before volume

Make a list of everyone on the team. Mark who appears in the feed and who does not. Absence is a question, not a verdict. Someone may have been away, changed roles, or delivered work that is hard to see. But a person who appears nowhere across several cycles deserves a closer look. So does the person with one generic thank-you and a quarter of critical behind-the-scenes work.

Contrast coverage with contribution, not with popularity. The feed is not a leaderboard for who is liked most. It is a map of where recognition is landing.

2. Read value tags against strategy

Group entries by Company Value. If almost every recognition lands under one value, that is a signal. It may mean the team has a narrow definition of good work. It may also mean your strategy language is not showing up in daily recognition.

Wudd calculates culture KPIs from recognition activity: an Innovation Rate from Innovation tags over a rolling 30 days, a Cross-Team Collaboration Index from collaboration tags that cross department boundaries, and an Integrity Signal from Integrity and Ownership tag volume. The rollups run nightly. Review the trend, not a single morning's number. Then ask whether the work you value most is actually being tagged.

3. Look at the edges, not the center

Under-recognized work often happens between teams. Look for recognition that crosses a department boundary. Look at who gives it, too. If someone is only recognized by their manager, their peer visibility may be thin. If a person is always the one recognizing others and rarely on the receiving side, that is worth noticing.

Wudd's Cross-Team Collaboration Index is built from collaboration tags that cross department lines. Use it as a prompt: who is bridging silos in real work? Are they named in the feed, or only in the project update?

4. Account for weights and caps

Recognition systems use weights and caps to keep the signal honest. Wudd applies weights and per-giver, per-receiver caps server-side. A cap prevents one enthusiastic colleague from flooding the feed. It also means the feed is not a complete count of every good act. Once a cap is reached, later work may not appear in the same way.

Do not treat a capped feed as a performance record. The underlying record keeps the giver, receiver, Company Value tag, weight, and timestamp. Use that detail to understand the pattern. If a high contributor disappears from the feed after a burst of recognition, check whether the cap explains it before you assume the work stopped.

5. Test every gap against the work

For each person who looks under-recognized, ask five questions:

  1. What did they deliver?
  2. Who benefited?
  3. Which Company Value does it map to?
  4. Was the work visible outside their immediate team?
  5. Did timing, shift, or role make it easy to miss?

Then check with a peer or manager who saw the work. Recognition data is one signal, not a performance rating. The goal is to explain the gap, not to assign blame for it.

6. Turn the gap into a specific action

Do not end the review with a vague instruction to recognize more. That produces generic praise. Make each action concrete:

  • Send a specific recognition now, naming the work and the outcome.
  • Ask a peer who saw the work to send it, so the signal is not manager-only.
  • Share the work in the place where the team already talks, so it becomes visible.
  • Add a standing item to your team meeting: one contribution that was easy to miss.
  • If the same role is always invisible, review how work is assigned and reported, not just how it is thanked.

In Wudd, recognition can be sent from a thread with a slash command or the wizard, so the thank-you lands where the work is discussed. Tag the value that fits, add the detail that makes the recognition specific, and let the entry become part of the record.

7. Close the loop on the next cycle

Follow up. Did the person appear in the feed? Did the value mix change? Did cross-team recognition increase? Wudd's KPI rollups update nightly from the Company Value tags, and dashboards read from pre-computed snapshots rather than waiting on live queries. That makes the feed practical to review, but it does not make one data point a trend. Compare cycles.

Keep a short review log: date, names reviewed, gap found, action taken, owner, and next check. If nothing changes after two cycles, the problem may be visibility or workload, not a shortage of thank-yous. Fix the condition as well as the recognition.

A simple review checklist

  • Who has no recognition in the last 30 days?
  • Whose recognition is generic or manager-only?
  • Which values dominate, and which are missing?
  • Where is cross-team work happening without a corresponding entry?
  • Who may be near a cap, and what does the underlying record show?
  • What specific recognition will be sent this week, by whom?
  • What will we check next cycle?

Recognition is a first-class action, not a buried text. The same feed your team scrolls is the feed your leadership can review for signal. In Wudd, the Recognition Feed is included in every plan starting at Silver. Product benefits depend on company configuration and adoption, so use your own baseline and review pattern to judge what changes.