Framework Relationships

“How cycles, practices, evidence, and metrics connect.”

Read the Framework as a Loop

The framework has three moving parts:

  1. Cycles decide when work receives attention.
  2. Practices define how the work is performed.
  3. Metrics and evidence show whether it worked.

Diagram: Cycles schedule the practices; practices produce evidence; evidence changes the next cycle.

flowchart LR
    C[Cycles<br/>Daily / Weekly / Monthly] --> P[Practices<br/>How work is performed]
    P --> M[Metrics and evidence<br/>What happened]
    M --> C

Practice Map

This is a navigation aid, not a second definition of the practices. Detailed guidance lives in Chapter 6; metrics live in Chapter 7.

PracticeDailyWeeklyMonthlyPrimary evidence
Service Level ManagementWatch SLOs and error budgetsReview trendsRevisit targetsSLI history, SLO decisions
Incident and Problem ManagementRestore service and capture eventsAnalyze recurring causesFund systemic fixesIncident timeline, action items
Change and Configuration ManagementExecute approved changesReview failures and schedule workAssess major changesChange record, configuration history
Capacity and Performance ManagementWatch saturation and latencyAnalyze trendsForecast demandCapacity and performance reports
Knowledge and Documentation ManagementCorrect runbooks while using themReview gaps and share knowledgeSet documentation prioritiesRunbooks, ownership records
Team and Skill DevelopmentPair and hand off workCross-trainReview capability gapsSkills matrix, training outcomes
Vendor and Contract ManagementEscalate service failuresReview vendor performanceReview contracts and riskSLA results, vendor decisions
Release ManagementWatch deployments and roll backReview delivery performanceImprove release policyDeployment records, release metrics
Asset ManagementCorrect ownership and inventory dataReconcile changesReview lifecycle riskAsset inventory, lifecycle decisions
Service Request ManagementFulfill standard requestsImprove or automate the queueReview the catalogRequest history, catalog changes
Financial ManagementFlag anomaliesReview cost trendsForecast and allocate spendingCost reports, budget decisions
Backup and Recovery OperationsVerify jobs and handle failuresTest restoresExercise recovery plansBackup results, restore evidence

Not every practice needs a separate meeting in every cycle. Combine reviews when the same people, evidence, and decision are involved.

Start with the Symptom

SymptomConnect these recordsWhere to continue
Repeated incidentsIncident → cause → action → owner → due dateChapters 6, 7, and 11
Failed changesChange → deployment → service metric → incidentChapters 6 and 10
Audit panicControl → required evidence → artifact → reviewerChapters 10 and 13
BurnoutPage → alert quality → rotation load → improvement workChapters 7 and 9
Unexplained costAsset → service → owner → vendor or cloud chargeChapters 6, 7, and 12
Slow recoveryService → dependency → runbook → restore testChapters 6 and 10

Dependencies That Matter

Most practices can improve independently. Start with the dependency that blocks real work:

  • Service levels need measurable services and named owners.
  • Incident response needs trusted alerts, escalation, and usable runbooks.
  • Change and release management need service ownership and rollback evidence.
  • Capacity planning needs consistent telemetry and demand context.
  • Asset, vendor, and financial management need shared identifiers.
  • Recovery needs explicit RTO/RPO targets and tested procedures.

Avoid turning this into a fixed implementation sequence. A team with failing backups should not postpone recovery work because its service catalog is incomplete.

The Feedback Loop

Diagram: Daily evidence exposes recurring work; weekly review improves it; monthly decisions fund larger changes.

flowchart LR
    D[Daily work and incidents] --> W[Weekly patterns and improvements]
    W --> M[Monthly priorities and investment]
    M --> D

If a cycle produces meetings but no evidence, decision, or changed behavior, remove or redesign it. That is process theater, not framework adoption.


← Previous: Glossary | Back to Book Overview →