💡 On-Call Health & Toil Governance Planning Workflow

[github-actions[bot]]

Summary

A new guided workflow (owned by Morgan) for designing sustainable on-call practices and toil governance: on-call rotation optimization, toil budget definition and measurement, burnout prevention guardrails, team health metrics, and operational load balancing. The Incident Response workflow mentions on-call rotation as one subsection but does not address the people-and-process side of operational sustainability — a gap highlighted by data showing 70% of SREs cite on-call stress as a direct burnout contributor.

Market Signal

Nearly 70% of SREs cite on-call stress as a direct contributor to burnout, and 46% report responding to more than five incidents in the past 30 days. After five consecutive years of decline, toil reversed course in 2024–2025, indicating current approaches are failing. Rootly launched an "On-Call Health" burnout detector feature in 2026, signaling market demand for tooling in this space. Teams with explicit on-call compensation and recovery policies show 30% lower after-hours activity spikes post-incident. Google SRE best practice targets under 50% toil (elite teams target under 10%), but most organizations lack a structured way to plan and measure this. Traditional metrics miss the real experience — incident counts and MTTR live in dashboards, but cognitive fragmentation from repeated interruptions rarely appears in any report.

User Signal

The Incident Response workflow (CR) step-03 defines IC responsibilities and on-call rotation mechanics (who is on call, how to escalate) but treats on-call as an incident response implementation detail. It does not address: toil measurement methodology, toil reduction targets and tracking, on-call rotation fairness analysis, burnout prevention policies, team cognitive load assessment, or the governance process for deciding when to invest in automation vs. accept operational burden. These are core SRE domain concerns that Morgan is ideally positioned to guide.

Technical Opportunity

This workflow fits after Incident Response (CR) in the dependency graph — once response procedures exist, teams can design the sustainable operational model around them. It cross-references observability (for alert fatigue analysis and alert-to-incident ratio), incident response (for on-call structure and escalation paths), and capacity planning (for operational load vs. team capacity). It follows the same SKILL.md + steps/ + templates/ micro-file architecture.

Assessment

Dimension	Score	Rationale
Feasibility	high	Process-focused content workflow; fits the established multi-step pattern well; Morgan's SRE persona naturally owns toil and team health
Impact	high	Addresses a critical gap (70% burnout rate) that directly affects team retention and system reliability; no competitor offers structured toil governance planning
Urgency	med	Persistent problem with worsening trends (toil reversal), but no specific regulatory deadline driving adoption; urgency is team-health driven

Adversarial Review

Strongest objection: On-call rotation is already part of the incident response workflow. Splitting it into a separate workflow fragments the planning experience and creates confusion about where on-call decisions live.

Rebuttal: The incident response workflow defines on-call MECHANICS (rotation schedule, IC selection, escalation paths). This workflow addresses on-call SUSTAINABILITY (toil budgets, burnout guardrails, team health metrics, operational load distribution). The distinction parallels how infrastructure planning and capacity planning are separate workflows despite both involving compute resources. The 70% burnout rate proves that defining who is on call is necessary but insufficient — teams also need to plan how to keep on-call sustainable. This is Morgan's expertise in reliability engineering applied to the human system, not just the technical system.

Suggested Next Step

Draft workflow skeleton with Morgan as owner, covering: current toil baseline assessment, toil budget and reduction targets, on-call rotation fairness analysis, burnout prevention guardrails (recovery time policies, max consecutive on-call hours), team health metrics and dashboards, automation investment prioritization framework, and validation. Add to module-help.csv with menu code CH (Create On-Call Health) and dependency after:bgr-3-create-incident-response.