Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

User Experience (UX) is a Team Sport

Following traditional "waterfall" methods, designers create wireframes & high-fidelity comps which are delivered to developers who build the product. This "handoff" of design to development can cause frustration and inefficiency when construction starts. What happens when it's not possible to realize all aspects of the design within the constraints of the project? What about edge cases the designer didn't consider? Once the issues are discovered, designers often aren't available to make changes and the development team has to use their best judgement when implementing the design.

What if there were a better way? What if designers could preview their work earlier and developers could give input about technical considerations? When designers and developers have necessary conversations, they can better support each other and build better products, faster.

In this workshop, Lane Halley and Mike Wynholds of Carbon Five share some "recipes" to help your team create necessary conversations and get your whole team engaged in the user experience of your product.

User Experience (UX) is a Team Sport

  1. 1. UX Designis a Team SportWednesday, May 29, 13
  2. 2. Lane Halley@thinknowlane@carbonfive.comMike Wynholds@mwynholdsmike@carbonfive.comWednesday, May 29, 13
  3. 3. What are the qualities ofhappy productive teams?Wednesday, May 29, 13
  4. 4. Good work comes from good teamsTrust OwnershipCreativityEmpathyFunEmpowermentFlowCommunicationProductivityWednesday, May 29, 13
  5. 5. CultureOur work at Carbon FiveWednesday, May 29, 13
  6. 6. Carbon FiveWednesday, May 29, 13
  7. 7. Design + Agile + Lean StartupDesign Thinkingempathy, creativity and rationalityAgile Developmentself-organizing teams, quality code, iterative & incremental deliveryLean Startupproducts people want, learning experimentsWednesday, May 29, 13
  8. 8. ProductOwnerDesignerDeveloperWednesday, May 29, 13
  9. 9. DeveloperProductOwnerDesignerWednesday, May 29, 13
  10. 10. OpportunityStatementWednesday, May 29, 13
  11. 11. People that (behavior) hate/need (problem)Our solution solves this by (key feature)We’ll know this works when (metrics)Wednesday, May 29, 13
  12. 12. it!Wednesday, May 29, 13
  13. 13. WireframeWalkthroughWednesday, May 29, 13
  14. 14. wireframe walkthrough• Collaborative design critique• For users, clients, designers, and developers• Print it out, post it up, stand at arms length• Use think aloud protocol• Document with stickies on the wireframesWednesday, May 29, 13
  15. 15. When to do it?•At start of project• During iteration planningWednesday, May 29, 13
  16. 16. Try it!Wednesday, May 29, 13
  17. 17. developer cheat sheet1. frame the conversation2. acknowledge the challenge3. act like a curious user4. questions over comments5. say “we” over “you” or “i”6. participate as a creative collaboratorWednesday, May 29, 13
  18. 18. Expert tips...Wednesday, May 29, 13
  19. 19. 1designer:print out and post the latest wireframes on a wallat gallery height.find a developer and put them at arms lengthfrom the drawings.Wednesday, May 29, 13
  20. 20. 2developer:ask about the current state of the designs andwhat kind of feedback they’re looking for.find out if the designer is more interested ingenerative or evaluative feedback.ask “where are you at?”Wednesday, May 29, 13
  21. 21. 3designer:let the developer know about your goals for thewalkthrough.say “i’m really interested in hearing yourthoughts on...”Wednesday, May 29, 13
  22. 22. 4developer:acknowledge the challenge.walk through the flow, pointing where yourmouse would be.narrate what you are thinking and doing as auser.“i’m trying to find out how to...”Wednesday, May 29, 13
  23. 23. 5designer:take notes on the stickies directly on the wireframes tomark the location of the comment or observation.this is a free usability test!Wednesday, May 29, 13
  24. 24. 6developer:note missing functionality or difficult technicalchallenges.ask questions about the user rather than makingstatements. for instance: “how would I find aforgotten password?” rather than “you forgot theforgot your password screen.”keep in mind that this is a cooperative discussionabout the design, not a judgement on thedesigner.Wednesday, May 29, 13
  25. 25. 7designer:take notes and offer insights into the currentdesign solution.listen, breathe, and try not to get defensive (orthink of elephants).postpone deep or off-topic discussions.“that’s something we’ve been really strugglingwith.”“we tried that but noticed...”Wednesday, May 29, 13
  26. 26. 8developer:suggest alternatives to any particularlychallenging engineering implications.“what user need are we trying to address here?”“we could try... and get a similar result with lesseffort.”“this is our main feature so it makes sense that wespend extra time on it.”Wednesday, May 29, 13
  27. 27. 9designer:thank the developer.incorporate feedback as appropriate.rinse and repeat.Wednesday, May 29, 13
  28. 28. Thank you!Carbon FiveLean UX & AgileDevelopment for Weband mobile productswww.carbonfive.comWednesday, May 29, 13