Problem Statements

Balogun Tobi
2 min readDec 8, 2020

--

Image is taken from: https://www.ehstoday.com/

One of the most important aspects of problem-solving is synthesizing data from research. This process sets the precedence for providing a solution. But more importantly, it prevents a situation in which the right solution for the wrong problem is provided. This stage of the process in Design Thinking is known as Define. What it is in essence is making sense of the information we have thus far. Therefore it's very important and imperative it is done rightly. One design technique that hugely contributes to the success of this process is called Problem Statements.

What are problem statements? A problem statement is an explicitly defined statement that describes the issues we are facing. Besides describing issues they also state one's perspective and communicates one's design vision. A problem statement should be direct and easy to assimilate even by an outsider.

A problem statement has 3 main components (parts). A specific user, what they need the product for, and the underlying reason for the need (known as the insight). A simple problem statement model goals as:

(User) needs to (users’ need) because (insight).

Examples

A fitness coach needs a portable speaker for his group sessions because clients are better motivated by music. The fitness coach is the user in this case. The coach needs a speaker to better motivate his clients. In addition, music also helps his clients camaraderie with each other.

An avid soccer fan needs a live report of games on his wearable to stay up to date with his favorite games while at work.

A newbie well-being enthusiast needs a bottle that notifies her how much water she drinks to help her achieve her daily water goal.

Advantages

The major advantages of the Problem Statement are as follows:

  1. Defines the current scope of work
  2. Provides a main perspective of the problem or challenge
  3. Sets a yardstick to measure success by

Keep it simple and relatable, use personas, embrace users’ emotions and you would have a solid problem statement.

--

--