There is a particular kind of helpfulness that quietly makes meetings worse.
Someone brings you a problem. You understand enough to see a path. You care enough to respond quickly. So you give the answer. You explain the fix. You move things along.
It feels efficient, and sometimes it is. But often you have solved the first version of the problem, not the real one.
The first version is usually incomplete. It is the version the other person can explain quickly, or safely, or without admitting how stuck they are. If you solve too early, you train the conversation around your speed instead of their clarity.
One clarifying question before your answer can change that.
Why solving is so tempting
Solving feels productive. It gives everyone the relief of motion. It also gives you a role: capable, useful, decisive.
That is especially tempting if you are a founder, manager, senior operator, consultant, or salesperson. Your value has probably been rewarded through answers. People come to you because you can see the pattern and name the path.
But the same strength can become a reflex.
When you solve too quickly, a few things happen:
- You may miss the constraint that makes your answer unworkable.
- You may take ownership of a problem the other person should learn to handle.
- You may make people less likely to bring half-formed thinking.
- You may create agreement without commitment.
- You may answer the emotional part with a technical fix.
There is also a subtler cost. When you always provide the answer, other people get less practice building judgement. They learn to escalate quickly instead of thinking one layer deeper.
That might feel useful in the moment. Over time, it makes you the bottleneck.
The one-question rule
Before you offer a solution, ask one clarifying question.
Not five. Not a full coaching performance. Just one question that helps you understand the shape of the problem before you touch it.
Good clarifying questions are simple:
- "What have you already tried?"
- "What is the part that feels stuck?"
- "What decision are you trying to make?"
- "What would a good outcome look like?"
- "What is the risk if we do nothing?"
- "Who else needs to be involved?"
- "What do you need from me: advice, a decision, or a second pair of eyes?"
That last one is especially useful. Many meetings become muddy because the request is unclear. The person might need approval, coaching, emotional backup, technical input, or a decision. If you assume the wrong need, your help becomes noise.
One question slows you down just enough to aim.
What to listen for
The goal is not to delay action. The goal is to locate the real problem.
Listen for the mismatch between what they say and what the situation seems to require. They may present a resource issue when the real issue is unclear ownership. They may describe a customer objection when the real issue is weak discovery. They may ask for advice when what they need is permission to make a call.
Here are a few common translations:
- "We need more time" might mean "We have not agreed what done means."
- "The client is difficult" might mean "We have not found the real buying concern."
- "I am blocked" might mean "I do not know who owns the decision."
- "Can you look at this?" might mean "I do not trust my judgement yet."
- "Just checking" might mean "I am worried this will come back on me."
Your first solution will often address the sentence. Your first question helps you address the situation.
How to avoid sounding like a robot
There is a way to ask questions that feels generous, and a way that feels like a leadership book has entered the room wearing shoes.
Do not interrogate people. Do not withhold help to prove a point. Do not turn every small request into a coaching moment with theatrical patience. People can feel that from across the table.
Keep it plain:
- "Before I answer, can I check one thing?"
- "I have a suggestion, but I want to understand the stuck point first."
- "What do you think the real decision is here?"
- "My instinct is to solve this too fast. What am I missing?"
That last sentence is disarming because it names your own habit. You are not making the other person perform. You are making the conversation better.
After the question, you can still be decisive. In fact, your answer will usually be cleaner because it is grounded in the actual problem.
The change you are really making
This habit is not just about better answers. It changes the power dynamic in the room.
When you ask before solving, you communicate that the other person has useful judgement. You create space for context. You reduce dependency. You make it safer to bring problems early because the meeting will not instantly become a lecture.
For managers, it builds capability. For salespeople, it earns the pitch. For leaders, it keeps decisions connected to reality. For teammates, it prevents the little misunderstandings that become expensive later.
The move is small enough to practise today. Pick one meeting where you normally advise quickly. Before your first answer, ask one clarifying question. Then notice whether the conversation changes.
Cutivo is useful here because this pattern shows up clearly in real transcripts. It can show where you moved straight to advice, where one question opened the room, and whether the next meeting contained the better habit. The point is not to ask questions forever. It is to solve the right problem.