Make the expectation explicit
Track the effort by category across a real release. Find a journey where an understandable visual workflow could reduce repeated authoring and handoff work.
Put it into practice
Run that journey in AuraCheck alongside the current test. Compare the time required to explain and resolve a failure, not only the number of lines of code.
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.