Points for the work velocity metrics throw away
Reviews, mentoring, runbooks, unblocking teammates — the invisible glue of engineering gets visible. Opt-in, team-level, and nobody ranks anyone on speed.
- The team chooses what counts and what it's worth
- Skill trees, not leaderboards, by default
- Individual rankings are an explicit guardrail-off setting
The problem
Good teams reward the wrong things
Velocity leaderboards reward the loudest work. The person who reviews carefully, mentors patiently and writes the boring docs gets a 'thanks' in Slack — and nothing else.
Care is invisible
Review depth and knowledge sharing don't show up in any number leadership reads.
Leaderboards distort
Rank people on output and you get gaming: padded estimates, cherry-picked tickets, hoarded knowledge.
Badges get insulting
Generic 'rockstar ninja' points at work that matters to nobody. Recognition people resent is worse than none.
What you get
Recognition your team actually designed
Every behaviour that earns points is chosen by the team, and the guardrails ship on by default.
Team-defined behaviours
The catalogue starts empty-ish: you pick what counts — pairing, incident command, docs — and its worth.
Skill trees
Craft, Collaboration, Stewardship paths with visible nodes. Progress is a map, not a race.
Team-level defaults
Recognition surfaces show branches and totals. Individual standings exist only if the team explicitly enables them.
Real work signals
Points attach to Jira events — merged reviews, closed spikes, runbook updates — not self-reporting.
Opt-in participation
People who skip the system skip it cleanly. Their work still counts in every other view.
Anti-pattern guard
We flag when a config starts rewarding volume over care — and say so in the UI.
01
Design the game, or don't
On day one the team votes on which behaviours earn points and how much. The product ships suggestions — reviews, mentoring, onboarding, tech-debt work — but nothing counts until your team says so.
- Voting built into setup
- Changes are logged and visible
- A behaviour nobody wants gets deleted, not enforced
02
Skill trees make growth visible
Instead of a ladder of points, contributions map onto branch nodes — 'Reliability: runbook author', 'Collaboration: unblocked three teammates'. New hires can see what the team values; veterans can see their range.
- Nodes unlock from real events, not nominations
- Branches mirror your actual engineering practices
- Everyone sees their own tree; the team sees the forest
03
The guardrails are the point
Turn off 'team-level only' and the UI shows you exactly what you're about to do: a ranking of humans by output. We made that consequence visible on purpose. Most teams leave it on.
- Opt-in participation, always
- Rankings require an explicit, logged team decision
- Quarterly prompt: is this config still what the team chose?
Gamification playground
A skill tree that rewards how good teams actually work
A toy version of the real thing — you decide what counts, and nobody competes on speed.
On: the XP UI shows branch totals for the team. Off: you can see exactly why we default this on.
Recognition only works when people choose it. The playground respects that.
- Review Craft
Locked · unlocks at 2 Craft XP
- Safe Shipping
Locked · unlocks at 5 Craft XP
- Debt Hunter
Locked · unlocks at 9 Craft XP
Reviews, safe shipping and keeping the codebase tidy.
- Pairing Basics
Locked · unlocks at 2 Collaboration XP
- Unblocker
Locked · unlocks at 4 Collaboration XP
- Team Glue
Locked · unlocks at 6 Collaboration XP
Pairing, unblocking and sharing context.
- Runbook Author
Locked · unlocks at 3 Stewardship XP
- Follow-through
Locked · unlocks at 7 Stewardship XP
- People First
Locked · unlocks at 11 Stewardship XP
Mentoring, docs and follow-through.
How it works
Set up in one retro, live forever
The whole configuration happens inside a ritual you already run.
- Step 1
Pick behaviours
Choose from the catalogue or write your own. Assign each a branch and a worth, by team vote.
- Step 2
Choose guardrails
Team-level recognition on, opt-in on. Flip either only as an explicit, logged decision.
- Step 3
Let events flow
Points attach to real Jira events automatically. Nobody logs anything by hand.
- Step 4
Review quarterly
The config asks for a refresh every quarter. Dead behaviours get retired before they get gamed.
Straight talk
Be honest about the fit
Works well if
- Teams that already recognise each other in retros
- Orgs where the quiet work genuinely goes unrewarded today
- People who want a map of what 'good here' looks like
Not for teams that
- Leaders wanting a productivity scoreboard — the guardrails exist to stop that
- Teams under trust pressure where any tracking feels like surveillance (start with wellbeing, not points)
- Anyone expecting us to force adoption: participation is opt-in, permanently
Who it's for
Who stops feeling invisible
The people the metric economy forgets, and the leads who need them to stay.
Senior reviewers and mentors
The work that makes everyone else faster finally shows up as progress, not just a favour.
- Reviews and pairing count
- Mentorship on the tree
- No more hidden load
New hires
A visible map of what the team values — faster than osmosis, kinder than guessing.
- Know what counts
- Clear next nodes
- Belonging signal
Tech leads
Recognition data that argues for the unglamorous work in planning meetings.
- Evidence for tech-debt time
- Care work made visible
- Culture you can point at
No black boxes
How points are earned
No mystery mechanics. Here's the whole rulebook.
- Events
- Points attach to verifiable Jira events: reviews merged, spikes closed with docs, runbooks updated, onboarding buddies completed. No self-declared points.
- Worth
- Each behaviour's value is set by team vote during setup, with sane suggested ranges. Changing a value is logged and shown to the team.
- Display
- Default view: branch progress and team totals. Individual standings require an explicit guardrail change, and the UI previews what that means first.
- Anti-gaming
- Volume spikes trigger a config review prompt, not a reward. Duplicate-event dedupe and a 'this looks weird' flag ship on by default.
Included in every plan
This product ships with the platform — Starter, Professional and Enterprise all include it. Pricing scales by seat, annual billing saves 20%.
What early teams say
“Our quiet reviewer finally has a tree that shows what everyone in the team already knew.”
“The guardrail preview convinced us not to turn on rankings. That screen is worth the subscription.”
Example quotes from early-access conversations. We publish attributed testimonials only with permission.
Shipped
Recent updates for this product
2026-07-15
Improvement
Skill trees recognise review and mentoring work
Gamification paths now include code review, pairing and knowledge-sharing activities, opt-in per team.
Make the invisible work visible
Run the setup vote in your next retro and start counting the work that actually keeps the team alive. 14-day trial, no card.