The meeting where nobody said the thing: communication skills for people who are not junior
Ganesh HS ·
In brief
Most communication failures in experienced teams are about what goes unsaid, not how things are said.
The skills are asking, summarising and disagreeing — not presenting.
Train on the team's own recent meetings, or it does not transfer.
The manager's reaction to the first hard truth decides whether the training holds.
A leadership team of eight met for forty minutes to review a project that everyone in the room privately believed was going to miss its date. The meeting covered progress, risks and next steps. Nobody said the date would be missed. Afterwards, in twos and threes in the corridor, everyone agreed it would be. The project missed by six weeks, and the review of why concluded that the risk had not been communicated clearly enough — which was true, and was not a problem of clarity.
Communication skills training is usually bought for juniors and delivered as presentation technique. The expensive communication failures happen among experienced people who present perfectly well and do not say the thing. That is a different skill set, and it is the one worth training.
What actually goes wrong
The known problem is not named because naming it feels like an accusation, and nobody wants to be the one.
Questions are not asked because asking reveals not knowing, and in a room of experienced people not knowing feels costly.
Disagreement is deferred to the corridor, where it is safe and changes nothing.
Summaries are skipped, so eight people leave with eight versions of what was decided.
The quiet person is not asked, and the quiet person had the information.
None of these is about articulacy. Each is about a moment in a meeting where a specific move — a question, a summary, a stated disagreement — was available and not made, because the person weighed the social cost and decided against it. Training that does not address the social cost teaches the move and leaves the reason it is not made untouched.
Three habits, not thirty techniques
What to practise
ASK 'What would have to be true for this to be
on time?' - a question that surfaces the
unsaid without accusing anyone of hiding it
SUMMARISE 'So we have decided X, Y is open, and Z owns
it by Friday' - said aloud before the meeting
ends, by anyone, every time
DISAGREE 'I see it differently, and here is the thing
I would want to be wrong about' - stated in
the room, in the first person, with the
reason attached
Three habits. A team that does all three leaves
meetings with the same decision and the real risks
on the table.
The disagreement habit is the one that changes the opening story. A form of words that makes disagreeing sound like contribution rather than confrontation is what lets someone say the date will be missed in the room instead of the corridor. It has to be rehearsed until it is available under pressure, and it has to be seen to be welcomed the first time it is used — which is the manager's job, and the part of the training that happens after the trainer has gone.
1
Bring the last three meetings
Not case studies. The actual agendas and, where people are willing, what was said in the corridor afterwards. The gap is the curriculum.
2
Rehearse the three lines in role
With the real topics. People will not use a line they have not said aloud in a safe room first.
3
Practise asking the quiet person
'You have been closest to this — what are we not seeing?' It is a specific move, it feels awkward, and it is where the information usually was.
4
Agree the summary rule
Every meeting ends with one person saying what was decided, what is open and who owns what. Rotate who. It takes ninety seconds and removes most follow-up email.
Why the corridor is rational
Before treating the corridor as a failing, it is worth seeing why capable people choose it. In the room, saying the date will be missed carries a cost: it may be read as blaming the project lead, as pessimism, or as volunteering to fix it. In the corridor, the same statement is free — it can be tested on one trusted colleague, hedged, and withdrawn. People are not being cowardly. They are managing a real risk that the room has never explicitly removed. The three habits work because they lower that cost: a question is not an accusation, a summary is a service, and a first-person disagreement with the reason attached is a contribution rather than an attack. Training that teaches the moves without acknowledging why they were not being made will be politely received and not used.
The manager can remove most of the cost in one sentence at the start of every review: 'If anyone thinks the date is at risk, this is the meeting to say it, and I would rather hear it here than in the corridor.' Said once, it is a nice sentiment. Said at every review, and followed by thanks the first time someone takes it up, it becomes a rule the room believes.
Writing is the same problem
The corridor version of the meeting also happens by email: a message that describes the situation carefully and asks for nothing, so that nobody has to act on it. The written habits are the same three — a question that surfaces the issue, a summary of what is being asked, a stated position — and they are covered in business writing and email etiquette for teams where the failure is mostly in writing. Most experienced teams need both, and the meeting version first.
The manager's first reaction
Everything above is undone by one moment: the first time somebody uses the disagreement line in a real meeting and the manager's face closes. Teams watch that moment with great attention, and they draw the correct conclusion from it. A manager who will run this training for their team has to be prepared for the first hard truth to be uncomfortable and to thank the person for it, visibly, before responding to the content. It is a rehearsable skill and it belongs in leadership and people management work for the managers, ideally before the team is trained.
Where the manager cannot do this — and some cannot — the honest advice is not to train the team. It will teach them the moves and then demonstrate, once, that the moves are unsafe, which leaves them worse informed about their own workplace than before.
What it is not
It is not presentation skills, which are a different need with a different session. It is not a personality assessment, which tells experienced people things they already know about themselves. It is not conflict resolution, though a team that disagrees in the room has fewer conflicts to resolve. It is the narrow, practical business of making sure that what eight capable people know is what the room hears, and communication skills training aimed at experienced staff should be judged on that alone.
The measure is the next review meeting. If the thing everyone knows gets said in the room, by someone, before the meeting ends, the training worked and the manager made it safe. If it is said in the corridor, one of those two failed, and it is usually the second. That test costs nothing and is more honest than any form; communication skills work that cannot pass it has not done its job.
Questions we are asked
Presentation and writing basics, perhaps. The expensive failures — the known risk left unsaid, disagreement deferred to the corridor — happen among experienced people, and that is a different, trainable skill set.
Ask a question that surfaces the unsaid without accusing anyone; summarise decisions, open items and owners aloud before the meeting ends; disagree in the room, in the first person, with the reason attached.
Social cost — naming a problem feels like accusing someone, asking feels like not knowing, disagreeing feels like confrontation. Training has to give forms of words that lower that cost, and managers have to show the cost is real-ly low.
Yes, and first. The manager's reaction the first time someone says a hard thing decides whether the team keeps doing it. That reaction is rehearsable.
At the next review meeting, does the thing everyone knows get said in the room before it ends? If it is said in the corridor instead, either the habit or the safety failed.
A proposal, a confident voice, a nod around the table, and a wrong decision nobody examined. What critical thinking and problem-solving training gives a team that has no time, and the four questions that would have caught it.
He had the facts, made his case, and the team stopped listening halfway through. What emotional intelligence training covers when it is stripped of jargon, why it is mostly noticing, and the three moments in a working week where it decides outcomes.
A new hire kept doing things that were 'obviously' not done, and nobody could point to where it said so. What professionalism and work-ethics training actually covers, why it fails as a lecture, and how to turn unwritten expectations into a standard a team agrees to.
Read the article
Let’s find your next step
Is your HR process ready to scale?
Identify critical compliance gaps, payroll leaks, and hiring bottlenecks with a free 360-degree HR audit. Get a clear roadmap for your business.