OPERATIONS

Horizontal programme rollout timeline

This horizontal timeline shows the sequence for a program that moves from discovery to a small pilot and then to a wider rollout. It begins by selecting pilot sites, followed by local-team training and a pilot-start milestone. Expansion is not automatic: the approval milestone makes the decision gate visible. The final rollout and programme review complete the path. A left-to-right layout makes the order easy to follow in a slide or status meeting. This example works for operational deployments, new services, or internal process changes. Add owners, budget decisions, and dependencies in the supporting plan when the program requires more delivery detail.

UPDATED 2026-09-24
EXAMPLEHorizontal programme rollout timeline
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

A multi-site operational rollout.

Key decisions

  • Pilot first: A small launch tests the approach before expansion.
  • Training period: Local teams are prepared during the pilot.
  • Approval gate: Expansion follows an explicit decision.

When to reuse this

Use for a program that progresses from discovery through pilot and broader deployment.

FAQ

Frequently asked questions

Why run a pilot before rollout?01
A pilot tests the approach with limited scope before the organization commits to wider deployment.
What is an approval gate?02
It is a decision point that must be passed before the next phase starts.
When is a horizontal timeline useful?03
It is useful when a group needs to scan the sequence and duration of a program from left to right.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.