The right response depends on whose needs have room in the conversation. Someone communicating passively may set their own needs aside; someone communicating aggressively may press ahead at another person’s expense. Both can leave a team unsure what has actually been agreed.
When silence becomes an agreement
What is passive communication? It is a pattern of holding back needs, preferences, or objections when expressing them would help others understand a situation. A colleague might say “whatever works” about a deadline they know they cannot meet, then work late in silence. The manager hears consent; the colleague experiences pressure. Neither has the information needed to make a workable plan.
A passive style of communication can blur boundaries because the limit remains unspoken. It can also make feedback harder to use: a polite nod may conceal a question, a disagreement, or a request for help. Quiet reflection is valuable, and a person may need time before responding. The practical distinction is whether a necessary concern eventually reaches the people who can act on it.
Try replacing an automatic yes with a specific constraint and an alternative: “I can finish the analysis by Thursday, or I can send the summary tomorrow. Which would be more useful?” The other person can now make a choice instead of guessing what the silence means.
Aggressive communication and the cost of pressure
Aggressive communication pushes a point through intimidation, blame, or disregard for another person’s chance to respond. In a meeting, a manager might say, “Your team always misses the point. Fix this today,” before anyone can explain the delay. The urgency is audible; the request is less clear. People may comply, defend themselves, or stop bringing problems forward.
The aggressive style of communication crosses boundaries by treating another person’s time, judgment, or dignity as obstacles to overcome. Strong disagreement and firm deadlines have a place at work. The difference lies in how they are expressed: naming a problem and inviting an answer leaves space for useful information; insults and threats crowd it out.
Instead of attacking the team, describe the gap and the decision needed: “The report is missing the customer data we agreed on. What prevented its inclusion, and when can we have a corrected version?” Listen to the answer before deciding whether the deadline or resources need to change.
Make the next exchange easier
A clear, respectful response states what you observe, says what you need, and leaves room for the other person’s perspective. It can be brief. At work, that might sound like this:
- When a meeting runs over: “I need to leave at three. Can we decide who will follow up on the remaining items?”
- When feedback feels too broad: “You mentioned that the presentation lacked focus. Which section should I revise first?”
- When a request conflicts with existing work: “I can take this on if we move the launch review to Friday. Does that tradeoff work?”
If you tend to communicate in a passive way, prepare one sentence about your limit before a difficult discussion. If you tend to press hard, pause after your request and give the other person time to answer. In either case, check the outcome in concrete terms: who will do what, and by when? A written recap can help when several people share responsibility.
Choose wording that makes your need clear while allowing the other person a real opportunity to respond.