[chiefalchemist]

> The communicator is responsible for communicating effectively, either by writing, speaking, diagraming, messaging, or designing tools that clearly convey intent.

> Meetings are a last resort. Favor asynchronous communication first.

Yes, the sender is responsible, but the context always matters. The receiver has to be familiar with the sender, trust them, etc. I've seen first how "less meetings" can be applied to a fault. And the team members with average or below comm skills suffered, as did the rest of the team.

An entire team simultaneously in flow is a wonderful ideal, but the reality is that's very rare (read: often a waste of energy). Accept the friction, monitor what works and what doesn't, and operate around thst

[DevOpsy]

Just like everything else in software delivery, you are not aiming for perfection and ideals, but to continuously optimize and improve. You may never get there but that also doesn't mean you need to accept friction and not do anything about it.

"Fewer meetings" could indeed be applied to a fault (like everything else) but that's definitely not the aim, the aim is to optimize for async communication and have more substantial meetings with outcomes when you need to have them. And also, it is far more rare to work at companies where they don't have enough meetings, usually, it is the opposite.