Behavior is communication, even when a person has not put the message into words. A missed deadline, a quiet meeting, a defensive reply, or a colleague who stops asking questions can tell a leader that something deserves attention. It does not tell you exactly what the person is thinking. Your task is to notice the signal without jumping to a conclusion, then create a conversation where the person can explain what is happening.

Talk with Jeff about leadership communication

What does it mean to say behavior is communication?

Communication is more than the words people choose. It also includes timing, tone, silence, facial expression, posture, follow-through, and the decision to participate, or not participate. These signals shape how others understand a message, even when the person sending them does not intend to send a message at all. Leaders can strengthen those exchanges by applying the practical ideas in this guide to the 7 C’s of communication.

Consider a team member who usually contributes ideas but has become quiet. The observable fact is that the person is contributing less. The reason is not yet known. Perhaps the person is overloaded, unsure whether their input is welcome, concerned about a decision, distracted by a personal challenge, or simply listening. Treating quietness as proof of disengagement confuses a signal with an explanation.

The same care applies to visible frustration, missed commitments, repeated questions, or a sudden change in tone. These actions may point to an unmet need, a misunderstanding, a competing priority, or a disagreement. They may also have an explanation unrelated to work. A leader should be curious about the context rather than label the person or assign a motive.

This distinction matters because leadership is communication. When leaders react only to the surface behavior, they can miss the issue underneath it. When they notice a change and ask about it respectfully, they make room for useful information and clearer expectations. That communication is part of the broader work of balancing leadership and management.

Think of behavior as a signal that invites inquiry, not a code that grants access to another person’s thoughts. The signal may be intentional or unintentional. A person may be trying to express a concern, may not know how to express it, or may not be sending a message at all. Your interpretation is a hypothesis. It becomes more reliable only after you check it with the person and consider the surrounding facts.

For example, an employee’s short answer could mean that they are frustrated with a proposal. It could also mean they are rushing to another meeting, processing a complex question, communicating in a concise style, or dealing with a distraction. If the leader immediately responds, “You are resisting this change,” the employee now has to correct a judgment before the actual work can be discussed. A neutral observation such as “You have been quiet since we discussed the new handoff; what questions or concerns should we make room for?” creates a better opening.

This principle is useful across roles and settings. A small-business owner may notice that a reliable employee no longer flags risks. A department head may hear agreement in a meeting and receive objections afterward. A project leader may see a capable colleague repeatedly ask for approval on decisions they previously handled. In each case, the behavior offers a reason to check understanding, conditions, expectations, or support. It does not justify a conclusion about character.

Behavior also communicates through what leaders do. If a leader says that questions are welcome but interrupts every question, the interruption may communicate more strongly than the invitation. If a leader asks for honest feedback and then punishes disagreement, the response tells the team what candor costs. Leadership communication is therefore not limited to the message a leader intends. It includes the experience people have when they try to respond.

Read the signal without pretending to read minds

Reading behavior well is not the same as decoding a hidden message with certainty. Nonverbal cues are not a universal code. A person crossing their arms might be cold, comfortable, concentrating, or feeling guarded. A delayed response might reflect workload, uncertainty, a technical issue, or a deliberate choice. Context, individual habits, and the relationship all matter.

Use observations as a reason to ask, not as evidence for a verdict. Replace “You do not care about this project” with “I noticed the last two check-ins were quiet, and the draft is later than we planned. How are things going from your perspective?” The second version separates what you saw from what you guessed.

It can help to compare behavior with a person’s own usual pattern, rather than compare them with a stereotype or with the most vocal person on the team. A change from someone’s baseline can be worth noticing. But even a clear change does not reveal its cause. Give the person space to name the cause, correct your reading, or tell you that nothing is wrong.

Keep the stakes and setting in mind, too. People may speak differently in a large meeting than in a private conversation. They may be cautious when a decision affects their role, when power differences are present, or when previous feedback has not led to action. The leader’s own habits can shape the signals they receive. If interruptions are common, people may stop volunteering ideas; if disagreement is punished, apparent agreement may not mean genuine support.

A useful discipline is to separate four things in your notes or thinking: what happened, what you think it might mean, what impact it had, and what you still need to learn. “The last two reports arrived one day after the agreed date” is an observation. “The employee does not care” is an interpretation. “The team had less time to review the figures” is a possible impact. “What changed in the workflow?” is a question. Keeping those categories separate helps prevent a tentative reading from hardening into a label.

Leaders should also account for differences in communication style, culture, personality, accessibility, and role. Some people think before speaking. Some prefer to prepare written comments. Some communicate directly, while others signal disagreement more indirectly. Some may avoid eye contact for reasons that have nothing to do with truthfulness or respect. None of these patterns should be treated as a reliable measure of commitment or competence. Ask about the work and the person’s preferred way to contribute instead of imposing one style as the standard.

One way to check your assumptions is to generate at least three plausible explanations before beginning a conversation. If a colleague missed an update, the possibilities might include unclear ownership, a changed priority, or a forgotten task. The point is not to construct an elaborate theory. It is to remind yourself that more than one story can fit the same behavior. Then ask a question that allows the person to supply the missing context.

Be alert to confirmation bias. Once a leader decides that someone is disengaged, every short answer may look like more evidence, while helpful work goes unnoticed. The reverse can happen as well: a leader who trusts someone may excuse repeated missed commitments without checking whether the team is carrying extra work. Describe the same concrete standard for everyone, and let information, not a preselected story, shape the next step.

Notice patterns that may carry an unspoken concern

One isolated moment rarely gives enough information to draw a meaningful conclusion. Patterns provide a more useful starting point. Notice whether the behavior is new, repeated, tied to a particular situation, or shared across the team. Then ask what conditions might be contributing to it.

• Silence where there used to be participation: People may be uncertain, disengaged, tired, excluded from preparation, or unconvinced that speaking up will help. Ask how the person sees the issue before deciding which explanation fits.
• Repeated agreement followed by little follow-through: The request may not be clear, priorities may conflict, or the person may not feel able to challenge the plan in the moment. Check both understanding and capacity.
• Frequent questions or requests for confirmation: The person may want clarity about the goal, decision rights, quality standard, or consequences of getting it wrong. Repeating instructions more firmly may not address the uncertainty.
• A sharper tone or visible frustration: There may be pressure, a perceived unfairness, an unresolved disagreement, or something outside the immediate conversation. Stay specific about the work issue and invite the person to add context.
• Withdrawal from informal collaboration: The person may be busy or prefer focused work, but a broader change in connection can also point to a process obstacle or a sense of exclusion. Ask what would make collaboration easier.
• Last-minute objections: People sometimes raise risks late because they did not have a safe or useful opportunity earlier, or because the risks became clearer as the work progressed. Find out which, rather than treating every late concern as resistance.

These are prompts for inquiry, not a diagnostic checklist. Avoid using behavior to infer a person’s character, health, or private circumstances. Focus on what is observable and relevant to the work. If a concern involves safety, harassment, discrimination, or another formal workplace issue, follow the appropriate organizational process instead of trying to resolve it through an informal coaching conversation alone.

