Making quality ownership part of every release

The challenge: testing without release authority

When I joined, QA tested the product but did not have meaningful ownership of the release decision. The team belonged to a different business unit, and delivery could proceed without QA sign-off when a deadline arrived. Quality was treated as a dependency, and QA was often seen as a bottleneck.

I made the expectation clear: we would not release without QA sign-off. That decision gave QA both responsibility and accountability. It also meant supporting the team to improve how they worked, rather than simply adding an approval gate.

The change: authority backed by better practices

I supported stronger test cases, separate sprint and release regression cycles, and a higher bar for automation. Quality became part of engineering ownership alongside development and release management.

A late-added feature made the change tangible. QA challenged whether they could complete testing and sign off within the planned release window. We agreed to move that feature into a separate interim release. The major release shipped on schedule, and the feature followed after QA sign-off.

We met both commitments by making a scope and sequencing decision early enough to act on it. The QA team could raise a delivery risk and influence the plan.

The leadership work behind the process

I coached QA leads, technical leads, and release management to use data and information when making decisions. I gave them room to resolve blockers and own releases, supported by clear expectations and trust.

When mistakes happened, we focused on understanding and correcting them, then preventing a repeat. Over time, leads and engineers took greater end-to-end responsibility, and I needed to intervene less in daily delivery discussions.

What changed

We saw stronger feature delivery, release stability, and post-release support with roughly the same total engineering headcount. The mix evolved toward more QA and automation capacity alongside a smaller development team.

For me, predictable delivery comes from clear ownership and sound trade-offs. A release gate is useful when the people behind it have the authority, capability, and trust to make it work.