Problem Statements in UX Discovery - Deepstash
Problem Statements in UX Discovery

Problem Statements in UX Discovery

Curated from: nngroup.com

Ideas, facts & insights covering these topics:

4 ideas

·

91 reads

3

Explore the World's Best Ideas

Join today and uncover 100+ curated journeys from 50+ topics. Unlock access to our mobile app with extensive features.

What Is A Problem Statement

A problem statement is a concise description of a problem that needs to be solved

It’s a helpful scoping device, focusing the team on the problem it needs to explore and subsequently solve. A problem statement makes clear what needs to be done in discovery and what’s out of scope. Problem statements are also great communication tools; well-written ones can be used to gain buy-in from stakeholders on why it’s important to explore and solve the problem.

5

35 reads

Examples Of Good Problem Statements

  1. Users of our newspaper app often export content from our app, rather than sharing content through our app. This is a problem because target audiences are less likely to know that the content came from our app, leading to lower conversion rates. This is also a problem for app users, as exporting content is time-consuming and could lead to a decrease in app usage.
  2. Sales reps spend a long time planning which leads to visits each month. Because planning is done manually — using Excel spreadsheets and printed paper lists — sales reps find it difficult to meet their targets. 

5

19 reads

What Should A Problem Statement Include

  1. The background of a problem: Which organization or department has the problem and what is the problem?
  2. The people affected by the problem: There could be multiple user groups affected by a specific problem in different ways.
  3. The impact of the problem on the organization: If the problem is not fixed, what will be the effect on the organization? Reputational damage? Paying unavoidable costs?

6

16 reads

A Problem Statement should not

1. Be A laundry list of unrelated problems: A discovery effort should have one problem statement focused on one problem

2. Not Contain A solution: Leave the solution out of your problem statement at the beginning that is absolutely important

3. It should Be Brief: Problem statements are effective when they are concise, if you condense the problem you will lose important information

5

21 reads

IDEAS CURATED BY

aodigital

Subscribe to my Newsletter now and receive weekly updates packed with key takeaways.

CURATOR'S NOTE

This is the first stage of the Double Diamond Design Thinking Process and it is very important

Anjola Omole's ideas are part of this journey:

How To Start Over: Reboot Your Life

Learn more about product with this collection

How to set new goals

How to take action towards a new life

How to create a plan for change

Related collections

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Personalized microlearning

100+ Learning Journeys

Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates