How to Think Through Hard Questions

Pretty standard 8th grade biology question you would love to see in an exam right? It's a straightforward, well-defined question with one answer, and you get a set of choices to choose from. Because the question is well defined, the answer is simple and unambiguous.

But why does it feel so satisfying? I think it has to do with how we were trained to answer questions like this, and more importantly, how we carry that same expectation into the real world.

We grow up looking for that same simple, clean, unambiguous answer for every question that comes our way, both professionally and personally. Before we can understand why that's a problem, we need to take a closer look at what actually makes a question like the one above so easy to answer in the first place.

The secret lies in how well-defined it is. A well-defined question is one that is bound by specific constraints and provides enough context for an unambiguous answer. And when you look at the original question through that lens, you start to notice just how many guardrails it quietly sets up.

Every element of the question's structure is doing work to narrow the solution space. The single blank immediately eliminates open-ended guessing. The multiple-choice format constrains the possibilities even further. And the phrase "powerhouse of the cell," always attached to the same answer, removes all remaining ambiguity, leaving room for only one undeniable response.

As a question becomes less constrained, the solution space grows. Say you're a carpenter and your client asks you to build a square wood panel with an area of 25 square meters. You set up the equation x² = 25, and there are two valid solutions: x = 5 and x = -5. To pick one, you need an additional constraint. In this case, a negative side length doesn't exist in the physical world, so the constraint resolves itself and you go with x = 5. But not every question is that clean.

Sometimes the constraint is flexible enough to be a matter of judgment. And sometimes there is no constraint at all and both answers are equally valid. Take a drone that you know has moved 25 square meters from its launch point. It could have traveled 5 units forward or 5 units backward, and without knowing the direction, both answers are correct.

Then there are questions that come with a range of answers. When a paleontologist dates a fossil, the answer looks something like "between 65 and 70 million years ago." The goal becomes applying as many constraints as possible, the type of rock, the decay rate of isotopes, the surrounding fossil record, to narrow that range down to something workable. The more constraints you find, the smaller and more useful your range becomes, and that is your answer.

And I would argue this extends far beyond scientific questions. Technical questions behave the same way. How much traffic can this system handle? How long will this battery last in the field? How many users will churn next month? The constraints narrow the estimate, but measurement error, environment, user behavior, and hidden dependencies always leave a band. The honest answer becomes somewhere between 120 and 160 milliseconds, 18 and 24 months, or 3 and 5 weeks.

But it goes even further than that. Some of the most consequential questions we face, personally and professionally, carry the same structure. What feature should we build next? Which market should we enter? What should my career be? These questions have no precise answer waiting to be uncovered. They have a range of reasonable answers, shaped by your constraints, your values, your resources, and your context. The more honestly you define those constraints, the more you can narrow the range.

But the real leverage comes when others can read what you wrote. In most professional settings, you are rarely the only person with relevant constraints. Your colleagues, your clients, your collaborators all carry constraints you have never thought of. When you write clearly, you give them something to react to. They can add their own constraints, challenge the ones you listed, or point out that something you treated as a wall is actually a door. The answer does not arrive all at once. It gets uncovered gradually, as the wrong possibilities get filtered out one by one. Writing is what makes that process possible. It turns a question you have been carrying alone for weeks into something the room can solve together. And if you do it well enough, if you stack the constraints clearly and completely, you might just get lucky and end up with a question so well defined that only one answer fits. Just like filling in the blank.

For me, this youtube video is the best description of that idea I have found. The Beyond The Build podcast has an episode on writing and communication where they describe it as taking the people around you on a journey through the solution space. Watch it. It is worth your time