Patterns can also appear in work products, timing, and decisions rather than gestures. A team may repeatedly reopen a decision after it has been announced. Several people may seek private clarification after the same meeting. A project may move forward on paper while ownership remains vague. A leader who looks only for facial expressions could miss these stronger, work-related signs. Track what happens in the process and ask where the expectation or decision is unclear.

Try to identify the smallest useful pattern rather than collect every annoyance. If a person was late once during an unusual week, that may not call for a broad discussion about reliability. If a deliverable was late several times after ownership changed, the repeated connection may be worth exploring. Good observation is selective: it focuses on behavior relevant to a shared outcome, not on building a case against a person.

Before initiating a conversation, check whether the pattern has another obvious explanation you can verify. Did the deadline move? Was a key decision postponed? Did you change the person’s responsibilities? Did the team receive inconsistent direction? This does not mean the leader must solve every issue alone. It means the leader should consider their own contribution and the operating conditions rather than assume the cause lies entirely with the employee.

Patterns across a group deserve particular care. If multiple people are quiet in one meeting, it may be a meeting design issue rather than a collection of individual attitude problems. If every function is waiting for approval, decision rights may be unclear. If everyone agrees in the room and then asks the same questions afterward, the communication process may not give people enough time or safety to raise uncertainty. Look at the shared conditions before holding separate corrective conversations with each person.

Use the Notice, Describe, Invite, Listen tool

A practical way to surface an unspoken concern is to move through four steps: Notice, Describe, Invite, and Listen. The tool keeps a leader grounded in facts while leaving the interpretation with the person who has the experience. It is not a script that guarantees a particular answer. It is a structure for entering a conversation with respect, clarity, and a willingness to learn.

1. Notice a specific change

Start with something concrete, not a broad judgment. “The last two project updates came in after the agreed time” is more useful than “You are unreliable.” “You have not weighed in during the past three planning meetings” is more precise than “You have checked out.” Choose an example that is recent, relevant, and fair to raise.

Before you speak, ask yourself whether you have a legitimate work reason to bring it up. Is there an effect on a deadline, a decision, a colleague, or the person’s ability to do the job? Or are you simply uncomfortable with a style that differs from yours? This pause can prevent a leader from turning personal preference into a performance concern.

Make the observation narrow enough that the other person can confirm, clarify, or correct it. “You have been difficult lately” is too broad to work with. “On Tuesday and Thursday, the client handoff notes were not in the shared folder by noon, which was our agreed time” is specific. If you cannot name when the behavior occurred or why it matters, take time to clarify your own concern before raising it.

Notice the difference between an event and a pattern. An event might be one missed handoff. A pattern might be several handoffs that were delayed after a new approval step was added. Describe the available evidence without inflating it. Avoid words such as “always,” “never,” “constantly,” and “everyone,” unless you can support them and they are truly necessary. In most conversations, precise dates and examples are more persuasive than sweeping terms.

Consider timing. If you are angry, rushed, or reacting in front of others, wait until you can speak calmly and privately, unless an immediate safety or operational concern requires prompt intervention. The aim is not to avoid a hard conversation. It is to make the conversation more likely to address the issue rather than the leader’s emotional delivery. If the subject is urgent, state the immediate expectation briefly and arrange a fuller discussion when possible.

Also consider whether the employee has already tried to tell you something. A concern may have appeared in earlier questions, a written note, or a request to revisit a decision. Reviewing that context can keep the conversation from repeating a question the person has already answered. It can also reveal whether you failed to close the loop on a prior discussion.

2. Describe what you observed

Use neutral language and, when possible, name the context. “In Monday’s planning meeting, I noticed we moved to the next topic before you had a chance to share your update.” Avoid dramatic words such as “always,” “never,” or “obviously.” They are easy to dispute and can make the conversation about the wording instead of the issue.

Describe impact without exaggerating it. “We did not have your risk assessment when we made the handoff decision” is clearer than “Your silence put the whole project in danger.” If the impact is uncertain, say so. Precision communicates respect and makes it easier for both people to correct the record.

A useful opening often has three parts: a neutral description, a reason for asking, and an invitation. For instance: “In our last two planning meetings, I noticed the schedule discussion ended before we reviewed your team’s capacity. I want to make sure the plan is workable. What would help us understand the constraints?” The description identifies what happened; the reason explains why it matters; the question leaves room for an answer the leader did not expect.

Use “I noticed” carefully. It can sound respectful, but it does not make an accusation neutral by itself. “I noticed that you are trying to undermine me” still assigns a motive. Describe something another person could also observe: a document, a statement, a missed deadline, a decision, or a change in participation. If you are unsure whether a statement is observation or interpretation, ask whether a camera could record it. A camera can capture that someone left the meeting early; it cannot capture that they were offended.

Speak directly to the person rather than discussing their behavior with other colleagues as a substitute for a conversation. There are valid reasons to seek advice from an appropriate manager or HR partner, particularly when the matter is sensitive or formal. But informal speculation among peers can spread a label without giving the person a chance to explain. Keep the discussion limited to people who need to be involved.

Allow the other person to correct factual details. Perhaps the deadline was changed in an email you missed. Perhaps someone else owned the deliverable. If the evidence changes, acknowledge that openly: “Thanks, I had the original date. I see the updated date was Friday, so I need to correct what I said.” A leader who can revise an account models the same honesty they ask of the team.

3. Invite the person’s perspective

Ask an open, non-leading question. For example: “How did that meeting feel from your side?” or “Is anything making it harder to meet the timeline we agreed on?” Another useful prompt is, “What am I missing?” This explicitly gives the other person permission to offer context that the leader has not considered.

Then stop talking long enough for an answer. A question followed immediately by a proposed explanation is not a genuine invitation. Avoid filling every pause, defending your intent, or asking the person to reassure you that everything is fine. If the answer is brief, you can say, “You do not need to solve it on the spot. Would it help to talk more now, or should we set a time?”

Open questions should not become vague interrogations. “What is going on with you?” can feel accusatory because it is broad and personal. A work-focused question gives the person a clearer route into the conversation: “What is making it hard to finish the review by Thursday?” or “What would help you share a concern before the decision is final?” Ask one question at a time. Several questions delivered in a row can sound like a cross-examination and make it hard to know which one deserves an answer.

Do not embed your preferred answer in the question. “You are worried the new process will create more work, right?” pressures the person to agree or correct you. Try, “What effect do you think the new process will have on your workload?” If you have a specific possibility to check, offer it as one possibility among others: “I wondered whether the approval step is adding time, but I may be missing something. How does it look from your side?”

Give the person choices about the conversation when choices are practical. A sensitive topic may be easier in a private meeting, a follow-up conversation, or a written response. The leader still owns the need to discuss a work issue, but can offer some control over the format. Say what is and is not optional. For example: “We do need to agree on the project handoff today. You can talk it through now, or send me your view before 3 p.m., and then we can decide together.” Clarity about boundaries reduces the risk that an invitation sounds like a trap.

