What Makes a Question Too Small?

The danger is not brevity. It is premature narrowing.

Framing the Question

What makes a question too small? A question is too small when it gives you an answer before it gives you a view. It aims at one visible symptom, one preferred fix, or one convenient metric while the real issue sits outside the frame. The problem is not that the question is brief. Some of the strongest questions are tiny. The problem is that the question is too narrow for the decision it is supposed to guide.

A Small Question Can Be Useful—or Dangerous

A question becomes too small when answering it well would not improve the thing that actually matters.

“How do we make this meeting shorter?” may be useful. But if the real problem is that no one knows who owns the decision, a shorter meeting just produces faster confusion. “How do we get more clicks?” may be useful. But if the product promise is wrong, better clicks can send more people into a bad experience.

The counterintuitive part is that too-small questions often feel practical. They are answerable. They sound efficient. They keep the room away from philosophy, politics, history, and tension. That is why they are dangerous. A small question can create the satisfying feeling of progress while quietly protecting the frame that created the problem.

A question is not too small because it is simple. It is too small when its boundary is false.

The Question Aperture Test

Think of a question like a camera lens. A tight frame can be powerful when you are looking for detail. It is useless when the important thing is happening just outside the shot.

Use the Question Aperture Test before answering a question that will drive money, time, trust, safety, or strategy:

1. Does the question name a symptom but ignore the system?
2. Does it assume the preferred solution is already correct?
3. Does it optimize a metric without asking what the metric represents?
4. Does it assign responsibility before the context is understood?
5. Could a smart answer improve the local task while leaving the larger problem untouched?

If two or more answers are yes, the question may be too small. Do not throw it away. Widen it first.

The Cost of Missing the Interface

The Mars Climate Orbiter is a useful reminder that the expensive mistake is not always inside the obvious component. In 1999, NASA’s Jet Propulsion Laboratory reported that preliminary findings pointed to one team using English units while another used metric units for a key spacecraft operation. NASA’s later mishap investigation tied the loss to ground software that produced thruster data in pound-force seconds where the interface expected newton-seconds.

The too-small question in a complex project is often, “Is each part working?” The bigger question is, “What assumptions must remain consistent when these parts touch?”

That difference matters. A subsystem can pass its own checks and still fail at the handoff. The right question has to include the seam between teams, tools, standards, and interpretations. In many failures, the truth is not hidden inside one box. It is lost between boxes.

A Workplace Version: Faster Support, Same Problem

Imagine a customer success team at a payroll software company getting 480 password-reset tickets a month. The support director asks, “How can we get agents through reset tickets faster?” The team writes better macros, adds a canned response, and cuts average handle time by 18 percent.

Then the next month brings 493 reset tickets.

The original question was too small because it treated the ticket queue as the problem. A wider question would be, “Where in the login experience are customers losing confidence or getting blocked?”

Now the team watches five users attempt a reset during shift change. They discover that reset links expire after ten minutes, but many restaurant managers check email between rush periods, not immediately. They also discover that SMS recovery defaults to the owner’s old phone number when stores change managers.

The better answer is not a faster support script. It is a longer reset window, clearer account handoff, and a recovery flow that recognizes how the customer’s work actually happens. The question did not need to become abstract. It needed to become big enough to include reality.

Small Is Right After the Frame Is Right

Small questions are not the enemy. Once you know the frame is sound, small questions are how progress happens.

“Which button label reduces checkout abandonment?” can be strong if you already know that unclear language is the bottleneck. “What should we say in the first sentence of the apology?” can be strong if you already understand the harm, responsibility, and repair required.

The order matters. Use larger questions to locate the real problem. Use smaller questions to act with precision.

A Sharper Question

Instead of asking:
“What makes a question too small?”

Ask:
“Would answering this question help us understand the real problem, or only help us act inside an untested frame?”

That sharper version makes the size of the question relative to the job. A question is not too small in general. It is too small for a particular decision, conversation, risk, or moment. The phrase “untested frame” is the hinge. It reminds you that the danger is not action. The danger is confident action inside a question that has already cropped out the truth.

What to Do With This

In a meeting, write the working question at the top of the notes. Under it, add five labels: symptom, cause, system, stakeholder, consequence. If one label is empty, the group may be answering too soon.

Before using AI, do not only ask for an answer. Ask: “What larger question might this prompt be avoiding?” Then ask the model for three wider versions and one narrower version. The contrast will often reveal whether you need scope or precision.

In a decision, add the sentence “too small for what?” If the answer is “too small for deciding the budget,” “too small for blaming a team,” or “too small for changing the policy,” you have learned something important. The question may still be useful, but not yet powerful enough to carry the decision.

Bringing It Together

A question is too small when it helps you move without helping you see. Better questioning is not about making every issue grand or complicated. It is about matching the question to the consequence. Start wide enough to see the real shape of the problem, then get small enough to do something about it. For daily practice in that judgment, follow QuestionClass’s Question-a-Day at questionclass.com—one question, a few minutes, better instincts.

Bookmarked for You

These books deepen the question by showing how framing, systems, and inquiry change what becomes visible.

Are Your Lights On? by Donald C. Gause and Gerald M. Weinberg - A sharp, playful book about figuring out what the real problem is before solving the wrong one.

Thinking in Systems by Donella H. Meadows - Helps readers see why narrow questions often miss feedback loops, incentives, delays, and unintended consequences.

Questions Are the Answer by Hal Gregersen - Shows how better questions can break stale assumptions in leadership, innovation, and decision-making.

QuestionStrings to Practice

A good QuestionString lets you widen the frame before you narrow the action. Use this when a question sounds practical but suspiciously easy to answer.

Aperture Widening String
For when a team, prompt, decision, or conversation may be operating inside too small a frame:

“What is this question trying to fix?” →
“What is it assuming is already settled?” →
“What system, stakeholder, or consequence is outside the frame?” →
“What would a good answer improve, and what might it leave untouched?” →
“What question would make the next action safer or wiser?”

Use it before approving a plan, diagnosing a conflict, writing an AI prompt, or redesigning a process. The goal is not to make every question bigger. The goal is to make sure the question is big enough before you trust the answer.