"Nothing ships without QA sign-off."
That sentence has done more harm to release cadence than any bug it ever caught.
A release process built around one person's signature at the end never speeds anything up. It moves the panic to Thursday afternoon and gives it a rubber stamp.
Alan Page and Brent Jensen put it plainly in their Modern Testing principles: the job of quality is to accelerate the team. A gate does nothing for the traffic behind it. It decides who gets stopped, usually at the worst possible moment.
Think of the bouncer outside a Wetherspoons at half eleven, solemnly checking ID on a queue of clearly-forty-five-year-olds. Everyone is fine and everyone is still queuing. Most QA sign-off steps work the same way: theatre performed on people who were never the risk.
In practice, accelerating looks like this:
- Testers sit in planning, not at the end of the pipeline, so risk gets caught in a conversation instead of a rejection.
- Feedback lands in minutes, not a Jira ticket that surfaces on Thursday.
- Testers coach developers to write sharper tests themselves, freeing the specialists for the genuinely hard, ambiguous work.
- Sign-off becomes unnecessary, because nobody is shipping anything a sign-off would catch.
Quality does not become invisible. It becomes earlier, cheaper, and the team's habit rather than your bottleneck.
A gate earns its keep only when everything upstream is broken enough to need catching at the end. Fix the upstream and the checkpoint turns into decoration, a laminated sign nobody reads.
The teams I would bet on are not the ones with the strictest gate. They are the ones who have forgotten they ever needed one.
into your process?
A QA Review finds the gaps in 1–2 weeks. From £1,200.