Digital Communication in Project Management

From apppm
Revision as of 12:54, 18 February 2022 by S183633 (Talk | contribs)

Jump to: navigation, search

Contents

Big Idea

Within the field of project management it is estimated, that project managers (PM) on average spend rougly 80% of their time on communication. [1] This explains why some refer to communication as the foundation of project management.[2]

Communication is the act of sharing and interpreting information across different project areas and interests. Communication is what holds together the people section of any project, but miscommunication can also be the downfall of any project which otherwise could have turned out successful.

The team members within any project rely on the ability to collaborate, share, gather and interprete knowledge and information to carry out the objectives of any project - hence, they rely on the ability to communicate. [3]

However, in recent times, ways of communicating when carrying out projects have undergone severe changes due to the consequences of the concurrent and ongoing pandemic, COVID-19. It is still unclear what all the consequences of these changes are, but patterns are emerging and it seems that at least some of these will be sustained. [4]

Although the digital tranformation is something that has been an ongoing trend in many facets of project management since the invention of the internet, COVID-19 has made its impact on the way we communicate within project teams. COVID-19 has not only inducted changes of consequential character. [4] New ways of communicating within projects are emerging and they propose new implementations and applications of existing communication practices. Project team members are experiencing these changes differently and it can be difficult to generalize these perceivings into implementable changes. However, an common emerging pattern is that projects and projects management will have to adjust to an everyday life with more digital communication and PMs will have to adjust to an everyday agenda with a more digital characteristic or at least with the possibility of communicating digitally with some frequency.

Communication in Project Management

When addressing communication in project management, it is relevant to first understand the basic mechanics of this.

"Communication is the process of acquiring all relevant information, interpreting this information and effectively disseminating the information to persons who might need it. Communication is of vital importance to everyone involved in, and influenced by, projects.[5]"

Communication Processes

Within project management, most communication will follow the interactive communication model; a sender encodes a message that is transmitted through a medium to a receiver that decodes the message and the receiver will in most cases will provide feedback on this message. This process happens both verbally and non-verbally, and it has been argued that the feedback on the message is of key importance to any PM, as it enables the PM to monitor the success of a communication process. The feedback will in this case be a confirmation of understanding from the receiving part [3]. Some non-verbal communication might, however, take the form of linear communication, where the feedback is not a necessity, i.e. informative e-mails or simple instructive messages.

Interactive Communication Model [6]


Characteristic for the interactive communication model is, that both the encoding and the decoding of the message depends on both parties' field of experience. People have different knowledge, behaviors, beliefs, situations, psychological factors, etc., and this might influence the effectivity of the communication. For the sending part, this defines the encoding, i.e. the content of the message, and for the receiving part this shapes the decoding of the message, i.e. the interpretation of the content. [7] This is something that a PM with a wish to attain effective communication must take into account when formulating communication.

This way of perceiving communication between two parties was developed by Browaeys and Price [8] and it introduces the idea that the content of the message itself and the channel by which the message is transmitted is influenced by the sender's current knowledge, experience, language, thinking and communication style as well as stereotypes and relationship to the receiver. Similarly for the receiving part, this influences the interpretation of the message. Browaeys and Price refer to this as "Cross-Cultural Communication".

Apart from the interactive communication type, two methods of communication will be mentioned; namely push and pull [8]:

  • Push:
Push communication is one-way communication that can take the form of one-to-one or one-to-many. Push communication is normally used when sending out emails, memos, reports, and so forth. The downside of push communication is that it inhibits the immediate ability to assess reactions and interpretations. This means, that it should be used carefully and with deliberate, clear intention.
  • Pull:
Pull communication can be viewed as the counter-part of push communications. It happens when a stakeholder seeks information through intranets to find templates, ongoing documentation or repositories. Pulling information is applied to sense the concerns/interests of stakeholders.

The big question in communication within project management is to make sure that it reaches all intended parties with the intended interpretation to avoid misunderstandings. The simple answer as to how to achieve this is simply to plan the communication. However, the reality of this might not be as easily simplified.

Planning Project Communication [3]

Because if the immense importance of communications within project management, it is of key relevance for the PM to actively and deliberately choose the right way of engagement with stakeholders, i.e. project members, external shareholders, and any others with relation to the project.

Communication Plan

The DS/ISO 21502: Guidance in project management [9] dictates that the PM must plan the communications to match the needs and expectations of the stakeholders and to include feedback mechanisms. Communications needs to be specifically directed, e.g. through campaings or events, at well-chosen audiences with a well-defined purpose and message.

It also states that the focus of communications should be at supporting project objectives by [8]:

  1. "increasing understanding and coorporation among varius stakeholders
  2. providing timely, accurate and unbiased information
  3. designing communication to minimize risk"

The PM has the responsibility not only to establish the organisational structure of the project to enhance project team creation but also the communication plan and lines of communication. Zulch argues that the communication plan should outline the following:

  • Who:
Lines of communication, responsibility and authority and involved parties
  • What:
Communication scope and form
  • When:
Primarily scheduling communication
  • Feedback:
How and when, document control
  • Filing/documentation:
For retrieval, backtracing, storing
  • How:
What type of information for what purpose?


After developing this communication plan, Zulch advises that consensus around it is achieved to provide a clear sense of direction to all related parties - and in particular when project complexity rises. Zulch also argues that the primary focal points of the communication plan are; keeping key stakeholders in the loop at all times, and promoting the project.

