Rethinking ux iue july 2010
11 likes907 views
The document explores the evolution of user experience (UX) design and its integral role in connecting customers with companies through iterative and collaborative processes. It emphasizes the shift from a prescriptive to a value-driven approach in product development, fostering an agile mindset and co-creation among teams. The piece calls for an organizational transformation that prioritizes customer needs and promotes continuous learning, collaboration, and innovation.
Rethinking ux iue july 2010
- 1. Rethinking UXWhat is the User Experience profession anyway and why are we doing this work?
- 2. Sort of, but not reallyWhat's the core of what we do?Connect customers and companies to make stuff people love
- 3. A StoryRewrite the story of Product Development
- 4. Why? Our World Has Changed“Have to” Has Become “Want to”OwnershipUbiquityChoice…
- 6. Agile and UXAgile means thinking differentlyAgile means changing behavior and mindsetsAgile + UX = BFFWe just don’t know itIt’s a UX dream come true:Iterative and incremental design and development
- 7. Time for a new way of thinking
- 8. Not a PrescriptionThis is the rethinking part:How do we serve our customers?What’s their UX of working with us?How involved and engaged are they?
- 9. History
- 10. What’s the CoreConnect customers and companies or customers and development teams
- 11. The ProfessionWhat is the UX Profession anyway? And why are we doing this work?Only measurements: Efficiency? Effectiveness? Satisfaction? Or more?Beyond the product?User Centered Design?Information architecture?Interaction Design?Human factors?Usability specialist?Users or Customers?
- 13. I think we know - reallyUser Experience ResearchAnd Design
- 14. Usability/UCD or Design?Usability Maturity ModelStage 1: Hostility Toward UsabilityStage 2: Developer-Centered UsabilityStage 3: Skunkworks UsabilityStage 4: Dedicated Usability BudgetStage 5: Managed UsabilityStage 6: Systematic Usability ProcessStage 7: Integrated User-Centered DesignStage 8: User-Driven Corporation
- 15. Design Is Never Done
- 16. Build to think"Design thinking is inherently a prototyping process. Once you spot a promising idea, you build it. In a sense, we build to think."
- 18. Comrades While UX was convincing companies to design software for humans, software engineers were also trying to get companies to understand how to develop software
- 19. Agile and UXAgile means thinking differentlyAgile means changing behavior and mindsetsAgile + UX = BFFWe just don’t know itIt’s a UX dream come true:Iterative and incremental design and development
- 20. Back to the Core
- 22. More on ValueAn understanding of how to capitalize on what we do know, find out about what we don’tResearch, dataPersonasPrototypesA strong sense of collaborationEveryone has a piece of the puzzle, let’s put them togetherWhat tools do we have to help keep the focus on the customer?
- 23. What’s important?When designing take this approachWho before whatWhat before howAsk “Why?” and “What’s the real problem?” liberally throughoutTest out the how with real people, often
- 24. Stop Building the Wrong Thing!
- 25. What does it take?
- 26. Organizational TransformationNot about schedules and timelinesIs about customers and colleagues, problems and solutionsAnd delivering value
- 27. Out of the Echo Chamber
- 28. Leading ChangeHow many does it take to make a change happen?
- 29. Use Your SkillsWhat’s missing?Who needs to be on board?How can you help them?A little WIFM goes a long way What experience can you create to facilitate understanding?What experiences create empathy with customers?
- 30. What’s different?Not about processNot about methodsNot about metricsThese are TOOLS
- 31. Defy limitationsKeep it simple
- 32. What does it look like?No more Feature driven developmentValue driven, iterative, flexible, agileDesign thinking organizationSolve problems rather than create featuresProvide value and emotional connectionsEveryone has a piece of the puzzle – fit them togetherCollaborateUser driven organizationTake it a step farther – watch users work, don’t just talk to themFind problems they don’t even recognize and solve themInnovate based on customer value
- 33. Value Driven Development Iterative incremental developmentPrototypes and visibility - get something valuable and complete to play with ASAPBe willing to throw away code (or whatever) – “design” vs production codeBuild the simplest thing that will workBuild value incrementally
- 34. Core Values
- 35. Our ValuesCo-creationIterative designReflective processCollaborative workIntegrative thinkingCommon understandingsEverything is an experimentDelivering on the promise of VALUEConnecting customers and companies
- 36. How do we get there?“Take the first step in faith…”Martin Luther King
- 37. Starts with EducationHow do we educate designers?How do we educate developers?How do we educate researchers?How ‘bout the rest of the organization? product managers? marketing? sales? executives?How do we educate ourselves?
- 38. Your take?Where are you and what makes sense?
- 39. Questions?
Editor's Notes
- #4: David and goliath?
- #5: Google my laptop over 27 mil results… for “my computer”
- #7: Why? Iterative and incrementalHOW?Encourage iterative and incremental design methods. Make agile milestones more “real”. Encourage teams to watch real users use their product. Perform analysis to help guide design effort in a quick and agile fashion. Testing makes sprint milestones more real.Encourage more iterative and incremental design methods by providing opportunities for teams to effectively evaluate iterations.
- #8: Regardless of agile or not, it’s timeWade CunninghamAgile is ever evolving, changing based on lessons learned in the last iteration, continuous improvement No implementation should be exactly the same as another
- #10: Our roots are in human factors, HF came about because we were building machines that hurt peopleWhat we said was, "gee wiz, let's design stuff for the humans who will be using it”Later Usability and HCI came about because computers were hard to use and scary – can still be true to this daywhat we said was, "gee wiz, let's design stuff for the humans who will be using it”
- #11: ObservationWith productWithout productCollaborative workDesignProblem solving
- #12: Too many job titles – we can’t even decide
- #13: What stands out?Taken from the UPA job board
- #15: Compare ucd and design lifecyclesRally around design – we all design or engage in design activities, easier to sell, encourage
- #16: Get to the point where you stop working on it…Advantages to design thinking….
- #17: Example – Wii remoteQuote from http://www.fastcompany.com/magazine/95/design-strategy.html?page=0,1http://www.ideo.com/images/uploads/thinking/publications/pdfs/FastCo-StrategyByDesignTimBrown.pdf
- #20: Why? Iterative and incrementalHOW?Encourage iterative and incremental design methods. Make agile milestones more “real”. Encourage teams to watch real users use their product. Perform analysis to help guide design effort in a quick and agile fashion. Testing makes sprint milestones more real.Encourage more iterative and incremental design methods by providing opportunities for teams to effectively evaluate iterations.
- #22: Not self referential design
- #28: Stop listening to ourselves talkStop arguing about who and howStop being self-referential
- #30: How would connect you to your users?Personas?Usability testing?
- #31: Tools get used when needed and you don’t need all tools for every job…
- #32: Design and design thinking – simple concepts, easy to see how we would beat the competition (be that antiquated systems or rival companies)Easy to see how to move to the next stepUsability is there to confirm – along with market research – that we designed the right thing
- #34: Couple years ago – only found Jeff Patton’s whitepaper on Business ValueDesign is never doneNot a one shot – except if you build the wrong thing…
- #37: Build the new in the shell of the old
- #38: In the classroom and with in the companyLive the values