How to improve team communication: five habits managers can practice this week

Improving team communication means making sure the right people know what matters, why it matters and what is expected of them, and that problems travel up as easily as instructions travel down. For a manager, that comes down to five habits: clarify, ask, listen, invite dissent and close the loop. Good internal communications software can carry the message to everyone, but it cannot tell you whether people understood it, believed it or felt free to push back. Those parts happen in conversations you lead.

The test is simple. A team communicates well when people can answer three questions without guessing: what are we trying to do this month, what is my part, and who do I tell when something is off? If answers differ from person to person, the team has a communication problem, whatever tools it uses.

The manager is the main channel most employees have. Gallup's research shows that managers account for at least 70% of the variance in employee engagement scores. Communication rhythm is a large part of that: employees whose managers hold regular meetings with them are almost three times as likely to be engaged as those whose managers do not.

Frequency and responsiveness both count. Gallup found engagement highest among employees who have some form of daily communication with their manager, whether face to face, by phone or digitally; managers who mix those channels do best, and engaged employees say their manager returns calls or messages within 24 hours. More recent Gallup work points to the same habit: one meaningful conversation per week with each team member builds high-performance relationships more than any other leadership activity.

None of this calls for more meetings. It calls for short, regular, two-way contact and a manager who answers.

The loop below turns the research into a weekly routine. Each habit fixes a specific failure: confusion (clarify), surface-level answers (ask), defensiveness (listen), silence (invite dissent) and decisions that evaporate (close the loop). Work through it in order the first time; after that, the weak spot on your team tells you where to spend effort.

Use it at three levels: in each one-on-one, in your weekly team meeting, and in any message that announces a change.

Most "why doesn't my team get it?" moments trace back to a message the manager understood and the team did not. Clarity is a common gap: Gallup found that fewer than half of employees with remote-capable jobs strongly agree they know what is expected of them at work. Among employees who report that they know what their coworkers are expected to do, that share jumps to between 77% and 84% depending on work location, which points to the fix: ongoing, explicit clarification of who does what, rather than a single announcement.

When you share a goal, a priority or a decision, cover four things:

1. What is expected, in observable terms ("first draft to the client by Thursday noon", not "move fast").
2. Why it matters, in one or two sentences tied to the customer, the team or the person's work.
3. What is not decided yet. Saying "we don't know the budget until the 15th" builds more trust than silence, and it stops rumors from filling the gap.
4. What would change it. People handle a shift in plans better when they knew in advance what could cause one.

Transparency without overload. Being transparent does not mean forwarding everything. It means people are never surprised by something you knew and could have shared, and that you explain decisions you cannot fully disclose ("I can't share the details yet; here's what I can tell you and when I'll know more").

Avoid mixed signals. A team reads what you do more closely than what you say. If you call quality the top priority but only praise speed, or ask for candor but go quiet when someone disagrees, the behavior wins. Once a month, compare what you said mattered with what you rewarded, praised and spent time on. When change is involved, the stakes rise; see our guide on how to lead change for the communication that keeps people with you through it.

Make the message land. Lead with the point, then the reason, then the ask. Use the team's words, not leadership vocabulary. And check understanding by asking people to play it back ("What will you do differently on Monday because of this?"), not by asking "Any questions?"

Managers are rewarded for having answers, so many talk first and ask second. Turning that around pays off. In three studies of live conversations, people who asked more questions, especially follow-up questions, were better liked by their partners. A follow-up shows you heard the first answer, and it is usually where the real issue appears.

Useful question types for a manager:

• Open starters: "What's getting in your way this week?" "What would make this easier?"
• Follow-ups: "Say more about that." "What makes you think so?" "What happened next?"
• Specifics, to get past vague talk: "What does 'almost done' mean in hours?" "Who exactly is waiting on this?"
• The last question: "What haven't I asked that I should have?"

A useful target for one-on-ones: at least two follow-up questions before you give your view, and an employee who talks for more than half the meeting.

Listening is easy to claim and hard to practice under pressure. Good listening is visible: attention without multitasking, checking that you understood, and a clear intent to understand rather than to win. In experiments on disagreement, that kind of high-quality listening made speakers feel more comfortable and connected and helped them reflect on their own views less defensively. In other words, the way you listen changes how the other person thinks, not just how they feel.

Three steps that work in any conversation:

1. Remove the distraction. Close the laptop, silence notifications, look at the person or the camera. If now is a bad time, say so and set a time; half-listening signals that the person ranks below your inbox.
2. Play it back. "So the issue isn't the deadline, it's that you found out about it last. Is that right?" Let them correct you.
3. Name the emotion before the solution. "That sounds frustrating" or "I can hear you're worried about the handoff" does real work. In a 2007 brain-imaging study, putting feelings into words reduced the response of the amygdala and other limbic regions to negative emotional images. People who feel understood are ready to solve the problem; people who are rushed to a fix keep defending their point.

Respect shows in small conversational moves: letting people finish, remembering what they told you last time, giving credit by name, and disagreeing with the idea rather than the person.

