A project can have a solid plan, a realistic budget and a talented team, yet still run into trouble because people are not communicating properly.
In my view, effective communication in project management is about much more than sending emails and arranging weekly meetings. It is about making sure the right people understand what is happening, what needs to happen next, who is responsible and where problems might be developing.
Think about a fairly common situation. A project team discovers that a deadline is likely to slip, but nobody tells the client because they are hoping to recover the lost time. A week later, the delay is unavoidable. The client is frustrated, senior management is asking questions and the team is suddenly under pressure.
The original problem was the delay. The bigger problem was the communication around it.
Research from the Project Management Institute (PMI) has highlighted just how important this is. PMI found that organisations with highly effective communicators completed 80% of their projects successfully, compared with 52% for organisations where communication was less effective. Its research also estimated that US$75 million out of every US$1 billion spent on projects was at risk because of ineffective communication.
So, if you are managing a business project, communication is not something to deal with when you have time. It is part of the job.
Why communication matters in project management
Project management involves bringing together people with different responsibilities, priorities and levels of technical knowledge. Someone has to keep those people moving in the same direction.
That is where communication comes in.
The Association for Project Management (APM) describes project communication as a two-way process involving stakeholders and recommends planning who communicates what, when, why and through which channels. It also emphasises the importance of feedback.
That two-way element is important.
Sending an update does not automatically mean you have communicated effectively. If your stakeholder reads your message and still does not understand what is happening, the communication has failed.
Good communication can help a project team:
- understand project objectives
- clarify individual responsibilities
- manage stakeholder expectations
- identify risks earlier
- resolve issues before they become serious
- make decisions more quickly
- reduce duplicated work
- build trust
- deal with changes more smoothly
In other words, communication helps turn the project plan into coordinated action.
What does effective project communication actually look like?
There is no single communication method that works for every project. A multinational transformation programme will obviously need a different approach from a small internal project involving six people.
However, the basic principles remain fairly consistent.
Start with the purpose
Before sending an email, scheduling a meeting or preparing a report, ask yourself one simple question:
What do I need this communication to achieve?
Perhaps you need a stakeholder to approve a change. Maybe the team needs to understand a new deadline. Perhaps you are reporting a risk that requires senior management’s attention.
Knowing the purpose makes it much easier to decide what information belongs in the message—and what does not.
For example, telling a project sponsor that a project is “70% complete” does not tell them very much. They may be more interested in whether the project is still within budget, whether the deadline is realistic and whether you need a decision from them.
Good communication focuses on what the recipient actually needs.
Understand your audience
One of the easiest mistakes to make is communicating with everyone in exactly the same way.
Your software developers probably need technical details. Your finance team may be more interested in costs and forecasts. A senior executive might only need to know about major risks, milestones and decisions.
This is where project stakeholder communication becomes particularly important.
APM recommends considering stakeholder interests, influence and communication requirements when developing an approach to stakeholder engagement.
I find one question especially useful:
What does this person need to know to do their job or make a good decision?
It stops you from sending information simply because you have it.
Choose the right communication channel
Email is useful, but it is not the answer to every communication problem.
A written message works well when you need a record of something or when the information is straightforward. A meeting or call may be more appropriate when a topic is complicated, sensitive or likely to generate questions.
Project-management and collaboration platforms are useful for keeping tasks, documents, discussions and decisions together.
The important thing is to establish some consistency. People should know where to look for project information instead of having to search through emails, chat messages and shared drives.
Atlassian’s stakeholder communication guidance also recommends defining communication channels, frequency and responsibilities rather than leaving communication to chance.
Make room for feedback
Communication should never be a one-way broadcast.
A project manager can provide a perfectly polished progress report while the team quietly struggles with a problem that has not appeared in the report.
Ask people what they are seeing. Give them an opportunity to disagree. Encourage them to raise concerns before those concerns become expensive problems.
Useful questions include:
- Is anything blocking your work?
- Have we missed a risk?
- Is the current deadline realistic?
- Is there anything unclear?
- Do you need a decision or additional support?
Sometimes the most useful information in a project is the information nobody initially wanted to report.
How to create a useful project communication plan
A project communication plan does not have to be a huge document.
For many projects, a simple table is enough to establish who needs what information and when.
Start by answering seven questions:
- Who needs the information?
- What do they need to know?
- Why do they need it?
- When should they receive it?
- How should it be communicated?
- Who is responsible for communicating it?
- How will you know whether the communication has worked?
For example:
| Stakeholder | What they need | Channel | Frequency | Owner |
| Project team | Tasks, blockers and dependencies | Team meeting/project platform | Weekly | Project manager |
| Project sponsor | Progress, risks and decisions | Progress report | Fortnightly | Project manager |
| Customer | Milestones and significant changes | Meeting/email | As required | Project lead |
| Finance | Forecast and cost variance | Financial report | Monthly | Project/finance lead |
| Senior management | Major risks and overall progress | Executive update | Monthly | Project manager/sponsor |
This is only a starting point. The communication approach should reflect the project.
A small project might need a handful of regular updates. A large project involving multiple departments, suppliers and external stakeholders will require a more detailed approach.
APM’s communication-planning guidance recommends considering the audience, information, timing, method and evaluation of communication, while also reviewing the plan as circumstances change.
If you want a practical template to work from, Atlassian also provides a communication plan template.
Communication changes throughout the project
The way you communicate at the beginning of a project should not necessarily be the same way you communicate during delivery.
During project initiation
At the beginning, people need clarity.
You should establish:
- why the project is being undertaken
- what the project is expected to achieve
- what is included in the scope
- who is responsible for key decisions
- who the main stakeholders are
- what the major assumptions and risks are
This is also a good time to agree how progress will be communicated.
Getting these basics right early can prevent plenty of confusion later.
During planning
Communication becomes more detailed during planning.
Team members need to understand their responsibilities, deadlines, dependencies and expected outputs. Stakeholders should understand how decisions will be made and how changes will be handled.
It is also worth agreeing where project documents and important decisions will be recorded.
Otherwise, you can end up with several different versions of the truth.
During project execution
This is where communication really earns its keep.
A useful project update does not need to tell stakeholders everything the team has done. It should give them enough information to understand the current position and act where necessary.
A straightforward update might cover:
- What has been completed?
- What happens next?
- Are we still on schedule?
- Has anything changed?
- What are the current risks?
- Are there any issues requiring attention?
- Does someone need to make a decision?
I have found that this approach is much more useful than filling a status report with activity that does not affect the project’s direction.
During project closure
Communication still matters when the work is almost finished.
The team should communicate what has been delivered, what remains outstanding, whether the expected benefits have been achieved and what lessons should be carried into future projects.
A proper close-out can prevent the same mistakes from being repeated on the next project.
Common communication problems in business projects
Even experienced project teams can fall into familiar communication traps.
Too much information
It is tempting to copy everyone into every update.
The problem is that important information can quickly get buried.
Better approach: give people the information relevant to their role and responsibilities.
Nobody owns the message
A team might assume that someone else has told the client about a change.
Then the client finds out through another channel.
Better approach: assign clear ownership for important stakeholder communications.
Problems are reported too late
Nobody wants to be the person who delivers bad news. Unfortunately, delaying difficult information rarely makes the situation better.
Better approach: raise significant risks early, even when the solution is not yet clear.
A useful risk update does not need to pretend everything is under control. Explain what has happened, what the potential impact is, what you are doing about it and what support you need.
Decisions disappear after meetings
People often leave the same meeting with slightly different interpretations of what was agreed.
Better approach: record important decisions, actions, owners and deadlines.
It does not have to be complicated. A short written summary can prevent a lot of unnecessary back-and-forth.
Too many meetings
More meetings do not automatically mean better communication.
If people spend most of their week attending meetings, they may have less time to actually complete the project work.
Better approach: give each meeting a clear purpose. If something can be communicated effectively through a short written update, there may be no reason to arrange another meeting.
Communication and employee performance
Communication is also closely connected with the way employees understand their responsibilities and contribute to organisational objectives.
The CIPD explains that effective performance management can include objectives, feedback, development, recognition and performance-related pay. It also highlights the importance of employees understanding what is expected of them and having the support and resources necessary to perform effectively.
That connection is easy to see in project work.
If an employee does not understand what success looks like, it becomes difficult to judge performance fairly. If feedback only arrives at the end of a project, there may be little opportunity to correct problems. If good contributions go unnoticed, people may also feel disconnected from the wider objective.
For readers exploring the relationship between performance, contribution and reward, the CIPD_5HR03_26_01 resource provides a related perspective on performance and contribution.
The underlying principle is straightforward: people perform better when expectations, feedback and objectives are clear.
A simple communication routine you can introduce
If communication on your project feels disorganised, you do not necessarily need another complicated system.
Start with a few practical steps.
Step 1: List your stakeholders
Write down everyone who can influence the project, approve decisions, deliver work or be affected by the outcome.
Step 2: Work out what each person needs
Avoid asking only, “What information do we have?”
Instead ask, “What does this person need to know?”
That small change can dramatically reduce unnecessary reporting.
Step 3: Agree where information belongs
Decide where people should find project documents, task updates, decisions and urgent issues.
Step 4: Establish a realistic rhythm
For example, you might have a weekly team update, a fortnightly sponsor review and monthly senior-management reporting.
The exact frequency will depend on the project. A high-risk project may need more frequent communication, while a stable project may need less.
Step 5: Make risks visible
Do not wait until a risk becomes a crisis before mentioning it.
Early communication gives the team more options.
Step 6: Confirm important decisions
After a significant meeting or discussion, record what was agreed, who owns the action and when it needs to happen.
Step 7: Review the approach
Your communication needs will change as the project develops. New stakeholders may become involved. Priorities may change. A project that initially needed weekly reporting might later require daily coordination.
APM similarly recommends reviewing communication as stakeholder needs and project circumstances change.
Final thoughts
Effective communication in business project management is not about becoming better at sending emails.
It is about creating enough shared understanding for people to make good decisions and do the right work at the right time.
That means understanding your audience, choosing appropriate channels, listening to feedback, documenting important decisions and being willing to communicate uncomfortable information early.
The strongest project communication is often surprisingly simple. People know what is happening. They know what is expected of them. They know where to find reliable information. And when something changes, they hear about it early enough to respond.
For me, that is the real measure of effective communication in project management.
Not the number of meetings held.
Not the length of the status report.
Not the number of emails sent.
It is whether communication helps the project move forward.