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. 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. 4.
  3. 5.
  4. 18.

    16

  5. 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
  6. 21.

    “Brainstorm” in isolation 19 SOLUTION Have a designated facilitator Embrace

    divergent thinking; conduct individual exploration Conduct a design studio, not a BRAINSTORM MEETING!!!
  7. 24.
  8. 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.
  9. 37.

    Be open to various forms of communication 37 SOLUTION Remind

    them that your job is to make them look good.
  10. 38.

    They help push hard features forward 38 It’s important to

    maintain daily communication with them.
  11. 40.

    They are usually the scrum master 40 A good project

    manager can make or break a project.
  12. 42.

    Be upfront and realistic about estimates 42 SOLUTION Build on

    existing trust and confidence. There is no such thing as over-communication.
  13. 45.

    Like reuse of code & efficiency 45 CHALLENGE Solutions oriented

    around technology rather than the needs of users.
  14. 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.
  15. 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.
  16. 53.
  17. 54.

    UX also needs to think about the business 54 SPOILER

    ALERT User needs + business needs = $$$ for everyone.
  18. 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.
  19. 57.

    57 Always present your work Never email a deliverable and

    assume they understand your lengthy email. SPOILER ALERT
  20. 58.

    57 Always present your work Never email a deliverable and

    assume they understand your lengthy email. SPOILER ALERT SELL
  21. 60.
  22. 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
  23. 64.

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

    feedback Pradeep Nayar prad.nayar@gmail.com designonmymind Kevin Leebroderick kleebroderick@tribune.com