Download as pdf or txt
Download as pdf or txt
You are on page 1of 8

EXPERIMENT EXPEDITION

A flight plan for design exploration

d.
d.
hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

hasso
Institu
ThisDesigning
PDF document wasSystems
for Social edited with Icecream PDF Editor.
Upgrade to Both
Thomas PRO &toNadia
remove watermark.
Roumani
Stanford d.school // V2 d. dh
hasso plattner
Institute of Design at Stanford In
EXPERIMENT EXPEDITION PLAN
An experiment expedition allows you to test and refine solution(s)/intervention(s) and
question underlying assumptions. There are typically many stages of prototyping before
determining your ultimate intervention. Mark your current understanding of your stage of
testing for this expedition (What are you testing?)

Test the Test the Test for Test for


CONCEPT EXPERIENCE BEHAVIOR OUTCOMES
- desirability - - usability - - behavior change - - impact -

Below is a generic sequence of methods for the work. Outline each specific steps for your expedition.

WITH WHOM?
WHAT TECHNIQUE(S) / FORMAT?
(Written, sketched, video, mock-ups, ...)

WITH WHOM?

Idea
Dashboard, Identify
Storyboard, Elements and
or Assumptions
Prototype to Test
/ Mock-up
WHAT FORM / FORMAT?

Create ways to _________________________________


human action
.

For __________________________________________
user group
. Build
Testable
Prototype
(While considering ____________________________
other stakeholders
.) (and testing
plan)
We really need to figure out

WITH WHOM? / WHERE? /


______________________________________________
questions / assumptions
HOW TO REACH THEM?

______________________________________________

Test and
Make Sense Track
and Make
Choices

HOW WILL YOU CAPTURE DATA?


(Observational, verbal, quantitative, etc.)
WITH WHOM?
d.
d.
hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

hasso
Institu
This PDF document was edited with Icecream PDF Editor.
Upgrade to PRO to remove watermark.
d. dh
hasso plattner
Institute of Design at Stanford In
IDEA DASHBOARD
FLESH OUT YOUR CONCEPT

WHAT...
What’s the intervention/solution?

WHO/HOW...
Who will implement it?
How can it be created in the system?

WHY...
What change does it creates for people?

DRAW IT

d.
d.
hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

hasso
Institu
This PDF document was edited with Icecream PDF Editor.
Upgrade to PRO to remove watermark.
d. dh
hasso plattner
Institute of Design at Stanford In
QUESTIONS AND ASSUMPTIONS TO TEST
LIST AND PRIORITIZE WHAT TO LEARN ABOUT FROM PROTOTYPING

ASSUMPTIONS
& QUESTIONS Assumption 2:
(What must be true for our concept to work?)
Easily installable i.e can be easily
integrated into current system such
that it is universal.

Assumption 1:
There is a widespread and urgent
need for this project/invention.

Question 1:
What is its cost?

Question 2:
Is it feasable?

Question 3:
Is it accurate and reliable such that
it works on time and accurately.?

PRIORITIZE AND SELECT


First, order the questions to test, as shown below.

Test/work out first Test/work out later

d.
More critical
More fundamental
d. More
More detailed
logistical
hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

Then select 1-3 to test now (balance criticalness with ease/ability to test). hasso
Make sure your testing answers “Would it matter if we created it?” before investing too much effort in “Can it be created?” Institu
This PDF document was edited with Icecream PDF Editor.
Upgrade to PRO to remove watermark.
d. dh
hasso plattner
Institute of Design at Stanford In
PROTOTYPING DASHBOARD
PLAN YOUR PROTOTYPE TESTING

PROTOTYPE CONCEPT
What will people (testers, stakeholders) do/experience?
And how will “observing” this help you learn?
(The prototype can be very different than your solution.)

SCENE
Where (or in what situation) will you test?
This can be found or created.

PROPS
What are the physical/digital things?
(To make or fake.)

ROLES d.
Who is “creating” the prototype/experience?
Who is “receiving the prototype/experience? d.
hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

hasso
Institu
This PDF document was edited with Icecream PDF Editor.
Upgrade to PRO to remove watermark.
d. dh
hasso plattner
Institute of Design at Stanford In
TEST TRACKING DASHBOARD
* This tool may be more appropriate
for later stage prototypes
(testing for usability, behavior
change, and outcomes)

STATE WHAT TO WATCH FOR IN ADVANCE OF TESTING

METRICS
For each specific assumption you have, state what testing data/response might confirm or
disconfirm that assumption. (At the same time, stay open to unexpected learnings.)

Question /
assumption:

The cost should be such that it is affordable for most of the


upper middle class upwards.

COST
METRIC(S) TO TRACK HOW WILL YOU MEASURE IT?
IS THERE A BASELINE?

Question /
assumption:

How much time taken to turn on motor after water is


detected in KWSB line and likewise how much time taken
or if accurately shuts off motor once water tank is full.
We can measure it by noting the time it takes for our system
to activate and deactivate pump and at what scenarios.
ACCURACY/RELIABILITY
METRIC(S) TO TRACK HOW WILL YOU MEASURE IT?
IS THERE A BASELINE?

Question /
assumption:

How easily our project can be integrated into different types


of systems such that it is universal.
This will be measured by testing it onto as many different
systems as possible and take notice of why and what systems
FEASIBILITY our project does not easily integrate into.
METRIC(S) TO TRACK HOW WILL YOU MEASURE IT? d.
IS THERE A BASELINE?
d.
hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

hasso
Institu
This PDF document was edited with Icecream PDF Editor.
Upgrade to PRO to remove watermark.
d. dh
hasso plattner
Institute of Design at Stanford In
MAKE SENSE AND MAKE CHOICES
WHAT ARE YOUR TAKEAWAYS FROM TESTING FEEDBACK

FEEDBACK GRID
Capture feedback you gathered using this simple structure.
After populating, group in each quadrant, cull 4-8 major takeaways, and determine next steps.

The system should be such that it can sync to multiple


devices at once if for example working on water system of
an entire building.

AMPLIFY ADDRESS
Elements/impact to make Elements not working.
more pronounced. Unmet needs you now see.

EXPLORE CONSIDER
Unexpected or unclear New ideas that came up
response to investigate. or strike you now.

d.
d.
hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

hasso
Institu
This PDF document was edited with Icecream PDF Editor.
Upgrade to PRO to remove watermark.
d. dh
hasso plattner
Institute of Design at Stanford In
EXPERIMENT EXPEDITION RESULTS
WHAT DID YOU LEARN? HOW DOES THAT INFLUENCE THE PROJECT?

Use the below to summarize takeaways from this expedition.

WHAT YOU DID


What prototype(s)? How tested? With whom?

The prototype was tested with family members and neighbours.

TOP FINDINGS
Important observations and new insights.

NEXT STEPS
Implement, test further, generate more ideas, new ethnography?

d.
d.
. hasso plattner
Institute of Design at Stanford

d.
d.
hasso plattner
Institute of Design at Stanford

hasso
Institu
This PDF document was edited with Icecream PDF Editor.
Upgrade to PRO to remove watermark.
d. dh
hasso plattner
Institute of Design at Stanford In

You might also like