It may take more than one invitation for a person to feel ready to speak. Do not force disclosure about personal life. If the person says they would rather not discuss the reason, respect that answer and turn to what is needed at work: “Understood. We can keep the conversation focused on the timeline. What can you commit to, and what support would make that possible?” Respecting privacy is compatible with a clear work expectation.

4. Listen, clarify, and agree on a next step

Listen for the person’s account, not just for evidence that confirms your first impression. Reflect the main point in plain language: “It sounds like the deadline changed after the team had already committed to other work. Is that right?” A reflection is a check for understanding, not a claim that you know how the person feels.

Ask a follow-up when a detail affects the work: “Which priority should come first?” or “What information would let you decide?” If the person raises a concern you can act on, identify one practical next step, an owner, and a time to check back. If the next step is theirs, ask what support or clarity they need. If there is no immediate action, agree on when you will revisit the conversation.

Listening does not require instant agreement. You can understand a person’s experience and still have a different view of the decision. First make sure you have heard the claim accurately. Then separate what you can acknowledge from what remains unsettled: “I hear that the new approval stage has made the sequence harder to manage. The stage still needs to happen, but we can review who owns it and whether the timing is realistic.” This avoids the false choice between empathy and accountability.

Pay attention to the content, not only the delivery. A tense tone may be uncomfortable, but the underlying information may still be important. If a person speaks sharply, you can set a boundary without dismissing the issue: “I want to understand the concern. I also need us to speak without personal attacks. Can you tell me which part of the plan you believe will fail?” If the exchange becomes too heated, pause and agree on a time to return. Do not use the pause to make the concern disappear.

Clarify terms that could mean different things. “Soon,” “ready,” “support,” “ownership,” and “done” are often interpreted differently. If a colleague says they need more support, ask what kind would help: access to information, another reviewer, a decision, time, or a change in priority. If they say a task is nearly done, agree on the remaining steps and a realistic completion point. Specific language converts a general concern into something the team can act on.

Close with a summary that both people can correct. “You will send the revised outline by Wednesday. I will confirm which source file is current by tomorrow morning. We will check in Thursday to see whether the approval path is still blocking the work.” This is more useful than ending with “Let’s communicate better.” For an important issue, follow up in writing using neutral wording. Record agreements and responsibilities, not unsupported judgments about intent.

Prepare for the conversation before you begin

A short preparation step can improve the conversation substantially. Write down the concrete observation, the work impact, the question you want answered, and the outcome you hope to reach. Then review the list for assumptions. This need not become a formal document. A few careful notes can help you avoid improvising a character judgment when you are frustrated.

Start by naming your purpose. Are you trying to understand a change, repair a working relationship, clarify an expectation, remove an obstacle, or address a performance issue? More than one purpose may apply, but one should lead. If you are seeking information, do not disguise a disciplinary decision as a curiosity conversation. If a decision has already been made, state that honestly and ask for input on implementation rather than pretending the decision is open.

Next, define what you know and what you do not know. For a delayed deliverable, you might know the agreed due date, the actual arrival time, and the downstream work affected. You may not know whether the delay arose from workload, unclear ownership, a dependency, or an error. Write the facts in one column and the questions in another. This simple separation can help you enter the discussion ready to learn.

Consider the other person’s likely concerns without treating your guess as truth. They may worry that raising a problem will damage their reputation. They may feel the leader has already decided who is at fault. They may not understand why the issue matters. Thinking about these possibilities can help you choose a less threatening opening and explain the purpose. It cannot tell you what the person actually feels; only they can do that.

Choose a setting that fits the topic. A routine process question may fit a regular check-in. A sensitive concern usually deserves privacy and sufficient time. Avoid raising a complex subject in a corridor, at the end of a meeting when everyone is leaving, or in a group chat where others can misread the exchange. If a formal workplace concern has been raised, use the appropriate process and seek the right support rather than improvising an informal inquiry.

Decide what you can offer and what is outside your authority. If the person identifies a barrier, you may be able to change a sequence, clarify a decision, or redistribute work. You may not be able to change a fixed deadline or policy. Do not promise a solution before you know what is needed. You can promise to consider the information, identify who can decide, and return by a stated time.

Finally, prepare to hear something inconvenient. The person may say the leader’s own behavior contributed to the problem, or that a process the leader designed is confusing. If you have asked for perspective, respond as though the answer matters. You can ask for examples and verify details without becoming defensive. If you cannot listen well at that moment, reschedule rather than invite candor you are not ready to receive.

Put the tool to work in everyday leadership moments

When a capable employee has gone quiet: A manager notices that a normally active contributor has not spoken in two project meetings. Rather than calling on the person abruptly in front of the group, the manager asks privately: “I noticed you have been quieter than usual in planning. Is there anything about the current process that is making it harder to contribute?” The employee might explain that the meeting agenda arrives too late to prepare. The team can test sending it earlier and check whether that helps.

There are several useful details in this example. The manager compares the person’s current participation with their own prior pattern, rather than with a stereotype of what an engaged employee looks like. The manager asks privately, where the employee can respond without an audience. The question offers one possible work condition but does not insist that it is the answer. The next step is a small experiment rather than a promise that a single change will solve every concern.

The manager can make the experiment concrete: send the agenda a day earlier for the next three meetings, identify any decisions that need input, and invite the employee to contribute in the meeting or in writing beforehand. Afterward, ask whether the change made preparation easier. If the employee remains quiet, do not treat that as proof that the experiment failed or that the person is disengaged. Ask what they prefer and whether there is another barrier. A reasonable result could be that the employee has no concern and simply wants to listen during that part of the project.

When a deadline is missed twice: The leader states the two dates and the agreed deliverables, then asks what got in the way. The answer may reveal an unclear approval step, changing priorities, insufficient capacity, or a missed commitment. The leader can then separate the immediate repair, what needs to happen now, from the longer-term expectation. Curiosity does not remove accountability; it helps make accountability specific and workable.

Imagine that a report was due Tuesday and arrived Thursday, then the next report was due the following Tuesday and arrived Wednesday. The leader can say: “The last two reports arrived after the agreed date, which left the review team less time to prepare. I want to understand what is happening and agree on a reliable plan. What factors affected the timing?” The employee may explain that two managers have been giving competing priorities. The leader should check whether that is true and clarify which request takes precedence. If the work was simply delayed despite clear priorities, the conversation still needs to address ownership and the next deadline.

Do not let a legitimate explanation erase the impact or turn accountability into blame. A fair follow-up can say: “I understand the priorities changed. We still need an early warning if a date is at risk. Let’s agree that you will flag it as soon as the conflict is clear, and I will resolve competing requests the same day.” If the employee does not agree with the dates or responsibilities, review the record together. The result should be a shared understanding of what happens next, not a forced admission of motive.

When a team agrees in the meeting but raises objections afterward: The leader can acknowledge the pattern without accusing the group of being dishonest: “We often hear important concerns after a decision. What would make it easier to raise them while we are still discussing options?” The group may need more time for discussion, a written way to submit concerns, or explicit permission to challenge a proposal. Agree on a small experiment and review whether it changes the conversation.

