There is a common saying that 80% of the project manager's job is communication. Frequently, many think that this communication is about working with team and writing status reports. On the contrary, most of this communication is working with both project management stakeholders and project team members. I always say that people's non-verbal communication carries more meaning. With various remote ways of working, it is important how the verbal and non-verbal communication play together in the leading people as the concept of communication is centered on five critical elements - clarity, correctness, completeness, cohesiveness, and conciseness.
Fortunately, I had my son who was studying linguistics in his college and sharing his thoughts on what he was learning. He mentioned to me that linguistics in a nutshell has five major elements which included phonology, morphology, syntax, semantics, and pragmatics. It was shocking to me how much language plays a pivotal role in leadership level communication and here are my connections on the influence of linguistics on project leadership.
Phonology: This area focuses on the study of sounds implemented within a language. It differs from phonetics where abstracts sounds that may or may not have any meaning associated. For instance, the letter "s" takes the sound of "z" while saying "cars". Particularly in verbal communication, this is very critical for people to understand each other as it lays the foundation for clarity. Especially when team members are from different culture or a technical communication channel is used with remote team members, clarity may be compromised and it is important for one to actively listen to avoid the risk of assumptions of what one thought they heard. In project meetings, I often ask people to summarize what their actions items are before meeting again and this helps me ensure that they heard me right.
I normally say, "writing is for the eyes and speaking is for the ears." However, even with written reports, if project managers do not think through how the report will sound to others, then, they may risk misinterpretation. Therefore, taking the time to read out the reports aloud eliminates how the report may sound to someone.
Morphology: This area focuses on the study of words within a sentence. The history of culture itself may influence how words are formed differentiating agglutinative, fusional, and polysynthetic structure. Now, just like morphology builds on phonology, I see correctness in project communication builds on clarity. When relying on bad news such as schedules delays, cost overruns, or resource challenges, the appropriate placement of words in the sentence may assuage fears. In other words, I feel that morphology addresses the "What's in it for me?" types of questions in both the verbal and non-verbal communication.
Syntax: This area focuses on the study of sentence formation with words and punctuations. Using an example of a syntax tree, the different parts of the sentence are constructed. I recalled how the lexical analysis was integral in computer science in assemblers, interpreters, and finally compiler design in computer science. To me, this syntax builds on morphology for larger level decision-making. For instance, the connections of various elements in project charter, the strategic connections between project charter and the business case, and the connections between business requirements document and functional specifications document are all examples of syntax analysis required for "completeness" in communication through the multiple artifacts.
Semantics: This area focuses on the study of meaning. Since meaning is interpreted by people, culture comes into play. This culture may not necessarily be limited to geographical cultures (e.g.: Hofstede Dimensions) but also role specific communication. For instance, the type of meaning people associated with words among various people. A business analyst sees "value" to be with customer where as the same "value" is connected with technical stability by a systems engineer. We can see how project delivery members mix up the words "iteration" from Agile and "sprint" from Scrum. The semantics elements therefore plays a critical role in push, pull, and interactive communications because of their use either for dissemination of information (broadcasting) or for alternative generation (brainstorming) for problem solving or decision-making, the concept of semantics brings "cohesiveness" in communication. So, semantics must be considered excessively by project managers to lead others.
Pragmatics: This area is the study of the social aspects of language semantics. All the essential above elements are codified in informal or formal language registers and take on additional focus especially with many areas such as the dialect, age groups, respect, etc. For instance, generational considerations may have to be incorporated in both verbal and non-verbal communication differentiated in informal and formal communication. When conflict resolutions come up, groupthink behaviors may have to be addressed in favor of smoothing and collaboration approaches. During all these interactions, pragmatics avoids unnecessary confusions by focusing on "conciseness."
Interesting to see how much the discipline of leadership is critical for project leadership! What do you see?
