Outcome-Metric Overlay Timeline

1  Slide Type Name
Outcome‑Metric Overlay Timeline

2  One‑Sentence Purpose Statement
Makes it easy to see “how each milestone or phase affects our key outcome metric over time.”

3  Visual Description (Designer Instructions)

• Build a 16 × 9 slide with a horizontal milestone timeline in the centre: a thin axis with evenly spaced date ticks.
• Place milestone markers (diamonds or small rectangles) on the axis; label each with a concise title and date (9 pt) above the line.
• Add a secondary Y‑axis on the right for the quantitative outcome metric (e.g., Net Promoter Score, defect rate %, $ cost per unit).
• Plot a translucent trend line or area that runs the full width of the slide against this secondary axis: use a 2 pt stroke, 40‑50 % opacity, colour‑matched to the corporate accent.
• Drop small circular markers on the trend line directly above (or below) each milestone; draw a faint dotted connector down to the milestone to emphasise causal linkage.
• If the metric should improve downward (e.g., defect rate), flip the secondary axis or annotate direction with an arrow.
• Optionally shade confidence bands around future metric points, or add target thresholds as horizontal dashed lines.
• Insert a vertical “Today” line if you want to distinguish actuals (solid trend) from forecast (dashed trend) to the right of today.
• Reserve the top 15 % for a headline and a compact legend explaining axes and line colours. Keep margins ≥ 0.5 in so labels are never clipped.
• Fonts: sans‑serif; milestone labels 9 pt; axis tick labels 10 pt; metric labels 9 pt; headline 16 pt bold.

4  Business Questions This Slide Answers

• How did each initiative shift our key outcome metric?
• Are the improvements (or regressions) sustained after milestones?
• Where are we today versus the target threshold?
• What trajectory is forecast if future milestones land on schedule?
• Which upcoming milestone is expected to deliver the next inflection?

5  When to Use (Typical Situations)

• Continuous‑improvement or Six Sigma reports (defects vs fixes).
• Customer‑experience programmes linking releases to NPS swings.
• Cost‑reduction roadmaps tracking unit cost over milestones.
• Security or reliability work showing incident rate vs mitigations delivered.
• Agile PI reviews tying velocity metrics to completed features.

6  Core Data Fields Required

• Milestone titles and dates.
• Outcome‑metric values over time (actuals and/or forecasts).
• Shared date axis.
•  Metric axis label and scale.
• Current date (“Today”) marker, if showing actual vs forecast.

7  Optional / Advanced Data Fields

• Confidence or forecast cone around future metric points.
• Horizontal target or threshold lines.
• RAG colour on milestone markers to reflect delivery status.
• Annotation badges on the metric line for outliers or special causes.
• Secondary metric plotted as a thinner line (e.g., cost vs quality).