1. LandOffer
  2. Blog
  3. All articles
  4. Recognize Good Work Without Rewarding Only the Most Visible People

People Management

Recognize Good Work Without Rewarding Only the Most Visible People

Write specific appreciation that credits the work and respects how someone wants it acknowledged. Three complete fictional messages and a monthly distribution check show how to notice maintenance, remote contributions and quiet coordination without turning praise counts into performance ratings.

10 min readLandOffer team

Recognize good work by naming the contribution, checking the evidence and choosing a form the person welcomes. Then inspect whose work you are noticing. A steady stream of praise for presenters can coexist with silence around the people who made the presentation possible. Sending more messages without changing what you notice can repeat the same imbalance.

This LandOffer.ai guide contains three complete fictional recognition messages and a completed monthly distribution check. The records and conversations are authored examples, not observations of real employees. Public institutional guidance informs the approach; no employer system was accessed and no message was sent.

Three adults hold and inspect a woven textile in front of a wooden loom.

Start with a contribution you can describe accurately

Useful recognition tells someone what you noticed and why it mattered. Begin with a specific artifact, decision or interaction rather than a personality label. “You are always amazing” gives the recipient little information about the work you value. It can also make the person responsible for maintaining an impossible reputation.

MIT's local recognition guidance connects appreciation to identifiable achievements or contributions and describes spot recognition delivered near the achievement. Its award funding and eligibility belong to MIT, but the communication principle is useful elsewhere: identify the work before choosing the acknowledgment. MIT recognition guidance.

Separate what the record establishes from what you infer. A corrected instruction is evidence of completed maintenance. It can make a useful contribution visible without attaching a speculative savings claim. It does not prove that every later support request was prevented. An acknowledgment can be meaningful without a financial estimate, an invented percentage or a claim that one person caused the whole outcome.

For collaborative work, ask who supplied the evidence, checked the result and carried the implementation. The person announcing completion may deserve recognition, but presenting the result is not evidence of sole authorship. Resolve attribution before writing a sentence that will travel beyond the original audience.

Choose a channel without making privacy the price of appreciation

Ask about recognition preferences during an ordinary one-to-one conversation, then check again when the subject or audience changes. Someone might welcome a small team message about a technical contribution but dislike company-wide attention. Another person may prefer a private note and no mention in a meeting.

MIT offers direct and public appreciation routes. GitLab's communication handbook describes several channels, asks contributors to be credited and says a person's stated wish not to receive recognition should be respected. These are organizational examples, not permission to publish someone else's work or personal information. MIT appreciation options, GitLab communication guidance.

Explain the proposed audience and wording rather than asking a vague “Can I share this?” A team channel may include contractors, visitors or integrations the recipient has not considered. Link to an artifact only when that audience already has an appropriate access route. Appreciation does not justify exposing a restricted investigation, customer name or personal circumstance.

A private preference should affect delivery, not whether you notice the contribution. Otherwise a public praise count becomes a measure of willingness to be visible. Keep the minimum record needed to remember that appreciation occurred; do not copy the private message into a broader manager report merely to improve your statistics.

Worked asset one: three evidence-backed messages

The following case is entirely fictional. Manager Eleri leads a six-person team maintaining an internal room-reservation service. October's work includes a public demonstration, maintenance of equipment instructions and coordination of a policy exception. These are different contributions, not a ranking of employees.

Message one: credit the visible presentation and the work around it

Tobin presented a revised booking flow on October 8. Review record V-14 shows that Nessa tested three exception paths and Farid checked the help text before the demonstration. Tobin has agreed to recognition in the team's written weekly digest; the other two have agreed to their contributions being named there.

Tobin, thank you for making the October 8 booking-flow demonstration easy to follow. Your explanation separated the confirmed behavior from the exception still awaiting a policy decision, so the group left with a clear unresolved question. Nessa's exception checks and Farid's help-text review supported that demonstration. The reviewed flow and remaining decision are recorded in V-14.

This message does not say the change was fully approved. It recognizes a clear explanation while keeping the open decision visible. Naming supporting contributors also avoids turning the presenter's thanks into an accidental claim that the presenter did all the work.

Message two: recognize maintenance without celebrating extra hours

Nessa corrected equipment-return instructions in document H-22 on October 15. Two completed walkthrough records show colleagues could identify the correct return desk using the revision. She prefers a private note. The manager has not measured support volume or time saved.

Nessa, thank you for checking the equipment-return instructions against the actual desk arrangement and correcting H-22. In the two recorded walkthroughs, colleagues found the correct desk using your revision. That is useful maintenance work that would be easy to overlook beside a new feature. I am keeping this appreciation private, as you requested; I am not claiming we have measured a reduction in support requests.

The note names a small observed result inside the fictional case. It does not praise being available late or imply that maintaining documentation should be unpaid extra work. If that maintenance is recurring, Eleri still needs to allocate capacity for it.

Message three: acknowledge coordination without revealing the exception

Farid coordinated a restricted booking-policy question on October 22. The authorized case record shows he identified the decision owner and kept the affected parties informed. He approves a short team acknowledgment that omits the person's circumstances and the case link.

