A problem lands, and you’re already reaching for a fix - but the first answer usually arrives before the real problem is even clear. You end up solving the version you assumed, not the one in front of you.
This puts a short wall between the problem and the solution: ten questions about it before any answer. By question ten, the problem usually looks different.
Example: a manager hears “the release is slow” and starts planning a faster pipeline. Ten Questions First makes them ask ten questions first - slow for whom? Since when? Every release or this one? - and by question six it’s clear the real issue is one approval step, not the pipeline.
Before proposing a solution, write ten questions about the problem. No answers until all ten are written. The questions expose the assumptions you were about to solve.
Why ten, and not one or two? One question is easy to answer from the assumption you already hold - you ask it, satisfy yourself, and carry on to the fix you’d picked. Ten is enough to run out of easy answers, and that’s when the problem starts looking different.
Solo ✓ Team ✓ Under 2 minutes - the moment before you start solving.
The time required is indicative and will depend on how quickly the questions come.
Read the short one-page guide first - about 3 minutes. It is a downloadable PDF on this page.
Use it in the moment a problem lands - before you start solving.
Use it whenever:
Not the right tool if: you already know the problem is real and you need to dig into why it happens - that’s Root Cause Drill. To surface and test what you’re assuming, use Assumption Breaker; to rebuild your understanding from the ground up, use First Principles; to work backwards from where you want to end up, use Future Back. The difference is speed and intent: this is a fast reflex-breaker you run in the moment, and the others are deliberate investigations you choose to sit down and do.
You’ve done it well when: by question ten, you’re solving a different problem from the one you started with.
The urge to solve arrives before the problem is fully understood. Once a solution is in mind, it’s easy to read everything as support for it. Ten questions keep the problem open long enough for the assumptions to surface - one or two rarely do; ten usually does.
One Ten Questions card (or any paper) and a pen. Ten lines, numbered. The numbering matters - it’s what stops you at three and makes you find seven more.
Output / Takeaways
You leave with:
Important rules
Planning to facilitate this activity? Access the resources below to get started.