A change advisory board reviews all production changes. Engineering wants automated gates. What is the actual trade?

What the board provides

A human assessment of whether a change is safe, visibility across teams, a forum for surfacing conflicts, and an accountable approval. In principle it catches what automation cannot: novelty, business timing, and interaction between changes.

What it actually costs

• Batching. Weekly review means changes accumulate, and a large batched change is riskier than the small changes it comprises — the control increases the risk it exists to reduce.
• Superficial review. A board assessing forty changes in an hour is not assessing them. Approval becomes a formality with a record.
• Delayed feedback, so problems are found further from their cause.
• An incentive to batch further, since if approval is expensive, teams bundle more into each request.

What automation provides

Tests, security scanning, policy checks, progressive rollout with automated rollback, and evidence for every change. These are objectively better than human review for everything mechanical, and they operate on every change rather than on a sample.

The trade honestly stated

Automation is better at the mechanical and cannot assess novelty or judgement. The right model is risk-tiered:

• Standard changes — a pattern that has been executed safely many times — automated end to end, with evidence.
• Significant changes — new integrations, data migrations, changes to the control environment itself — human review, with a defined trigger so the classification is a rule rather than an under-pressure judgement.
• Emergency changes — a fast path with mandatory review afterwards.

The measure that settles the argument

Change failure rate and recovery time, by tier. If automated changes fail less often and recover faster than reviewed ones — which is the usual finding — the board is not providing the assurance it is credited with, and the conversation moves from opinion to evidence.