LEARN. PRACTICE. GROW.Concept and mechanism
A roster filled with names does not demonstrate operational capability. Recovering a service needs knowledge, access, tools, time, and an escalation route. When only one person knows the task, identify the dependency before absence or a critical window. Prepare another person through explanation, accompanied execution, and authorized rehearsal. The aim is observed capability rather than training-hour counts. In planning, subtract reserved work and absences without double-counting categories. One hundred person-days with 60 for RUN and 15 non-overlapping absence days leave 25 before other constraints. Those days are not automatically interchangeable among Oracle, network, and application skills.
Guided application
Shift-left can bring resolution closer to the request’s first contact when suitable capability exists. Define what L1 may do, which information it should collect, and when L3 is needed. A guide lacking version context or requiring unavailable access may increase repeat contacts. Measure effective resolution, total effort, and reopenings as well as fewer escalations. In this path’s pilot, the L3 queue shrinks while contacts double: that does not establish success. Correct knowledge and usage conditions before expanding. SRE guidance on rosters and readiness is complementary operational evidence; it imposes no universal team model, capacity percentage, or working schedule.
Before removing the weekend specialist, confirm the rostered person can execute the procedure and reach expected support.
Common pitfalls
Training as readiness; people as interchangeable skills; shift-left as rerouting; excessive privileges as autonomy.
Related topics: Information, automation, and integration · New service and operational transition
Transfer resolution capability and measure the effect on the complete service.
Reference: SRE Workbook: On-Call · ITIL 4 CDS; observed syllabus v1.0 mirror, 2025 update comparison pending