Method
A repeatable advisory cadence: sample reality, score readiness, leave a backlog your engineers can own.
1. Scope with honesty
We agree on one primary product surface, the on-call group involved, and the consoles we may read. Scope stays narrow so findings remain actionable instead of encyclopedic.
2. Sample signals and stories
We inventory metrics, logs, traces, and alert routes, then interview people who carried the last few incidents. Documents and lived experience both count.
3. Score and prioritize
Gaps receive severity based on user impact and recovery friction. You leave with a ranked backlog, not a vague maturity slogan.
4. Read out and rehearse
A live session aligns leads on owners and near-term drills. Optional follow-on workshops deepen signal design, runbooks, or facilitation skills.