Blog · AI and self-service analytics
A plain argument for lists over dashboards as the output of sales analytics: what a dashboard asks the reader to do, what a list asks, why the dashboard's forty tiles produce no action and the list's ten rows produce ten, the four properties a list needs to be worked, ranked, valued, reasoned and owned, and how the dashboard survives as the place to check rather than the place to start.
Every sales organisation has a dashboard and most have a story about how few people open it. The dashboard is not bad; it asks the wrong thing of the reader. This guide sets out what each asks, why one is worked and the other glanced at, and the four properties that make a list work.
| Dashboard | List | |
|---|---|---|
| Asks the reader to | Look at forty numbers and decide | Do row one |
| Deciding done by | The reader, forty times | The arithmetic, once |
| Refreshes | Constantly | Weekly, on a stated cut |
| Ends | Never | When the rows are done |
| Success looks like | Opened | Worked |
A tile says coverage is 61 percent. The reader has to know what it was, whether that is bad, which rep, which accounts, and what to do. Five decisions per tile, forty tiles, before the first call. The rational response is a glance and a return to the inbox, which is where the actual list lives.
Row one says: account 4471, $310,000 last year, tier 2, no touch in 71 days, cadence 45, owner R-04, action: call, reason: table 3 row 4. Every decision has been made except whether to pick up the phone. The list is worked because that is all it asks.
| Property | Test | Without it |
|---|---|---|
| Ranked by value | Row one is worth more than row two | The reader re-sorts by instinct |
| A reason on every row | The row cites the table it came from | The reader distrusts the row |
| An owner per row | One name | Everyone's list is nobody's |
| A stated action | Call, sell line B, move the deal | "Review account" is not an action |
The same finding, two forms.
Dashboard. Coverage tile: 61 percent, down from 68. Filter to region North. Filter to rep R-04: 53 percent. Open accounts view. Sort by last activity. Scroll.
List. Row 1: R-04, account 4471, $310,000, 71 days since touch, cadence 45. Call.
The dashboard route is nine steps and requires the reader to know that coverage is where to look. The list route is one row, and it was produced because coverage moved past its threshold.
As the place to check. The list makes a claim; the dashboard shows the trend and the roll-up behind it. A reader who doubts row one opens the dashboard at the row's citation and sees the table. That is a dashboard used well: on demand, at a known location, to verify.
List built as a report. Forty rows, no ranking, no owner. Glanced at.
Action as a category. "At risk" is a label; "call about line B" is an action.
Dashboard as the start. The reader is asked to find the finding.
List without a citation. The reader cannot check it and stops trusting it.
Mapped once, the tables produce the list, ranked, reasoned, owned and with an action, every week, and the dashboard behind it for anyone who wants to check. Covirage builds both from the exports as they are. The sales insights solution describes the setup, and the Monday brief guide shows the list in one industry's vocabulary.
No. A dashboard is the right place to verify: the list says coverage fell for rep R-04, the dashboard shows the trend and the roll-up. It is the wrong place to start, because starting there means scanning forty tiles for the one that moved.
Four properties. Ranked by a value the reader agrees with. A reason on every row, citing the table. An owner per row. And a stated action, not a category. A list missing any one of those becomes a report, and reports are glanced at too.
Short enough to finish. Ten rows for a rep's week; ten movements for a leader's Monday. If more than ten qualify, the rest are counted and available, not shown. A list that cannot be finished is not worked from the top; it is skimmed.