Part I: Coming up with an idea
5. What are you assuming?
Write down what needs to be true, then choose what to check first.
Some parts of your problem sentence will come from things you've seen or heard. Other parts will be guesses. Write down which is which before you go looking for evidence.
An assumption is something you're treating as true without yet knowing enough to rely on it. You need assumptions to get started. Making them visible gives you a way to check them, and a way to notice when an idea depends on something that turns out to be wrong.
Take the sentence you've been working on:
Person X can't do Y because Z.
You might know X personally and have seen them struggle with Y. But is Z really the cause? Does the difficulty matter enough for them to do something about it? Are there other people in a similar situation? Each of those questions could change what you build, or whether you build anything.
Write statements you can check
“People want an easier way” doesn't tell you much. It's hard to imagine someone arguing with it, and it gives you little direction for a conversation.
Make the assumption specific enough that you could discover it's wrong. In our hypothetical designer example, you might write:
Waiting for client decisions regularly prevents this designer from finishing work when they planned to.
That gives you something to investigate. You can ask about recent projects, what held them up, and what happened because of the delay. If the designer usually finishes on time, or the delays come from their own workload, you have a reason to revisit the assumption.
Keep separate guesses on separate lines. “Designers have this problem and will pay for an app” contains two things to check. Evidence of the problem doesn't establish willingness to pay for your proposed solution.
Check the assumptions that matter most
You don't need to investigate everything at once. Look for an assumption that would change your whole plan if it were false, especially one you currently know little about.
For the designer, finding out whether waiting causes a real difficulty comes before deciding what features a feedback tool should have. If the designer is content with the current process, first find out whether there's anything they want to change about it.
A simple table can help. These are possible assumptions to check for our imaginary designer.
| Assumption | What would make you reconsider? |
|---|---|
| Waiting for decisions disrupts the designer's work. | Recent projects show the wait has little effect. |
| Clients are unsure what decision they're being asked to make. | They understand the request, but are waiting on someone else's approval. |
| The designer wants to change the current process. | They've considered alternatives and prefer what they do today. |
| Other designers face a similar difficulty. | People doing similar work describe a different problem. |
| The designer would pay for a solution or change how they work to use it. | The benefit doesn't justify the money or effort it would cost them. |
Add your assumptions to the notes you've been keeping. Beside each, record what you've seen or been told. Leave the rest as “unknown.”
Decide what would change your mind
It's easier to explain away an unwelcome answer when you haven't decided what you're looking for. Before a conversation, write down what would make you less confident in the assumption you're checking.
You could learn that the problem is rare, that your explanation is wrong, or that the current solution is good enough. Be willing to record that. You can still decide to investigate further, but give the answer a place in your notes.
Choose the most important uncertainty to take into your next conversation. Write a question that could help you learn about it. We'll work on asking those questions in Talking to people.