Including and engaging the right stakeholders in the right way is essential to any project. Since project teams is in fact a collection of stakeholders and since stakeholder engagement heavily relies in interpersonal relations, considerations on the engagement should be carefully included in the planning of communication. Stakeholders are actively engaged throughout the project to minimize negative impacts and to maximize positive impacts. [8]

By making a such agreement, the PM and the stakeholders formalize and streamline the intentions of all parties. The agreement becomes a project artifact that can be used at any given time and will provide guidelines throughout the project. By formalizing it even further and transforming it into a contract, the artifact becomes a mutually binding agreement that obligates all parties to uphold the terms agreed upon which at certain times may be practical to serve as a reminder of where the responsibility lies. [8]

Lines of Communication

Zulch divides the lines of communication in two primary categories; formal and informal communication.

Formal communitation:

Generally speaking, formal communication is any communication with a formal, project-related purpose. It happens in four directions:

    1. Downward communication: Flows from the top and down through project levels with the purpose of providing information on topics such as strategies, goals, or policies. It is likely to be filtered based on management intention with communication.
    2. Upward communication: Flows from lower levels and up to supply information. This is crucial to any PM!
    3. Horizontal communication: Happens between project members at adjacent levels and usually coordinates work efforts. This prevents tunnel vision within departments.
    4. Diagonal communication: Takes place between project members at different levels usually to provide relevant information on occasion.

The PM must be aware of these when planning the communication, since the positioning within the project authoritative hierarchy defines the method, content and intention with the communication, i.e. the PM must use different communication skills for different levels.

Informal communication:

Informal communication is mostly any communication without a formal purpose. It may be project-related but in most cases it constitutes the unofficial communication based on both facts and rumours. It can flow in any direction within the project organisation and uses the grapevine as its primary channel. Characteristic for this type of communication is that it takes place without the influence of the PM, but it is a fact that it affects the effetiveness of the communication from the PM.


Practical examples from both of these can be seen in the table below:

Practical examples of communications [8]

Modern Communication in Project Management

Communication as a general theme is something that has been reinvented numerous times over the past decades. Buzzwords to explain this revolution lies within globalization, and within the realm of project management it has become a standard to introduce work across borders in the project teams. This has made it a necessity for project teams to rely on digital communication methods, and, in recent time, this has especially been accelerated by the ongoing, global pandemic. It seems that industry is accepting workers' desire to have flexibility on location.

Ganis and Waszkiewicz [10] finds that project teams rely on "fast (real-time), reliable and easy-to-use communication tools, which helped them to connect them all at the same time". Ganis and Waszkiewicz finds that a interdisciplinary team cannot run in modern projects without effective digital communication, and that respective project teams should have the ability to choose the platform with which they base their communication. The platform should be flexible and user-friendly, and the team should have the option to change it, when their needs change, e.g. when the intention of the communication fits better with another platform.

Recent Changes

To assess the impact of the recent changes due to COVID-19, we present a case study of communications within a construction project. The study




Methods of application / Methods to tackle digital communication in project management

" Engaging stakeholders requires the application of soft skills, such as active listening, interpersonal skills, and conflict management, as well as leadership skills such as establishing the vision and critical thinking."

Systems thinking when planning

Pitfalls and shortcomings

Needs for communication is everchanging/metamorphobic

References

  1. Geraldi, Joana; Thuesen, Christian; Oehmen, Josef; Sting, Verena (2017), Doing Projects. A Nordic Flavour to Managing Projects, Engineering Systems Division, Management Engineering Department, Technical University of Denmark.
  2. Zulch, B. (2014):Communication: The Foundation of Project Management. Procedia Technology, 16, 1000–1009. https://doi.org/10.1016/j.protcy.2014.10.054.
  3. 3.0 3.1 3.2 BG Zulch, Communication: The Foundation of Project Management, Procedia Technology, Volume 16, 2014, Pages 1000-1009, ISSN 2212-0173, https://doi.org/10.1016/j.protcy.2014.10.054 (https://www.sciencedirect.com/science/article/pii/S2212017314002813)
  4. 4.0 4.1 Encinas, E., Simons, A., & Sattineni, A. (2021). Impact of COVID-19 on Communications within the Construction Industry. 2(Cdc), 165–156. https://doi.org/10.29007/lhs4
  5. Egeland, B. Project communication series: PM communication skills. [online]. Available from: <http://pmtips.net/project-communication-series-pm-communication-skills/>.; 2010.
  6. Llopis-Lorente, A., Díez, P., Sánchez, A. et al. Interactive models of communication at the nanoscale using nanoparticles that talk to one another. Nat Commun 8, 15511 (2017). https://doi.org/10.1038/ncomms15511
  7. https://study.com/academy/lesson/interactive-model-of-communication-definition-application.html [online]. Visited on: 16-02-2022 20:00
  8. 8.0 8.1 8.2 8.3 8.4 8.5 Project Management Institute, Inc. (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – 7th Edition and The Standard for Project Management. Project Management Institute, Inc. (PMI). Retrieved from https://app.knovel.com/hotlink/pdf/id:kt012LZF43/guide-project-management/effectively-engage-with
  9. Standard, D. (2021). Dansk standard Vejledning i projektledelse Project , programme and portfolio management –.
  10. Ganis, M. R., & Waszkiewicz, M. (2019). Digital Communication Tools as a Success Factor of Interdisciplinary Projects. Problemy Zarzadzania, 4/2018(77), 85–96. https://doi.org/10.7172/1644-9584.77.5
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox