Vertical Milestone Stack

1  Slide Type Name
Vertical Milestone Stack

2  One‑Sentence Purpose Statement
Clarifies “what happens next” when milestones span a long time range or limited horizontal space by listing them sequentially from top to bottom.

3  Visual Description (Designer Instructions)

• Set the slide to a clean 16 × 9 canvas with generous left and right margins.
• Draw a single vertical axis (2 pt line) centered horizontally, running from 20 % down from the top edge to 20 % above the bottom edge; add a downward‑pointing arrowhead to indicate chronological flow.
• Place circular or diamond milestone markers on the axis, evenly spaced or proportional to the actual time gaps.
• Position the milestone date in a small, consistent format (e.g., “15 Aug 2025”) flush left of each marker.
• Extend a short horizontal leader line from each marker to the right, connecting to a rectangular call‑out box that holds the milestone title (one line) and, if space allows, a brief descriptor on the next line.
• Align all call‑out boxes along a common right margin to form a neat column; maintain 0.4 line spacing between boxes to preserve readability.
• Use one corporate accent color for markers and leader lines; keep text and axis in dark neutrals.
• Optionally add a shaded highlight or bold outline around the “current” milestone to signal progress.

4  Business Questions This Slide Answers

• What are the upcoming milestones and their sequence?
• How much time separates each major event?
• Which milestone is currently active or next in line?
• Have any deadlines moved since the last review?
• Where are there potential bottlenecks caused by milestone clustering?

5  When to Use (Typical Situations)

• Work‑stream reviews when the schedule spans many months or years
• Board or steering‑committee updates where horizontal space is already occupied by other elements (e.g., financial charts)
• Agile ceremonies that need to show multiple sprint reviews in a compact form
• Regulatory programs with long lead times and many approval gates
• Historical timelines that list achievements over decades

6  Core Data Fields Required

• Milestone dates (exact or period)
• Milestone titles
• Chronological order of milestones

7  Optional / Advanced Data Fields

• Status indicator (e.g., RAG color, check mark, “In progress”)
• Owner or responsible team initials
• Confidence level or risk flag for each milestone
• Expected benefit or KPI achieved at each point
• Percentage complete bar alongside each call‑out