Make the expectation explicit
Keep many fast unit checks, use integration tests for boundaries, and choose a focused set of user journeys for E2E. Prioritize revenue, access, and irreversible actions.
Put it into practice
Use AuraCheck for the selected interface journeys and inspect failures with the lower layers in mind. A UI failure can originate in the backend, test data, network, or environment.
Try this on your next release
Choose one journey, define the expected result, and inspect the evidence from a completed run. Expand the suite after the first test is useful.