Acknowledgments:

We would like to specifically recognize and thank:

The Nueva School, Kim Saxe, & the Stanford d.School
for being able to adapt from their materials.

Every problem is a gift, without them, we would not

grow.

What is Problem Finding?

Problem finding is our Deep Dive! This is

about discovering a need through exploring
quality information. Exploration could include
reading a novel, studying history, using the
Internet, or observing the world around you. It is
okay to have a broad problem statement we will
define the focus after seeking empathy.

Problem Finding:

As you observe the world, study history, math,
science, or read a novel

Ask yourself
o How might we?
o What if?
o Why? Why not?
o How? How come?
o Why is it the way it is? Does it have to
be that way?

The problem statement is thoughtful in

nature and is a non-Googleable problem.
Being unique is great! A strong problem
would be our Essential Question, or a

Driving Question for your project.
The problem statement is non-
Googleable and is written like an
Essential Question, or a Driving

Question.
There is limited description or scope of a
problem, or it is easily answered with
traditional means (it is Google-able).

Little or no effort made to find a problem.

Write a short narrative about the problem

that was researched and explain three
interesting or surprising things about it.

We need to learn to see things with a fresh set of eyes, and

empathizing is what gives us those new eyes.

What is Empathy?

This piece of the puzzle is all about understanding

different needs and viewpoints.

How to Empathize:

Observe: Watch others while they interact or

participate in events.
Engage: Interview others for their perspective.
What do they need? Try to find stories,
feelings, and emotions. What is
surprising?

Imagine: Put yourself in the shoes of a fictional
character, historical figure, or
someone / something else.

Developed a detailed description of user

needs, including a variety of insights,
gained by utilizing a variety of observation
strategies and interviews.
Developed a description of user needs,
including a few insights, from some
observation strategies or interviews.

Vague descriptions of user needs with

limited insights.
Little to no description of user needs.

What needs have you discovered?

Observation:

Be like a fly on the wall.
Watch what they do, not what they say.
Watch for habits, quirks, work arounds.
Be on the look out for patterns.
Observe similar users.
Consider observing non-users.
o Why dont they ever go there; or why
dont they use it; etc.

Interviewing:

Interviewing is questioning a user about their
needs:
o "Tell me more about..."
o "Could you tell me a story about..."
o "What would I find surprising about..."
o "Why do you say that..."
o "Tell me more..."
o "How did you feel when ___ happened..."
o "Why..." etc.

Never underestimate the power of Why?
o Thats interesting, tell me why
o Why do you think that is?
o Why did they decide to do that?
o Why do you think that is important?
o Why do you say that?

Defining the focus is where we create needs statements
for the
user.

What is Defining the Focus?

This piece of the puzzle is about bringing clarity

and a focus to your problem. The goal is to create
a needs statement that will drive your actions.

How to Define the Focus:

Think
o What is needed?
o Who needs it?
o What stood out from empathizing?
What connections did you make?
o Is this something that will spark a
creative & innovative solution?

Do
o Create a problem statement
(DT Madlibs see back of card).
o Try writing multiple needs statements:
you will focus on only one, but multiple needs
statements give you more choices.
o Perform the Goldilocks test: Not too
general, nor not too specific, but just right.

Attention was paid to the users needs

through empathizing, and a thoughtful
and actionable needs statement was
created, based on those needs.
The needs of the user were identified, and
an actionable needs statement was
created, based on those needs.

A user was identified, and a needs

statement was created.
Either no user, or no needs statement were
created.

________________________________
(user)
______________________ so as to/because
(users needs)
_______________________________.
(surprising insights / underlying problems).

Its not about coming up with the right idea; its about
generating the broadest range of possibilities

What is Ideating?

This piece of the puzzle is about generating a lot of

ideas.

How to Ideate:
-- Individual Brainstorming: this is a safe space;
there are no bad ideas. Document in some way.
-- Group Brainstorming: Each person shares his/her
favorite idea and the group builds on it. Practice
using Yes, and statements versus No, but.
-- Each person also shares his/her wildest idea and
the group builds on them. Document in some way.

While you ideate, try starting with the worst
idea you can think of, then consider these prompts:
o What is the most obvious solution?
o What if you had unlimited resources?
o What if you had no resources?
o What if you had superpowers what
would you do?
o How would a 6 year old child solve this?



