Capability-Maturity Ladder Timeline

1  Slide Type Name
Capability‑Maturity Ladder Timeline

2  One‑Sentence Purpose Statement
Shows “how our capabilities climb from basic to optimized levels over time—and where we are on the ladder today.”

3  Visual Description (Designer Instructions)

• Lay out a 16 × 9 slide with the time axis running left‑to‑right across the bottom third.
• Above the axis, draw a stepped “ladder” that ascends vertically through 4‑5 maturity stages (e.g., Initial → Managed → Defined → Quantitatively Managed → Optimized). Each stage is a horizontal platform spanning a period of time; the next stage begins at a higher Y‑level, creating a staircase shape.
• Use distinct, progressively darker shades of a single brand colour for each maturity platform; label the stage name inside or just above the platform in 11 pt bold.
• Mark the start and end date of each stage on the horizontal extensions, aligning them to the shared time axis below. Optionally include milestone icons or gate symbols at the step‑ups to indicate audits, certifications, or management reviews that unlock progression.
• Add a vertical “Today” line that intersects the current platform and extends down to the time axis, accompanied by a badge reading “Current Level”.
• If multiple capabilities are tracked (e.g., Data, Security, Automation), stack 2‑3 parallel ladders side‑by‑side, keeping the same Y‑scale so maturity levels align visually.
  
• Reserve the top 15 % of the slide for a headline and a small legend explaining colour coding. Ensure text and steps do not touch slide edges; maintain ≥ 0.5 in margins.
• Fonts: sans‑serif; stage labels 11 pt, time‑axis dates 9 pt, milestone call‑outs 8 pt.

4  Business Questions This Slide Answers

• Which maturity stage have we reached, and when did we achieve it?
• How long did—or will—each stage last?
• What steps/gates trigger advancement to the next level?
• Where are capability gaps most acute across different domains?
• Are we on track to hit the target maturity by the deadline?

5  When to Use (Typical Situations)

• Digital‑transformation roadmaps showcasing capability uplift.
• Security or data‑governance programmes moving through compliance tiers.
• Process‑improvement initiatives adopting CMMI or ITIL maturity frameworks.
• Operational‑excellence reviews comparing functions’ maturity trajectories.
• Board updates linking investment to capability advancement over time.

6  Core Data Fields Required

• Capability or domain name (if multiple ladders).
• Maturity stage names in correct ascending order.
• Start and finish dates (or planned dates) for each stage.
• Current date (“Today”) marker.
• Optional gate or certification events at stage transitions.

7  Optional / Advanced Data Fields

• Quantitative KPI targets per stage (e.g., defect rate ≤ 2 %)
• Owner or accountable leader for each stage.
• RAG or confidence indicator for stage‑completion probability.
• Cost or benefit estimate aligned to each maturity level.
• Benchmark line showing industry‑average maturity for comparison.