Swim-lane (Multi-Stream) Timeline

1  Slide Type Name
Swim‑lane (Multi‑Stream) Timeline

2  One‑Sentence Purpose Statement
Shows “what happens when, and by whom” across multiple work‑streams—letting the audience see interactions, overlaps, and hand‑offs at a glance.

3  Visual Description (Designer Instructions)

• Use a 16 × 9 slide with a clean white background.
• Divide the content area into horizontal lanes of equal height (typically 4–6 lanes). Tint each lane with a very light gray band to differentiate rows without overpowering the content.
• Left‑justify a bold lane header (work‑stream, function, geography, or product) inside a colored pill or a boxed label; align all headers vertically for easy scanning.
• Run a single, full‑width time axis along the top edge of the lanes. Segment it into equal intervals (weeks, months, quarters) with thin gridlines extending downward through all lanes. Place interval labels above the gridlines in 10‑pt gray text.
• Within each lane, place milestone markers (filled circles or diamonds) exactly at their date positions on the grid. Connect related milestones with thin arrows if dependencies exist.
• If tasks span a duration, draw slim horizontal bars between start and end dates within the lane, filling them with a muted corporate accent color. Keep bar heights identical for consistency.
• Optionally insert a bold vertical “Today” line across all lanes in a contrasting color to anchor viewers in the schedule.
• Maintain generous horizontal padding between milestones; avoid stacking symbols in the same vertical slice. Use a sans‑serif font and limit color usage to the lane headers, milestone markers, and “Today” line.

4  Business Questions This Slide Answers

• Which teams/functions are doing what—and when?
• Where do work‑streams overlap or risk collision?
• Are dependencies between functions clearly sequenced?
• How does progress in one lane affect downstream lanes?
• What remains to be completed before a common milestone (e.g., launch)?

5  When to Use (Typical Situations)

• Program‑management reviews covering several concurrent tracks (tech, ops, legal, comms).
• Product‑launch plans where marketing, engineering, and supply‑chain timelines must align.
• Regional roll‑outs showing staggered go‑live dates by geography.
• Transformation roadmaps that map initiatives across “people, process, technology.”
• Executive dashboards that need a one‑page view of cross‑functional cadence.

6  Core Data Fields Required

• Lane name (work‑stream / function / region).
• Milestone date and title—or task start and finish dates for duration bars.
• Overall project time scale (start and end dates).
• Dependency links (arrow from predecessor milestone to successor).

7  Optional / Advanced Data Fields

• Milestone owner initials or team icons.
• RAG status or %‑complete shading on duration bars.
• Benefit value or KPI target noted beneath key milestones.
• Critical‑path highlight for milestones that gate others.
• Confidence level or risk flag (e.g., ⚠, ✓, ?).