Gamification & recognition
Skill trees, points for the behaviours your team votes on, and reward redemption.
Gamification & recognition
The default is not a leaderboard
Points map onto skill-tree branches — Craft, Collaboration and Stewardship — and the default views are team totals and personal progression. Individual ranking exists only behind an explicit guardrail switch that shows you the consequences before you turn it on.
What earns points
Your team votes on which behaviours count: code reviews, mentoring, onboarding someone, documentation, tech-debt work. Points attach to verifiable events in the workspace rather than to self-reporting, so a claim has a source.
Where it lives
/dashboard/gamification shows your points, skill branches, achievements and available rewards. /api/gamification/me is your own record; /api/gamification/<userId> is another member's public view.
Skills and achievements
- GET /api/gamification/skills — the skill tree definition.
- GET /api/gamification/achievements — what has been unlocked and what is still locked, with the requirement for each.
Rewards
- GET /api/gamification/rewards — the catalogue and its costs.
- POST /api/gamification/rewards/redeem — spend points. Redemption checks the balance, records the redemption and notifies the person who approved the catalogue.
Configuration
PUT /api/gamification/configure changes the point values, the guardrail switch and the reward catalogue. It is an admin action, and the change is announced so nobody's points move silently.
Using it without harm
- Let the team choose the behaviours. Points for the wrong thing produce the wrong work.
- Keep rankings off unless there is a specific reason, and revisit that reason each quarter.
- Read gamification next to /dashboard/ethical-metrics — recognition that concentrates on the same three people is a workload signal, not a success story.