What 4DX Gets Right About Sprint Scoreboards
Every team that has ever set up a sprint dashboard has watched the same thing happen: it gets configured with real care, it gets shown off once in a planning session, and then nobody opens it again. The data stays accurate. The chart stays correct. It just stops being looked at.
The usual explanation is that the team isn’t disciplined enough, or that the tool needs better notifications. There’s a more useful explanation, and it comes from a management book rather than an engineering one.
Discipline 3: keep a compelling scoreboard
The 4 Disciplines of Execution (McChesney, Covey, Huling) devotes its third discipline to “Keep a Compelling Scoreboard.” The 4DX framework argues something narrower and more testable than “measure things”: that people play differently when a score is being kept, and that the design of the scoreboard is what determines whether that effect shows up at all.
The canonical example in the book is a pickup basketball game. Walk past one where nobody’s tracking the score and you can see it in the body language — the effort on defense, the intensity of the contest. Start keeping score and behaviour changes without anyone being told to try harder.
This is worth taking seriously precisely because it isn’t a claim about metrics being useful for analysis. It’s a claim about visibility changing behaviour in the moment. Those are different jobs, and the book’s sharpest observation is that a single scoreboard cannot do both.
(4DX is cited here as a framework worth reading, nothing more — ScoreZen has no affiliation with the authors or FranklinCovey.)
The coach’s scoreboard and the players’ scoreboard
The distinction that matters most for sprint tooling:
| Coach’s scoreboard | Players’ scoreboard | |
|---|---|---|
| Purpose | Analysis, study | Engagement, in-the-moment behaviour |
| Density | Rich, many measures | Simple, few measures |
| Audience | The person managing the team | The team itself |
| Question it answers | “What patterns should I act on?” | “Are we winning right now?” |
A coach’s scoreboard is supposed to be dense. Someone is sitting with it, looking for patterns across weeks, deciding what to change. Cycle-time distributions, PR review latency, throughput by work type — that’s a good coach’s scoreboard, and it’s genuinely valuable to the person whose job is to study the team.
A players’ scoreboard has a completely different success condition. It has to be readable in the two seconds someone glances at it between tasks, and it has to make the current state of the game obvious without interpretation.
Here’s the critique that follows: most sprint dashboards are coach’s scoreboards handed to players. They’re built for study and then placed in front of people who need to know, in one glance, whether the team is winning. The dashboard isn’t ignored because the team lacks discipline. It’s ignored because it was never designed for the person being asked to look at it.
The four tests
4DX gives four tests for whether a scoreboard actually works as a players’ scoreboard. They translate to sprint tooling almost without modification.
1. Is it simple?
The test isn’t “does it contain the right metrics,” it’s “can the team hold the whole thing in their head.” A handful of numbers — points against the sprint goal, days remaining, on-track or not — passes. A screen with twelve panels does not, no matter how well-chosen each panel is.
Density is the failure mode here, and it’s a seductive one, because every individual metric anyone proposes adding is defensible on its own.
2. Can the team see it?
A scoreboard that requires navigating to a reporting section is a scoreboard the team consults deliberately, which means occasionally, which means never. The physical scoreboard in the book is on the wall of the gym. The software equivalent is persistent — present on whatever screen the team is already on, not somewhere they have to decide to go.
3. Does it show both lead and lag measures?
The lag measure is the outcome: points shipped against the sprint goal. It’s the thing you actually care about and the thing you can’t directly control today.
The lead measure is the behaviour that drives it: the pace this week, the work moving today. It’s controllable right now, which is what makes it actionable. A scoreboard with only the lag measure tells the team where they ended up. A scoreboard with only the lead measure tells them how busy they’ve been. Both together tell them whether today’s pace gets the team to the goal.
4. Can you tell at a glance whether you’re winning or losing?
This is the test most dashboards fail hardest. A chart that requires reading axes and doing arithmetic to determine whether the team is on track has failed it — the information is present but the verdict isn’t. On-track, at-risk, behind: a players’ scoreboard states the verdict, and the chart underneath is there for anyone who wants to know why.
The framing that matters: team score, not individual ranking
There’s a version of “keep score visibly” that goes badly wrong in software teams, and it’s worth naming directly because it’s the reason a lot of engineering managers flinch at the word “scoreboard.”
Ranking individuals by story points is a well-documented anti-pattern. It drives estimate inflation, discourages people from picking up the unglamorous work, and turns a planning artifact into a performance record.
But notice that 4DX’s argument doesn’t require it, and the basketball analogy actively cuts against it. The score on the wall in a basketball game is the team’s score against the opponent. It’s the thing everyone in the building is oriented toward, and it’s a shared outcome — you win or lose together.
The fix for the anti-pattern isn’t to turn the volume down on keeping score; a scoreboard nobody can see is just a spreadsheet. The fix is to move the score being kept from the individual to the team. Team points against the sprint goal is a team object, and winning a sprint is a team outcome. Contribution stays visible — people should see their work land — but the headline number is the team’s progress toward a shared goal, not a ranking of people against each other.
What this means for choosing a tool
Once you’ve got the coach/players distinction, a lot of the sprint-tooling market sorts itself out quickly.
LinearB, Swarmia, and Jellyfish are excellent coach’s scoreboards. They’re rich, analytical, and built for someone whose job is to study delivery patterns across teams and act on them. If that’s the job you’re hiring a tool for, they do it well.
They are not players’ scoreboards, and they don’t claim to be. The mistake isn’t in the tools — it’s in buying one of them and then wondering why the team doesn’t look at it.
The right structure is two views over one source of truth, never one view trying to be both. The moment a players’ scoreboard gets enriched to satisfy the analytical use case, it stops passing test 1, and it goes back to being ignored. Keep them distinct.
How ScoreZen is built against these tests
ScoreZen is built as a players’ scoreboard, and the four tests are close to a literal feature list:
- Simple — points against the sprint goal, days left, on-track status. Four numbers, not four panels.
- Always visible — a persistent header bar on every page, so the score is present rather than consulted.
- Lead measure — daily velocity: the pace the team is setting right now.
- Lag measure — a burn-up of cumulative points against an ideal pace line: the outcome, and how far the team is from it.
- Winning at a glance — an on-track / at-risk / behind indicator that states the verdict, with the chart underneath for anyone who wants the detail.
The score updates as work actually lands — a card moving to Done, or a linked GitHub issue closing — so there’s no separate bookkeeping step that can quietly drift out of date. An untrustworthy scoreboard gets ignored just as fast as an unreadable one.
And the coach’s view
The coach’s question — “how are we trending across sprints?” — is a real question, it’s just a different one, and it belongs on a different screen. On the Reports page, the cross-sprint velocity trend chart plots one bar per completed sprint with a stepped line showing each sprint’s goal, and highlights the sprints that met or beat their goal so the pattern reads without studying the axis. It needs at least two completed sprints before there’s a trend to show — one bar is a reading, not a trend.
Free teams see this over their recent sprint history window (the last three sprint reports); Pro lifts the history limit and adds CSV export and multiple admins. Same dataset, two views, depending on who’s looking.
The short version
If your team ignores the dashboard you set up for them, the most likely explanation isn’t discipline. It’s that you handed them an instrument built for study and asked them to use it for orientation.
ScoreZen is free for teams up to 5 people, no credit card required.