We see this at Raygun with our Crash Reporting and Real User Monitoring products (measuring errors, and end user experience in general). Nearly all power users are more likely to be in product, or very senior/executive developers.

Very low engagement out of QA. I'm not sure if they just have a way they like to work, or they think that if they exist then no bugs make it to prod (don't laugh, plenty of our twitter adverts get comments from folks thinking you don't need any monitoring if you have a tester on the team or if a dev writes unit tests).

Understand how the end user experiences your software. That's the actual source of the truth.

That seems to work for Microsoft so far.

> The burden of ensuring software quality can be shifted to devs and PMs

This in itself is a not a problem, coming from an oncall minded company. You take care of code you write and you're given time budget to KTFLO.

i.e. Netscape.

It was a point of nerd pride on Usenet how well your operating system could handle a Netscape crash back in the day.