A common challenge in project communication – and a practical way to address it

Step 1 – Filter issues before bringing them to a meeting

Three questions can be used as a filter:

1. Can the factory decide or test this internally?

2. Does it impact deliverables (timeline, quality, cost)?

3. Does the customer need to provide input or make a decision?

If all answers are NO → handle internally.

If it impacts deliverables but does NOT require customer decision → inform the customer before the meeting to check if need to do further discussion

If it impacts deliverables and requires customer decision → bring it high priority to the meeting

This simple filter reduces unnecessary discussion significantly.

Step 2 – Adjust the message for different roles

The same issue should be communicated differently depending on the audience.

To technical team
Explain the current situation, planned tests, timeline, and potential risks.
This allows their technical team to understand the issue, not just the conclusion.

To procurement or supply chain representatives
Focus on cost and timeline.
Is the delivery date affected? Is there a cost impact? Does an order adjustment need to be considered?

To decision-makers
Focus on launch success.
Will this affect launch timeline, product quality, or customer experience?
And what is the consequence if no decision is made?

Two supporting habits

Before the meeting (24 hours in advance)
Send the issue list to the customer. Mark each item as "for information" or "for decision".

After the meeting
Each action item should clearly state: responsible person, deadline, and deliverable.

These habits help reduce the common pattern of "talking without concluding, concluding without deciding, deciding without acting".

Summary

Effective project communication is not about putting every issue on the table.
It is about filtering issues appropriately and communicating them to the right audience in the right way.

This is not a soft skill. It is a core project management discipline.

Have you encountered similar situations in your projects?
What filtering rules have you found useful?