What is project communication management?
Project communication management is the discipline of planning, executing, and continuously adapting how information flows between the project manager, the team, stakeholders, and the project board. It encompasses the formal and informal channels of communication, the methods and cadence for different audiences, and — crucially — the skill of sensing what is happening beneath the surface before it reaches the surface.
The standard definition stops there. Henning Christiansen's framework in Project Management: The Red Pill goes considerably further. For Christiansen, communication management is the primary mechanism through which a project manager prevents chaos — not just transmits information. Once the technical routines of project management are mastered, communication is where the real complexity lives. It is where Monkey Poker starts, where conflicts ferment, where trust is built or destroyed, and where the difference between a Unicorn project manager and an average one becomes unmistakably visible.
"Communication is not just about sending out messages. It is about creating a calm and focused atmosphere for the project team, where they can fully concentrate on their tasks without distraction or confusion."
— Henning Christiansen, Project Management: The Red Pill
The seven principles of effective project communication
Christiansen defines communication not as a channel or a tool, but as a discipline with seven interlocking principles. Every one of them matters. Miss one and the others compensate badly — like a chain where every link except one is steel.
The three modes of project communication
Not all communication serves the same purpose, and not all communication channels are equal. Understanding what each mode is for — and what it cannot do — is foundational to building a communication plan that holds together under pressure.
If the project manager relies mainly on written communication, they risk losing insight into stakeholder attitudes entirely. Written communication makes it almost impossible to accurately interpret opinions and emotions. More critically: a stakeholder who is dissatisfied but does not wish to express it openly will be extremely cautious about committing to writing. You will not see their dissatisfaction coming — until it arrives as an escalation to the Monkey King.
The 7-38-55 rule: why words are almost irrelevant
In the 1970s, psychologist Albert Mehrabian published research that became one of the most cited findings in communication — and one of the most misunderstood. His 7-38-55 rule proposes that in emotional or interpersonal communication, only 7% of the message is carried by the words themselves, 38% by tone of voice, and 55% by body language.
Christiansen draws a direct implication for project managers: relying on written communication as the primary channel means operating with roughly 7% of the available information. The other 93% — tone, expression, posture, energy — is invisible. And it is precisely in that invisible 93% that you find dissatisfaction, hidden agendas, and the early signs of Monkey Poker before it breaks into the open.
It means noticing the pause before the answer. The slight shift in energy when a topic changes. The team member who is usually engaged but sat with arms crossed the entire meeting. The stakeholder who sends one-line replies to messages that previously prompted paragraphs. None of this shows up in a status report. All of it is communication.
Tailoring communication to each stakeholder
The project communication plan is not a broadcast schedule — it is a stakeholder-by-stakeholder map of who needs what, in what form, at what frequency, and communicated in a way that actually reaches them. This requires understanding two things about each stakeholder: what motivates them, and how they process information.
Understanding motivation: Maslow in the project context
Christiansen draws on Maslow's hierarchy of needs to identify the four key areas that commonly drive stakeholder behaviour within a project environment. Understanding where each stakeholder operates in this hierarchy determines what they will respond to — and what they will use the project for.
Understanding communication style: NLP in practice
Once motivation is mapped, the next question is how each stakeholder processes information. Christiansen draws on NLP (Neuro-Linguistic Programming) to identify four primary communication styles — each requiring a different approach to reach the person effectively.
Building the project communication plan
The project communication plan is the documented strategy that codifies all of the above: who needs what, when, through which channel, in what format, and with what frequency. It is a living document — updated continuously as stakeholder dynamics evolve and as the project moves through its phases.
A project communication plan that only exists as a document produced at kickoff is not a communication plan. It is a filing exercise. The value of the plan is not in its creation — it is in its continuous use as the project manager's primary navigation tool for the political landscape of the project.
What the communication plan must capture
- Each stakeholder's primary interest and motivation — what are they actually looking for from this project?
- Their stakeholder type — Chameleon, Rooster, Honey Bee, Parrot, Monkey King? This determines their likely behaviour under pressure.
- Their communication style — visual, auditory, kinesthetic, or logical?
- Their preferred channel and frequency — weekly report, monthly board meeting, informal one-on-one, ad-hoc message?
- Known tensions and alliances — who is aligned with whom? Where are the fault lines?
- What they must not learn through informal channels — significant bad news that reaches a stakeholder via the rumour mill before it reaches them from the project manager destroys trust permanently.
- Trigger points — which developments will activate their personal agenda? Knowing this in advance means you can communicate proactively before the trigger fires.
A project manager who has a current, detailed communication plan knows where the political risk is before it materialises. When a Chameleon starts building alliances to push a personal agenda, the project manager who understands that stakeholder's motivation, style, and relationships can intervene early — with a one-on-one conversation that acknowledges their interests before they feel they need to escalate. The communication plan turns reactive crisis management into proactive relationship maintenance.
The communication cycle: a continuous loop
Effective project communication is not a schedule of events. It is a continuous cycle that the project manager runs in parallel with everything else. Christiansen describes this as a feedback loop: monitor, assess, respond, repeat.
The power of praise and recognition
One of the most underrated elements in Christiansen's communication framework is the explicit role of praise and recognition. Not as a soft management nicety — as a strategic communication tool with specific, measurable effects on project dynamics.
Effective praise serves two functions simultaneously. First, it elevates Honey Bees and Parrots — who are primarily motivated by security — into higher levels of engagement, where they become genuinely invested in the project's success rather than just performing their tasks. Second, it creates a team environment where Chameleons and Roosters find it harder to pursue personal agendas, because the culture of shared recognition makes individual visibility-seeking look small by comparison.
"Praise and recognition are not limited to formal feedback or public praise. They can also take the form of small, personal gestures. Stakeholders also want to be recognised as individuals, and when the project manager shows genuine interest in and remembers their personal priorities, it boosts their sense of value. Above all — be sincere or do not do it at all."
— Henning Christiansen, Project Management: The Red Pill
The Unicorn project manager gives the team five things consistently: a sense of purpose, trust and freedom to solve tasks their way, respect and inclusion, constructive feedback, and genuine appreciation for them as people — not just as workers. Each of these is a communication act, delivered through daily interaction rather than formal channels.
What to do — and what to avoid
- Build and continuously update a stakeholder communication plan
- Match the communication channel to the situation — face-to-face for sensitive conversations, written for formal decisions
- Communicate bad news early and directly — never let it arrive through informal channels first
- Listen actively to what is not being said: tone, energy, body language, silences
- Tailor every message to the recipient's motivation and communication style
- Establish a regular, predictable rhythm of updates so stakeholders never fill silence with assumptions
- Praise and recognise contributions genuinely and frequently — especially quiet, reliable work
- Communicate approved changes as shared successes, regardless of who drove them
- Follow up one-on-one after group communications — the real reactions happen privately
- Apply the Godfather rule in every difficult conversation: stay calm, composed, and evaluative
- Don't treat a communication plan as a kickoff deliverable — it must be maintained throughout
- Don't rely primarily on email to manage stakeholder relationships
- Don't deliver the same message in the same way to every audience
- Don't wait for problems to escalate before communicating — proactive communication is always cheaper
- Don't confuse being informed with being aligned — people can read every update and still not be with you
- Don't ignore the informal network — what people say in corridors matters more than what appears in reports
- Don't ignore seating dynamics in meetings — power positions affect who speaks with authority
- Don't give generic praise ("great job, team") — it is worse than no praise, because it signals you weren't paying attention
- Don't allow a Rooster or Chameleon to work the room before you do — their narrative takes hold quickly
- Don't skip the follow-up after a rejected change request — unacknowledged frustration becomes resentment
Case study: the 1941 Disney animators' strike
Christiansen uses the 1941 Disney animators' strike as a vivid illustration of what happens when communication fails not at the level of information transmission, but at the level of human dignity and recognition.
The strike occurred shortly after Disney moved its operations to a new studio in Burbank — a move that made visible, for the first time, the hierarchy between senior and junior animators. In the previous Hyperion Studio, such divisions had not been so obvious. The new physical environment made inequality concrete and undeniable.
The strike was publicly framed as a wage dispute. But its real cause was something deeper: a demand for respect, equitable treatment, and acknowledgment of individual contribution. Disney leadership appears to have genuinely believed they had created a family culture. They had failed to test that belief against employee reality. Most critically — they had failed to listen.
The lesson for project managers is precise: what people say a conflict is about is often not what it is actually about. A Rooster who raises quality concerns may actually be frustrated that someone else got the interesting work. A Chameleon pushing for scope expansion may actually be trying to build a relationship with a senior stakeholder they want to impress. Communication management means understanding the real motivation — and addressing that, not just the stated complaint.
Communication management in Proglar
Proglar supports the communication disciplines described in this article by connecting the project model, the change register, and the stakeholder record in a single platform. When a change request is submitted, logged, assessed, and decided upon, the decision and its rationale are immediately available to all relevant parties — creating the transparency that prevents the "no one told me" complaints that fuel political escalation.
Time tracking data and milestone status are visible in real time, which means the project manager can communicate progress proactively — backed by current data — rather than scrambling to compile a status report before each board meeting. The rhythm of communication becomes part of the project's operating infrastructure, not a manual effort mounted in parallel to everything else.
Communication clarity built into every project
Proglar connects your project model, your change register, and your stakeholder record — so communication decisions are backed by current data, not memory. Try free for 30 days.