What is the User Experience profession anyway and why are we doing this work? I want to help people make products people love. Some of us in the field are making products people love - what are they doing differently? What is Agile and how do we fit in? How do we rethink our profession in this world where technology and implementation move so fast? Get back to the core of what we do: connect customers and companies; understand our users (not just the ones who use the product, but those who use our services) and focus on the value we offer. Not the value of the test or the report, but the value of the intelligence we provide. The landscape has changed: people have higher expectations about the products and service they use. Things should just work, they shouldn't be hard. How can we help companies and product teams get there? This talk would be my take on the subject, I would love to hear yours too.
6. Agile and UX Agile means thinking differently Agile means changing behavior and mindsets Agile + UX = BFF We just don’t know it It’s a UX dream come true: Iterative and incremental design and development
8. Not a Prescription This is the rethinking part: How do we serve our customers? What’s their UX of working with us? How involved and engaged are they?
10. What’s the Core Connect customers and companies or customers and development teams
11. The Profession What 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?
12.
13. I think we know - really User Experience Research And Design
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 UX Agile means thinking differently Agile means changing behavior and mindsets Agile + UX = BFF We just don’t know it It’s a UX dream come true: Iterative and incremental design and development
22. More on Value An understanding of how to capitalize on what we do know, find out about what we don’t Research, data Personas Prototypes A strong sense of collaboration Everyone has a piece of the puzzle, let’s put them together What tools do we have to help keep the focus on the customer?
23. What’s important? When designing take this approach Who before what What before how Ask “Why?” and “What’s the real problem?” liberally throughout Test out the how with real people, often
29. Use Your Skills What’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 process Not about methods Not about metrics These are TOOLS
32. What does it look like? No more Feature driven development Value driven, iterative, flexible, agile Design thinking organization Solve problems rather than create features Provide value and emotional connections Everyone has a piece of the puzzle – fit them together Collaborate User driven organization Take it a step farther – watch users work, don’t just talk to them Find problems they don’t even recognize and solve them Innovate based on customer value
33. Value Driven Development Iterative incremental development Prototypes and visibility - get something valuable and complete to play with ASAP Be willing to throw away code (or whatever) – “design” vs production code Build the simplest thing that will work Build value incrementally
35. Our Values Co-creation Iterative design Reflective process Collaborative work Integrative thinking Common understandings Everything is an experiment Delivering on the promise of VALUE Connecting customers and companies
36. How do we get there? “Take the first step in faith…” Martin Luther King
37. Starts with Education How 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?
Google my laptop over 27 mil results… for “my computer”
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.
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
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”
Compare ucd and design lifecyclesRally around design – we all design or engage in design activities, easier to sell, encourage
Get to the point where you stop working on it…Advantages to design thinking….
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
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.
Not self referential design
Stop listening to ourselves talkStop arguing about who and howStop being self-referential
How would connect you to your users?Personas?Usability testing?
Tools get used when needed and you don’t need all tools for every job…
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
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…
Build the new in the shell of the old
In the classroom and with in the companyLive the values