designing better features
play

DESIGNING BETTER FEATURES BY SOLVING BETTER PROBLEMS WREN LANIER - PowerPoint PPT Presentation

DESIGNING BETTER FEATURES BY SOLVING BETTER PROBLEMS WREN LANIER PROBLEMS MAKE US ANXIOUS SOLUTIONS MAKE US FEEL GOOD REAL TALK We ship too many solutions that dont actually solve a problem FALL IN LOVE WITH THE PROBLEM not the perfect,


  1. DESIGNING BETTER FEATURES BY SOLVING BETTER PROBLEMS WREN LANIER

  2. PROBLEMS MAKE US ANXIOUS

  3. SOLUTIONS MAKE US FEEL GOOD

  4. REAL TALK We ship too many solutions that don’t actually solve a problem

  5. FALL IN LOVE WITH THE PROBLEM not the perfect, finished solution

  6. BENEFITS OF BEING PROBLEM-ORIENTED • More emphasis on learning instead of deliverables • Better insights lead to better solutions • Easier to sell value of solutions to stakeholders • Brings clarity to prioritization discussions

  7. UNDERSTANDING USERS by understanding their problems

  8. https://blinkux.com/blog/agile-ux-research/

  9. Image Credit: Renee Lin https://uxdesign.cc/a-crooked-little-ux-journey-at-a-big-bank-8f1f2f375989

  10. STRATEGIC UX INPUT REQUIRES INDEPENDENT PROBLEM DISCOVERY Don’t ask for permission. Just do it.

  11. DISCOVERY: GOOD IS BETTER THAN PERFECT • Doesn’t have to be part of a project timeline • Focus on users’ work & goals, less about your software • Ask lots of open-ended questions

  12. ASK QUESTIONS LIKE Tell me about the last time you created a personal budget . • What’s the hardest thing about making & managing to-do lists ? • What’s the best new tool you’ve started using lately? • What do you wish you could do that you can’t do? • What do you need? •

  13. “I’m hungry, and I don’t have time to eat a meal.”

  14. DO YOU KNOW WHAT PROBLEM(S) your product is solving for your users?

  15. DEFINING USER PROBLEMS State problems in the simplest language possible, no jargon • Relate each problem to an important user goal • Identify the pain point, something that is too di ffi cult / 
 • too slow / too expensive / too complicated User problems are not software usability problems •

  16. SHIFTING OUR WORK to focus on user problems

  17. TALK ABOUT DESIGNS IN TERMS OF THE PROBLEMS YOU’RE SOLVING

  18. INSTEAD OF Users need to go faster TRY Ti e problem users have is that their produce has a short lifespan which makes it hard to sell before it goes bad. Users want a faster way to get their produce to market and sell it before it spoils.

  19. INSTEAD OF Users need more fj ltering options TRY Ti e problem users have is that they can’t fj nd their previous campaigns to see the results they achieved. Customers feel like our product isn’t providing any bene fj t because they can’t fj nd their results.

  20. MAKE THE CONNECTION USER PROBLEM BUSINESS PROBLEM

  21. EVOLVE HOW WE TALK ABOUT OUR WORK User Research Discovering User Problems Design Iteration Exploring Multiple Solutions Lean Experiments Validating Our Solutions

  22. #GOALS Replace your roadmap with a list of high-priority user problems

  23. MINING USER FEEDBACK to understand important problems

  24. MOST USERS WILL ASK FOR SOLUTIONS 
 (I.E. FEATURES) INSTEAD OF ARTICULATING PROBLEMS

  25. Users asked for this a lot

  26. FEATURE REQUEST I want to pin notes to my contacts. WHY? I need pins so I can FIND my notes. REAL PROBLEM I need to fj nd things more easily. WHY? Ti e search results aren’t useful.

  27. DIG INTO FEATURE REQUESTS FOR CONTEXT Tell me about a time when feature would have helped you? • What’s most frustrating/worrying about not having feature ? • How do you deal with this situation today? • Ask about where they’ve seen or used feature before. •

  28. USERS DON’T ALWAYS KNOW WHAT THE REAL PROBLEM IS OR THE BEST SOLUTION Ti at’s okay. Ti at’s not their job.

  29. DESIGNERS NEED TO TRANSLATE FEATURE REQUESTS INTO PRODUCT INSIGHTS Ti is is totally our job.

  30. VALIDATING USER PROBLEMS Target discovered problems with additional interviews • Look for similar problems in support requests • Look for similar problems in help site search logs •

  31. PRO TIP Use a tool like Google Site Search to track the query terms customers use on your Help Site

  32. IDENTIFYING BURGER KING FEATURES A request for customization, usually of the UI • Not painful enough to inspire user hacks • No underlying problem except users think they want it •

  33. ORGANIZING FEEDBACK around user problems

  34. NEVER ORGANIZE FEEDBACK AROUND FEATURE REQUESTS Seriously. Not even once.

  35. DON’T ASK HORSE USERS TO INVENT THE AUTOMOBILE

  36. BUILD MEASURE LEARN INNOVATION COMES FROM CONTINUOUS LEARNING

  37. ORGANIZE FEEDBACK BY PROBLEM “I can’t fj nd things” • “I forget about things.” • “I need to share things with people who don’t have an account.” • “I haven’t done it yet because it seems too complicated.” •

  38. Yes Slack, please remind me about this!

  39. FOCUSING ON FEATURES LEADS TO MISSED OPPORTUNITIES When all you have is a hammer…

  40. UNDERSTANDING THE PROBLEM IS OFTEN THE BIGGEST CHALLENGE Great design starts here.

  41. BUSINESS GOALS DRIVE PRIORITIES By amount of pain (great when dealing with churn) • By user type, i.e. support your best users • By level of di ffi culty, to ship improvements as fast as possible •

  42. CHANGE TAKES TIME …but it gets easier the more people you 
 bring along with you

  43. WORK ON PROBLEMS THAT ARE WORTHY OF YOUR LOVE & ATTENTION It will make you happier, I promise.

  44. THANK YOU! WREN LANIER Find me @heywren or wrenlanier.com

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend