Launch-Pipeline Timeline

1  Slide Type Name
Launch‑Pipeline Timeline

2  One‑Sentence Purpose Statement
Clarifies “where each product sits in the launch funnel—from concept to sunset—and what comes next.”

3  Visual Description (Designer Instructions)

• Use a 16 × 9 slide with a vertical “pipeline” or funnel on the left and a horizontal time axis on the right.
• Pipeline Column (left 35 %): stack 4‑5 horizontal bands that represent launch gates—Concept / Validation → Alpha / Prototype → Beta / Pilot → General Availability → Sunset. Tint each band a progressively darker shade of the brand accent and label in 11 pt bold.
• Product Swim‑Lanes (right 65 %): for every product or feature, draw a slim horizontal bar that begins inside its current gate band and extends rightward to its expected GA date on the time axis. Position bars so they align vertically with the stage they occupy today.
• Place milestone icons (e.g., ✔ for gate approval, ▲ for risk) on each bar at the forecast gate‑exit dates; annotate with dates in 9 pt text.
• Add faint vertical guide lines for calendar quarters across the right side to give a sense of timing, but keep the left pipeline purely categorical.
• Include a vertical “Today” line cutting through the time‑axis section, intersecting all product bars; optionally shade the bar segments completed before today.
• Colour‑code product bars subtly (one muted hue per product family) or keep them grey so the stage‑band colours dominate.
• Reserve the top 15 % for a headline and a compact legend that explains bar colour meaning and milestone icons. Maintain ample white margins and avoid placing any bar text inside the funnel area.
  

4  Business Questions This Slide Answers

• Which gate is each product currently in, and when will it reach GA?
• Do any offerings cluster at the same gate, risking resource congestion?
• Which launches are at risk of missing quarter‑end targets?
• How long does each product spend in each gate (Concept, Beta, GA)?
• Where do we anticipate pipeline gaps or an end‑of‑life (sunset) wave?

5  When to Use (Typical Situations)

• Portfolio reviews of multiple product lines.
• Executive pipeline discussions prior to quarterly planning.
• Marketing calendar alignment across launches.
• PMO dashboards tracking gate approvals and commercialization pace.
• Risk reviews where slipping one product could cascade onto others.

6  Core Data Fields Required

• Product or feature name.
• Current gate/stage.
• Forecast exit date for each remaining gate.
• Final GA (or Sunset) date.
• Current date (“Today”) marker.

7  Optional / Advanced Data Field

• Gate‑approval status (Pending, Approved, Blocked).
• RAG or confidence rating for each forecast date.
• Expected revenue or strategic value at GA.
• Resource owner or squad responsible for each product.
• Link to deeper roadmap or backlog for each bar (interactive decks).