Skip to content

Part I: Coming up with an idea

2. Finding problems

Where to look for problems, and how to choose which ones to investigate.

Start with the things you can see people struggling with. Your own work is a good place to look. So are the people you know and the communities you're already part of. You have somewhere to start asking questions, and a chance of understanding the answers.

A problem might be so familiar that you barely notice it. You copy the same information into different places. Someone has to chase a reply before they can finish their work. A task is awkward enough that you keep putting it off. Look for the things people have accepted as part of getting through the day.

You don't need to know how to code to notice any of this. Knowing how a job actually gets done gives you something useful to build from.

Look at what people already do

Complaints can point you towards a problem. What happens after the complaint is useful too.

Someone might keep a spreadsheet because their existing tools don't quite do the job. They might pay for software they find frustrating, or ask a colleague to handle something by hand. Those workarounds give you a place to look more closely. What are they trying to achieve? Which part keeps going wrong?

In our hypothetical designer example, imagine that the designer keeps a spreadsheet of projects waiting for client feedback. They check it and send follow-up messages before starting the day's work. You can now investigate a specific activity: keeping projects moving when a client hasn't replied.

Checking projects waiting for feedback, then sending follow-ups.

The spreadsheet itself might work perfectly well. Seeing it doesn't automatically mean you should replace it with an app. Find out which part of the work, if any, the designer wants to change.

And if someone has no workaround, ask why. They might have given up, lack the means to do anything about it, or simply have more pressing things to deal with. You need that context before deciding how much the problem matters.

Is it worth looking into?

At this stage, you're choosing what to investigate. You can make that choice without knowing whether anyone will buy a product yet.

For each problem you notice, ask:

  • When does it happen, and how often?
  • What does it stop the person from doing?
  • What happens if they leave it unsolved?
  • What do they already spend, in time or money, trying to deal with it?

You won't know all the answers yet. Write down what you've seen, and keep the unanswered questions for when you talk to the person. “I don't know yet” is useful here.

A frequent annoyance might be worth solving because it takes up part of every day. Something that happens rarely could still matter a lot if the consequences are serious. Frequency helps you understand the problem; it doesn't decide its value on its own.

If someone already pays for help with a problem, that's a reason to look closer. So is spending their evenings doing the work by hand. Both suggest the problem matters to them. You'll still need to find out whether they'd try your solution and, if you plan to charge, whether they'd pay for it.

Write down the problem you noticed

Keep a short list. If you already have an idea, start with the problem you think it solves. You don't need to find a different one to do this exercise.

For each entry, write what someone was trying to do, what got in the way, and anything you actually saw them do about it. Leave questions beside the bits you're guessing.

Using our imaginary designer, an entry could look like this:

The designer needs a client's decision before finishing a project. They're still waiting for a reply, so they keep the project on a spreadsheet and send follow-up messages.

I still need to find out: what stops the client from replying? How much does the delay affect the designer's work?

For your own entry, only describe something as having happened if you've seen it or someone has told you about it. If you're imagining what might happen, write that down as a question to check.

Be careful with entries like “there's no app for this.” That tells you what you might build. It leaves the person's difficulty unexplained. Try describing what they struggle to do today, without mentioning your proposed app.

One problem is enough to take into the next chapter. If you have several, we'll work through them by finding a real person behind each one.

Before you move on0 / 3