Reframe it as risk, and let the decision-makers choose with full information. Risk-based testing gives testers and stakeholders a shared language: which areas are highest risk, what has been covered, and what has not, which also serves as a negotiating tool when time is short. Say what a quick pass would and would not cover, then offer options, such as a 30-minute smoke test of critical journeys, a longer targeted pass with an estimate, or release behind a feature flag or canary with monitoring. Record the decision and the accepted risks in the ticket or release notes. Your role is to make the risk visible, not to be the release gatekeeper.

Sources: Luxe Quality on risk-based testing, Testlio, BrowserStack on risk-based testing in agile