What DevOps practice should an organization use when developing their application to help minimize disruption caused by bugs?

Pausing production until all bugs are eliminated is impractical and eliminates service availability, causing far greater disruption than the bugs themselves.

Large bugs in production are more complex and time-consuming to review, not easier, and waiting for them to appear increases risk.

Implementing small, incremental changes is a core principle of continuous integration and continuous delivery (CI/CD), limiting the blast radius of any single defect. Smaller change sets are faster to test, review, and roll back, directly reducing mean time to recovery (MTTR) when bugs are introduced. This practice keeps the application in a consistently releasable state and prevents large-scale disruption.

Batching large changes together makes it significantly harder to isolate the cause of a bug and increases the complexity and risk of any rollback.