Design by Committee in an Agile environment
5 likes2,231 views
The document discusses the challenges and strategies of participatory design within an agile environment at Tribune Company. Key recommendations include effective collaboration with stakeholders, product managers, developers, and QA teams, emphasizing the importance of early involvement and continuous feedback. The document highlights the need for cohesive solutions rather than brainstorming sessions that may lead to fragmented ideas.
Design by Committee in an Agile environment
- 1. UXPA 2012 Tribune Company Design by Committee in an Agile environment Myths, tricks & strategies... Pradeep Nayar @DesignOnMyMind UX Principal Tribune Company Kevin Leebroderick UX Architect Tribune Company
- 2. Our Goal: Participatory Design Design by Committee in an Agile environment UXPA 2012 Tribune Company 2
- 3. more than 150 years old
- 5. We’re AGILE ...almost UXPA 2012 Tribune Company 5
- 6. Agile = Collaboration UXPA 2012 Tribune Company 6
- 7. Scenario: A major stakeholder wants to replace our mobile sites with a responsive site. UXPA 2012 Tribune Company 7
- 8. Hey..Scott (Stakeholder) wants us to wrap our heads around this whole responsive design thing... Pam Project Manager UXPA 2012 Tribune Company 8
- 9. ...I know Sunil (Software Architect) just attended a conference where he heard someone talk about it... Pam Project Manager UXPA 2012 Tribune Company 9
- 10. ... Patrick (product manager) spoke to Bob and told him that we’ll brainstorm some idea... Pam Project Manager UXPA 2012 Tribune Company 10
- 11. ... I’m going to schedule a meeting for us to talk...Can you get some your “creative” UX people for the meeting? Pam Project Manager UXPA 2012 Tribune Company 11
- 12. NEVER GET EVERYONE IN A ROOM TO “BRAINSTORM” A SOLUTION Why? People get excited about solutions that don’t solve the problem Some solutions are not cohesive with the overall experience UXPA 2012 Tribune Company 12
- 13. PEOPLE INVOLVED Stakeholders Product Mgr Project Mgr UX QA Developers UXPA 2012 Tribune Company 13
- 14. SPHERES OF INFLUENCE Stakeholders Project Team UX Team UXPA 2012 Tribune Company 14
- 15. Within the UX team Tip #1 Sketch several ideas Review with UX peers Critique & repeat UXPA 2012 Tribune Company 15
- 16. Within the UX team Tip #2 Believe in your solution UXPA 2012 Tribune Company 16
- 17. With the project team (Product, QA, Dev) Tip #3 Never go alone... always tag team UXPA 2012 Tribune Company 17
- 18. Step 1: WORK WITH DEVELOPERS Remember • They can be your best friend or worst enemy • Include them early in a solution UX • Show them examples of what you like and don’t like • Explain the thought behind a design • Thank them for a job well done • Always remind them...we are trying to make a better product Developers UXPA 2012 Tribune Company 18
- 19. Step 2: WORK WITH PRODUCT Remember • They are your closest ally • There is a grey area...work it out UX • You are there to make them look good • They help you push “hard” features forward Product Mgr UXPA 2012 Tribune Company 19
- 20. Step 3: WORKING WITH QA Remember • If UX is the quarterback then QA is the receiver • They assure the quality of the experience UX • They are the final line of defense before the customer QA UXPA 2012 Tribune Company 20
- 21. With stakeholders Tip #4 Always present, never email UXPA 2012 Tribune Company 21
- 22. Final Tip It’s not a war We’re all in this together UXPA 2012 Tribune Company 22
- 23. QUESTIONS? UXPA 2012 Tribune Company
- 24. Thank You. UXPA 2012 Tribune Company