Stacked area or heat-map beneath the timeline axis showing headcount or dollars committed per period; surfaces capacity pinch points.
1 Slide Type Name
Resource‑Load Timeline
2 One‑Sentence Purpose Statement
Reveals “how our resource demand fluctuates over time and where capacity pinch‑points emerge.”
3 Visual Description (Designer Instructions)
- Lay out a 16 × 9 slide with a standard horizontal timeline axis across the upper third (weeks or months).
- Directly beneath the axis, add a stacked‑area chart (or alternatively a heat‑map matrix) that shows resource utilisation per period: each coloured band represents a function, vendor, or cost category.
- Ensure the Y‑axis at the left is labelled with the relevant unit—Headcount (FTE), $ k OpEx, Sprint Points, etc.—and scales high enough to display peak demand clearly.
- Overlay a thin horizontal capacity line (e.g., “150 FTE ceiling”) so the audience can spot where the stacked area exceeds available capacity; tint the overflow region lightly in red or hatch it for emphasis.
- Add milestone markers on the timeline axis itself—project phase gates or release dates—and, if useful, vertical dotted guide lines down into the area chart to relate demand spikes to milestones.
- Optionally draw a bold vertical “Today” line to distinguish past actuals (solid colours) from future forecasts (lighter opacity of the same colours).
- Keep the legend for colour bands in the lower‑right corner and ensure it does not overlap the chart. Maintain generous left and right margins so axis labels are not clipped.
- Fonts: sans‑serif; axis labels 10 pt, legend 9 pt, headline 16 pt bold.
4 Business Questions This Slide Answers
- When will resource demand exceed our capacity or budget ceiling?
- Which work‑stream or department drives each upcoming spike?
- How does demand profile change once key milestones pass?
- Are we ramping down resources efficiently after peak?
- What is the cumulative utilisation trend versus baseline?
5 When to Use (Typical Situations)
- Portfolio or PMO reviews to pre‑empt staffing bottlenecks.
- Budget planning sessions linking spend profile to timeline.
- Agile release trains balancing squad allocation across increments.
- Vendor‑management meetings where external capacity is limited.
- Capital projects or construction schedules with labour peaks.
6 Core Data Fields Required
- Time periods (weeks, months, sprints).
- Resource demand values per period and per category.
- Capacity ceiling (people, dollars, points).
- Milestone dates and titles (optional but recommended).
- Current date (“Today”) marker if highlighting actuals vs forecasts.
7 Optional / Advanced Data Fields
- Separate colour palette for actuals vs forecast.
- RAG shading for periods over capacity (+10 % amber, +20 % red).
- Cost conversion line (headcount → $ burn) on secondary axis.
- Owner or function labels embedded inside area segments at their peak.
- Tooltip annotations or footnotes for extraordinary spikes (e.g., “M&A integration wave”).