Design by Committee

Design by Committee

Presenters: Pradeep Nayar and Kevin Leebroderick
UX work in an Agile (or almost Agile) environment can sometimes feel like 'Design by Committee'. The Tribune UX team would like to share some tips, thoughts and strategies we use internally, to maintain the sanctity of a participatory design environment. We will stay as practical as possible, using recent projects to walk through what we do. The goal is to leave you with some key takeaways to try in your workplace.

8704e7380b12d7552e66eeb5e35ec4d7?s=128

Pradeep Nayar

July 19, 2012
Tweet

Transcript

  1. Kevin Leebroderick UX Architect Tribune Company July IXDA 2012 @

    Tribune Company DESIGN BY COMMITTEE Maintaining Sanity in an Agile Environment Pradeep Nayar UX Principal Tribune Company
  2. We are a MEDIA COMPANY 23 TV STATIONS 8 NEWSPAPERS

    50+ WEBSITES
  3. 160 years old

  4. None
  5. None
  6. 5 PRIOR UX WORK

  7. L.A. TIMES IPAD APP

  8. L.A. TIMES WINDOWS PHONE 7 APP

  9. CRIME L.A. ANDROID APP

  10. CHICAGO TRIBUNE WINDOWS 8 APP

  11. Mobile Social Tablet TV Web Strategy CONCEPTS 10

  12. PRIOR UX WORK 11 CHICAGO TRIBUNE RESPONSIVE SITE

  13. “DESIGN BY COMMITTEE” OUR GOAL 12

  14. “DESIGN BY COMMITTEE” PARTICIPATORY DESIGN OUR GOAL 12

  15. Redesigning the Stop sign http://www.youtube.com/watch?v=xwqPYeTSYng

  16. 14 WE’RE AGILE! ...almost

  17. AGILE = COLLABORATION 15

  18. 16

  19. LET’S BRAINSTORM

  20. Brainstorm meetings 18 Lack focus Progress too quickly to a

    solution without exploring options Most powerful, loud and/or obnoxious person wins! People get excited about an existing solution rather than solving the problem Some solutions are not cohesive with the overall experience CHALLENGE
  21. “Brainstorm” in isolation 19 SOLUTION Have a designated facilitator Embrace

    divergent thinking; conduct individual exploration Conduct a design studio, not a BRAINSTORM MEETING!!!
  22. THE CREW STAKEHOLDERS DEVELOPERS PRODUCT MANAGER PROJECT MANAGER QUALITY ASSURANCE

    TEAM UX
  23. SPHERES OF INFLUENCE STAKEHOLDERS DEVELOPERS PRODUCT MANAGER PROJECT MANAGER QUALITY

    ASSURANCE TEAM UX
  24. TEAM UX

  25. You are a design facilitator 25 SPOILER ALERT In an

    agile environment...
  26. Not enough time 26 CHALLENGE

  27. 27 SOLUTION START SKETCHING!!!

  28. NO EXCUSES!

  29. SOLUTION PRESENT internally CRITIQUE not gut reaction PROTOTYPE Test it!

    many ideas SKETCH rinse & repeat
  30. Believe in your solution 30 You can’t sell it if

    you don’t believe it.
  31. Never go alone Always tag team. 31 SPOILER ALERT VISUAL

    DESIGNER UX ARCHITECT +
  32. PRODUCT MANAGER

  33. They are your closest ally but... 33 There is a

    grey area - work it out!
  34. Let’s do what the N.Y. Times does... 34 CHALLENGE “Follow

    the leader” approach.
  35. Explain why it may not work Time to show your

    expertise on interface design. 35 SOLUTION Look at other examples to force a conversation. Focus on the problem you are trying to solve and question the solution.
  36. They might try to design the interface 36 CHALLENGE Let

    them sketch ideas.
  37. Be open to various forms of communication 37 SOLUTION Remind

    them that your job is to make them look good.
  38. They help push hard features forward 38 It’s important to

    maintain daily communication with them.
  39. PROJECT MANAGER

  40. They are usually the scrum master 40 A good project

    manager can make or break a project.
  41. Over promises on deliverables 41 CHALLENGE Trying to please an

    impatient stakeholder.
  42. Be upfront and realistic about estimates 42 SOLUTION Build on

    existing trust and confidence. There is no such thing as over-communication.
  43. DEVELOPERS

  44. 44 Best friend or worst enemy They make your ideas

    come to life.
  45. Like reuse of code & efficiency 45 CHALLENGE Solutions oriented

    around technology rather than the needs of users.
  46. 46 Reality of agile development Stuff always changes.

  47. It’s all about building a better product 47 SOLUTION Walk-through

    the interface using specific scenarios. Take the time to explain the thought behind your design. Thank them for a job well done! Try to include them early in a solution.
  48. QUALITY ASSURANCE

  49. If UX is the quarterback... 49 QA is the receiver.

  50. QA only tests functionality 50 CHALLENGE

  51. Set expectations & keep in touch 51 SOLUTION Need to

    emphasis how important they are to the project. The success of the project depends on them. Talk about a holistic testing approach. Conduct occasional walk-throughs with them.
  52. STAKEHOLDERS

  53. 53 Talk to them in a language they understand Talk

    about customers, not users.
  54. UX also needs to think about the business 54 SPOILER

    ALERT User needs + business needs = $$$ for everyone.
  55. 55 CHALLENGE Dealing with an alpha personality

  56. 56 Let’s face it. You’re not going to win, but...

    SOLUTION Figure out what makes them tick. Find an influencer and become their buddy. Don’t be scared - they’re not going to bite.
  57. 57 Always present your work Never email a deliverable and

    assume they understand your lengthy email. SPOILER ALERT
  58. 57 Always present your work Never email a deliverable and

    assume they understand your lengthy email. SPOILER ALERT SELL
  59. 58 Selling the idea Consider making it a experience. Presentation

    Experience
  60. None
  61. Give them options, but lead them to your choice Always

    tell a story. Solution A Normal Solution B Better Solution C What they should want
  62. 61 What are you selling? TRUST & CONFIDENCE

  63. It’s not a war 62 FINALLY! We’re all in this

    together.
  64. Thanks! 63 Get in touch with questions, comments or other

    feedback Pradeep Nayar prad.nayar@gmail.com designonmymind Kevin Leebroderick kleebroderick@tribune.com
  65. Special thanks to 64 Kim Ruelo Adam Jankowski Kate Rosendale

    Andre Alforque Trent Sherrell