Skip to content

Practices Overview

First PublishedLast UpdatedByAtif Alam

This section holds practices content — the human, process, and tooling patterns that surround the technical work covered elsewhere in the library. That includes how engineers plan software before coding, how platform teams plan delivery next to on-call, and how they communicate in incidents. Pages are written for senior engineers on infrastructure, platform, and SRE teams; titles and ladder levels vary by org but the practices generalize.

The library does not replace your organization’s training, ladder rubrics, or vendor-specific playbooks. It connects practice patterns to the rest of this site’s content (CI/CD, observability, Kubernetes, QA, AIOps, system design).

  1. Leadership and Mentoring — judgment and facilitation that cut across everything below.
  2. Technical Design Document — plan a change before you build (problem, scope, stack, risks).
  3. Agile for SRE and Platform Work — ship that work under interrupts and toil.
  4. Incident Tooling and Customer Communications — when production breaks, page, escalate, and communicate.
  • Leadership and Mentoring — Mentoring structures, coaching debugging methodology, feedback patterns, calibrating technical judgment, roadmap influence, and resolving cross-team prioritization conflicts.
  • Technical Design Document — Industry names for planning docs (PRD, design doc, tech spec, RFC, ADR) and a reusable fill-in template for planning software before coding.
  • Agile for SRE and Platform Work — Scrum and Kanban applied to interrupt-driven platform work, sprint commitments alongside on-call, toil budgets, ceremonies that help vs ceremony theater, and Definition of Done for infrastructure changes.
  • Incident Tooling and Customer Communications — On-call schedules, escalation policies, status pages (internal vs external), severity-driven customer comms templates, and stakeholder updates during long incidents. Pattern-first; vendor-second.
TopicWhere to Go
Reliability and qualityQA, QA reliability guide
Incident command and postmortemsIncident response and on-call
Pipeline guardrails for platform teamsCI/CD best practices
Service readiness before productionService readiness checklist
Large system design reviewDesign review checklist
System design foundationsSystem design