Then you have test execution, not assurance.
It is entirely possible to have a large test team and still reach the launch meeting with nobody willing to answer the only question anybody cares about: what do we know, what do we not know, and what happens if we go live?
If nobody can turn all that testing into a release view, that is an assurance problem we can help untangle without inventing another governance layer.
Running tests is not the final product
Tests produce evidence. Somebody still has to interpret it. That means understanding the critical journeys, the impact of remaining defects, important areas that were not covered, environment limitations, specialist risks and what the business can tolerate. The result should be a useful management test report, not just a list of executed cases.
The tester should not personally ‘sign off’ a business release unless that is genuinely their authority. But the test function should absolutely be able to say what the evidence supports and where it is weak.
If the answer is always ‘it depends’ followed by a twelve-tab spreadsheet, the organisation has paid for a lot of execution and very little judgement.
Check whether the team is actually allowed to give a view
Sometimes testers are not the problem. Reporting has been designed around neutral metrics. Delivery owns the narrative. Suppliers are measured on execution volume. Nobody has explicitly asked the test lead to provide independent assurance, and everybody is surprised when they do not.
Fixing that may require changing the mandate rather than hiring more testers. Test leaders need visibility of defects, environments, non-functional work, major delivery assumptions and operational readiness if you expect them to say anything useful about release risk.
Independence does not mean sitting in a separate tower
The person giving the assurance view can work closely with delivery without becoming responsible for defending the date. The problem starts when their performance is judged mainly on helping the release stay green. At that point the reporting model has designed its own conflict of interest.
A useful release view sounds like a human being talking
In a decent release meeting, the test lead should be able to explain which important journeys have strong evidence, what serious problems remain, which areas are still uncertain and whether the available mitigations make those risks tolerable.
They should also be able to say ‘we do not have enough evidence’ without being treated as obstructive. Delivery can still decide to accept the risk. What it should not do is rewrite the testing view until everybody appears to agree.
If you want an independent release view, we can review the evidence, speak to the people doing the work and give you a written recommendation in plain English. No ceremonial maturity model required.