Goal: migration and rollout
Reader: Programme leads sequencing a migration, cutover or rollout. Meta cluster: D — knowledge & expression Scenarios: 7 · Examples: 7
Scenarios
| Scenario | Tier | Engines | Example files |
|---|---|---|---|
| migration programme | T2 | plantuml | cloud-migration-programme.md |
| work breakdown | T2 | plantuml | work-breakdown-structure.md |
| cutover window | T2 | infographic | migration-cutover-window.md |
| launch effort | T2 | infographic | launch-effort-curve.md |
| migration waves | T2 | infographic | data-platform-migration-waves.md |
| rollout phases | T2 | infographic | device-rollout-phases.md |
| service lifecycle | T2 | infographic | service-lifecycle-wheel.md |
Reading order
Waves for sequencing, cutover windows for the risky night, work breakdown for scope ownership.
Engines in this goal
infographic— template-driven boards, sequences and comparisonsplantuml— diagrams with icon families and UML/ArchiMate/BPMN semantics
Details, limits and anti-patterns: ../engines/infographic.md · ../engines/plantuml.md.
Palette
Every figure takes its colours from a theme. Pick one in
../styles/palette.md — the token contract, the theme index and the
per-engine blocks all start there.
Most figures in this set want Default. Depart from it for the medium, not the topic: Print when it may be photocopied, Contrast for low vision or large-print handouts, Vivid when it will be projected, Accessible when colour must not be the only cue, Editorial for long-form reading, Slate for technical reference, Pastel when the figure sits inside gentle prose, Nord for a cool Nordic register. Every theme is designed for a light ground — the set has no dark page.
Don't
- A migration plan without a rollback step
- Rollout stations that run in parallel drawn as a zigzag