The farmer arrived at the healer's cottage bent nearly in half, one arm wrapped around his stomach.
"It's the pain again," he said through his teeth. "Started two days ago. Feels like it's burning."
The village healer had seen a hundred cases like this. Bad grain was going around that season, and half the village had come through with the same complaint. He didn't need to hear much more.
"Spoiled feed," he said, already reaching for the shelf. "Happens every harvest. Drink this, rest for two days, and stay off anything heavy."
The farmer nodded, grateful someone had an answer so quickly, and went home with his remedy.
Three days later, he was back, worse. Fever now. Sweat on his brow even in the cool morning air. The healer frowned, gave him a stronger dose of the same purge, and told him to be patient.
By the end of the week, a traveling physician passing through the village was called in. She knelt beside the farmer and did something the first healer hadn't.
She asked.
"Where exactly does it hurt? Show me.”
"Has anything happened to you these past weeks? An injury, a fall, anything like that?"
The farmer hesitated, then lifted his tunic. Along his ribs, hidden beneath the fabric, was a wound gone the color of a bruised plum, hot to the touch. A bull's horn had caught him three weeks earlier while he was working the fence line, just a graze, barely broke the skin. Nothing worth mentioning. He'd cleaned it himself and gone back to work the next day.
It had festered beneath the surface ever since, and everything the farmer felt, the fever, the burning, the pain, had been his body trying to tell someone about a wound no one had thought to look for.
The physician didn't give him another remedy. She opened the wound, cleaned it properly, and within days, the fever broke.
The first healer wasn't careless. He was fast, confident, and experienced. He'd simply treated the symptom he expected instead of the wound that was actually there, because he never asked the question that would have revealed it.
The Diagnosis Nobody Made
Most of us don't hand out herbal remedies for a living. But we make the same mistake constantly, in ordinary conversations, at a pace that would make the healer look patient by comparison.
Someone brings us a complaint, a frustration, a problem, and within seconds we've already diagnosed it. We reach for the answer we're most confident in, the one that matches the symptom we recognize, and we deliver it. An opinion. A fix. A "here's what you should do."
It feels efficient. It often feels generous, even. We're trying to help.
But just like the first healer, we're frequently treating a symptom we assume, not a wound we've actually confirmed exists. And the person in front of us can usually tell the difference, even if they can't name it.
Statements Feel Like Progress. Questions Feel Like Delay.
There's a reason we default to statements so quickly.
Statements move fast. They sound decisive. They let us feel useful in the moment, because we've offered something concrete instead of sitting in the uncomfortable space of not yet knowing.
Questions, by comparison, feel slower. Less impressive. Like we're stalling instead of helping.
But advice given before you understand the full picture doesn't actually help. It's a guess dressed up as an answer. And guesses, however confident, tend to land the way the healer's remedy did: they treat what's visible while the real thing keeps festering underneath.
This doesn't mean statements are wrong. Once you actually understand what's going on, sharing your perspective is valuable, sometimes essential. The mistake isn't making statements. It's making them before you've asked enough to know what you're actually responding to.
The Problem With Solving Before You Understand
There's a related mistake, and it usually shows up right behind the first one: solving a problem before there's real clarity about what the problem is.
Most things people bring to us aren't actually the full story. "This isn't working." "I'm frustrated with how this is going." "Something needs to change." These are symptoms. They point at something, but they rarely explain it completely on their own.
When we jump straight to solving, we risk fixing the version of the problem we assumed instead of the one that's actually there. And even a genuinely good solution, aimed at the wrong problem, tends to fall flat. The other person doesn't feel helped. They feel unheard, and worse, unseen, the same way the farmer's fever kept climbing no matter how much of the remedy he drank.
Clarity has to come first. Not because questions are more polite than answers, but because they're the only way to find out what you're actually treating.
What This Looks Like at Work
A manager gets a message from someone on her team: "Hey, can we talk? I'm really frustrated with how the project's going."
The instinct is to start solving immediately. Maybe it's the timeline. Maybe it's the workload. She's managed enough projects to have three ideas before the meeting even starts.
Instead, she opens with a question. "Tell me more, what's felt most frustrating about it?"
It turns out the timeline is fine. What's actually wearing the team member down is that decisions keep getting made during side conversations she's not part of, and she finds out about changes after the fact. No amount of timeline or project scope adjustments would have touched that. But a single question found the real wound in under a minute.
What This Looks Like at Home
A father brings up something to his son over dinner. "Hey, I've noticed you've seemed kind of off lately. Everything okay?"
The son shrugs. "I don't know. Just tired, I guess."
The instant reflex is to fix it. "You should get to bed earlier." "Maybe cut back on your schedule." "Have you tried exercising in the morning?"
Each suggestion is reasonable. None of them land, because none of them were asked for yet.
If he pauses instead and asks, "Tired like you're not sleeping, or tired like something's weighing on you?" he might learn his son isn't sleepless at all. He's overwhelmed by a friendship that's gone sideways, and hasn't known how to bring it up. That's not a bedtime problem. It's a wound that was never going to show up until someone asked the right question.
A Question Before Every Statement
You don't need a script for this. You need one habit, repeated until it becomes automatic.
Before you offer a statement, an opinion, or a fix, pause and ask yourself two things:
Is there a question I could ask instead?
Do I actually have clarity here, or just urgency?
If the honest answer is that you're not sure yet, stay curious a little longer. Ask what's underneath the complaint. Ask what happened before this started. Ask what would actually feel different if it were resolved.
This is the same instinct behind Why Defending Yourself Backfires, Even When You’re Right: both come from the discipline of staying in the question a little longer than feels comfortable, so you're responding to what's real instead of what you assumed. And it works best paired with Dig Them Out Before You Explain the Mountain: once you know whether someone is speaking from emotion or logic, the questions you ask can actually meet them there instead of talking past them.
Try this Today:
The next time someone brings you a problem, whether it's a coworker, a partner, a friend, or your own kid at the dinner table, catch yourself before the first statement leaves your mouth.
Ask one question instead. Just one.
Then listen to the answer like it might change everything you were about to say, because it very well might.
The fix will still be there in a few minutes. The wound, if there is one, won't show itself until someone finally asks to see it.