• Save
Test Driven Design at Balanced Team Conference, Sept 2011
Upcoming SlideShare
Loading in...5
×
 

Test Driven Design at Balanced Team Conference, Sept 2011

on

  • 2,430 views

 

Statistics

Views

Total Views
2,430
Views on SlideShare
1,295
Embed Views
1,135

Actions

Likes
4
Downloads
0
Comments
0

10 Embeds 1,135

http://joshuaseiden.com 1034
http://sprmario.posterous.com 46
http://think-out-loud.posterous.com 25
http://sprmario.tumblr.com 11
http://lanyrd.com 6
http://posterous.com 5
http://flavors.me 5
http://twitter.com 1
http://translate.googleusercontent.com 1
http://paper.li 1
More...

Accessibility

Upload Details

Uploaded via as Apple Keynote

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \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
  • \n
  • \n

Test Driven Design at Balanced Team Conference, Sept 2011 Test Driven Design at Balanced Team Conference, Sept 2011 Presentation Transcript

  • TEST-DRIVEN DESIGN Balanced Team Conference September 25, 2011 Josh Seiden, @jseiden
  • Blog it! Josh Seiden @jseiden #leanUX www.luxr.co @luxrco #leanStartupwww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden 2 Share Alike 3.0 United States
  • 9 Lean UX Principles1. 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 pursue8. Recognize hypotheses & validate them9. Rapid cycles: think/make/check Research with users is the best source of informationwww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden 3 Share Alike 3.0 United States View slide
  • 9 Lean UX Principles1. 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 pursue8. Recognize hypotheses & validate them9. Rapid cycles: think/make/check Research with users is the best source of informationwww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden 3 Share Alike 3.0 United States View slide
  • 9 Lean UX Principles1. 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 pursue8. Recognize hypotheses & validate them9. Rapid cycles: think/make/check Research with users is the best source of informationwww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden 3 Share Alike 3.0 United States
  • Principle #8 Declare your assumptions...www.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden 4 Share Alike 3.0 United States
  • Principle #8 Declare your assumptions... A way to re-frame requirementswww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden 4 Share Alike 3.0 United States
  • 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
  • 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
  • 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
  • 7
  • Internet Mouse…www.luxr.cowww.slideshare.net/jseiden ? 8 License: Creative Commons Attribution- Share Alike 3.0 United States
  • Internet Mouse…www.luxr.cowww.slideshare.net/jseiden ? 8 License: Creative Commons Attribution- Share Alike 3.0 United States
  • Internet Mouse…www.luxr.cowww.slideshare.net/jseiden ?! 8 License: Creative Commons Attribution- Share Alike 3.0 United States
  • Method: Declare your assumptionswww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden Share Alike 3.0 United States
  • Method: Declare your assumptionsWhat assumptions do you have?www.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden Share Alike 3.0 United States
  • Method: Declare your assumptionsWhat assumptions do you have?…about your customers?www.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden Share Alike 3.0 United States
  • Method: Declare your assumptionsWhat 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
  • 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
  • Method: Write the test firstWe 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
  • Method: Minimum Viable Productwww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden Share Alike 3.0 United States
  • Method: Minimum Viable ProductWhat is the smallest thing we can make to testour hypothesis?www.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden Share Alike 3.0 United States
  • Method: Minimum Viable ProductWhat is the smallest thing we can make to testour 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
  • 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 purposeswww.luxr.co License: Creative Commons Attribution-www.slideshare.net/jseiden 13 Share Alike 3.0 United States
  • 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