Guidelines:
-- Capture everything: all ideas are good ideas and
get documented.
-- Use Yes, and statements versus No, but. By
being positive in our brainstorming, we increase
creativity. Negativity reduces our creativity.
-- Quantity Counts: Dont get stuck on good or
bad ideas. The more ideas the better!
o Encourage Wild Ideas: use the idea of
Draw the idea that would never work!
o Build on the ideas of others: Shift from
I to We statements.
-- Which ideas are actionable what can I do?

Techniques:
-- Sketching ideas, mind-mapping, post-it notes, digital
capturing.
-- Utilize Visual Thinking strategies.

Consider the Funnel:

A large number of ideas have been

generated. All members of the team have
contributed ideas, and used Yes, and
statements. In addition, the team has
utilized the concept of How Might We
was utilized.
A large number of ideas have been
generated. Most members of the team
have contributed ideas, and How Might
We was utilized.

A few ideas have been generated by one or

more members of the team.
Little or no ideas have been generated.

How might your ideas
meet user needs?

Fail early and fail often.

What is Prototype mode?

This is the doing piece of the puzzle; this is
where we create something. What we create can be an
actual product that we build with our hands, such as a
model. Or it can be a detailed plan, a letter, a process,
an art piece, a story, a role-playing activity, etc.

What we create can be anything that brings form to our ideas.

How to Prototype:

Just Start!: Pick up some kind of material

and just start building, doing, writing, sketching, or
making!
Build with the user in mind: Are you meeting the
true needs of the users, based on empathy, and how?
Try more than one prototype: Multiple options
allow for the most creativity.
Create a to do list: Help every team
member contribute and stay on task.
Never give up: Push through and do not
give up even if you feel that you are stuck
in the process. Go back to the ideate piece for more
ideas. Apply the concept of the mathematics of
innovation.
for more ideas
Think outside the box: Look for non-traditional
ways to do something.







One or more innovative solutions were
developed based on meeting the needs of
the user. Grit and determination were
demonstrated throughout the process
the team never gave up.
At least one innovative solution was
developed based on meeting the needs of
the user.

A solution was developed that relates to

the needs statement.
Little of no evidence of a solution was
prototyped in relation to the needs
statement.

Describe your process of prototyping.
1. Reflect on your prototyping process: what
worked, what didnt work, and what did you learn
from this?
2. How did you or your team demonstrate grit?
What specific strategies helped you persevere?

Could this
work?

What is Test mode?

This is where you see if your prototype satisfied the

users needs, and if it didnt what changes need
to be made? Testing is about making things better.
We must re-define failure as an opportunity for
growth!

How to Test:
-- Show dont tell: Put your prototype in the hands of
others as much as possible -- or have them experience
your prototype. This can include historical
simulations, character experiences, or products.
-- Watch and learn: Watch reactions so you can learn
and grow your prototype.
-- When something fails: Ideate and re-prototype
before you test again. Dont give up! Seize the
opportunity to learn, grow and improve!
-- Qualitative & Quantitative: Realize that there
are different measures to determine effectiveness.
Each prototype test may vary depending on the
context that we are prototyping for and what the
needs of the users.

1. Which piece of this project was most difficult for
you/your team and why? What strategies did your
team develop to help with this?
2. If you were giving advice to another team who was
going to do a similar project, what would it be?
3. Are there parts of the design process that remain
unclear to you or that you have questions about?
What are they?
4. What, if anything, would you like to share with the
users who you developed this solution for?

Biased towards action!

o Design Thinking is action-oriented, it is
about doing!
Rapid Prototyping!
o When we create something, it doesnt have
to be perfect the first time! We want to go
through as many iterations as needed we
build our knowledge and confidence the
more we do it!
Deep Dive!
o This is where we really sink our jaws into
something we learn all we can about the
needs of our users.
o This is our research phase.
Users!
o These are the people we are designing for!
Human Centered!
o Design Thinking is successful because of its
commitment to seeking the viewpoints of
others, through empathy.
Radical Collaboration!
o This is where we work in teams that we may
have never imagined working with. This
helps us to get as many ideas as possible!
o Cross Pollination -- we may need a
Ballerina and a Mechanical Engineer, and a
Poet all working together!

As an innovator never forget why we
design. It is for our users & VIDAs GILLs
should always ground our work.