The document discusses the principles of test-driven design and lean UX. It outlines 9 lean UX principles including having a unified product team, externalizing work, being goal-driven, and conducting rapid cycles of building, testing, and learning from user research. The document advocates for declaring assumptions as hypotheses to test, writing tests before building products, creating minimum viable products to test assumptions quickly and cheaply, and getting out of the building to directly validate assumptions with users.
Test Driven Design at Balanced Team Conference, Sept 2011
1. TEST-DRIVEN DESIGN
Balanced Team Conference
September 25, 2011
Josh Seiden, @jseiden
2. Blog it!
Josh Seiden @jseiden #leanUX
www.luxr.co @luxrco #leanStartup
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 2 Share Alike 3.0 United States
3. 9 Lean UX Principles
1. Design + biz + development + ... = 1 product team.
2. Externalize!
3. Goal-driven and outcome-focused.
4. Repeatable and routinized.
5. Flow: think, make, check.
6. Focus on solving the right problem.
7. Generate many options & decide quickly what to pursue
8. Recognize hypotheses & validate them
9. Rapid cycles: think/make/check Research with users is
the best source of information
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 3 Share Alike 3.0 United States
4. 9 Lean UX Principles
1. Design + biz + development + ... = 1 product team.
2. Externalize!
3. Goal-driven and outcome-focused.
4. Repeatable and routinized.
5. Flow: think, make, check.
6. Focus on solving the right problem.
7. Generate many options & decide quickly what to pursue
8. Recognize hypotheses & validate them
9. Rapid cycles: think/make/check Research with users is
the best source of information
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 3 Share Alike 3.0 United States
5. 9 Lean UX Principles
1. Design + biz + development + ... = 1 product team.
2. Externalize!
3. Goal-driven and outcome-focused.
4. Repeatable and routinized.
5. Flow: think, make, check.
6. Focus on solving the right problem.
7. Generate many options & decide quickly what to pursue
8. Recognize hypotheses & validate them
9. Rapid cycles: think/make/check Research with users is
the best source of information
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 3 Share Alike 3.0 United States
6. Principle #8 Declare your assumptions...
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 4 Share Alike 3.0 United States
7. Principle #8 Declare your assumptions...
A way to re-frame requirements
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 4 Share Alike 3.0 United States
8. Principle #8 Declare your assumptions...
A way to re-frame requirements
Every decision you make about your offering is a
design decision.
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 4 Share Alike 3.0 United States
9. Principle #8 Declare your assumptions...
A way to re-frame requirements
Every decision you make about your offering is a
design decision.
Every design decision is an hypothesis.
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 4 Share Alike 3.0 United States
10. Principle #8 Declare your assumptions...
A way to re-frame requirements
Every decision you make about your offering is a
design decision.
Every design decision is an hypothesis.
Declare your assumptions and test them.
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 4 Share Alike 3.0 United States
19. Method: Declare your assumptions
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
20. Method: Declare your assumptions
What assumptions do you have?
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
21. Method: Declare your assumptions
What assumptions do you have?
…about your customers?
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
22. Method: Declare your assumptions
What assumptions do you have?
…about your customers?
…that if proven false, will cause you to fail?
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
23. What assumptions are we making?
Who is the user? Who is the customer?
Where does our product fit in their work or life?
What problems does our product solve?
When and how is our product used?
What features are important?
How should our product look and behave?
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 10 Share Alike 3.0 United States
24. Method: Write the test first
We believe that person type has trouble/need/desire doing
problem/oppty. [that can be addressed by our offering.]
We will know we have succeeded when qualitative and
quantitative outcome. This will improve KPI.
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
25. Method: Minimum Viable Product
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
26. Method: Minimum Viable Product
What is the smallest thing we can make to test
our hypothesis?
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
27. Method: Minimum Viable Product
What is the smallest thing we can make to test
our hypothesis?
The answer to this question is your MVP.
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
28. Method: Get out of the building
Identify who do you want to talk to and what you
want to learn
In other words, what assumptions will you test?
Stay tuned for Lane’s talk...
Plan your interview themes as a team
Collect artifacts, debrief and share
Use your visits for multiple purposes
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden 13 Share Alike 3.0 United States
29. Want to attend a workshop? Tweet #LUXiNYC to @LUXrCo
THANK YOU!
www.luxr.co License: Creative Commons Attribution-
www.slideshare.net/jseiden Share Alike 3.0 United States
Editor's Notes
\n
\n
\n
\n
\n
\n
\n
\n
Why is it important to declare and test your assumptions?\n
Why is it important to declare and test your assumptions?\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Figure out where in the stack your candidate has worked\n
Figure out where in the stack your candidate has worked\n
Figure out where in the stack your candidate has worked\n