Manager participation review: surface overlooked contributors without rankings or quotas

Problem

Recognition naturally flows unevenly. People in visible, cross-functional roles tend to receive more appreciation — and that's expected. But uneven counts alone don't tell you whether someone's contributions are genuinely being noticed or quietly overlooked.

Today, PraisePal provides recognition analytics (participation and activity by person/team) and posting guardrails (short, repetitive, and duplicate-message checks). These help administrators spot patterns and discourage low-effort posts, but they don't address a harder question: how do managers notice contributions that aren't being acknowledged?

Blunt tools like pre-approval, posting caps, or receiving limits risk recreating the bureaucracy of formal awards — the opposite of spontaneous, everyday peer appreciation.

Proposal: periodic manager participation review

A private, manager-only view designed around reflection rather than scorekeeping:

Design choice	Rationale
Unranked participation summary over a meaningful window (e.g. quarter)	Avoids manufacturing a "bottom of the list"
Adjusts for join date, leave, and inactive periods	Reduces misleading gaps
Prompts reflection, not clearance — e.g. "Whose contributions might be easy to miss?"	Directs attention toward the work, not the count
No targets, quotas, or red warnings	Reduces pressure to generate token praise
Explicitly separated from performance assessment	Recognition frequency ≠ contribution quality
Accounts for private recognition where applicable	Public post count isn't the full picture

Optional future extension

Lightweight pattern hints for workspace admins — e.g. dense reciprocal exchanges, whole teams with very low participation — as investigation prompts, not automatic enforcement.

Non-goals

Equalising recognition counts across employees
Blocking recognition because someone has "received enough"
Public zero-recognition lists or employee-facing ranking
Default pre-moderation of all posts (separate concern)
Replacing points budgets, structured programmes, or lifecycle awards — those serve different purposes

Open questions

What window and team scope (direct reports vs custom groups) works without overwhelming noise?
How should success be measured — more specific recognition of previously quiet contributors, or simply fewer people receiving none?
Should concerns about reward value fairness be addressed separately from peer visibility?