Program Atlas
A thematic map of how automation programmes become measurable — the layers we walk during a Program Analytics Baseline or scorecard design.
Layers we chart
Each layer answers one question. Missing a layer is how ghost programmes and inflated completion rates survive for quarters.
Catalogue & ownership
Which programmes exist, who owns them, and what business outcome they claim. Without this layer, analytics reviews argue about names instead of health.
Start & stage signals
Where work enters, which stages emit events, and which transitions stay silent. Silent stages are where throughput maps go blind.
First-pass vs eventual
Whether completion means the first attempt or any later retry. Sponsors need both if overnight retries hide daytime failure.
Outcome markers
Terminal proof that the programme finished work the business cares about — not only that a queue drained.
Review cadence
Who reads which pack, on which Hong Kong windows, and which indicators earn a place every cycle.