For example, the leader can distinguish the meeting’s decision points: which items are open for discussion, who has final authority, and when the decision becomes final. Invite each function to identify one risk before the leader offers a preferred solution. Provide a brief written channel for people who think better after the meeting, while setting a clear deadline for input. If objections arrive later, ask whether they are new information, a concern that was present but difficult to raise, or a response to an unclear decision process. Each answer suggests a different adjustment.

The leader should not assume that every late objection means the team was afraid. Sometimes a risk becomes visible only after people examine the details. Sometimes the decision was communicated as final when it was not. Sometimes a person supports the direction but sees a practical implementation problem. Ask which applies and adjust the process without punishing useful information. At the same time, make clear how late changes affect the work and how the team should handle genuinely new evidence.

When someone’s tone becomes tense: Do not mirror the sharpness or immediately correct the person’s attitude. Return to the issue: “I hear that this is frustrating. Which part of the decision is most concerning to you?” If the conversation is becoming unproductive, set a respectful boundary and take a short pause. The purpose is not to excuse disrespect; it is to understand the disagreement and address behavior clearly without escalating it.

Suppose a colleague says, “This plan makes no sense, and nobody asked the people doing the work.” The leader can respond to both the content and the manner: “I want to hear what you believe we missed. Let’s keep the discussion focused on the plan and avoid personal attacks. Which step will create the biggest problem for your team?” If the answer identifies a real operational concern, the leader can examine it. If the tone continues to prevent discussion, the leader may pause and return later with a clear expectation for respectful communication.

When someone asks for approval on every small decision: A leader may be tempted to say, “You need to be more independent.” First ask what the employee believes they are authorized to decide and what consequences they fear if they choose incorrectly. Perhaps decision rights were never made explicit. Perhaps a previous error received a disproportionate response. Or the decisions may involve consequences that appropriately require approval. The leader can outline what the employee can decide alone, what requires consultation, and what must be escalated. Give examples and ask the employee to apply the categories to current work.

A practical follow-up could involve a decision log for a short period. The employee records the decision, the information considered, and whether they acted independently or sought input. The leader reviews a few examples and gives feedback on the decision process, not just on whether the outcome happened to be successful. This builds clarity without abruptly withdrawing support. If confidence grows, reduce the check-ins; if uncertainty remains, find out which rule or risk is still unclear.

When a strong contributor stops flagging risks: A leader notices that a colleague who usually catches dependencies has stopped raising concerns. Rather than praising silence as agreement, the leader asks what has changed in the review process. The colleague may say earlier warnings were dismissed because the schedule was already committed. The leader can ask what would make a warning actionable, then define how the team will record a risk, decide who owns it, and report what happened. The point is not to guarantee that every concern leads to a change; it is to show that concerns receive a clear response.

When an employee pushes back on a request: A leader hears, “I can’t take that on,” and interprets it as a lack of commitment. A better first question is whether the obstacle is capacity, skill, timing, unclear scope, or a disagreement about priority. The leader can ask, “What work would need to move if this becomes the next priority?” If the request remains essential, the leader must make a real tradeoff visible rather than treating capacity as an attitude problem. If the person has misunderstood the assignment, define the scope and check what remains feasible.

In each example, the leader does three things: describes a real observation, asks rather than assumes, and follows up on what the person says. A single conversation will not always reveal the whole story. It can, however, replace speculation with better information and a defined next step.

Ask better questions when the first answer is not enough

People do not always know how to answer a broad invitation. A leader may hear “It’s fine,” “Nothing,” or “I don’t know.” Those answers could mean the person has no concern, needs time, does not trust the setting, or is unsure what the leader is asking. Do not treat a brief answer as proof of concealment. Make the question easier to answer, allow a pause, or offer another time.

Useful prompts are specific, open, and connected to work. Ask, “Which part of the handoff is hardest to predict?” rather than “Why are you being difficult?” Ask, “What would make the decision clear enough to act on?” rather than “Do you understand?” A yes-or-no question can be useful for checking a concrete fact, but it may not reveal a concern. Follow it with an invitation: “You said the deadline is clear. What risks could still affect it?”

Questions can also help separate the immediate problem from the underlying process. “What needs to happen today?” addresses the immediate need. “What caused the same obstacle to appear again?” looks at a recurring pattern. “What would prevent this next time?” moves toward a future condition. Do not rush to the future question before understanding the current impact. A person may need to know that the leader has heard the immediate problem before they can help design a fix.

When someone raises a broad concern, ask for an example without implying disbelief. “Can you walk me through a recent instance?” is more neutral than “Prove that happens.” Examples help both people identify what the concern means in practice. If the employee says, “The priorities change every day,” ask which request changed, when it changed, and what work was affected. Then check the facts. The aim is shared clarity, not cross-examination.

Use questions to uncover assumptions on both sides. Ask, “What did you understand the decision to be?” and “What did you think I was asking you to do?” Then explain your own intent without insisting that intent settles the impact. A leader might say, “I meant to ask for options, but I can see the wording sounded like the decision was final. Let’s clarify what is still open.” This kind of repair can prevent people from acting on different versions of the same conversation.

Some questions are better asked in sequence. Start with “What happened from your perspective?” Then ask “What made that difficult?” and “What would help now?” The first question gathers an account; the second explores conditions; the third turns toward action. If you ask all three rapidly, the employee may feel rushed toward a solution before you have understood the problem. Let the answer to one question shape the next.

Keep a balance between inquiry and leadership. Endless questions can feel evasive if the employee expects a clear decision. After listening, state what you have learned and what you will do: “I hear that there are two approval paths and neither has a named owner. I will clarify ownership by tomorrow. For this week’s deadline, use the existing path and alert me if the review is not complete by Wednesday.” The leader’s responsibility is not only to gather information but to help the team move forward.

Make it safer to speak before behavior has to carry the message

Leaders cannot expect people to voice every concern if the workplace gives them reasons to stay quiet. The everyday response to disagreement teaches people what is safe. If a leader asks for candor and then interrupts, retaliates, or dismisses the answer, the invitation loses credibility. If the leader listens, explains decisions, and closes the loop, people have more reason to raise questions directly.

Build predictable opportunities for input. Share the purpose of a meeting and the decision to be made. Invite views before announcing your preferred answer. Make room for people to contribute in different ways, including a brief written follow-up when appropriate. After a decision, explain what you heard, what you chose, and what remains open. People may still disagree, but they can see that their input was considered.

Follow-through is especially important. If an employee describes a recurring obstacle, do not thank them and then let the issue disappear. Tell them what you can change, what you cannot change, and why. If you need to gather more information, give a date for an update. Trust is shaped not just by the invitation to speak but by what happens afterward.

Leaders should also make their own communication easier to interpret. State expectations directly. Clarify who owns a decision, what success looks like, and when to raise a risk. When you change direction, explain what changed. Clear words reduce the burden on employees to infer a leader’s intent from silence, hurried messages, or shifting priorities.

