Ops Signal Atlas
A field map of business analytics for developer operations insights — where each signal lives, who should own it, and which programme teaches the craft.
Layer one
Pipeline truth
Commit-to-production timestamps, flaky-test tax, and blocked merge queues. These feed Foundations first — you cannot brief executives on lead time until the clocks agree.
Open Foundations
Layer two
Customer-visible wait
Support queues, refund tickets, and failed callback rates aligned to release notes. Incident Cost Mapping teaches the pound translation; Studio teaches which charts to retire.
Open Cost Mapping
Ready to practise on your own timeline?
Browse the catalogue or write to the desk with a decision you cannot currently evidence.