Skip to main content

> Term

Release Friction

Any technical or administrative barrier that slows down, complicates, or discourages the process of shipping software.

Detailed Explanation

Release Friction encompasses slow CI builds, flaky tests, mandatory Change Advisory Board (CAB) meetings, manual QA phases, and convoluted deployment scripts. It measures how painful it is for an engineer to push a change to users.

Why It Matters

High release friction encourages developers to batch large changes together, which dramatically increases the risk of catastrophic deployment failures.

Common Failure Mode

Adding more process (like extra manual sign-offs) to prevent bugs, which actually increases release friction and results in larger, riskier deployments.

Practical Example

A minor CSS bug fix taking three days to reach production because it requires a manual staging deployment and VP-level approval.

Production Manifestation

Lengthy PR review cycles, code freezes, release branches that live for weeks, and engineers avoiding small refactors because releasing them is too hard.

Frequently Asked Questions

What is Release Friction in short?

Any technical or administrative barrier that slows down, complicates, or discourages the process of shipping software.

What is the most common failure mode?

Adding more process (like extra manual sign-offs) to prevent bugs, which actually increases release friction and results in larger, riskier deployments.

AI Summary

Any technical or administrative barrier that slows down, complicates, or discourages the process of shipping software. High release friction encourages developers to batch large changes together, which dramatically increases the risk of catastrophic deployment failures.