LEARN. PRACTICE. GROW.Describe the required outcome
A fictional fund service needs application recovery, renewal of the connection identity, and batch validation. Start by describing these tasks and the outcome that establishes completion. In the exercise matrix, Ana and Bruno restore the application; only Ana renews the identity; Bruno and Carla recover batch processing. If Ana is absent, two tasks retain nominal coverage while the third has a gap. Team headcount does not reveal that distinction. Record practice evidence by task, procedure version, and the conditions under which it was observed. The matrix organizes discussion and identifies dependencies. It is neither an overall ranking of each person’s value nor automatic production authorization.
Check combined conditions
Add availability and authorization to observed capability. Bruno may have completed a rehearsal while still awaiting approved access for Saturday’s window. An accurate record retains both facts. Next check concurrency: recovery and validation require two distinct people in the same interval, but only Ana has demonstrated both. Every task has a name although the combined assignment is infeasible. Duplicating Ana in a calendar creates no second person. In the laboratory, an enumerator searches assignments to distinct people and finds none in this configuration. If Bruno demonstrates validation and is available and authorized, a feasible assignment exists. The model checks only supplied rules. It does not decide competence, assess fatigue, or certify an actual rotation.
Delegate with usable boundaries
Manager backup requires more than calendar access. Prepare pending decisions, expected outcomes, boundaries, contacts, and escalation, then confirm understanding with the person taking over. In the exercise, delegation covers low-risk test changes until 18:00 UTC. A production request exceeds the delegated environment even at low risk. Approval exactly at 18:00 also fails the explicit rule now < expires. That convention belongs to the fictional case and is not a general banking rule. The appropriate step is to obtain a decision from valid authority, or explicit new delegation where applicable. Do not invent authorization because the manager is absent. Record the actual decision and actual time, including the impact of waiting.
Revisit dependencies after change
Two backups may execute the same runbook while depending on one person to obtain a credential. Examine that complete path before declaring redundancy. The solution must respect applicable access procedures without copying secrets into shared documents or using colleagues’ personal accounts. Also bind evidence to version. If N+1 changes the identity step rehearsed in N, analyze impact and repeat affected steps with the necessary dependencies. Retain the earlier result as history. To close the case, present the service owner with the gap, options, required capacity, and acceptance condition. If rehearsal can become sequential rather than parallel, that change needs agreement and a revised duration forecast.
Task Demonstrated people
Recovery Ana, Bruno
Identity Ana
Batch Bruno, Carla
Ana absent -> identity gap
Recovery + validation exclusive to Ana -> no concurrent assignmentAna covers recovery and validation; if both roles require concurrency and exclusivity, per-task coverage is insufficient.
Common pitfalls
Confusing names with capability; duplicating availability; overlooking a shared credential dependency; extending delegation for convenience.
Related topics: Capacity and operational load · Readiness and learning
Coverage must work under the window’s conditions and within authority that was actually granted.
Reference: Engineering Management · GitLab Handbook 2026; DORA current five-metric model; SRE and engineering guidance reviewed 2026-09-30