• 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
    On this page
      • What this is
      • How the playbook is organised
      • How to read it
      • What this is
      • How the playbook is organised
      • How to read it
    home

    Overview

    A practitioner’s playbook of automation practices that are treated as best practice across IT — from CI/CD and infrastructure as code to incident response, security, and AI-assisted operations.

    school folder

    Foundations

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

    autorenew folder

    CI/CD Pipelines

    The delivery path from commit to production: pipeline design, test strategy, deployment patterns, and safe rollback.

    layers folder

    Infrastructure as Code

    Describing infrastructure in version-controlled code: module design, state and drift, immutability, and policy as code.

    hub folder

    GitOps & Platform Engineering

    Git as the control plane for running systems, and internal platforms that make the automated path the easiest path.

    monitoring folder

    Observability & Incident Response

    Automated instrumentation, alerting that respects on-call humans, executable runbooks, and self-healing systems.

    security folder

    Security & Compliance Automation

    Security controls that run in the pipeline: scanning, secrets, supply chain integrity, and compliance as code.

    smart_toy folder

    AI-Assisted Automation

    Where language models genuinely help operations work, and the guardrails that keep them from making things worse.

    insights folder

    Measurement & Governance

    Proving automation works, automating change control, controlling cost, and scaling practice across teams.

    collections_bookmark folder

    Case Studies

    Well-documented industry patterns examined for what genuinely transfers to other organizations — and what does not.


    © 2026 IT Automation Playbook. Built with Lotus Docs