Safety is built through repeated conduct, not a single statement that “my door is always open.” An open-door invitation can be useful, but employees also need to see that raising a concern leads to a fair hearing. When you receive difficult feedback, thank the person for being specific, ask what they need you to understand, and avoid immediately explaining away the issue. You can review the facts later. In the moment, show that the person will not be punished simply for speaking.

Make participation possible for different people. Send an agenda early enough for preparation. Avoid letting the fastest speaker determine the full discussion. Use a round of brief input when a decision affects multiple functions, but do not force personal disclosure or public performance. Offer written follow-up when it serves the work. These practices make it easier to contribute without assuming everyone will express a concern in the same way.

Clarify how disagreement works. Teams often benefit from knowing whether a discussion is brainstorming, consultation, or a decision meeting. Explain who decides, what evidence matters, and how dissent will be handled. When a leader says, “I have heard the risks, and I am choosing this option because of these constraints,” people can understand the outcome even when they would choose differently. Silence after an unclear discussion should not be mistaken for agreement.

Close the loop visibly. If a team raises an issue, report what happened next even when the answer is no. For example: “We reviewed the request to change the handoff time. We cannot move it this month because of the external deadline, but we can assign a second reviewer. We will revisit the schedule after this cycle.” A clear response helps people decide whether to raise future concerns through the same channel. Silence from leadership can communicate that input disappears into a void.

Leaders should invite feedback on their own communication in a specific way. Instead of asking, “Am I a good communicator?” ask, “When I changed the project priority last week, what part of my explanation was unclear?” or “What is one thing I could do in the next planning meeting to make it easier to raise a risk?” A narrow question is easier to answer and more likely to produce something actionable. Then identify what you will try and return to the person to say what changed.

Match the conversation to the kind of concern

Not every behavior signal calls for the same response. A missed task, a disagreement, an emotional reaction, and a safety concern require different levels of attention. The Notice, Describe, Invite, Listen tool can start many conversations, but the leader still needs to recognize what kind of issue is present and choose an appropriate next step.

For a clarity problem, restate the outcome, owner, deadline, and decision rights. Ask the person to describe the plan in their own words, not as a test but as a way to identify gaps. If two people understood the instruction differently, correct the shared process instead of declaring one person careless. Put important agreements in writing so that everyone can check the same reference.

For a capacity problem, make tradeoffs visible. List the current commitments, identify which are fixed, and ask what can move if a new request is added. Avoid asking someone to “just make it happen” without discussing what work will be delayed or what support is available. If the leader controls priorities, the leader should help resolve conflicts rather than expecting employees to guess which request matters most.

For a skill or confidence gap, clarify the task and offer appropriate instruction, examples, review, or practice. Do not assume repeated questions mean a person lacks ability. The instructions may be incomplete, the stakes may be unclear, or the employee may have been penalized for a previous mistake. Identify the exact point where the person needs support. Set a check-in that helps them build ownership rather than requiring approval for every step forever.

For a disagreement about a decision, separate the quality of the discussion from the authority to decide. Invite the strongest concern and ask what evidence could change the decision. If the decision remains yours, say so and explain the reason. If the decision is open, describe when it will be made and who must be consulted. Do not keep asking for input after the choice is closed while implying that dissent could still change it.

For a performance concern, be direct about the expectation and the gap. Curiosity should help identify causes and support, not obscure the standard. State the work requirement, provide relevant examples, ask for the employee’s perspective, and agree on a measurable next step and review point. If the matter belongs in a formal performance process, follow the organization’s procedures. Avoid vague statements about attitude that leave the person unable to respond constructively.

For a relational conflict, identify the specific interactions and their effect on the work. Do not ask one person to diagnose the other person’s motives. If appropriate, help the parties state what happened from their own perspectives and what they need going forward. Set ground rules for respectful discussion. Some conflicts require a neutral facilitator or formal process rather than a leader attempting to mediate alone.

For a potential safety, harassment, discrimination, retaliation, or other serious policy issue, do not treat informal coaching as a substitute for established reporting and response procedures. Listen without promising confidentiality you cannot guarantee, record factual information according to organizational policy, and involve the appropriate people. A nonverbal impression is not a finding. The leader should act on concrete concerns through the proper channel and avoid conducting an improvised investigation beyond their role.

These distinctions keep the leader from using one technique as a solution to every problem. A conversation can surface information; it cannot replace a needed decision, resource, policy response, or formal review. The appropriate response is the one that fits the actual concern, not the one that makes the leader most comfortable.

Common mistakes that turn signals into conflict

• Assuming one cue has one meaning: A facial expression or pause is not proof. Ask what the person means and consider the setting.
• Making the conversation public too soon: Correcting or questioning someone in front of colleagues can create embarrassment and defensiveness. Use a private conversation for sensitive feedback unless immediate safety requires action.
• Using curiosity to avoid clarity: Asking what is wrong does not replace setting expectations. If a commitment was missed, explain the requirement, discuss the barrier, and agree on what happens next.
• Turning a work observation into a character judgment: “The report was late” is an observable fact. “You are careless” is a conclusion that invites conflict and gives little guidance.
• Listening only to prepare a rebuttal: If every answer is met with a defense, employees learn that explaining the situation is pointless. Hear the account first, then clarify facts and responsibilities.
• Expecting disclosure: An employee may choose not to discuss personal circumstances. Respect that boundary. You can still discuss work needs, available support, and agreed expectations.

When the concern involves a serious policy or safety matter, do not rely on body language or informal impressions to investigate it. Record concrete observations, use the organization’s established reporting channels, and involve the appropriate people. Thoughtful communication and formal accountability can work together.

Another common mistake is confusing an explanation with an excuse. An employee who describes a workload conflict is providing information. The leader still needs to decide how the work will be handled. Responding, “That is no excuse,” before understanding the facts shuts down useful information. Responding, “I understand, so the deadline no longer matters,” may also be unhelpful. A stronger approach is: “I understand the conflict. We still need to deliver the work. Let’s decide what changes and how we will flag the risk sooner.”

Leaders can also overcorrect by treating every quiet moment as a problem to solve. Some people are naturally reflective or prefer to contribute after considering the question. A team member who has not spoken in a particular meeting may still be engaged and effective. Ask whether the person’s input is needed for a decision, provide more than one way to offer it, and avoid pressuring them to perform a particular personality style. The goal is meaningful communication, not constant talking.

A further mistake is asking a question and then disputing the first answer. If the employee says the instructions were unclear, the leader may immediately respond, “I explained them twice.” That reply focuses on the leader’s effort rather than the employee’s understanding. Try asking, “Which part did you interpret differently?” You may find that the instruction was clear to the leader but incomplete for the person who had to act on it. If the account is inaccurate, you can clarify after hearing it.

Do not use “behavior is communication” to excuse harmful conduct or to imply that leaders must tolerate every action. Understanding context helps choose a fair response; it does not remove boundaries. If a person insults a colleague, state that personal attacks are not acceptable and address the impact through the proper process. You can still ask what concern the person was trying to raise, but a concern does not make the harmful delivery acceptable.

