A Problem Statement should not - Deepstash

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

CURATED FROM

IDEAS CURATED BY

aodigital

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

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

The idea is part of this collection:

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

Similar ideas to A Problem Statement should not

How should your problem look like for a startup?

How should your problem look like for a startup?

In a world where there tons of problems found daily, tons of ideas culminating in minds, only few of them sustain, and remaining, fail! So what exactly are some of the things that you should keep in mind about your problem, before you think of starting up!

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