The role map
Each surface answers one person's recurring question, at the freshness their decision actually needs:
| Role | The recurring question | Core content | Honest freshness |
|---|---|---|---|
| C-level | Is the business on plan, and what moved? | Revenue bridge with drivers, actives trend, acquisition efficiency, exceptions | Daily |
| CRM / retention | Who needs an action today? | Segment movements, cohort reads, campaign results vs holdout, VIP queues | Hourly to daily |
| Payments | Is money moving, and where is it leaking? | Approval rate per provider/method/market, payout SLAs, pending queues | Near real-time |
| Risk / trading | Where is exposure right now? | Open liability, limits utilisation, settlement anomalies | Real-time |
| RG / compliance | Are obligations being met, per player, on time? | Intervention queues with SLAs, exclusion enforcement checks, reporting deadlines | Near real-time queues, daily summaries |
| Finance | Do the books reconcile? | Period views, cashier/ledger reconciliation deltas, restatement log | Daily, frozen at close |
Design rules that survive contact
- Display, never define. Every tile reads from the metric layer; a dashboard that computes its own version of a metric has forked the truth, however pretty it is.
- Every number carries its comparison. A value without a baseline — prior period, plan, control group — is decoration. The comparison is what turns a number into a decision.
- Freshness on the surface. "As of" timestamps and reconciliation status visible, so a stale surface announces itself instead of quietly misleading.
- Exceptions above averages. The operating surfaces earn their place by what they push — queues, breaches, anomalies — not by what they display. An average that never changes anyone's morning belongs in a monthly review, not a dashboard.
- Drill ends at the fine grain. Any aggregate should open to the players, transactions or bets behind it — the trust-building move that only works if the warehouse kept the grain.
- One owner per surface. Named, with the authority to retire tiles. Unowned dashboards decay into wallpaper within a quarter.
The anti-patterns
| Anti-pattern | What it costs |
|---|---|
| The everything dashboard | Serves every role, decides for none; each viewer scans past forty tiles to find their three |
| Per-team metric forks | The recurring "whose number is right" meeting — the dispute the dictionary exists to end |
| Real-time everything | Intraday jitter teaches executives to distrust the surface; late events make yesterday move |
| Screenshot reporting | Numbers detach from lineage the moment they enter a deck; export with definitions or expect drift |
| Vanity green | Thresholds tuned so everything passes; the surface stops carrying information at all |
From dashboards to briefs
The mature end-state is not more surfaces but fewer lookups: the operating question shifts from "what does the dashboard say" to "what should I do this morning" — a prioritised, priced action list per role, with the dashboards remaining as the drill-down behind it. That operating pattern — the daily brief with money attached to every alert — is described in the AI operations brief and its VIP cockpit companion; the discipline in this cluster is what makes such briefs computable at all.
Continue reading: The metric dictionary — the layer that keeps every surface honest. The Turbo Stars platform — reporting built on one set of definitions.