Finally, avoid turning a single conversation into a promise of secrecy, a diagnosis, or a resolution you cannot provide. Tell the person what you can keep private and when you may need to share information with an appropriate decision-maker. Do not guess at health conditions or assign a psychological explanation. If the person needs support beyond your role, point them toward the relevant organizational resource without presenting yourself as a clinician or investigator.

Follow up so the conversation leads to change

A conversation that ends without a next step may feel respectful but leave the work unchanged. Before closing, summarize the concern in neutral terms, identify any action, name who owns it, and set a reasonable time to check progress. The next step can be small: clarify an assignment, share a document earlier, revisit a decision, or give the employee space to return with more information.

Write a brief follow-up when the issue affects multiple people, deadlines, or responsibilities. Keep the message factual. For example: “We agreed that I will confirm the review owner by Wednesday, and you will send the revised schedule by Friday. If the dependency remains unresolved Thursday morning, please flag it so we can decide whether to adjust the plan.” Avoid adding a judgment such as “You finally admitted the process was confusing.” That phrasing can damage trust and distort the record.

Check whether the promised action happened. If the leader said they would clarify a priority, the employee should not have to raise the same issue repeatedly. If the employee agreed to provide an early warning, review whether the warning came in time and whether the leader responded. Shared responsibility means both parties have a role in improving the communication pattern.

Evaluate the outcome against the original work need, not against whether the person became more agreeable or expressive. If the goal was to get accurate risk information before a decision, ask whether the team now has that information. If the goal was a reliable handoff, check whether ownership and timing are clear. Avoid treating a warmer conversation or visible enthusiasm as the only evidence of progress. Respectful disagreement may remain after a good conversation.

If the first action does not work, treat that as information. Perhaps the chosen adjustment addressed a symptom rather than the cause. Revisit the observation and ask what happened. “We moved the agenda earlier, but the risk review is still being missed. What is preventing that section from happening?” This is different from accusing the person of failing to appreciate the leader’s effort. Iteration is normal when the team is learning how a process works.

Sometimes the next step is a boundary or a decision rather than another round of discussion. A leader may need to say, “I have heard your concern. The deadline remains Friday, and I need the draft by Wednesday for review. If you believe that is no longer feasible, tell me by noon tomorrow so I can reassign or revise the plan.” The leader can be open to information and firm about the next operational requirement at the same time.

Review the communication pattern over time. If the same issue keeps returning, look beyond the individuals involved. Are priorities consistently changing? Are decisions made without the people who do the work? Do people have a clear place to surface risks? Do leaders acknowledge mistakes when they create confusion? Recurrence can mean that a process change is needed, not that the people involved need another reminder to communicate.

Turn a conversation into a communication habit

After a conversation, take a moment to review your own part. Did you describe behavior accurately? Did you leave room for a different explanation? Did you listen without interrupting? Did you make a promise you can keep? These questions help leaders improve the quality of the next exchange without treating every interaction as a formal exercise.

It is also useful to notice whose signals you tend to read generously and whose you tend to read negatively. Familiarity, role, communication style, and past conflict can all affect interpretation. When in doubt, check your assumptions with a neutral question. Consistency matters: the same standard for respectful conversation should apply across roles and personalities.

Over time, teams can develop a shared practice for raising concerns early. A short check-in might ask: What is clear? What is still uncertain? What risk have we not discussed? What support would help? These questions do not guarantee agreement, but they can bring hidden assumptions into the open while there is still time to respond.

A leader can also make this practice part of ordinary meetings without turning every meeting into a lengthy group therapy session. Reserve a few minutes at the end of a planning discussion for risks, unresolved questions, and owners. Ask participants to distinguish between a concern that blocks the decision and one that can be monitored. Record the next step and the person responsible. The structure helps the team address real issues while keeping the meeting focused on its purpose.

Build a regular opportunity for individual check-ins as well. A check-in should not be limited to “Everything okay?” which can invite a quick yes and move on. Ask about the work: “What is taking more effort than expected?” “Which decision are you waiting on?” “What should I know before our next review?” Then listen to the answer and respond. If the person does not have an issue, accept that rather than repeatedly searching for hidden distress.

Leaders can make their own signals clearer by pairing words with action. If you say a deadline is flexible, explain what flexibility means. If you say you want dissent, show how a dissenting view will be considered. If you cannot discuss a decision yet, say when you expect to share more. Ambiguity can force employees to spend time interpreting what a leader might mean instead of doing the work.

Notice when the leader’s behavior may be creating the signal. If people ask for approval repeatedly, have you made the boundaries clear? If concerns arise only after a meeting, do people have enough time and permission to challenge the proposal? If a colleague has stopped sharing updates, have prior updates been ignored or punished? These questions are not an invitation to accept blame automatically. They are a way to check whether leadership practices are part of the environment that shapes behavior.

It may help to use a short personal review after a difficult exchange: What did I observe? What did I assume? What did the other person say? What did we agree to do? What do I need to communicate next? The review keeps the focus on learning and follow-through. It also helps leaders avoid retelling the event later as though their first interpretation were a proven fact.

Over time, the aim is not to eliminate every misunderstanding. People have different roles, priorities, and perspectives, and some disagreements will remain. The aim is to make it normal to identify an ambiguity, ask what someone means, and correct a misunderstanding before it grows into avoidable conflict. Leadership IS communication: the quality of the conversation affects whether the team can coordinate, make decisions, and work through change.

Practice the method with realistic leader scenarios

A communication tool becomes easier to use when leaders rehearse it against ordinary work situations before a difficult moment arrives. Practice does not mean memorizing a script. It means learning to notice where an observation ends and an assumption begins, then selecting a question that invites useful information. You can use a current situation, a recent case with names removed, or a hypothetical example. Write down the first sentence you are tempted to say. Then revise it to include what you directly observed, why it matters, and an open invitation. If your first draft labels a person, convert the label into a description of an action or a work result.

For example, suppose a project lead’s first thought is, “Maya is not a team player because she never helps.” That sentence contains a judgment and a sweeping claim. A closer review might show that Maya declined one request to review a draft while handling a deadline of her own. The leader can identify the concrete question: “Last week you were not able to review the customer notes before our handoff. How should we plan peer review when both teams have deadlines?” This framing allows the leader to discuss capacity and shared work without treating one refusal as a personality diagnosis.

Rehearsal can also make it easier to respond when the other person disagrees with your description. If the leader says, “I noticed you left before the final discussion,” and the employee replies, “I told the organizer I had a client call,” the correct next step is to update the account, not defend the original interpretation. You might respond, “Thanks, I did not know the call was scheduled. I still want to make sure you have a way to weigh in on the final decision. Would a written update beforehand work?” That response uses the corrected information to address the real need.

Leaders can practice with a partner by taking turns as manager and employee. The person playing the employee can give an unexpected answer: the issue was a missing resource, an unclear decision, a personal boundary, or no issue at all. The manager’s task is to listen and ask one clarifying question before proposing a fix. Afterward, discuss what felt like an invitation and what sounded like a disguised accusation. Keep the exercise brief and focused on observable wording rather than judging who performed well.

