Our own company learned the truth about requiring an operations team the easy way - they hired some and their reliability went up. Outages started being handled before it impacted customers.
It's been fun watching the volume of "Oh Shit" emails dropping precipitously.
Identifying scope and purpose, and it's impact and documenting the design are just some of the things an platform operations team is -supposed- to take care of.
The largest problems of development have nothing to do with administering anything (edit: for example, bad design often results from bad design decisions that are neither prevented nor fixed by seeing that the required documents have been written.) The idea that Winslow Taylor's principles can solve these problems is a fallacy - a commonly held one, but a fallacy nonetheless.
Proper infrastructure engineers (or "site reliability engineers" as google now calls them) are key for helping architect highly available systems like this; Yet the trend seems to be forcing software engineers follow tutorials from google on setting up key pieces of infrastructure nowadays.
Edit: it's ettiquite to say why you're going to downvote someone, if what I said wasn't relevant please let me know.