• Building the Business Case
    • Choosing What to Automate
    • The Automation Maturity Model
    • Anti-Patterns and Failure Modes
    • Pipeline Design Principles
    • Automated Testing Strategy
    • Deployment Strategies
    • Release Orchestration and Rollback
    • IaC Principles and Tool Landscape
    • Module Design and Reuse
    • Drift, State, and Immutability
    • Policy as Code
    • The GitOps Operating Model
    • Progressive Delivery
    • Internal Developer Platforms
    • Golden Paths and Service Scaffolding
    • Automating Observability Instrumentation
    • Alert Design and Noise Reduction
    • Runbook Automation
    • Self-Healing and Auto-Remediation
    • Shift-Left Security in the Pipeline
    • Secrets Management Automation
    • Software Supply Chain Security
    • Compliance as Code
    • Where AI Fits in Operations
    • Agentic Workflows and Guardrails
    • AIOps and Anomaly Detection
    • Automating Code Review and Documentation
    • DORA Metrics and Beyond
    • Automating Change Management
    • FinOps and Cost Automation
    • Scaling Automation Across Teams
    • Chaos Engineering as a Reliability Practice
    • Error Budgets and the SRE Model
    • Trunk-Based Development at Scale
    • Zero-Touch Environment Provisioning
    • GitHub
  • to navigate
  • to select
  • to close
    • Home
    • Foundations
    On this page
    school

    Foundations

    Deciding what to automate, how far to take it, and which failure modes to avoid before writing any code.

    lightbulb

    Building the Business Case

    How to justify automation work in terms a budget owner will accept — and why 'it saves time' is the weakest argument available.

    filter_alt

    Choosing What to Automate

    A repeatable screening method for ranking automation candidates, and the categories of work that reliably repay the effort.

    stairs

    The Automation Maturity Model

    Five honest stages of automation maturity, what each one feels like from inside a team, and how to move up one level at a time.

    report_problem

    Anti-Patterns and Failure Modes

    The recurring ways automation programmes waste money or create new risk, with the specific countermeasure for each.


    © 2026 IT Automation Playbook. Built with Lotus Docs