A simple practice sheet can contain four prompts: What did I observe? What impact can I name without exaggerating? What am I assuming? What question would help me learn? Add a fifth prompt after the conversation: What did we agree to do and when will I follow up? These prompts can be used during one-on-one preparation, not as a bureaucratic form for every interaction. Their value is the pause they create between noticing behavior and reacting to it.

Choose the right channel and setting

How a leader raises a concern is part of the message. A sensitive question sent in a group chat may feel like public criticism. A long email about an ambiguous interpersonal issue can invite misunderstanding because tone and immediate clarification are missing. A private conversation may be better for exploring a change in participation, while a written note may be useful for confirming a clear deadline or capturing an agreed task. Choose the channel according to the purpose, urgency, sensitivity, and need for a record.

For a routine issue with a simple answer, a direct message can be efficient: “I noticed the draft is not in the shared folder yet. Is the Thursday date still workable?” For a recurring pattern with several possible causes, schedule a conversation that gives both people enough time. Explain the topic in advance without announcing a verdict: “I’d like to review the handoff timing and understand what is getting in the way.” Surprising someone with a serious concern in the final minute of a meeting leaves little space for reflection and may produce a defensive response.

Consider whether the location offers privacy and whether the person can participate comfortably. Avoid sensitive conversations where colleagues can overhear. For remote teams, check that the person has a chance to speak without being interrupted by a room full of participants. If a video call is not practical, a phone call or written exchange may fit better. Do not assume that one format works equally well for every person; ask what would help them contribute while preserving the need to address the issue.

Urgency matters. If a behavior creates an immediate operational or safety risk, address the immediate requirement promptly and clearly. You can say, “Pause the handoff until the review is complete,” then discuss the broader pattern when there is time. Do not delay urgent instructions in the name of curiosity. Conversely, do not treat a nonurgent change in tone as an emergency simply because it makes the leader uncomfortable. Match the response to the actual consequence.

Written communication deserves special care because a brief sentence can sound harsher than intended. Avoid sending an accusation while angry. Use concrete language, state the question, and keep the audience limited to people who need the information. If the subject has several interpretations, use the written message to arrange a conversation rather than conduct the entire discussion through fragments. After talking, a concise written summary can confirm responsibilities and dates without attempting to document private emotions.

When a person does not respond to an invitation, do not immediately infer defiance. Check that the message reached them, that the request was clear, and that they understood when a reply was needed. A second message can explain the purpose and offer a reasonable choice of times. If there is still no response and the issue affects work, state the requirement and next step directly. Respectful inquiry does not require a leader to wait indefinitely for participation when a decision or deadline must be handled.

Separate individual signals from system conditions

When the same type of behavior appears repeatedly, ask whether the team’s system makes the behavior more likely. If several people miss a review deadline, the cause may be a poorly sequenced process, competing priorities, or an unclear owner. If employees repeatedly ask the same question, the answer may be hard to find or may change depending on whom they ask. Treating each instance as an isolated attitude problem can leave the underlying obstacle intact and create more frustration.

Map the work from beginning to end. Identify who starts the task, what information they need, where a handoff occurs, who approves the result, and how changes are communicated. Ask where work waits and which decisions are routinely reopened. A simple map can make an invisible dependency visible. For example, a report may be called late even though the analyst has completed it; the report might be waiting for an approver who was never named. The useful leadership response is to clarify ownership and timing, not to tell the analyst to show more urgency.

Review how requests enter the team. Multiple leaders may give employees separate assignments without coordinating priorities. A manager may describe an outcome but omit the quality standard or the person empowered to resolve questions. A deadline may be repeated in a meeting but not recorded where the team can find it. When behaviors cluster around these conditions, leaders should improve the communication system as well as discuss individual responsibilities. One clear source of current priorities can reduce the need for employees to infer what matters most.

Look at how the team makes decisions. Does everyone know whether they are giving advice, approving a choice, or carrying out a decision already made? Is there a clear point at which debate ends? If not, repeated objections may be a predictable response to uncertainty rather than resistance. Define the decision owner, the people whose input is needed, the deadline for input, and the way the final choice will be communicated. Then see whether the behavior changes. The process itself can convey respect by showing people when and how their contribution matters.

System thinking does not mean that no individual is accountable. A process can be unclear and a person can still be responsible for asking a question or flagging a risk. The leader’s task is to establish conditions where those responsibilities are reasonable and understood. If a team member continues to miss a clear commitment after barriers and expectations have been addressed, direct performance feedback may be appropriate. The sequence matters: clarify the system and the expectation, hear the person’s account, then address the remaining gap with specific examples.

Use a small experiment rather than making a sweeping organizational claim. If agendas arrive late, try sending them earlier for a few meetings. If late objections recur, add a structured risk round before decisions. If ownership is confused, publish a simple decision map for one project. Define what you will look for, when you will review the result, and who will gather feedback. A limited test makes it easier to learn whether the adjustment helped without pretending to solve every communication issue at once.

When the experiment does not help, ask what the result teaches you. Perhaps people need more time to prepare, but the agenda is not the only obstacle. Perhaps a written route exists, but employees do not know whether the leader reads it. Perhaps a decision map clarified approval but left capacity conflicts unresolved. Avoid defending the intervention merely because it was your idea. A leader models effective communication by being willing to revise a process in response to what the team learns.

Give feedback without turning behavior into identity

Feedback is most useful when it describes a behavior the person can understand and influence. “You are careless” turns an event into an identity. “The last two client summaries did not include the agreed review date” names a specific gap that can be corrected. Identity labels often trigger argument about character; behavior descriptions support a discussion about expectations, impact, and next actions. The same principle applies to positive feedback: identify what the person did and why it helped, rather than relying only on a broad label such as “You are a natural leader.”

Use a clear sequence: state the situation, name the behavior, describe the impact, and ask for the person’s view. For example: “During Monday’s handoff, the revised file was shared after the review had begun. The team worked from two different versions for part of the meeting. What happened from your perspective?” This description is specific and open to correction. Once you understand the facts, agree on the standard for the next handoff and how both sides will know it has been met.

Be timely but not impulsive. Feedback delivered close to an event can be easier to connect to the work, but a leader who is still angry may overstate the case. Take enough time to verify what happened, then raise it while the details are useful. If you need to delay, do not let the issue disappear. Tell the person you want to discuss the handoff and schedule a time. Waiting indefinitely can make the eventual conversation feel surprising or unfair.

Make feedback two-way. Ask whether the expectation was clear and whether the person had the information or authority needed to meet it. The answer may reveal a leader’s own communication gap. A manager might say, “I expected the revised version in the shared folder, but I did not specify that the team should stop using the email attachment. I should have made that clear. Going forward, let’s name one source of truth.” Taking responsibility for unclear instructions does not prevent the leader from setting a standard; it makes the standard more credible.

