Asking Better Questions

From "how do payments work?" to "which system should be authoritative for whether an order has been paid?" — questions that reduce uncertainty, and how to ask people.

"How do payments work?" cannot be answered in a way that changes what you build. "Which system should be authoritative for whether an order has been paid?" can. The move is rewriting the question until an answer would decide something.

Q · You are stuck on payments and the only question you can form is "how do payments work?" — how do you turn it into one whose answer changes what you build next?

The Question Quality Ladder

▶ lab

A question is vague, researchable or decisive, and the difference is checkable: does it name a component, name a boundary, ask for a mechanism, scope itself to my system, and ask for a decision? Five criteria, applied to your own questions before you send them anywhere.

Q · How can you tell, before you spend an hour on it, whether a question is one that can be answered — and whether its answer will decide anything?

Questions That Reduce Uncertainty

Among all the questions you could ask, the one worth asking next is the one whose answer removes the most uncertainty per hour spent — and a question is an experiment, with a cost, an expected answer, and a decision that depends on it.

Q · You have many open questions and limited time — which one do you ask next, and how do you know it was worth asking?

Asking People

A stakeholder, a senior, a provider's support desk: each can answer in minutes what would take you days — if the question arrives with what they need. Bring the expected, the actual, the evidence and your hypothesis, so the answer is usable and so the asking is not delegating your understanding.

Q · When the fastest route to an answer is another person, what do you bring so that their answer is usable — and so that asking does not replace your own understanding?