Is mutual recognition a problem?

Not by itself. Colleagues who collaborate often may have valid reasons to recognise one another. Look at the substance and context rather than treating every two-way relationship as suspicious.

How can a programme discourage score trading?

Avoid treating message counts as a performance ranking, explain what a useful recognition describes and make any reward rules clear. Review patterns responsibly rather than encouraging employees to monitor one another.

Can reciprocal patterns prove misuse?

No. A pattern may suggest a question, but it does not establish intent. Consider team structure, shared projects and the actual messages, with appropriate access controls and a fair process for any concern.

Recognition glossary

Reciprocal recognition

Reciprocal recognition describes colleagues recognising one another over time; it may reflect mutual contribution, while arranged exchanges made mainly to increase scores can distort a programme’s signals.

Mutual thanks can reflect real work

People who collaborate closely are likely to see one another’s contributions. A two-way pattern of recognition may therefore be ordinary evidence of a working relationship. The important question is what the messages describe, not whether each person has thanked the other at some point.

Specificity helps. One colleague may recognise a careful handover while the other thanks a useful review. Those are different contributions, even when they happen on the same project. Do not discourage natural gratitude by treating all mutual appreciation as an attempt to influence a score.

Watch the incentives created by the programme

If a leaderboard or reward rule encourages people to maximise message counts, arranged exchanges can become attractive. The programme then risks measuring participation in the scoring system instead of the work it intended to acknowledge. Explain what recognition is for and avoid using raw counts as a proxy for individual performance.

The recognition equity guide addresses access to appreciation across roles. Someone with fewer visible collaborators may receive fewer messages without making a smaller contribution.

Interpret a pattern with context

Data alone does not reveal why two people recognise each other. Any review needs an appropriate purpose, access and process, with room to consider shared work and team structure. Do not publish accusations from a simple count. Use recognition-bias guidance to examine the programme’s design and the quality of its signals before drawing conclusions about individuals.

What it looks like

Example: two colleagues thank each other for different contributions to a shared project, each describing specific work.
Example: a pair agrees to exchange generic messages every week solely to increase reward balances, without referring to a contribution.

Questions people ask

Is mutual recognition a problem?: Not by itself. Colleagues who collaborate often may have valid reasons to recognise one another. Look at the substance and context rather than treating every two-way relationship as suspicious.
How can a programme discourage score trading?: Avoid treating message counts as a performance ranking, explain what a useful recognition describes and make any reward rules clear. Review patterns responsibly rather than encouraging employees to monitor one another.
Can reciprocal patterns prove misuse?: No. A pattern may suggest a question, but it does not establish intent. Consider team structure, shared projects and the actual messages, with appropriate access controls and a fair process for any concern.