• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Operational tasks are automated before they become recurring toil

Purpose and Strategic Importance

This standard ensures recurring operational tasks are automated before they become a burden, preserving engineering focus for high-value work. It helps teams scale sustainably and avoid burnout from repetitive manual effort.

Aligned to our "Automate everything possible" policy, this standard improves efficiency, consistency, and system reliability. Without it, teams risk wasted effort, growing technical debt, and reduced capacity for innovation.

Strategic Impact

  • Improved consistency and quality across teams
  • Reduced operational friction and delivery risks
  • Stronger ownership and autonomy in technical decision-making
  • More inclusive and sustainable engineering culture

Risks of Not Having This Standard

  • Slower time-to-value and increased rework
  • Accumulation of inconsistency and process debt
  • Reduced trust in engineering data, systems, or ownership
  • Loss of agility in the face of change or failure

CMMI Maturity Model

Level 1 – Initial

Category Description
People & Culture Teams accept toil as unavoidable.
Manual, repetitive work dominates operational tasks.
Process & Governance No process exists to identify or reduce toil.
Repetition is tolerated without challenge.
Technology & Tools Automation tools are unused or unknown.
Manual scripts are scattered and unmanaged.
Measurement & Metrics No visibility into frequency or cost of toil.
Automation efforts are unmeasured.

Level 2 – Managed

Category Description
People & Culture Some individuals automate tasks on their own initiative.
Awareness of toil emerges across teams.
Process & Governance Reactive automation occurs when issues become painful.
No formalised mechanism for prioritising toil reduction.
Technology & Tools Basic scripts or ad hoc tools used for repetitive jobs.
Reuse and documentation are limited.
Measurement & Metrics Toil is acknowledged in retrospectives.
Tracking is ad hoc and team-specific.

Level 3 – Defined

Category Description
People & Culture Teams prioritise toil reduction as part of sprint planning.
Collaboration occurs around shared pain points.
Process & Governance Toil is tracked and proactively identified.
Clear process to flag and automate repetitive work.
Technology & Tools Automation is implemented using reusable patterns.
Teams contribute to shared tooling libraries.
Measurement & Metrics Teams measure task frequency and automation ROI.
Improvement trends are reviewed regularly.

Level 4 – Quantitatively Managed

Category Description
People & Culture Teams embed automation thinking into development and operations.
Toil metrics influence team health reviews.
Process & Governance Governance frameworks include toil thresholds.
Roadmaps reflect automation targets and ownership.
Technology & Tools Tooling supports automation-at-source and telemetry.
Shared services are enhanced based on toil data.
Measurement & Metrics Automation coverage, manual effort, and task duration are all tracked.
Reports inform investment decisions.

Level 5 – Optimising

Category Description
People & Culture Automation is celebrated and continuously refined.
Toil reduction is part of cultural norms and onboarding.
Process & Governance Feedback loops refine standards and practices.
Cross-team initiatives share automation improvements.
Technology & Tools Tooling evolves through internal and open-source contribution.
Proactive alerting on new recurring toil patterns.
Measurement & Metrics Toil is minimised and tracked to near-zero.
Automation ROI is visible across the organisation.

Key Measures

  • % of recurring tasks automated
  • Frequency and duration of toil tasks per team
  • Time saved through automation
  • % of teams actively tracking and reducing toil
  • Number of automation-related incidents or failures
Associated Policies
Associated Practices
  • Self-Healing Systems
  • Runbooks and Playbooks
  • Drift Detection & Correction
  • Log Correlation for RCA
  • On-Call Rotation Health Checks
  • Health Checks & Readiness Probes
  • Security Testing in CI/CD
  • GitOps
  • Continuous Delivery (CD)
  • Continuous Deployment
  • Continuous Integration (CI)
  • Shadow Testing in Production
  • Ensemble Testing
  • Test Data Management
  • Load & Performance Testing
  • Operational KPIs for Dev Teams
  • InnerSource Development
  • Twelve-Factor App
  • Developer Environment Automation
  • Observability-Driven Design
  • Async Collaboration Norms
  • Code Reviews & Pull Requests
  • Immutable Infrastructure
  • Data Mesh
  • Serverless Architecture
  • Infrastructure as Code (IaC)
  • Security as Code
  • Configuration as Code
  • Compliance-as-Code
  • Deployment Freeze Windows
  • Deployment Pipelines
  • Automated Rollbacks
  • Feedback Loops from Ops to Dev
  • Automated Incident Response
  • Real-time Event Streaming

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering