Direct doesn't have to mean disrespectful: asking clarifying questions without sounding confrontational

A manager I came across recently ran into a problem I suspect a lot of people recognize. Two years into managing, reporting to an executive, she was on a call and asked three questions: what was the purpose of the meeting, why were we invited, and what were the takeaways for her team. Afterward, someone on that call went to her boss. The feedback that came back was that she had been “too direct and not a team player.”

She was not defensive about it. She wanted to know how to be better. When she asked more experienced managers for advice, the useful responses were not arguing about whether she was right. She mostly was. They pointed at something more specific: the questions were reasonable, and the framing was what got her in trouble.

I build a tool that lives right in the middle of this problem, the gap between what people think and what they feel safe saying at work. I went through the advice she got and the communication research behind it. The pattern that emerged is worth laying out, because “be less direct” is bad advice and most managers know it. The better version is narrower and more useful.

Key takeaways

The manager’s questions were legitimate. Experienced managers and the research agreed. What landed badly was how and when she asked, not what she asked.
Swapping “why” for “how” or “what” turns a question from a challenge into an offer to help, while getting you the same information.
Direct and respectful are not opposites. Radical Candor calls the goal caring personally while challenging directly. The trouble is challenge with the care left invisible.
Tone carries more weight when your words are ambiguous, which is exactly the situation a blunt clarifying question creates. On a call with no camera, delivery does most of the work.
Some of this is not your fault. Directness gets read differently depending on gender and culture. You can still control framing and timing.
The deeper fix is meeting hygiene. Most of these questions never need asking if the meeting had an agenda in the first place.

The questions were fine but the delivery wasn’t

Start with what almost everyone agreed on, because it matters. “What is the purpose of this meeting” and “what should my team take away” are not hostile questions. Several people who described themselves as blunt communicators said they would have asked the same things. The diagnosis that kept coming up was simple: the questions were valid, but words and phrasing can put people on edge, and derailed communication turns unproductive fast.

So this is not a story about a manager who was wrong and needs to soften into agreeability. Overcorrecting into silence is its own failure. Asking for clarity is part of good management. The skill is making the question sound like you are helping the group move forward rather than questioning why the meeting exists. That is close to the whole point.

Trade “why” for “how” and “what”

The single most repeated piece of advice was a small one: start clarifying questions with “how” or “what,” and avoid “why.”

“Why” puts people in a defensive posture. It asks them to justify a decision, and most people hear “why are we doing this” as “this was a bad idea.” “How” and “what” ask for the same information but frame you as someone trying to contribute. One version of the rule is worth memorizing: “why” is nice-to-know, while “how,” “what,” “when,” and “where” read as need-to-know. Change the word and you flip the tone from a challenge of authority into an offer of collaboration.

The before and after versions make it concrete:

Sounds like a challenge	Reads as collaboration
“Why are we doing this?”	“What are the goals we’re aiming for here?”
“Why was my team invited?”	“How can my team best contribute?” or “How can I help?”
“What was the point of this meeting?”	“So I take the right actions back to my team, could you clarify the main objective and expected outcomes?”
“There’s no agenda?”	“Could we add a short agenda to the invite next time so everyone comes prepared?”
(pushing back on a claim)	“Help me understand how you’re seeing this.” or “I’m curious about that, tell me more.”

Same information every time. The right column just does not make the other person feel put on trial. Some people mentioned running their messages through an AI to soften tone before sending, which is fine, but the “how/what” habit is something you can do live, in the moment, without a tool.

Direct and respectful are not opposites

“Be less direct” treats directness as the problem. The real problem is directness without warmth.

Kim Scott’s Radical Candor framework maps this on two axes, how much you care personally and how much you challenge directly:

Challenge, no care: obnoxious aggression. Blunt and cold.
Care, no challenge: ruinous empathy. The boss who never tells you anything useful.
Both at once: the goal. Clear about the issue, clearly on your side.

The manager was challenging directly. What the other person did not feel was the care. That is fixable without dialing down the challenge. “How can my team best contribute” asks the same thing as “why are we here,” but it signals you are on the same side. A velvet glove for the same message, not a boxing glove.

One more idea worth naming: psychological safety, Amy Edmondson’s term for a team where people can raise concerns without fear of looking foolish or being punished. Clarifying questions are supposed to be a sign of it. The irony here is that the manager asked a safe question in a way that lowered someone else’s safety, by putting the organizer on the spot in front of the group. Which brings us to timing.

Timing: praise in public, critique in private

The same question changes meaning depending on when you ask it. Those questions likely came at the end of the meeting, publicly, after the manager had already decided it was a waste of time. At that point they stop being clarifying and start being a verdict, with no runway left to fix anything.

Same words, different moment:

Up front: “What’s the objective, and how should my team prepare?” Sets the meeting up.
At the end, in the room: “What was the purpose of this meeting?” Reads as “you wasted my time.”

If a meeting has no agenda and you want to raise it, do it before it starts or one on one afterward, framed as a process suggestion. Not during the meeting as a scorecard in front of everyone.

Some of this is not about your wording

Two honest caveats, because both are real and neither is fully in your control.

Tone does real work, but not 93% of it. You may have heard the 7-38-55 rule, the claim that 7% of a message is the words, 38% the tone, and 55% body language. Be careful with it. Those numbers come from a pair of narrow 1960s experiments by Albert Mehrabian on communicating feelings, and they get badly overstated whenever someone claims words barely matter. Words matter a lot. The honest kernel is narrower: when your words and your tone conflict, people trust the tone. A clipped clarifying question is exactly that kind of mixed signal, and on a call with no camera, your voice does the work body language usually shares.

