Product and UX - are the roles blurring?

3,562 views
3,273 views

Published on

For most web-based companies, it appears that product managers have started to evolve their user experience (UX) skills in order to sell key concepts to developers, executives and even customers. On the flip side, UX folks contribute significant requirements and user stories in their design process and user research. So are the two roles becoming one? This covers the roles and why they are unique or not and even delves into the creation of annotated wireframes or prototypes instead of long-winded requirements docs - in an attempt to speed up the process to validate features and designs sooner rather than later with customers.

Published in: Design

Product and UX - are the roles blurring?

  1. 1. Product and UXAre the roles blurring?<br />It would be easier for me to just mock this up!<br />How could they miss all these user stories?<br />
  2. 2. Questions for you<br />Are you PM, Marketing or UX?<br />Where do you sit in the org?<br />Agile vs. waterfall?<br />You’re here because…<br />You see this same conflict day-to-day?<br />You want to learn how to be UX-minded/capable?<br />You want to shorten the time from idea to release?<br />Other reasons?<br />2<br />
  3. 3. UX vs. UXP vs. UE<br />All mean the same thing<br />3<br />CONFIDENTIAL<br />
  4. 4. UI is the interface <br />UI vs. UX<br />4<br />CONFIDENTIAL<br />
  5. 5. UI vs. UX<br />the person, their surroundings, the handling of the iPhone and its uses, etc.<br />+<br /> UX is the<br />5<br />CONFIDENTIAL<br />
  6. 6. PM vs. UX<br />UI Development<br /><ul><li>Develop UI
  7. 7. Flesh out and rebuild prototypes
  8. 8. Client side logic
  9. 9. Works with testing and rest of dev</li></ul>Product<br />Gather feedback<br />Requirements<br />Business case<br />Roadmap<br />Releases<br />Communication (with Marketing)<br />Measurement<br />PM Titles<br />Product Mgr/Owner<br />Biz/Product Analyst<br />Requirements Mgr<br />User Experience<br /><ul><li>Discovery
  10. 10. Research
  11. 11. Personas
  12. 12. User stories
  13. 13. User flows
  14. 14. Design
  15. 15. Wireframes
  16. 16. Prototypes
  17. 17. Visual design
  18. 18. Test and refine</li></ul>UX Titles<br /><ul><li>Interaction Designer
  19. 19. Visual Designer
  20. 20. Usability Analyst</li></ul>6<br />
  21. 21. = Possible user testing<br />PM & UX in product development<br />Product Development<br />Release<br />Feedback<br />Monthly major releases with 2 week sprints<br />Scorecard<br />Weekly Updates<br />Product Roadmap<br />Product Backlog<br />Sprint Plans & Architecture<br />Test & Release<br />PM<br />prioritization<br />Technical Specs & Documentation<br />PRD<br />Wires<br />Hi-Fi Mocks / Prototypes<br />continuous customer feedback<br />Product<br />UX<br />Development<br />Testing & Ops<br />Recurring meetings – 1 month sprint planning w/ mid month review and daily stand-ups <br />7<br />
  22. 22. PM tools and deliverables<br />Microsoft Excel for backlogs, business cases, etc.<br />Microsoft Word for requirements docs, updates, etc.<br />Microsoft Powerpont for roadmaps, product overviews, etc.<br />Microsoft Visio for wireframing and work/user flows<br />TechSmithSnagit for screen captures and quick UI changes<br />Adobe Photoshop Elements for color selection, etc.<br />8<br />
  23. 23. PM and UX in action<br />
  24. 24. Customer feedback/research<br />“I need a way to prioritize my backlog more effectively.”<br />“Can I score my projects based on my quarterly company objectives? <br />“Instead of only specific target results – you might want to consider allowing high and low values too.”<br />10<br />
  25. 25. Backlog<br />11<br />
  26. 26. PM user stories<br />Project: Add scorecard<br />Users need to see these columns – objective title, weighting, target date, low result, target result, high result, project points and total points.<br />Users need the option to add “project points” (0-5) per objective within a selected timeframe.<br />The “total points” column should be calculated as project points times weighting.<br />12<br />
  27. 27. Wireframe<br />13<br />
  28. 28. UX user stories<br />Project: Add scorecard<br />User should be able to edit pre-existing objectives and attributes – but for now not add additional ones.<br />The “project points” column needs to be differentiated enough to prompt the user to edit it.<br />Overall project score should also be highly visible to the user.<br />14<br />
  29. 29. Visual Design<br />15<br />
  30. 30. Real world example<br />16<br />Posted Fri, Feb 26 on “Agile Usability” (a Yahoo groups site)<br />“I am a designercurrently working on an agile project and we are in iteration 0, the story discovery phase. The team has been using story trawling to discover all the various stories, and it has worked to a degree, but after some of the basic CRUD stories have been written, the more complex flows honestly require more thought and perhaps a wireframe to truly flesh out all the functionality. In essence, for the complex flows, we are all in some way imagining some kind of interface/flow, and are trying to write it down into stories but they just seem haphazard. It's not clear to me at this time, if some of the stories will be used, and more importantly if we missed some of the stories because we don't have a solid narrative supported by a clear wireframe to write those stories.”<br />
  31. 31. Questions?<br />Jesse Gant<br />@gantjd<br />http://www.slideshare.net/gantjd<br />

×