Two committees, not one: authorizing pre-production and production

The problem with a single decision

A single committee decides before anything is installed. It approves a plan: tests in QA, a rollback document, a date. What it cannot see is how the change behaves in an environment that looks like production.

Two gates

DevGob's deployment flow has two: To Committee authorizes the installation in pre-production; To Committee Prod authorizes production once the change has been installed and validated in pre-production.

• The first gate checks readiness: the review, the QA results and the rollback plan.
• The second gate checks reality: the pre-production install evidence and acceptance.
• Each decision is recorded with its approver, its date and its minutes number.

Is it slower?

It adds one decision, usually minutes long when the evidence is complete. In exchange, problems found in pre-production never reach users, and the production approval rests on facts instead of expectations.

When one gate is enough

Low-risk standard changes may not need both. DevGob already classifies each change as normal, standard or emergency; dedicated paths for standard and emergency changes are on the roadmap.