Now we're going to take those insight statements and

reframe them into problem statements.

Identifying and defining the design problem is an important step

that will set the direction and focus for you and the rest of your team.

Defining problem statements is done by combining your knowledge about the user

you're designing for.

Their needs and the insights which you've come to know in your research.

Look at your insight statements, particularly the ones that are problems

users have, and start writing problem statements.

Once you've written them down, decide which problem or problems you and

your team are going to focus on.

In a real life situation, you will also need to consider the goals of your company

and see how that impacts the problems your team should be solving.

For our project, let's focus on the problem

users need a mobile solution that is familiar, visually appealing, and

trustworthy for buying, selling, or browsing items on Craigslist.

The last exercise before we get into the ideation phase is

to create how might we statements.

These statements are created by rephrasing and framing your problem statement

as several questions by adding how might we at the beginning.

You can also break the larger problem statement into smaller actionable and

meaningful questions.

Your how might we questions should generate a number of possible answers and

will become a launchpad for your ideation sessions.

From our problem statement, start listing some how might we questions, and

keep in mind that these statements should be broad enough to allow for

a variety of solutions.

If you find it helpful, in a new frame,

create a problem statement worksheet where you can put your problem statement,

key insights, how might we statements, and design principles in one place.

This can help you quickly refer back to your research

as you begin the ideation phase.