Keep an eye on the bugs you find further downstream and your feedback times, and adjust this balance as required.
See if defects are creeping too far down the deployment pipeline due to heterogeneity in pipeline stages (unit tests, integ tests, manual tests, canary etc). Periodically evaluate whether to make stages more prod-like (incurring complexity, deployment slowness, infra costs in the process) to avoid misssing problems that only arise in more distributed/prod-like envs. Eg make sure test environments have critical clustering/replication in place of code changes can break them (example in text was data serialization--seen that bite teams late in the game before too).
