Most active
Everyone, ranked by how much they did, whatever your sources send.
any source
Leaderboards
Most tools ship one leaderboard and hope it is your business. If what matters this quarter is resolved escalations, filings accepted or deals closed, rank on it this afternoon without asking us.
What you choose
| Field | What it controls |
|---|---|
metrics[] | Which event types count, and at what weight |
scope | Rank individuals, or rank teams |
team_filter[] | The whole org, or a set of teams, expanded through the hierarchy |
window | Week to date, last 7 or 30 days, last week, all time, an explicit range, or a competition |
sort_by, tie_breaks[] | The comparator chain, ending in the subject id so ordering is total |
visibility, limit | Who appears, and how deep the board goes |
Weights are what stop a board rewarding the wrong thing. Two closed deals worth $2,000 should not outrank one worth $400,000, so score the revenue and show the deal count beside it without letting it count. Most bad leaderboards are one number that could have been two.
Start here
Two of them work for any team at all, whatever they do. The rest assume you ship software. All eight are a starting point you can change, not a menu you are stuck with.
Everyone, ranked by how much they did, whatever your sources send.
any source
The same, by team rather than by person.
any source
Ranked by work shipped. The general-purpose board.
mergedapprovalsdeploys
Approvals alone, where merges cannot drown them out.
approvals
Production deploys over the last 30 days.
deploys
Everything since the beginning, not just this month.
mergedapprovalsdeploys
Cards opened, all time. Works as soon as any rule fires.
cards_pulled
The same work, ranked by team rather than by person.
mergedapprovalsdeploys
Speed
A board that gets slower every month is a board people stop opening. Yours opens as fast on three years of history as it did in week one.
No waiting
Send us something we have never heard of: escalation_resolved, filing_accepted, demo_booked, and it is rankable immediately. There is no list of supported metrics to be missing from, and no request to open with us.
Which also means a name you invent can never break anything, and we test for that specifically.
Visibility
Whichever you choose, it is not a preference the product can forget. Nobody sees a name you said they could not see, including through an export.
Individual boards return nothing, and say why, so the page can explain itself rather than showing a blank table. Team boards are unaffected, so the executive question is answerable without ranking a single person.
A person appears once they have opted in. Absence means not opted in, so silence reads as privacy rather than as exposure.
The default, because the restrictive mode left every new org’s first board blank by policy, on day one, with nothing explaining it.
In every mode a viewer sees their own row. Hiding someone’s own work from them is not privacy, it is a broken page.
Competitions
Put dates on a board and it becomes a competition, such as a quarter-end drive or a bug-squash week. When it ends, the result is settled for good.
Modifiers
Better odds for a ticket closed inside an hour, worse for one reopened three times. You choose what earns the good cards, so the board rewards the behaviour you wanted rather than volume.
A deliberate omission
Thanks given in Slack shows on a feed and a profile, and no board ranks it. Ranking gratitude turns it into a currency people farm, and the farming is louder than the thanks.
Free for your first 50 people. No card, no sales call.