Lean UX Recipe Cards (set 01)

  • 1,445 views
Uploaded on

Conversation, Cadence & Culture: recipes to inspire collaborative teams. Print-your-own recipe cards from workshop at http://leanuxnyc.co/nyc/ April 12, 2013. Print two sided on 8x5"x11" card stock. …

Conversation, Cadence & Culture: recipes to inspire collaborative teams. Print-your-own recipe cards from workshop at http://leanuxnyc.co/nyc/ April 12, 2013. Print two sided on 8x5"x11" card stock. Cut in four pieces. Produces two sets of six cards. Keep one, share one with a friend!

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,445
On Slideshare
0
From Embeds
0
Number of Embeds
4

Actions

Shares
Downloads
38
Comments
0
Likes
4

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. #c5recipeApr.30.13Lean UX NYC 2013#leanux- Activity -Six-upsNote: This activity works better if the team has a shared understandingof the project goals and user(s) and if everyone participates in both thedrawing and the subsequent conversation.Step 1: Agree on a topic question,for example “How might we createexperiences that help serious bike commuters evaluate and purchasebikes at Wheel Nice Guys?”Step 2: Fold an 8.5”x11”piece of paper in half longways and then fold itin thirds.Unfold and you’ll have six sections.Set a timer for 15 minutes.Step 3: Draw a picture in each section.If you’re stuck,think abouta setting or situation where the user solves a problem with yourproduct/service.What are the the key elements of that solution ?Step 4: Tape your six-ups on a wall.One person at a time,describe yourconcepts.Other people just listen & take notes (on stickies).Step 5: When all the concepts are introduced,talk about all the ideas,adding more notes (stickies) as necessary to capture the conversation.The project brief helps the team understand the objectives of thecurrent project phase,experiment,milestone or MVP.• Start with a blank document that contains the sections below.Writethe project brief as a team.• Use a shared Google doc or pass the keyboard and make differentpeople type different sections to increase ownership in the outcome.• Review often (i.e.when you write,prioritize or size user stories) andrevise as necessary to reflect the accurate project goals.project brief SECTIONS• Project name• Date last updated• Opportunity statement• Key personas• Key scenario titles• Key metricsWheel Nice Guys “Bike Builder”last updated: April 7,2013Opportunity StatementProblem: Serious bike commuters find it difficult to learn about,configureand purchase bikes. Solution: A Web application that lets serious bikecommuters explore different components,envision different combinations andunderstand price.Key Persona(S)PETER (serious bike commuter) because bike commuting will be a point ofmaket differentiation for our shop. Our solution might also be attractiveto FRAN (sports training biker) but we’re NOT going after NOONA (budget-conscious weekend rider).Key Scenario Titles• Peter explores options for a new bike (information,cost,configurationchoices)• Peter shares his configuration with friends• Peter makes an appointment to visit WNG to discuss the bike he configuredKey MetricsSerious bike commuters who use the bike builder will:• Look up info and change bike components in the bike builder (engagement)• “Like”the bike builder and share bikes they configured in the bike builder(market intelligence,virality)• Make an appointment to talk to an advisor (qualified leads)• Buy a bike (revenue)Why use six-ups?• Visual thinking unlocks new ideas because it engages a differentpart of your brain than talking.• You don’t need to be good at drawing to be an effective visualcommunicator. You can do a lot with simple shapes and stick people.• Sketching six-ups as a team helps expose everyone’s assumptionsand starts good conversations about priorities and unknowns.Project BRiefSix-upFor more information see: bit.ly/c5r-project-brief
  • 2. #c5recipeApr.30.13Lean UX NYC 2013#leanuxWhy use six-ups?• Visual thinking unlocks new ideas because it engages a differentpart of your brain than talking.• You don’t need to be good at drawing to be an effective visualcommunicator. You can do a lot with simple shapes and stick people.• Sketching six-ups as a team helps expose everyone’s assumptionsand starts good conversations about priorities and unknowns.The project brief helps the team understand the objectives of thecurrent project phase,experiment,milestone or MVP.• Start with a blank document that contains the sections below.Writethe project brief as a team.• Use a shared Google doc or pass the keyboard and make differentpeople type different sections to increase ownership in the outcome.• Review often (i.e.when you write,prioritize or size user stories) andrevise as necessary to reflect the accurate project goals. project brief SECTIONS• Project name• Date last updated• Opportunity statement• Key personas• Key scenario titles• Key metricsProject BRiefSix-upWheel Nice Guys “Bike Builder”last updated: April 7,2013Opportunity StatementProblem: Serious bike commuters find it difficult to learn about,configureand purchase bikes. Solution: A Web application that lets serious bikecommuters explore different components,envision different combinations andunderstand price.Key Persona(S)PETER (serious bike commuter) because bike commuting will be a point ofmaket differentiation for our shop. Our solution might also be attractiveto FRAN (sports training biker) but we’re NOT going after NOONA (budget-conscious weekend rider).Key Scenario Titles• Peter explores options for a new bike (information,cost,configurationchoices)• Peter shares his configuration with friends• Peter makes an appointment to visit WNG to discuss the bike he configuredKey MetricsSerious bike commuters who use the bike builder will:• Look up info and change bike components in the bike builder (engagement)• “Like”the bike builder and share bikes they configured in the bike builder(market intelligence,virality)• Make an appointment to talk to an advisor (qualified leads)• Buy a bike (revenue)- Activity -Six-upsNote: This activity works better if the team has a shared understandingof the project goals and user(s) and if everyone participates in both thedrawing and the subsequent conversation.Step 1: Agree on a topic question,for example “How might we createexperiences that help serious bike commuters evaluate and purchasebikes at Wheel Nice Guys?”Step 2: Fold an 8.5”x11”piece of paper in half longways and then fold itin thirds.Unfold and you’ll have six sections.Set a timer for 15 minutes.Step 3: Draw a picture in each section.If you’re stuck,think abouta setting or situation where the user solves a problem with yourproduct/service.What are the the key elements of that solution ?Step 4: Tape your six-ups on a wall.One person at a time,describe yourconcepts.Other people just listen & take notes (on stickies).Step 5: When all the concepts are introduced,talk about all the ideas,adding more notes (stickies) as necessary to capture the conversation.For more information see: bit.ly/c5r-project-brief
  • 3. #c5recipeApr.30.13Lean UX NYC 2013#leanux- tips -Opportunity Statement• Ask your project stakeholder(s) to write an opportunity statementand use that as a starting point for a conversation about projectscope and vision.• An opportunity statement can be used to define an experiment,milestone or MVP the team will design,deliver and validate.• Use the opportunity statement as a way to prioritize design anddevelopment activities. Ask“How does doing this help us achivewhat we set out to do in the opportunity statement?”• The opportunity statement contains assumptions that must bevalidated by making things and showing them to customers. As youmake things,get feedback and learn more, revisit the opportunitystatement periodically to make sure it’s still valid.- Example -Persona 4x4NamE & rOle• Sketch of Peter,wearing a bike helmet• Peter,serious bike commuterDescription• Owns several bikes• Does NOT own a car• Bikes are a hobby--he loves looking at bikes and talking about bikesBehavors• Rides everywhere--work,store,errands• Rides in all weather• Carries a lot of stuff (computer,groceries)Needs & Goals• Arrive clean and not too sweaty• Share his enthusiasm• Be safeA persona is a model of your understanding of “the user.” Personas canevolve over time as you talk to users learn from showing them productexperiments. Sketching personas as a group can help your team:• Talk about how different people will use your product• Prioritize different kinds of users• Recognize when you don’t know who the user really is• Find what kinds of people you want to find and talk toPersona 4x4ExampleProblemCustom bike shoppers find it difficult to learn about,configure andpurchase bikes.SolutionA Web application that lets custom bike shoppers explore differentcomponents,envision different combinations of components andaccessories and understand price.We will know we’ve succeeded whencustom bike shoppers use the tool,share with their friends,generatequalified leads and purchase bikes.Opportunity StatementAn opportunity statement articulates the team’s undestanding of theaudience we’re trying to reach and the problem we’re trying to solve.PAtternProblem<people with this behavior> <have this problem>.Solution<short sentence describing key features>.We will know we’vesucceeded when <qualitative and/or quantitative metric>.
  • 4. #c5recipeApr.30.13Lean UX NYC 2013#leanux- Example -Persona 4x4NamE & rOle• Sketch of Peter,wearing a bike helmet• Peter,serious bike commuterDescription• Owns several bikes• Does NOT own a car• Bikes are a hobby--he loves looking at bikes and talking about bikesBehavors• Rides everywhere--work,store,errands• Rides in all weather• Carries a lot of stuff (computer,groceries)Needs & Goals• Arrive clean and not too sweaty• Share his enthusiasm• Be safeA persona is a model of your understanding of “the user.” Personas canevolve over time as you talk to users learn from showing them productexperiments. Sketching personas as a group can help your team:• Talk about how different people will use your product• Prioritize different kinds of users• Recognize when you don’t know who the user really is• Find what kinds of people you want to find and talk toPersona 4x4- tips -Opportunity Statement• Ask your project stakeholder(s) to write an opportunity statementand use that as a starting point for a conversation about projectscope and vision.• An opportunity statement can be used to define an experiment,milestone or MVP the team will design,deliver and validate.• Use the opportunity statement as a way to prioritize design anddevelopment activities. Ask“How does doing this help us achivewhat we set out to do in the opportunity statement?”• The opportunity statement contains assumptions that must bevalidated by making things and showing them to customers. As youmake things,get feedback and learn more, revisit the opportunitystatement periodically to make sure it’s still valid.ExampleProblemCustom bike shoppers find it difficult to learn about,configure andpurchase bikes.SolutionA Web application that lets custom bike shoppers explore differentcomponents,envision different combinations of components andaccessories and understand price.We will know we’ve succeeded whencustom bike shoppers use the tool,share with their friends,generatequalified leads and purchase bikes.Opportunity StatementAn opportunity statement articulates the team’s undestanding of theaudience we’re trying to reach and the problem we’re trying to solve.PAtternProblem<people with this behavior> <have this problem>.Solution<short sentence describing key features>.We will know we’vesucceeded when <qualitative and/or quantitative metric>.
  • 5. #c5recipeApr.30.13Lean UX NYC 2013#leanuxGoals• Create a shared understanding of the emerging design• Discuss time/effort of different approaches and identify trade-offs• Get input from developers about ways to enhance the userexperience with new technologies• Identify areas where the design needs to be fleshed out in greaterdetail for discussion and construction- Tips -Wireframe WalkthroughUse the right fideltiyAsk yourself “What is the lowest level of design fidelity (completeness/polish) necessary to create the necessary conversation?”Separate style from functionCreate “neutral/unstyled”key screens with real (or at least realistic)content and all UI elements placed in a layout.[no “lorem ipsum!”] Ifyour team needs to see visual design,create a single styled screen orseparate style sheet to show how the look would be applied.Consider mixed mediaUse a paper prototype or sketches for detailed interactions which aretime-consuming to create as multiple states in an electronic tool.Use a narrativeDemonstrate the design’s features with a narritive (scenario).Tella story about how the user would interact with the product toaccomplish a common workflow or activity that supports a businessobjective (e.g.This is how Peter configures a bike and shares it.”) - Example-Conversation GuideProduct: service for diners who use mobile devicesIntroDo you dine out and use mobile devices? (screening question)We’re interested in what you think.No wrong answers.Collect ContextWhat’s your name.What do you do? When do you eat out? Why?Collect a StoryTell me about a recent dining experience.What restaurant? With who?Occasion/motivation? What was memorable? How much was the bill? Howmuch did you pay? Any problems?Show the Demo LastHow would you use this product to <something they told you about earlierin the conversation>. If they get stuck ask“what do you think should happennow?”Thank you! May we contact you later? Who else should we talk to?When you plan as a group,everyone is more engaged and it’s easier tofocus on what you want to learn during customer conversations.Alignthe team by asking “What do we wish we knew about our customers?”and “What kinds of people do we need to talk to?”Tips• Have a specific learning objective in mind• Recruit 3-5 people who match your target audience (persona)• Collect stories,listen more than you talk• Show the demo lastWireframe WalkthroughCustomer Conversations
  • 6. #c5recipeApr.30.13Lean UX NYC 2013#leanux- Tips -Wireframe WalkthroughUse the right fideltiyAsk yourself “What is the lowest level of design fidelity (completeness/polish) necessary to create the necessary conversation?”Separate style from functionCreate “neutral/unstyled”key screens with real (or at least realistic)content and all UI elements placed in a layout.[no “lorem ipsum!”] Ifyour team needs to see visual design,create a single styled screen orseparate style sheet to show how the look would be applied.Consider mixed mediaUse a paper prototype or sketches for detailed interactions which aretime-consuming to create as multiple states in an electronic tool.Use a narrativeDemonstrate the design’s features with a narritive (scenario).Tella story about how the user would interact with the product toaccomplish a common workflow or activity that supports a businessobjective (e.g.This is how Peter configures a bike and shares it.”) - Example-Conversation GuideProduct: service for diners who use mobile devicesIntroDo you dine out and use mobile devices? (screening question)We’re interested in what you think.No wrong answers.Collect ContextWhat’s your name.What do you do? When do you eat out? Why?Collect a StoryTell me about a recent dining experience.What restaurant? With who?Occasion/motivation? What was memorable? How much was the bill? Howmuch did you pay? Any problems?Show the Demo LastHow would you use this product to <something they told you about earlierin the conversation>. If they get stuck ask“what do you think should happennow?”Thank you! May we contact you later? Who else should we talk to?Goals• Create a shared understanding of the emerging design• Discuss time/effort of different approaches and identify trade-offs• Get input from developers about ways to enhance the userexperience with new technologies• Identify areas where the design needs to be fleshed out in greaterdetail for discussion and constructionWireframe WalkthroughWhen you plan as a group,everyone is more engaged and it’s easier tofocus on what you want to learn during customer conversations.Alignthe team by asking “What do we wish we knew about our customers?”and “What kinds of people do we need to talk to?”Tips• Have a specific learning objective in mind• Recruit 3-5 people who match your target audience (persona).• Collect stories,listen more than you talk• Show the demo lastCustomer Conversations