How to Make Recognition and Feedback Part of Everyday Work

Organizations have tried many ways to make peer recognition routine: appreciation campaigns, internal praise boards, gratitude challenges, and peer bonuses such as points or gift cards. Their shared aim is to make noticing and acknowledging a colleague’s contribution an everyday action, rather than an occasional event.

Yet the results differ. In one organization, recognition becomes a lasting practice; in another, it remains a quarterly campaign. What makes the difference?

Section 1. Why peer feedback can feel difficult

In many Korean workplaces, employees hesitate to give colleagues feedback. The term may sound like criticism or evaluation because it is associated with formal performance conversations. Feedback from a manager to a direct report feels part of the manager’s role, while a peer or a more junior employee may wonder whether speaking up is appropriate. Some worry that feedback upward will look like flattery, or that commenting on a peer’s work is not their place.

The criteria may also be unclear. If the organization has never said what merits recognition, employees must decide both what to write and whether the event is significant enough to mention. Even a program limited to positive feedback can stall on these questions.

Recognition can begin with an observation: “You did this, and it had this effect.” It does not require someone to judge a colleague’s overall performance. Anyone who saw the contribution can acknowledge it, whether the recipient is a peer or a manager. Praise often sounds more evaluative: “You did a great job.” Describing a specific observed contribution lowers that barrier.

Why build a culture of recognition?

Being seen can give someone energy for the next challenge. Research by Workhuman and Gallup tracked more than 3,400 employees from 2022 to 2024 and found that those who received high-quality recognition in 2022 were 45% less likely to have left their jobs by 2024 (The Human-Centered Workplace).

Recognition also tells others which behaviors the organization values. When a contribution is acknowledged visibly, colleagues see an example of work that matters here. Recognition therefore benefits more than the recipient.

That makes recognition something to design, not simply hope for. Organizations can immediately address one major source of hesitation: unclear criteria. Voluntary participation can become the goal, but it rarely works as the starting point. Initially, HR needs to set criteria, scope, and cadence; autonomy becomes easier once the practice is familiar.

Section 2. Opening a feedback channel is not enough

Without guidance, a recognition channel may receive a few short posts in its first week, often from managers or a handful of enthusiasts. Activity then declines. The barrier is not the absence of a text box. Faced with a blank field, employees must decide what counts, what to say, and whether they are the right person to say it.

talenx addresses this by letting employees select a feedback badge as they write. A badge represents a type of contribution the organization has defined in advance, such as Speed, Customer Success, or Commitment. A short list shifts the question from “What should I say?” to “Which behavior did I observe?” It also makes accumulated feedback easier to review by type than a collection of unstructured messages.

What should badges be based on?

Choosing badges is a policy decision, even though it takes place during system setup. Poorly defined badges leave employees unsure what to select and can signal that the organization values the wrong things. The useful starting question is: Which behaviors do we value?

Many organizations have already answered that question through their core values. Even without a formal values statement, recurring hiring criteria, celebrated examples of good work, and messages from leadership reveal what matters.

Section 3. Four steps to make recognition a shared practice

Step 1. Define recognizable behaviors

Start with core values, then describe how each value appears in real work. A label alone does not tell someone what they should have observed. Values often become visible when a person exercises judgment and goes beyond simply following a procedure.

An observed example is specific, while the description must work across the organization. The Customer Success badge can apply to internal support teams as well as customer-facing teams. Use language employees naturally use, but avoid labels such as “Best” or “Outstanding” that sound like ratings and may make senders question their authority to judge.

Avoid descriptions that merely repeat a value, such as “collaborates well.” If any action qualifies, one badge absorbs most recognition and the records become less useful. Five to ten badges are a practical starting range: too few blur different contributions; too many make categories hard to distinguish.

If a value is hard to translate into behavior, collect recent examples of work colleagues called especially good and sort them by value. If no example comes to mind, ask leaders what they would expect to see. In talenx, organizations can set badge names, descriptions, and icons, then activate or deactivate badges as priorities change.

Step 2. Decide where to launch and what to share

A staged pilot is not automatically best for recognition. A broad launch tells employees it is a company-wide practice and allows more people to see examples of valued behavior. A small team pilot may generate too little feedback to assess the program. Large organizations or those with very different types of work may start at division or business-unit level instead.

Set a default visibility policy. If every sender decides independently, people uncomfortable with feedback may choose private messages, limiting the opportunity for others to learn which behaviors are valued. In his book Work Rules!, former Google People Operations leader Laszlo Bock described gThanks as a way to make messages of appreciation visible to colleagues rather than confining them to private email.

