I'll give you a big reason why this behavior exists: people refuse to write high quality documentation regarding their systems/processes/etc. Or they are willing do it, but do an extremely poor job and are oblivious to its low quality. This will necessitate meetings to "Clear things up". And sometimes your documentation ticks all the boxes, but people get pissy about updating it because it's not in their preferred format and it rots away into irrelevance.
When I became an engineering manager I invested a ton of effort into providing solid documentation where people expect it: Swagger docs with real examples for our RESTful services for devs, confluence documentation for wider audiences, various guides and FAQs, and even in-repo ADRs. It probably saves us about 15 labor hours of meetings a week and maximizes my team's hands-on-keyboard time and minimizes interruptions.
When I became an engineering manager I invested a ton of effort into providing solid documentation where people expect it: Swagger docs with real examples for our RESTful services for devs, confluence documentation for wider audiences, various guides and FAQs, and even in-repo ADRs. It probably saves us about 15 labor hours of meetings a week and maximizes my team's hands-on-keyboard time and minimizes interruptions.