Skip to content
JiraVision
Ethical Metrics
Receipts included

Every metric opens to show its formula

Predictability, load balance, review equity, after-hours drift — team-level indicators with the calculation, source and caveats printed next to the number.

  • Methodology visible on every card, always
  • Team-level by default; individuals see their own slice
  • Anti-patterns documented: what we refuse to measure

The problem

Metrics people distrust get ignored or abused

When a number appears with no formula, one half of the team assumes it's wrong and the other assumes it's a weapon. Both readings are rational.

01

Vanity leaderboards

Velocity rankings make slides and destroy behaviour — the fastest way to game a metric is to publish it per person.

02

Invisible imbalance

Review load and after-hours work concentrate quietly. Nobody's dashboard says so because nobody trusts dashboards.

03

Args that never end

'Your numbers are wrong' is unresolvable when nobody can show how the number was made.

What you get

Numbers with receipts

A deliberately small set of metrics, each fully documented, each pointing at an action.

Predictability

Committed vs delivered per team per cycle — with the definition of 'delivered' printed on the card.

Workload distribution

Who carries points, reviews and after-hours work — shown as spread, flagged past thresholds you set.

Review equity

Review load balance and depth proxies, so the quiet reviewers stop being the default janitors.

Drift alerts

Slow-burn changes — after-hours creep, growing imbalance — flagged with the trend line attached.

Formula on the card

Every metric expands to numerator, denominator, source events, exclusions and last recalculation.

The refusal list

We publish what we won't build: lines-of-code, per-person velocity, activity scores, keyboard-time.

01

Open a metric, read its mind

Click any number and the card expands: the exact formula, which Jira events feed it, what's excluded (and why), and the team's own threshold. Disputes become edits to a definition, not arguments about motives.

  • Numerator and denominator, in words
  • Source events listed by type
  • Exclusions explained, not hidden
A dashboard of figures on a laptop screen

02

Distribution, not ranking

The equity view shows the shape of load across the team and names the outliers as numbers, not as a league table. Managers see the pattern; the flagged imbalance comes with the rebalance moves to fix it.

  • Watch thresholds set by the team
  • Flagged bars marked with a rule, not a vibe
  • One click hands the fix to the AI Scrum Master
A team comparing load charts on a wall screen

03

Drift before drama

After-hours commits and review concentration rarely spike — they creep. Trend alerts fire on slope, not just level, with the seasonality check printed alongside.

  • Slope-based alerts you configure
  • Seasonality and release-week context shown
  • Alert history is auditable, including dismissed ones
A planner week written up beside a coffee
Demo data

Ethical metrics

Workload & equity explorer

Which engineer is quietly overloaded? Switch metrics and watch the same six-person team through four lenses.

Synthetic numbers. The point is the pattern: every metric here opens to show exactly how it's calculated.

Within watch bandPast watch threshold (marked *)Team mean

Engineer A is taking on 1.4× the team's average sprint load. (Watch above 130% of the team mean.)

Synthetic demo dataset — six anonymised engineers. Active metric: Sprint points · watch above 130% of the team mean.
EngineerBandSprint pointsptsReviews per weekreviews/wkAfter-hours commitscommits/moComp index× band midpoint
Engineer Awatch *III41321.04
Engineer BII38450.98
Engineer CII36941.00
Engineer DIII21630.86
Engineer EI182111.06
Engineer FI24230.95

How it works

From dashboard to decision

A metric that can't be acted on is decoration. Every card links to a move.

  1. Step 1

    Pick the set

    Start from the documented menu of nine metrics. Enable only what someone owns and will act on.

  2. Step 2

    Set thresholds

    Watch bands are team decisions — the defaults come from the product's own playbook, not a benchmark we invented.

  3. Step 3

    Read the working

    Every review starts from the formula panel. Definition changes are logged and visible to the team.

  4. Step 4

    Act on the flag

    Tripped thresholds offer concrete moves — rebalance, re-scope, recovery week — each traceable back to the signal.

Straight talk

Be honest about the fit

Works well if

  • Teams tired of metric disputes with no shared definition
  • Leads defending predictability or headcount with evidence
  • Orgs ready to publish their refusal list internally

Not for teams that

  • Anyone wanting per-person performance numbers (not coming)
  • Companies looking for vendor-invented industry benchmarks
  • Teams wanting 40 dashboards — we ship nine metrics with moves attached

Who it's for

Who gets the argument settled

The metric fights that eat review meetings — ended by showing the working.

Executives

Portfolio predictability and load balance across teams, with methodology one click away for the sceptics in the room.

  • No vanity metrics
  • Comparability caveats printed
  • Trend vs noise distinguished

Engineering leads

Defensible numbers for reviews and headcount cases — because the team agreed to the definitions.

  • Formula-first reviews
  • Drift alerts with context
  • Audit trail on every flag

Teams

Proof that the quiet work is counted and the loud numbers aren't being used against anyone.

  • Team-level by default
  • Thresholds you own
  • Refusal list you can read

No black boxes

Our metric contract

The rules every metric in this product must pass to ship.

1 · Formula visible
Numerator, denominator, exclusions and source events on the card. If it can't be written plainly, it doesn't ship.
2 · Team-level
Individual granularity exists only for the person themselves. Manager views stop at the team boundary.
3 · Actionable
Every metric documents the move it's meant to trigger. Metrics without moves go on the deprecation list.
4 · Refusal list
Lines of code, per-person velocity, activity/keystroke scores and anything resembling surveillance are permanently out of scope.

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

“Opening a metric and seeing its formula ended a standing argument with my staff engineers. That alone was worth it.”
Early-access participant — CTO — Health-tech startup
“The refusal list is why we bought. A vendor that tells you what it won't measure is one that understands measurement.”
Early-access participant — VP Engineering — Fintech scale-up

Example quotes from early-access conversations. We publish attributed testimonials only with permission.

Shipped

Recent updates for this product

  1. 2026-08-28

    Feature

    Ethical metrics methodology view

    Every fairness and workload metric now links to the exact formula and data window behind it.

Full changelog

FAQ

Questions about this product

All questions

Put the receipts on the dashboard

Start with three documented metrics, set the thresholds with your team, and end the 'whose numbers are these' meeting. 14-day trial, no card.