Heat-Map Timeline

1  Slide Type Name
Heat‑Map Timeline

2  One‑Sentence Purpose Statement
Shows “how the intensity of a metric (risk, spend, workload, etc.) rises and falls over time” so leaders can spot hot spots and take action.

3  Visual Description (Designer Instructions)

• Create a 16 × 9 slide with a left‑aligned vertical list of work‑streams (or risk categories, cost centres) and a horizontal time axis (weeks, months, quarters) across the top—forming a matrix.
• Each cell in the matrix is a square or rectangle whose fill colour represents the magnitude of the chosen metric for that period: use a diverging or sequential colour scale (e.g., light grey → deep red for risk; pale blue → dark blue for spend).
• Include a slim, clearly labelled colour‑bar legend above the grid that maps colour intensity to numeric values or qualitative bands (Low / Med / High).
• Add thin grid lines (0.5 pt) to delineate cells but keep them subtle so colour blocks dominate.
• Highlight the current period column with a light vertical band, and optionally draw a bold outline around any cell exceeding a predefined threshold.
• Place concise numeric or symbol overlays (e.g., “$2.1 M”, “▲”, “⚠”) inside selected cells only when detail is essential; avoid over‑cluttering.
• Reserve the top 15 % for a headline and legend; ensure legend and time labels never overlap. Maintain ample white space around the grid edges.
• Use a sans‑serif font; time labels 11 pt bold, work‑stream labels 11 pt regular, cell overlays 9 pt.

4  Business Questions This Slide Answers

• Which periods and work‑streams face the highest risk, spend, or resource load?
• How does the intensity trend—are hot spots getting better or worse?
• Where do multiple high‑intensity streams coincide, creating pinch points?
• Are mitigation actions shifting intensity to later periods or other streams?
• How close are we to breaching thresholds or budget caps?

5  When to Use (Typical Situations)

• Portfolio‑risk heat‑maps in programme‑management offices.
• Resource‑capacity planning across teams or factories.
• Spend‑burn visualisations for transformation budgets.
• Compliance or cyber‑risk dashboards showing monthly threat levels.
• Agile release trains tracking defect density or velocity over sprints.

6  Core Data Fields Required

• Time buckets (dates or period labels).
• Work‑stream / category names.
• Metric value for each time bucket–stream pair (numeric or ordinal).
• Colour‑scale definition (min, max, or band thresholds).
• Current period indicator.

7  Optional / Advanced Data Fields

• Threshold flags for cells exceeding targets (icon or outline).
• Trend arrows or mini‑sparklines adjacent to each row.
• Owner or team responsible for each work‑stream.
• Commentary pop‑outs summarising drivers behind extreme cells.
• Secondary metric overlay (e.g., confidence level via hatch pattern).