Silence is the most expensive communication failure because you cannot see it. In an interview study of 40 employees, 85% said they had at least once felt unable to raise an issue with their boss even though they thought it was important. The most common reason was fear of being viewed or labeled negatively and damaging valued relationships. The third most common was futility: a quarter of respondents felt speaking up would not make a difference.

Each reason has a counter-move:

• Against fear: ask a specific person for dissent ("You know this area best. What's the strongest argument against this plan?"), thank the first person who disagrees in front of the team, and admit your own mistakes first.
• Against futility: close the loop on every concern raised, including the ones you decline ("We're not changing the launch date, and here's why. We are adding a review step because you flagged the risk").
• Against shutting people out: watch for habits that end conversations, such as answering your own question, finishing other people's sentences, or replying "yes, but".

Share the airtime. In a study of 699 people working in groups of two to five, the group's collective intelligence was not strongly tied to its members' individual intelligence but was correlated with social sensitivity and an even spread of conversational turn-taking. In meetings, that suggests concrete rules: the most senior person speaks last, go round the table before open discussion, and use a written round (everyone types one risk in the chat) when a few voices tend to dominate. More on team dynamics in our guide to high-performing teams. When disagreement turns personal or stalls, move to the playbook in how to resolve conflict in the workplace.

When you are the one staying quiet. Managers face the same choice upward. Before you raise a concern with your own leadership, check three things: is it specific (what, where, how big), do you have a proposal or at least an option, and is this the right moment and setting (one-on-one before the meeting, rather than in front of a large group)? If the answers are yes, speaking now usually costs less than explaining later why you did not.

Decisions made out loud fade quickly. A short written recap turns a conversation into a commitment: what was decided, who owns it, by when, and what is still open. It also protects people who missed the meeting, which in a hybrid team is often a large share of it.

Writing has its own trap. Five experiments by Kruger, Epley and colleagues suggest people believe they communicate over email more effectively than they actually do. A message that sounds brisk and friendly in your head can read as cold, sarcastic or alarming.

Before you send anything that matters, run a five-line check:

1. Is the point or the ask in the first two lines?
2. Could a reader who missed the meeting act on this without asking you?
3. Are owners and dates named?
4. Would this read the same way if the reader were already anxious?
5. Should this be a call instead (see the table below)?

Delivery counts out loud too. In meetings and presentations, the same message lands differently depending on pace, structure and tone. Start with the conclusion, give no more than three supporting points, pause for questions, and end by restating the ask. If your team keeps misreading your tone, ask one trusted person for direct feedback on how you come across; our guide to giving feedback shows how to ask for it and act on it.

Many communication problems are channel problems: a sensitive message sent by chat, a simple update turned into a meeting. Use this table as a default and agree on it with your team.

Hybrid and remote teams. Agree on reply windows per channel (for example, same day for direct messages, within 24 hours for email), core hours for live work, and one place where decisions live. Record or write up meetings for people in other time zones. Rotate meeting times if the team spans regions so the same people do not always join at 7 a.m.

• Adding channels instead of fixing habits. A new tool spreads the same unclear message faster.
• Announcing without explaining. People fill a missing "why" with the least generous version.
• Asking for candor, then reacting badly to it. One sharp response teaches a whole team to stay quiet.
• Listening to reply. Planning your answer while the other person talks shows, and it skips the emotion they needed you to hear.
• Letting the loudest voices set the direction. Without turn-taking rules, meetings reflect confidence rather than knowledge.
• No follow-up. Concerns that vanish after being raised teach people that speaking up is futile.
• Treating remote staff as an afterthought. Hallway decisions that never get written down exclude everyone who was not there.

Measure a few things regularly rather than many things once. Run a short anonymous pulse every quarter, on a five-point agree scale, with items such as:

1. I know what is expected of me this month.
2. I understand the reasons behind recent decisions that affect my work.
3. I can raise a concern with my manager without worrying about how it will be seen.
4. When I raise a concern, I hear back about what happened.
5. In our team meetings, everyone gets a real chance to contribute.

Then track behavior signals that need no survey:

• Decision hygiene: share of decisions with a written owner and date.
• Airtime: in a sample of meetings, how many people spoke and whether the same two or three dominate.
• Early warnings: whether risks are raised before deadlines or discovered after them.
• Rework and repeated questions: how often work is redone or the same question is asked twice because a message was unclear.
• One-on-one rhythm: share of planned weekly one-on-ones that actually happened.

Review results with the team, pick one item to improve next quarter, and say what you will change. An eNPS question can sit alongside these items as a broad signal, but it will not tell you which habit to fix.

Software solves distribution and memory: an internal communications platform gets the same message to office, remote and frontline staff and keeps decisions findable; survey tools run the quarterly pulse and keep it anonymous; engagement platforms prompt regular one-on-ones and show where they lapse. What software cannot do is ask the follow-up question, notice the person who has gone quiet, or explain why a decision was made. Choose tools that make your five habits easier and judge them by whether your pulse scores and behavior signals improve.