How this site reads¶
Story structure¶
Every case page follows the same six steps, so a reader always knows where they are:
- Context - what the operation is and what it promised.
- Question - one business question, in plain words.
- KPI - the tiles answer the question; each links to its catalog page.
- Finding - charts, each carrying one message.
- Decision - what someone should do on Monday, sized with the data.
- How we keep measuring - owner, cadence and the trigger that fires the next action.
Chart rules¶
| Rule | How it is enforced |
|---|---|
| One message per chart | One highlight colour (blue); everything else is context grey. |
| The title is the conclusion, not a description | Titles are generated from the numbers ("One queue explains the breach…"); the subtitle says what is plotted. |
| Annotate the finding | The event, the threshold or the outlier is labelled on the chart itself. |
| Accessible, consistent palette | A colour-blind-validated order (blue, orange, aqua) and a reserved status palette; status always travels with an icon and a word (✓ On target, ! Watch, ✕ Act). |
| Targets are visible | A thin reference line or a shaded band - a status without a target is not shown. |
| Zero-based bars | Bar lengths start at zero; line charts may zoom, and say so. |
| No 3D, no pies with more than three parts | The catalog schema cannot even recommend a pie. |
| Data behind every chart | Most charts have a "Show the data" table under them. |
Leading and lagging¶
Each case pairs an outcome KPI (lagging: SLA compliance, availability, OTIF, retention) with one that moves first (leading: aged backlog, PM compliance, forecast bias, revenue at risk). The monitoring tables at the end of each case review the leading ones more often.