Farid, thank you for routing last week's booking-policy question to the authorized decision owner and keeping the agreed follow-up on track. You distinguished the question we could answer from the decision that needed another owner. The matter is still pending, so this is appreciation for the coordination already completed, not an announcement that the exception was approved. I have omitted the private circumstances and restricted record.

A manager who cannot safely describe the contribution publicly can use a private message instead. There is no requirement to make sensitive work visible to everyone in order to acknowledge it. The team version above is deliberately narrower than the underlying record.

Worked asset two: inspect a month of recognition distribution

A count can reveal a pattern worth investigating, but it cannot establish fairness by itself. Eleri reviews an illustrative October log containing twelve manager-originated recognition events. Each event names one primary recipient, so twelve events do not mean twelve different people. Collaborative credit inside a message is recorded separately; it does not create additional events in this particular count.

Team member Work arrangement October events What the log initially captured
Tobin Hybrid 5 Demonstrations and spoken project updates
Ivo Hybrid 4 Visible training sessions and coordination
Nessa Remote 1 Equipment-instruction maintenance
Farid Remote 1 Policy-question coordination
Liora Remote 1 A peer-review contribution
Cassian Hybrid 0 No manager recognition recorded

Nine of twelve events went to hybrid colleagues: 75%. Three went to remote colleagues: 25%. Each group contains three people, but equal group size does not mean their contributions or opportunities were identical. The result gives Eleri a reason to inspect her observation habits. This small illustrative log cannot establish discrimination, contribution shares or an appropriate quota.

Ten events were delivered in a group setting and two privately. Nessa's private note counts as recognition in the manager's minimal log. The public channel alone would therefore misrepresent the month's coverage. These are delivery counts, not measures of how appreciated anyone felt.

Eleri next compares the log with work records and asks each person for missing context through the team's normal check-in process. The review finds the three message cases above were recorded accurately. It also finds two maintenance contributions by Liora in M-31 and one permissions review by Cassian in A-09 that had not been considered for appreciation.

The records identify the contributors and completed actions, but they do not establish every claimed downstream benefit. Eleri verifies Liora's maintenance with the document owner and Cassian's review with the authorized reviewer. She does not open restricted details to the whole team or require the employees to justify why they deserve praise.

The completed review decision

Eleri records the following fictional conclusion on October 27:

My recognition log is concentrated around work I hear presented. I have verified two overlooked maintenance contributions by Liora and one completed permissions review by Cassian. This is a gap in my observation, not evidence that either person contributed less. I will offer specific private appreciation first and ask about any broader audience. I will not add a public shout-out merely to make the count look balanced.

Those three overlooked contributions are not retroactively added as sent messages. The month still contains twelve recorded events at the review point. Adding three planned acknowledgments would inflate the delivered total from twelve to fifteen before anything was sent. The record separates verified contributions, proposed acknowledgment and actual delivery, so a plan cannot masquerade as completed recognition.

For November, Eleri reserves fifteen minutes in each of four weekly planning sessions to inspect completed work across delivery, maintenance, review and coordination. That is sixty minutes of manager review time, not a promised productivity gain. She will inspect the existing maintenance queue, review records and weekly delivery notes, then ask for context in ordinary conversations. Employees do not have to write a separate recognition report.

At the next monthly review, she will check whether verified contributions received an appropriate acknowledgment and whether preferences were respected. A more even count would not, by itself, prove the new practice worked. Missing records, repeated recognition of one activity and employees who decline appreciation all require interpretation.

Two adults inspect the reverse of a woven textile, one pointing at a seam and one holding a magnifier.

Keep appreciation separate from workload, ratings and rewards

Daily recognition should not quietly become a substitute for pay, promotion or a fair assignment of work. “You are so good at helping everyone” can leave the same person with an expanding support burden. A useful follow-up asks whether that work is planned, supported and appropriately represented in the person's actual role.

Likewise, a month with fewer thank-you messages does not establish weaker performance. Some work has longer completion cycles, some details cannot be shared and managers see different parts of the team. Formal evaluation needs its own criteria and evidence. An informal appreciation log is a narrow record of manager behavior, not an employee league table.

Avoid rewarding emergency availability as though it were the preferred way to contribute. GitLab's guidance explicitly cautions against routinely praising work outside normal hours. In your own setting, acknowledge the specific help without making repeated late work an expectation; address the capacity or process problem through the appropriate management route.

If a gift, cash award or formal nomination is proposed, stop treating it as an ordinary message. Check the employer's approval, eligibility and confidentiality rules. The examples here concern day-to-day nonfinancial recognition; they do not authorize spending or decide a formal award.

Make the next acknowledgment specific and proportionate

Choose one completed contribution you have enough evidence to describe. Confirm who did it, what result you can support and what remains unknown. Ask how the person would like it acknowledged, then use language that credits collaborators and respects the audience's access limits. If attribution or permission remains uncertain, resolve that point before sending the broader version.

Afterward, inspect your pattern of attention. If maintenance, remote collaboration or quiet coordination rarely enters your notes, improve how you learn about that work. Do not ask people to manufacture visibility just to fit the channel you already watch. Keep recognition a response to work, rather than another competition for airtime.

These LandOffer.ai workplace guides support practical professional tasks. In this case, the useful next step is an accurate acknowledgment and a better observation habit; neither is a promise about engagement, promotion or compensation.

Sources and Further Reading