Question the Question: The Meta-Skill That Changes Everything
I asked 18 experts to solve a naming problem. They gave me 18 different answers. Then I questioned my question—and found the real problem wasn't naming at all.

I asked 18 experts to solve a naming problem.
They gave me 18 different answers.
Every answer was technically correct. Every expert was working at the top of their game. And if I'd picked any one of them, it would have worked—sort of.
Then I questioned my question.
The problem wasn't naming. It never was. The real problem was coordination—the system's components weren't communicating properly. Once I saw that, the solution was obvious. Not 18 restructures. Just a few triggers connecting what already existed.
This is the meta-skill nobody teaches.
The Trap of Brilliant Answers
In Ask a Better Question, I talked about layering context instead of chasing answers. About how one "why" question handles 90% of what ten "what-ifs" try to solve.
But there's a step that comes before even that.
Before you layer context, before you consult experts, before you do anything—you need to question the question itself.
Because here's what I've learned: Experts are brilliant at answering whatever question you give them. That's the problem. Hand an expert a bad question, and they'll give you a perfect answer to it. A well-crafted, thoroughly researched, completely useless answer.
The question shapes the answers you can possibly receive. And most people never question the question.
Question the Question
Most of us accept the question as given. Someone asks "Should we do X or Y?" and we immediately start analyzing X versus Y.
But what if neither X nor Y is the point?
Here's the meta-skill: Before you answer, before you even add context, ask yourself:
"Why would this be the right question?"
Not "what's the answer?" Not even "what's a better question?" Just: Why would this particular framing be correct?
Watch what happens when you apply this:
Original question: "Should this tool be configured as Type A or Type B?"
Question the question: "Why would the type configuration be the problem at all?"
What emerged: The type was never wrong. The triggering mechanism was broken. 18 experts would have debated A versus B forever. Questioning the question revealed the real issue in minutes.
The Three-Level Framework
Here's how it works in practice. Same core question, but you're challenging the question itself at each level.
Level 1: State the question
Write down what you think you're trying to solve.
"Should I hire a specialist or a generalist?"
Level 2: Question it
Ask: "Why would this be the right question?"
"Why would the specialist-vs-generalist framing be correct? What if the problem isn't hiring at all?"
Level 3: Find the real problem
Keep questioning until you hit something that feels different—something the original question didn't capture.
"The real problem is I don't know what this role should accomplish. Hiring either type would fail because I haven't defined success."
The question shifted from "who to hire" to "what does success look like." Completely different problem. Completely different solution.
When Frameworks Work on Themselves
Here's where it gets interesting.
In Jiu-Jitsu Is Easy, I talked about the Three Things framework—from any position, only three things can happen. Top: maintain, advance, or submit. Bottom: escape, sweep, or submit. The simplification creates clarity.
The meta-insight: The same frameworks that simplify solutions also simplify questions.
Collapse to one root cause. Subtract what doesn't matter. Layer context until clarity emerges.
But now apply that to the question itself:
- Root cause: Can I collapse my multiple questions into one?
- Subtraction: What's in this question that doesn't actually matter?
- Layering: What context, if added, would make this question obviously wrong?
When I was stuck with those 18 expert opinions, I applied the frameworks to my question:
18 answers → collapsed to 7 themes → collapsed to 3 patterns → collapsed to 1 root cause.
The 1 root cause had nothing to do with my original question. It was a coordination problem masquerading as a naming problem.
The frameworks work on themselves. That's when you know they're actually frameworks and not just tricks.
The Army of Georges Problem
In Army of Georges, I talked about building systems that amplify your presence—specialists that extend what you can do without requiring you to do more.
But specialists only work when they're coordinated.
What I discovered in that naming problem: I had specialists. Excellent ones. Each knew their domain deeply. But when I asked for collective input, they operated in parallel—each giving their best answer—instead of synthesizing.
The technology wasn't the hard part. Knowing what I actually wanted was.
I thought I wanted an answer to a naming question. What I actually wanted was unified output when multiple perspectives were needed. The naming question was a symptom. The coordination gap was the disease.
Questioning the question revealed that. No amount of expert consultation would have.
There's a related trap: verification bias. You can ask the right question, get the right answer, and still fail—because you verified the answer instead of the result. I wrote about this in The Phantom Complete: when documented completion masks actual execution failure.
The Pattern Across Domains
This applies everywhere.
In BJJ:
"How do I improve my guard?"
Question it: "Why would 'improving my guard' be the right frame? What if my guard isn't actually my problem?"
Layer context: "Given that I keep getting passed, but only from certain angles..."
Real problem revealed: It's not guard improvement—it's angle awareness. Completely different training focus.
In Business:
"Should I raise prices or add more value?"
Question it: "Why would this be a pricing problem at all?"
Layer context: "Given that my current clients stay forever but new clients are hard to find..."
Real problem revealed: It's not pricing—it's positioning. The service is underpriced because the wrong people are finding it.
In Fitness:
"What's the best exercise for my lower back?"
Question it: "Why would an exercise be the solution?"
Layer context: "Given that the pain started after I began sitting more, and it disappears on vacation..."
Real problem revealed: It's not an exercise problem—it's a movement frequency problem. No exercise fixes eight hours of sitting.
How to Practice This
1. Catch Yourself Before You Start
Before you consult anyone, before you research, before you spend any energy—write down your question and ask: "Why would this be the right question?"
If you can't answer clearly, you're probably already off-track.
2. Notice When Expert Advice Conflicts
If smart people are giving you contradictory answers, that's a signal. They might all be right—and you might be asking the wrong question. The contradiction often lives in the question, not the answers.
3. Apply Your Frameworks Recursively
Whatever tools you use to solve problems—apply them to your problem definition first. Collapse, subtract, layer. But do it to the question, not just the answer.
4. Find the Real Problem Before Inviting the Experts
Here's the uncomfortable truth: experts cost attention. Theirs and yours. If you bring them in too early, before you've questioned your question, you'll burn through resources answering something that isn't the real problem.
Question first. Then consult.
The Meta-Skill
I don't teach techniques. I teach frameworks. And the most powerful frameworks are the ones that work on themselves.
"Ask a better question, get a better question." But what if the question itself is wrong?
Then you need to question the question.
This is the meta-skill. The skill that makes all other skills more effective. Because it doesn't matter how good you are at finding answers if you're searching in the wrong place.
Question your question. Not once, but as a practice.
Why would this be the right question? What context, if added, would make this question obviously wrong? What problem am I actually solving?
Keep going until you feel it shift. Until the original question seems almost naive compared to what you now understand.
That's where the real work begins.
Ready to question your questions? Book a session.
George Samuelson is a second-degree black belt, award-winning digital marketer, and business consultant. He helps athletes, entrepreneurs, and professionals develop the frameworks that make everything else work. He's based in New Jersey and works with clients online and in-person.