Are you solving the right problem?

A problem statement sets the goals of your project. Before investing time and resources, make sure you're on the right track to solve the right problem.

icon of someone standing clueless where to go. multiple arrows are pointing in multiple directions, adding to the confusion.

A problem statement sets the goals of your project. We always ensure we have problem statements and key hypotheses before writing a single line of code for any products we work on. Here are some ideas on how to get started.

What is a problem statement?

A problem statement concisely describes an issue to be addressed or a condition to be improved upon. It identifies the gap between a process or product's current and desired state. It focuses on the facts.

Why frame a problem?

Can't seem to agree on the problem your project is tackling? Have the same discussions over and over again? Team members advocating wildly different solutions – so different that the answers don't even seem to map to the same problem? It’s probably time to frame your problem space again.

Take time to explore your problem space through your users' eyes so you can make decisions and understand their reasons.

How can a problem be framed?

The Four Ws

By asking four simple questions, everyone can put their thoughts together and synthesise the content to find focus and clarity. Ideally, this method gathers key stakeholders around a pile of Post-its and a large wall.

Who is affected? Who is experiencing the problem? Can this user be further specified (by demographic, persona, motivation, and reason for being in the situation)?

What is the problem? What are the struggles? What task needs to be accomplished? What pain point needs to be relieved?

Where or when does it happen? What is the context in which the user experiences the problem? Is it in a physical or digital space? Who else is involved?

Why does it matter? Why is this problem worth solving? What value does it bring to the user? What value does it bring to the business?

Exercise: Problem Framing

This is a great workshop for large-ish groups with diverse skills and experience levels. More perspectives = better problem definition.

Step 1 Set the stage - 3 mins.
We're here to define the problem you're working on – not to brainstorm solutions. Your goal is to walk out with a single problem statement.

Step 2 Draw up a W4 board - 2 mins.
Divide your whiteboard into four equal spaces and label them, Who, What, Why and Where. Work in pairs or small groups. Give each group a piece of paper to replicate the W4 board.

Step 3 Talk amongst yourselves - 10 mins
Discuss the questions on page 2 and use sticky notes to write your thoughts on each “W”.

Step 4 Come back together - 10 mins.
Ask people or each group to stick their best sticky notes on the whiteboard in the corresponding area. Dot vote the most relevant. Discuss which points in each area are the most revealing. Are there further questions to research?

Example

From the user’s point of view, you first need to list who they are, what they are trying to do, what is the barrier and why, which makes them feel..? For example:

“I am a new mum trying to take care of my baby in the best way possible, but I don’t know if I’m doing a good job because I’m always at home alone and don’t have anyone to talk to about it, which makes me feel isolated and alone.”

Then re-arrange that into insight by answering who they are (persona), what they want (user’s need) and the reason behind that (insight). Based on the previous example, you can say:

New mums need a way to connect with other mums because they are often at home alone during the day and feel isolated and alone.”

Using the 4 Ws to help you synthesise your findings and you have the following:

“Our new mum has the problem that she has no one to talk to about the best way to care for her baby when she is at home alone every day. Our solution should deliver a way for her to feel connected to other mums, so she feels less isolated and alone.”

Last but not least, a good problem statement:

  • Focuses on only one problem.

  • Should not suggest a solution.

  • Is specific enough to be understood by everyone.

  • Is broad enough to allow for creative solutions.


Thanks for reading Modern Work! Subscribe for free to receive new posts and support our work.

Previous
Previous

How to write the perfect Enterprise Product Design Brief👌 - Intro