I believe that I used to be guilty of this, as well. Maybe I still am, but I haven't gotten much feedback on it in a long while (and I try to elicit feedback on

I believe that I used to be guilty of this, as well. Maybe I still am, but I haven't gotten much feedback on it in a long while (and I try to elicit feedback on these things _very_ frequently -- weekly). What I've done is to take a step back and try to channel communications into asynchronous channels. I find it very challenging, if not outright impossible (again, this may just be me and my personality talking) to try to explain my thoughts and opinions in real-time in a room, or worse a video conference, where you're forced to make all manner of assumptions about other peoples understandings of what you are saying. When it goes async, you can lay out the foundation and point towards specific points in the sort of nuanced and context-rich environment that technical conversations demand. On the team that I lead, this looks like Slack, email, Confluence, and Jira. Decisions are distilled down from all of these sources and worked on in shared documents, maintained in a decisions log that people can be pointed towards to get a better understanding of the projects. This documentation is very useful for rooting out incorrect assumptions, inaccuracies, confusion, etc..., in the topics that we talk about. It takes a lot of work, of course, but I think the outcome is better. This team has much more cohesion and a higher degree of collaboration (as in boosting each other up vs. simple cooperation) than the other teams I've been part of.