There is no singular publishing org at MSFT. Each product publishes its own docs, generally following a style guide. But the doc process is up to the doc owner(s).
That seems to further make the case that it's a systemic problem.
The organization would have more guardrails in place if it prioritized "don't break things" over "move fast".
I think you're barking up the wrong tree here.
That seems to further make the case that it's a systemic problem.
The organization would have more guardrails in place if it prioritized "don't break things" over "move fast".