The three Cs of communication: Context, communicate, check

Communication is frequently listed as a core project management competency. It is less frequently treated as a delivery risk. Yet communication failure is one of the most consistent drivers of project problems, not because project professionals communicate too little, but because the communication that happens is often incomplete in a specific and correctable way. The message is sent. The understanding is assumed. The gap between the two is where projects get into trouble.

Why communication failure is a governance problem

Communication has long been recognised as a core project management competency. APM guidance emphasises the importance of stakeholder engagement, shared understanding and effective information exchange throughout the project lifecycle, while PMI research suggests that ineffective communication contributes to approximately one-third of project failures. The issue is rarely a lack of communication; it is a lack of shared understanding. Effective project communication is not simply about transmitting information, but ensuring that it is understood, acted upon and, where necessary, challenged.

These are not wording problems. They are context problems. In the AI era, as AI-assisted drafting, summarisation and status reporting become standard, the volume of project communication is increasing while the quality of shared understanding is not necessarily keeping pace. An AI system can produce a well-structured stakeholder update in seconds. It cannot know what the recipient needs to understand about the organisational history, unspoken constraints, stakeholder relationships or political dynamics that make the message meaningful. Context is what transforms information into understanding, and understanding is what enables effective decisions. 

1. Context: Say what you mean and why 

Context is the part of project communication that leaders and project managers most often assume others already have. They rarely do. Context answers the questions that turn information into meaning: what are we trying to achieve? Why does this matter now? What decision is needed, and by whom? What does success look like?

In project environments, shared language is a specific and underestimated risk. Words like ‘urgent’, ‘risk’, ‘done’, ‘delivery’ and ‘transformation’ are used constantly. They sound shared. They often are not. One team hears ‘urgent’ and mobilises resources today. Another adjusts their next sprint. Context is not background detail. It is the frame that turns project information into project knowledge. 

2. Communicate: Clarity is not simplicity 

Clear project communication is not about brevity. It is about saying what matters in a way the audience can act on. Effective project communication needs to make four things explicit: what is happening, why it is happening, what it means for this audience, and what action, decision or response is required. Omitting any of these creates space for misinterpretation.

Ambiguity in project communications does not leave a neutral gap. It leaves a gap that cognitive bias fills. Confirmation bias means people notice the parts of a message that support what they already believe. The practical test is whether a stakeholder who receives a project communication understands not just what is being said, but what to do with it. 

3. Check: Communication is not complete until it has landed 

The third C is the one most consistently missed. Communication in a project context is not complete when the message has been sent, the briefing delivered or the paper approved. It is complete when the message has been understood in the way it was intended. And that can only be established by checking.

Useful checking goes beyond asking ‘any questions?’ at the end of a meeting. It means asking: what have you understood the priority to be? What does this mean for your workstream? What is still unclear? What risks do you see that we have not discussed? These questions verify understanding and surface the information project managers actually need, but which team members will not volunteer unless they are specifically asked.

Communication in the age of AI 

AI tools are increasingly embedded in project communication: drafting stakeholder updates, summarising meeting outputs, generating reports. Used well, they accelerate delivery and improve consistency. Used without judgement, they create a specific risk: communication that sounds clear without creating shared understanding.

A well-structured stakeholder update generated by a language model will be grammatically correct and professionally formatted. It will not know what the stakeholder most needs to understand. Clarity of language and clarity of shared understanding are not the same thing, and AI can produce the former without the latter.

Practice checklist

• Establish shared language at initiation: Define what key terms mean for this programme. Document them. Return to them when interpretations drift.
• Communicate context, not just content: Every significant project communication should state purpose, intent, what action is needed and what success looks like, not just what is happening.
• Design checking into governance milestones: Build explicit understanding-verification into stage gate reviews, stakeholder briefings and team meetings. ‘Any questions?’ is not checking.
• Treat AI-generated communication as a draft: Human review for context, accuracy and appropriateness before sending. AI can produce clarity of language without clarity of shared understanding.
• Name communication breakdown as a delivery risk: Add it to your risk register. Identify where shared understanding is most likely to break down in your programme and address it proactively. 

 

You may also be interested in:

• How to Use Artificial Intelligence in Your Projects
• What is project communication?
• Discover project communication modules through APM Learning