A public default can help establish the practice, while constructive or sensitive feedback may need a narrower audience. talenx can require feedback sent with a badge to be visible company-wide, leaving the employee to decide whom and what to recognize.

Step 3. Give people a reason to participate

A clear badge list and visibility rule may still leave the same few people writing every message. Recognizing someone’s contribution and putting it into words are different actions. The program needs a prompt that turns one into the other.

Bock also described a peer-bonus feature in Google’s gThanks: employees could award a colleague $175 without manager approval. His example illustrates the value of allowing employees to recognize contributions directly. If every message has to wait for sign-off, recognition can start to feel like an administrative request and lose its immediacy.

One way to create a prompt is to give all employees a limited number of thank-you gifts to send within a defined period. If these are linked to an actual reward, the organization should decide the amount and frequency together, start small, and adjust based on use. Unused gifts expiring at the end of a period may encourage employees to look for contributions worth acknowledging. Keep allocations equal across job levels so recognition does not become a privilege of rank. Where gifts are converted to cash and paid through payroll, an unused allocation may feel like a missed opportunity, adding an incentive to recognize a colleague. The employer should decide how such awards are administered in its own payroll process.

talenx lets employees attach a thank-you gift to feedback. A gift is an added expression of appreciation for a particularly meaningful contribution, not a separate type of badge. Its limited availability encourages employees to choose those moments thoughtfully and describe the contribution more specifically.

Step 4. Review distribution and content

Concentration in one badge may mean its description is too broad, or that the underlying behavior truly is common. An unused badge may be unclear, or its associated behavior may not yet appear in work. Check both before revising it.

If participation stays low despite thank-you gifts, speak with team leaders. People may not have heard enough about the program, or work may be so independent that colleagues rarely see one another’s contributions. In the latter case, changing gift frequency will do less than creating opportunities for collaboration.

A person may receive little recognition because they joined recently, work independently, or belong to a team whose manager does not participate. Review role and team context rather than trying to equalize counts. The aim is to create opportunities for different kinds of work to be seen. Check message quality quarterly or twice a year; if posts collapse into generic thanks, improve examples and badge guidance.

talenx lets HR review badges sent and received by employee, team, and period and export the data to Excel. Comparing the first months with later quarters helps assess whether changes to the program made a difference.

For the first quarter, set badge criteria, launch scope, visibility, and gift rules before launch. In month one, share descriptions and examples with all employees and ask managers to review participation. After one month, examine badges and feedback sent and received. At the end of the quarter, review actual messages, revise badges and descriptions, and adjust gift allocations if needed.

Section 4. Make recognition part of the organization’s language

The message gives a badge its meaning

Employees remember why they were recognized more than the badge name. The badge identifies a type of contribution; the message records the situation, action, and result.

Share good and weak examples side by side when introducing the program. Real examples from within the organization can later become the strongest writing guide.

Ongoing recognition and 360 feedback serve different purposes

If the two are treated as the same process, employees may see informal recognition as a hidden performance review. The distinction lies in what prompts the message. A 360 review starts with a request to designated respondents and can cover both strengths and development needs, usually with confidential responses. Ongoing recognition starts when someone observes a contribution and chooses to acknowledge it without being asked. It concerns positive contributions and can be shared so others see examples of valued work.

The practices can reinforce each other: employees accustomed to describing a colleague’s specific contribution may also provide more concrete 360 feedback. Avoid heavily promoting ongoing recognition during a 360 review cycle, when their purposes can become blurred.

Section 5. How should recorded recognition be used?

Peer recognition creates a record of the situation, action, and outcome behind a contribution. Managers cannot observe every cross-team collaboration or every way an employee helps beyond their formal duties. Colleagues often can.

In talenx, received feedback and badges can be viewed as reference material in the data tab when writing performance evaluations and reviews, alongside goals, 360 feedback, and one-on-one meeting records. Feedback attached to a badge can be connected to the relevant goal and work context.

The mix of badges may suggest recurring strengths: Coaching for someone who helps colleagues grow, or Customer Success for someone who thinks beyond the immediate request. Counts alone should not determine an evaluation; they are influenced by who sends feedback and by team norms. Read the accompanying messages to understand what actually happened.

Aggregated badge patterns can also show which core values are visible in daily work and which appear less often. An unused badge calls for investigation: perhaps its definition is unclear, or the behavior is not being observed. The organization decides what to recognize and which examples express its values. talenx supplies the structure for exchanging recognition and reviewing the resulting data.

Recognition becomes a habit when people repeatedly notice contributions as they happen and record what someone did and why it mattered. To explore where to start designing that practice in your organization, speak with the talenx team.