Notes on communication skills questions from the field as of 2027

Some questions cannot be answered usefully. Not because the topic is hard, but because the question is built so that the easy answer costs nothing and the true answer costs something.

Each entry below takes a common workplace question, says what it actually asks for, and gives the version that produces information.

What to take away

"Does that make sense?"

What it asks for: reassurance. What it gets: yes.

The reader has to weigh a small confession of confusion against a costless agreement, in front of other people, usually at the end of a long explanation. The odds are not close.

Better: what would you do first? The answer either matches your intent or shows exactly where the explanation failed.

"Any questions?"

What it asks for: a volunteer to go first. What it gets: silence, which is then

read as understanding.

Better: name a specific area and invite an objection to it. "What is the weakest part of this?" gets an answer because it is a request for expertise rather than a confession of confusion.

"Are we aligned?"

What it asks for: an end to the conversation. What it gets: agreement about the word "aligned", which nobody has defined.

Better: state the thing you believe you have agreed and ask what is wrong with it. Alignment that survives being written down in one sentence is real. Alignment that only exists as a word is a scheduling convenience.

"Do you have capacity?"

What it asks for: a yes. What it gets: a yes, because capacity in the abstract always exists somewhere.

Better: ask what this would displace. That converts an abstract question into a comparison, and comparisons produce honest answers. The distinction between capacity and utilization is set out among the operating word pairs, and it is the same confusion in a personal register.

"Is this urgent?"

What it asks for: a priority. What it gets: yes, because the asker has usually already implied the answer.

Better: ask what happens if it waits until a named date. Urgency described as a consequence is checkable. Urgency described as an adjective is a mood.

"Can you take a look?"

What it asks for: unclear. What it gets: a look, which is not a defined action.

Better: name the verb. Read for errors, comment on the approach, or approve for release are three different jobs taking three different amounts of time, and the reader cannot guess which one you meant. The asking and chasing words set out the full range.

"Who owns this?"

This one is a good question, and it fails for a different reason. Asked in a group, it invites a general answer. Asked after the fact, it sounds like blame.

Better: ask it in advance and ask for a name, not a team. Then say what owning it means here: deciding, doing, or being answerable for the outcome. Those three can sit with different people, and the trouble starts when everyone assumes otherwise.

"Why did this happen?"

What it asks for: a cause. What it often gets: a person, because the fastest

answer to why is a who.

Better: ask what the process allowed. That keeps the answer in the system, where it can be fixed, not in someone's judgment, where it cannot.

The pull to explain outcomes by character rather than situation is the fundamental attribution error. Asking about process is the practical counterweight. Habit matters more than wording: people answer the question they think you are really asking.

The pattern

Every repair in the right-hand column does the same thing. It replaces a request

Questions nobody can answer from a page

Some questions belong to your situation, not to any guide. Whether a message goes to a person or a group, whether a relationship can take direct correction, and whether your organization treats a written decision as binding are local facts.

A page can tell you what to ask. It cannot tell you what the answer is where you work.

Where a question touches employment, contracts or anything with legal weight, the honest answer is that a general page is the wrong source. Guidance from the relevant public body, or an advisor who knows your jurisdiction, is the right one.

Common questions

Will people find these questions blunt?

Some will, the first few times. Blunt is about tone and can be softened. Specific is about content and should not be. Federal guidance on testing a document with real readers recommends the same substitution: watch what someone does rather than ask whether they understood.

What if I am the one being asked a bad question?

Answer the better version and say you are doing it. "I think what you are asking is whether Thursday is realistic, and the answer is no unless the data arrives tomorrow" is helpful rather than pedantic.

Does this apply to written messages as well as meetings?

More so. In writing the reader can decline to answer at no social cost, so a vague question gets nothing at all. The communication skills guide covers how the channel changes the calculation.

Is there ever a reason to ask a question you have already decided?

Only if you would genuinely change the decision. Otherwise say what was decided and what is still open. Repeatedly asking closed questions teaches people that answering is pointless, and the nine communication errors treat that as one of the more expensive habits.