Skip to content
JiraVision

Gamification

Gamification for developer productivity

Skill trees instead of speed leaderboards: how the team votes on which behaviours earn points, and where the guardrail switch sits.

35 minutes · 5 steps

No recording published

We are not going to embed a video that does not exist. What follows is the outline the session works through, in order — every step names a page or a setting you can open yourself. When a recording is published it appears above this note.

Follow it in the dashboard

Session outline

What the session covers, step by step.

  1. 1

    Skill trees, not leaderboards

    Points map onto Craft, Collaboration and Stewardship branches. The default views are team totals and personal progression.

  2. 2

    Choosing the behaviours

    The team votes on what earns points — reviews, mentoring, onboarding, documentation, tech-debt work. Points for the wrong thing produce the wrong work.

  3. 3

    Verifiable events

    Points attach to events in the workspace rather than to self-reporting, so every claim has a source.

  4. 4

    Achievements and rewards

    Achievements state their requirement before they are unlocked; redeeming a reward checks the balance and notifies whoever owns the catalogue.

  5. 5

    The guardrail switch

    Individual ranking exists only behind an explicit switch that shows the consequences before you turn it on.

Want a session on something else?

Tell us what your team is stuck on and we will say honestly whether we can cover it.

Propose a session

Get the outline by email

One email when a session outline or a recording is published. No tracking pixels.