UIEtips: Winning a User Experience Debate

Jared Spool

July 12th, 2011

It’s time for feedback on your design. Good or bad, productive or not, you’re given some insight into that design. In many cases, that critique comes from stakeholders or paying customers.

Sure, critique should be constructive and impartial, yet it’s inevitable that you’ll occasionally disagree with the feedback you receive. Critique is a crunch moment for the undercover designer—you’re sticking your neck out and taking the lead of the design process. However, stakeholders sometimes see design as a complex, unpredictable subject that can cause havoc in the wrong hands. Who wants to let a bull loose in their china shop?

In today’s UIEtips, Cennydd Bowles shares an excerpt from Undercover User Experience Design, a book he co-wrote with James Box. Cennydd outlines his advice for winning a UX debate and explains what to do when you disagree with the feedback you receive on your design. We love this book, and think this excerpt is a great way to immerse yourself in his concept of undercover UX design.

Read the article: Winning a User Experience Debate

It just so happens that Cennydd is conducting our next virtual seminar on July 21: UX Design when Time, Money, and Support is Limited. At the end of this seminar, you’ll be able to put UX principles into practice in any organization, and learn how to make the case for user experience design with results, not theory. Learn more about this virtual seminar.

2 Responses to “UIEtips: Winning a User Experience Debate”

  1. How to Win a User Experience Debate « jpreardon.com Says:

    [...] via UIEtips [...]

  2. Gail Swanson Says:

    If all you have to back up your design is design theory, you don’t have a very strong debate position. When your stakeholder takes a strong stance on a design issue, and that’s all you have, you may be better served by backing off and conceding the issue. Preserve the relationship and focus on working with their direction.

    Another tactic to add to the validation stack could be finding examples that illustrate your point. Use other’s work to demonstrate to the stakeholder how the experience will look and feel if you go in their direction. Do some guerilla usability testing on that example to prove your point if it’s that pivotal an issue.

Add a Comment