Directness is not read the same way for everyone. Women in the discussion, including executives, pointed out that the same words that make a man sound assertive can make a woman sound aggressive. It is a real double standard and it is not fair. There is also a cultural layer: what counts as normal directness in one place reads as blunt in another, which researchers describe as high-context versus low-context communication. You cannot control any of that. You can control framing and timing, which is where you actually have room to act.

The real fix is the agenda

Most of these questions never need to be asked in a tense moment, because a decent agenda answers them in advance. The manager noted the meeting was scheduled last minute, late in the day before a holiday, with no agenda. Of course people were confused about why they were there.

Roger Schwarz, who writes about meeting design, has a few habits that remove the need for anyone to play detective mid-meeting. His guidance on agendas is worth reading in full, but the parts that map directly onto this problem are these:

Write agenda items as questions the group needs to answer. Not “office space,” but “under what conditions, if any, should we reallocate office space.” A question tells people how to prepare and how to know when the discussion is done.
Label each item’s purpose: is this to share information, gather input, or make a decision. Most frustration comes from people not knowing whether to just listen or to weigh in.
Say who should attend and why, and send updates to read beforehand instead of reading them aloud.
End with a quick plus/delta: what went well, what to change next time. Two questions, five minutes, and meetings get better on their own.

If you are the one being invited to agenda-less meetings, the collaborative version of the complaint is a standing request: “could we get a one-line objective in the invite so we can come prepared.” That fixes the root cause for every future meeting instead of litigating this one.

Where TeamMood fits

Look at what actually happened here. The manager’s honest reaction, that the meeting was a waste of her team’s time, was real and probably shared by others in the room. It had nowhere safe to go, so it came out as a pointed question at the wrong moment. The organizer’s discomfort also had nowhere safe to go, so it traveled to the boss as secondhand feedback. Two people avoided saying the direct thing to each other, and the direct thing leaked out sideways anyway.

That is the gap TeamMood is built to sit in. It gives a team a low-stakes, anonymous channel to say the thing that is hard to say to a face, before it turns into either a tense meeting moment or a complaint routed through someone’s manager.

A few concrete ways it helps with exactly this problem:

Meeting fatigue shows up in the mood trend. When a run of agenda-less meetings is grinding people down, you tend to see it in the check-ins and comments before anyone risks saying it out loud. That is your early signal to fix the agenda, and it saves your team from having to confront you in the moment.
Anonymous comments remove the tone tax. This whole problem is about the cost of being honest to someone’s face, a cost that falls harder on women and on blunt communicators. When a comment is anonymous, the “how you said it” pressure mostly drops away and you get the substance.
It closes the loop the way a plus/delta does. Schwarz’s advice to end meetings by asking what to change works because people see action follow. Bringing an anonymous comment into a retro and saying what you changed because of it is the same move at team scale. It teaches people that raising something leads somewhere, which is what keeps them raising things.

None of this replaces learning to ask a good “how” question in the moment. It gives the honest signal a place to land so it does not have to come out as a confrontation or a complaint behind your back.

Final thoughts

The advice the manager was given, to be less direct, was the wrong lesson from a real event. Her questions were fine. What tripped her up was reaching for “why” instead of “how,” asking at the end instead of the start, and doing it in a room that never had an agenda to begin with. Every one of those is fixable without becoming vaguer or more agreeable.

Direct and respectful were never in tension. The managers who pull it off are not softer. They are just clearer about being on your side while they challenge you, and they build the kind of meetings and feedback channels where the honest thing has an easy way out. Do that and “too direct” stops being a complaint people take to your boss.

FAQ

Is it wrong to ask why we’re having a meeting?

No. Asking the purpose of a meeting and what your team should take away is reasonable and, done well, is good management. The issue is usually framing and timing. Starting with “why” can sound like a challenge, and asking at the end of a meeting can read as a verdict. Ask “what is the objective and how can my team contribute,” and ask it up front.

How do I ask a direct question without sounding rude?

Swap “why” for “how” or “what,” which requests the same information but frames you as trying to help rather than challenging a decision. Add a short reason for asking, such as “so I take the right actions back to my team.” Soft openers like “help me understand” or “I’m curious about that” also work.

Does being direct mean I’m not a team player?

Not at all. Directness and being a team player are independent. In Kim Scott’s Radical Candor framework, the goal is to care personally and challenge directly at the same time. Problems come from challenge that shows no warmth, not from directness itself.

Is the 7-38-55 communication rule real?

Partly. The numbers come from narrow 1960s experiments about communicating feelings and are widely overstated. Words matter far more than 7% in most situations. The reliable takeaway is narrower: when your words and tone conflict, people tend to trust your tone, which is why delivery matters most for ambiguous or blunt questions.

How can TeamMood help with meeting and feedback tension?

It gives teams an anonymous, regular channel to surface frustrations, like meetings with no clear purpose, before they turn into tense moments or secondhand complaints. Managers can spot dips in mood tied to meeting overload, read anonymous comments without the tone pressure that makes honesty risky, and close the loop by acting on what they learn. TeamMood is at teammood.com.

Learn more about TeamMood
and sign up here

Header photo by Johannes Plenio