← Back to principles

Platform

Actively Enable Fast, Predictable Flow

Statement

Actively Enable Fast, Predictable Flow

What this means in practice

Friction, handoffs, and repetitive manual steps are removed so software moves smoothly from code to running systems and can be changed safely and repeatedly. The platform team actively identifies and eliminates bottlenecks in the delivery pipeline, providing automated, reliable pathways that teams can depend on for consistent deployments.

Why this matters

Fast, predictable flow enables teams to deliver value frequently and with confidence. When flow is impeded by manual gates, inconsistent processes, or unreliable tooling, delivery slows, risk increases with larger batch sizes, and teams lose trust in the deployment process. Predictable flow is foundational to sustainable pace and continuous improvement.

Practices that meet this principle

  • CI/CD pipelines are fully automated from commit to production with minimal manual intervention

  • Deployment processes are repeatable, consistent, and well-documented

  • Lead time from commit to production is measured and actively improved

  • Manual approval gates are minimised and replaced with automated quality checks where possible

  • Platform changes are deployed using the same pipelines and standards as application changes

Validation

A project meets this principle when:

  • Software can be deployed to production through an automated pipeline

  • Deployments are repeatable and produce consistent results across environments

  • OR:

  • Teams can deploy independently without waiting for platform team involvement

Scoring Guide

  • Score −1 — Disagreement / Rejected: The team acknowledges this principle is applicable but has explicitly decided not to follow it for this product. A rationale and decision record exist explaining why enabling fast, predictable flow is not adopted.

  • Score 0 — Not doing: Deployments are manual, inconsistent, or require significant platform team involvement. No CI/CD pipeline. Lead time and deployment frequency are not measured. Manual gates dominate the process.

  • Score 1 — Planned: The team has committed work to enable fast, predictable flow. An owner and target date exist for introducing CI/CD pipelines, automated quality checks, and deployment metrics. The plan is tracked.

  • Score 2 — Adopted for new work: All new work is deployed through automated CI/CD pipelines with minimal manual intervention. Deployments are repeatable and consistent across environments. Lead time and deployment frequency are measured. Automated quality checks replace most manual gates. Any exceptions are explicit and reviewed.

  • Score 3 — Enforced for new work + migration plan: Fast, predictable flow is systematically enforced for all new work through process or tooling (e.g. mandatory pipeline standards, automated deployment gates). A tracked migration plan exists to bring legacy deployments and manual processes into the automated pipeline.

  • Score 4 — Fully adhered: Fully automated pipelines for all work including platform changes. Lead time and deployment frequency are tracked and actively improved. Teams deploy independently without platform team involvement. Manual intervention is eliminated or limited to exceptional cases. Deployment process supports continuous delivery with confidence. Remaining gaps are minimal, known, and time-bound.