Dashboards can perform trust; evidence earns it
A fancy dashboard can look authoritative and still compromise trust. When a figure cannot be traced back to a story or a tracked value, people cannot tell whether it is real, so they either defend it or dismiss it. Reports rooted in evidence do the opposite: every claim can be opened, questioned, and followed back to the work that produced it.
Reports built from stories, kept source-linked
A report should be assembled from the underlying responses, the stories and signifiers people actually submitted, rather than retyped into a deck. In ScrumDo the story pack is the report, and it stays linked to its source stories, so a live pack reflects the latest submissions and a reader can open any pattern to the accounts beneath it.
- Story packs gather the actual responses behind a pattern, not a summary of them.
- Live packs stay tied to current submissions instead of going stale.
- A per-card evidence view keeps intake, in-process, and post-delivery evidence attached to the card it shaped.
- Publishing has an audience and an audit trail, so who saw what, and when, stays on the record.
Outcomes measured by the change, not the checkbox
Completion is not the same as progress. An outcome review asks whether delivered work changed value, reduced risk, improved service, or met its timing, and keeps that judgment on the same cards and releases as the work. Delivered-card outcomes roll up the values tracked all along.
| What an outcome review weighs | Tracked throughout as |
|---|---|
| Did it create value? | Business value carried on the card and rolled up to the release |
| Did it reduce risk? | A risk-reduction signal tracked from shaping to delivery |
| Was it worth the cost? | Hours reported and labor cost attributed to the work |
| Did it answer the need? | The customer signals linked to the card it shaped |
Values tracked throughout, not reconstructed after
The values an outcome review needs are not gathered at the end; they are tracked the whole way. A card carries business value, time criticality, and risk reduction from shaping, its economics follow it through planning, and time logged against it becomes the labor cost in the budget. By the review, nothing has to be reconstructed from memory, the evidence is already there.
Share enough to learn, not enough to harm
Evidence-based does not mean exposed. Before anything circulates, decide what the report is for and who it protects. Aggregate patterns can travel widely for shared orientation, while the raw stories underneath move only with consent and context.
| Decide | The question it answers |
|---|---|
| Purpose | What decision or learning loop does this support? |
| Audience | Who needs to learn, and who can safely see detail? |
| Visibility | Patterns travel widely; stories move only with consent and context. |
| Protections | Minimum-count thresholds and role-based access on the underlying stories. |
| Confidence | How grounded is this, and where are the evidence gaps? |
Closing the loop is validity, not courtesy
People gave their time and their truth. The work is not done until they hear what changed. People often stop participating not because nothing changed, but because they could not tell whether what they offered mattered. Closing the loop is not "here are the results"; it is "here is how your meaning shaped our next step."
- What we heard, the patterns, not individual exposures.
- What we changed, something small and already underway.
- What we will check next, and when we will come back.
Catch misuse early
Misuse rarely announces itself; it shows up in how a report is talked about. When you see these, do not message harder. Reopen the stories, restore shared interpretation, and restate the protections.
- Charts used to win arguments, with no story read alongside them.
- "Top three issues" language that replaces the real mechanism.
- Requests to identify individuals, framed as accountability.
- Actions that turn punitive instead of experimental.
- Publishing that is one-and-done, with no revisit to see what moved.
Key terms
- Story pack
- A report assembled from the actual responses behind a pattern, kept linked to its source stories.
- Outcome review
- A check of whether delivered work changed value, risk, quality, or timing, kept on the same card and release as the work.
- Evidence gap
- An explicit flag that a release or decision is missing the evidence it should have.
- Confidence level
- An honest signal of how grounded a report’s claims are, not a statistical interval.
- Two ledgers
- The value of the work and the money spent on it, kept separate so a review can weigh both.
- Return loop
- Coming back to people with what was heard, what changed, and what you will check next.