When feedback concerns repeated conduct, describe the pattern carefully and explain why it matters. Provide more than one example if the claim is about repetition. Give the person a chance to respond before deciding what the pattern means. Then state the expectation plainly. “I need you to flag a likely delay by the morning it becomes apparent, rather than after the deadline. Is there anything that would prevent you from doing that?” This question checks feasibility while preserving the requirement.

Do not use body language as a shortcut for giving feedback. Saying “You looked disrespectful in the meeting” is less clear than identifying the observable action: “You spoke over two colleagues before they finished their updates.” If the concern is an expression or posture that cannot be tied to a work impact, consider whether it needs to be raised at all. Leaders should not police harmless expressions or demand that employees perform agreement to make the leader comfortable.

Positive behavior can also be named with specificity. If a colleague raised a concern early, say what they did: “You flagged the dependency before we finalized the timeline, so we had time to adjust the review plan.” Explain the value without claiming to know the person’s motive. Specific recognition tells the team which actions support clear coordination and reinforces that speaking up can lead to thoughtful consideration, even when the proposed change is not adopted.

Adapt the conversation to remote and hybrid work

Remote and hybrid settings remove some of the informal context leaders may rely on in a shared workplace. A person who is not speaking in a video meeting may be taking notes, managing a technical issue, or participating through chat. A short message can appear abrupt without vocal tone. A camera being off does not reveal a person’s level of attention. Leaders should not turn digital presence indicators or response speed into a universal measure of commitment.

Set explicit communication expectations for the team. Clarify which channel is used for urgent requests, which is used for project updates, and when a response is expected. If a message needs an answer by noon, say so. If no immediate response is needed, indicate that too. People should not have to infer urgency from repeated pings, punctuation, or a leader’s online status. Predictable norms reduce accidental silence and help distinguish a missed expectation from a difference in communication habits.

Provide ways to contribute that do not depend on speaking at the exact moment a question is asked. Share materials in advance, allow chat or written input, and summarize decisions afterward. For a complex meeting, state the question and leave time for people to think. If a colleague has been quiet, ask privately whether the format is working rather than demanding that they turn on a camera or speak without preparation. The standard should be meaningful participation in the work, not a particular display of participation.

Take care when interpreting delayed responses across time zones, schedules, and caregiving or focus periods. A leader can set a service expectation for a role, but should communicate it clearly and consistently. If the expectation is a same-day response during specified working hours, say that. Do not assume that a person who is unavailable outside those hours is disengaged. If a delay creates a real dependency, discuss coverage, ownership, or escalation rather than making a judgment about commitment.

For a sensitive remote conversation, choose a private channel and confirm that the person can speak freely. A video call may support a nuanced exchange, but it is not always the best format. Offer a phone call or another appropriate way to talk. Avoid raising a personal or performance concern in a public chat thread. If a written message could be forwarded or misunderstood, use it to arrange a discussion and send a neutral summary of work agreements afterward.

Remote work can make follow-through especially visible. When a leader says they will send a decision, update the project record. When someone flags a blocker in chat, acknowledge it and explain who will act. If a concern is raised in a one-on-one, do not expect the employee to repeat it in a public channel simply so the work can move. Agree together on what should be shared with the team and what should remain private. Clear coordination helps prevent the same silence from being interpreted differently by different people.

Measure communication improvement by work outcomes

Leaders often want to know whether a conversation worked. Avoid measuring success by whether the employee smiled, agreed, or appeared more relaxed at the end. Those signals can mean many things, and the person may remain uncomfortable even when the discussion was respectful. Define success in terms of the original work need: Is ownership clear? Was a risk raised in time? Does the employee know the priority? Did the team make a decision and communicate it? These questions focus attention on observable results.

Set a simple baseline when a recurring pattern matters. If a team wants to raise risks earlier, note where in the project risks currently appear and what happens after they are raised. If ownership is often unclear, list the handoffs that lack a named owner. A baseline is not a scorecard for judging people’s personalities. It is a practical reference that helps the team decide whether a change in process is useful.

Review outcomes with the people affected. Ask whether the new approach made information easier to share and whether any burdens shifted to another part of the team. A process that improves one person’s visibility but adds unnecessary work for someone else may need adjustment. Invite concrete examples: “Which handoff was clearer this week?” is more useful than “Is communication better now?” Specific examples help the team learn what to keep and what to change.

Do not overmeasure every interaction. Excessive tracking can make a team feel monitored and encourage people to perform indicators rather than communicate honestly. Choose a small number of work-related signs, review them at a reasonable interval, and discontinue measures that do not help decisions. The goal is to improve coordination and understanding, not to score silence, facial expressions, or personality traits.

Separate a successful conversation from a successful outcome. A leader may listen fairly, clarify the issue, and agree on a sensible next step, yet a project can still encounter a new obstacle. Conversely, a deadline may be met even though employees were afraid to mention risks. Evaluate both the quality of the conversation and the outcome of the work. If the plan did not succeed, ask what new information emerged and what should change next time.

Make learning visible. At the end of a project, ask which communication practices helped the team act, where people had to guess, and what they would change for the next project. Keep the discussion focused on examples and systems rather than assigning motives after the fact. A team that can examine a communication breakdown without turning every review into blame is more likely to raise the next concern while there is still time to address it.

Connect with Jeff about communication coaching

Frequently asked questions

Does behavior always communicate an intentional message?

No. Behavior can affect how others understand a situation even when the person did not intend to send a message. A late reply, silence, or change in participation might be purposeful, accidental, or related to circumstances the leader cannot see. Treat it as a cue to check context, not proof of intent.

How can a leader interpret body language accurately?

There is no dependable universal translation for one gesture or expression. Consider the setting and the person’s usual communication pattern, describe what you actually observed, and ask an open question. Avoid drawing conclusions about honesty, interest, or commitment from a single nonverbal cue.

What should I do if an employee says nothing is wrong?

Accept the answer without insisting that the person disclose more. You can make it clear that the conversation remains available and discuss any concrete work expectation that needs attention. If there is a specific operational concern, describe it and agree on how you will handle the work, regardless of whether the employee wants to explain a personal reason.

Does curiosity mean a leader should avoid accountability?

No. Curiosity helps a leader understand what happened and what support or correction is needed. The leader can listen carefully and still restate a deadline, standard, or boundary. A fair conversation addresses both the context and the responsibility for the next step.

When should a concern go beyond an informal conversation?

When an issue involves safety, harassment, discrimination, retaliation, or another formal workplace matter, follow the organization’s established reporting and response process. Do not rely on impressions of body language or attempt to conduct an investigation outside your role. Use the appropriate channels and share factual observations.

Make the next conversation clearer

Behavior can alert a leader to a message that has not been spoken, but only a conversation can help clarify what that message means. Notice the change, describe it fairly, invite the person’s perspective, and listen for a practical next step. The goal is not to interpret people perfectly; it is to communicate well enough that they do not have to rely on silence or signals alone.

When leaders respond to behavior with careful questions and consistent follow-through, they make clearer communication a shared responsibility rather than a guessing game.