it's real impact, but it requires folks to be able to confidently talk about counterfactuals—"we would have wasted X days if not for..."—which I've found to be really hard at most places
the exception was places where leadership already thought in the same terms about software quality/etc, which meant I didn't have to do much convincing :P
how would you build teams or structures to support that sort of holistic thinking about software?