Do your project meetings turn into debates about the project scope or intent of project tasks or deliverables? Do your customers really understand the project's status
Communicating between technical disciplines or between technical and non-technical parties has a high risk of misinterpretations simply because of the specialized nature of our professions. Adding buzzwords, acronyms and techno-jargon increases the risk of communication failures. Communications that is not understood is just noise. Communication that confuses your customer, makes them feel uneasy or erodes their confidence does little to help the customer's value proposition for your services.
How do people on your team understand each other? When you communicate with your teammates do they understand what you mean to communicate?
When you communicate with your customer do they really understand what you need them to hear?
How do you know they understand or don't understand?