Decision-Tree Timeline

1  Slide Type Name
Decision‑Tree Timeline

2  One‑Sentence Purpose Statement
Clarifies “what sequence of events unfolds under each possible decision or scenario, and by when.”

3  Visual Description (Designer Instructions)

• Set up a 16 × 9 slide with time running left‑to‑right along the top third; draw a thin horizontal axis with evenly spaced date ticks (weeks or quarters, depending on horizon).
• Place the initial milestone (Decision 0) on the axis. From this node, draw two or more diverging branches downward at a 30–40° angle—each branch represents a decision outcome (e.g., Regulator Approves, Regulator Rejects).
• On each branch, convert back to horizontal flow: plot subsequent milestones / tasks as small rectangles or diamonds, laid out in a true time sequence beneath the main axis. Label each with title + date in 9 pt text.
• When further forks occur, repeat: a new decision diamond, then branches showing alternate timelines. Keep branch angles consistent so the tree reads cleanly; use curved connectors or angled straight lines (1.2 pt).
• Colour‑code each branch path (maximum 3‑4 hues) to distinguish scenarios; match milestone boxes to branch colour but keep axis neutral grey.
• Add a vertical “Today” line intersecting the entire tree if status matters. Optionally annotate each path with probability (%) or NPV in a small badge near the branch stem.
• Reserve the top 15 % for the slide title and a legend mapping colours to scenario names; ensure no branch intrudes into this safe zone.
• Fonts: sans‑serif; branch labels 10 pt bold near the split; milestone text 9 pt; headline 16 pt bold.

4  Business Questions This Slide Answers

• What happens next if Decision A goes one way or the other?
• How long is the critical path for each scenario?
• Which contingent activities can start only after a specific decision point?
• What is the latest we can make a decision without sliding the schedule?
• How do cost, probability, or benefit differ across alternative timelines?

5  When to Use (Typical Situations)

• Regulatory approval planning with go/no‑go implications.
• Scenario‑based supply‑chain contingency timelines (e.g., port strike vs no strike).
• Capital‑project gating where design choice drives downstream tasks.
• Strategic option evaluation (acquire vs partner vs build).
• Crisis‑management playbooks outlining alternate response paths.

6  Core Data Fields Required

• Decision nodes (titles, dates).
• Branch labels (scenario name or outcome).
• Milestone titles and dates for each path.
• Current date (“Today”) if highlighting live status.

7  Optional / Advanced Data Fields

• Probability or confidence for each branch.
• Financial impact or cost per scenario.
• Owner or accountable team per branch.
• RAG status on milestones within each path.
• Cumulative duration or critical‑path indicator shown alongside each branch.