E2E also has the potential of being a cross-team nightmare when multiple teams own individual components of a process rather than a single team owning the entir

E2E also has the potential of being a cross-team nightmare when multiple teams own individual components of a process rather than a single team owning the entire tech stack. So focusing on outcomes rather than output doesn't necessarily work because the teams doing the work are only given responsibility for an output. This is mostly an organizational problem but it does trickle down to the team level. And yah, it's not 'agile' which I feel like this post is just reiterating one of those pillars. I think this post glosses over the reality that tech workers primarily want to make things work correct, and they generally would write good tests (whichever kind that means for their problem) if they had the time and resources. But the final words seem to indicate doing a check on if the test is valuable... But that's not really where the problem or difficulty lies. It's often an organizational/team barrier (at least in the places I've worked) not a tech problem. And the commentary is often 'well this test is as good as we can do without engaging with all of these known pains'