Unlocking the Power of ChatGPT and AI in Testing - A Real-World Look, present...
Meaningfuldesignfeedback
1. Building Bridges, Connecting Communities
LISA REX @lisarex
Acquia
Design Validation
(aka how to suck less)
Friday, May 24, 13
2. Building Bridges, Connecting Communities
LISA REX @lisarex
Acquia
Design Validation
(aka how to suck less)
Meaningful Design Feedback
Friday, May 24, 13
3. This session was made possible by
✤ Christine Perfetti
✤ Dani Norden
✤ Drew Robertson
✤ James Elliott
✤ Jeff Noyes
✤ Julie Marobella
✤ Ken Woodworth
✤ Kevin O’Leary
✤ Matt Edmunds
✤ Michael Cooper
✤ Nica Lorber
✤ Roy Scholten
Friday, May 24, 13
4. My name is Lisa Rex and I’m a
senior user experience researcher
Friday, May 24, 13
5. This is the design team at Acquia
Preston So, Kevin O’Leary, Matt Edmunds, Lisa Rex, Jeff Noyes, Drew Robertson, James
Elliott and Dharmesh Mistry.
Not pictured: Christine Perfetti and Al Steffen
Friday, May 24, 13
6. The UX interaction designers
✤ Design briefs / style guides
✤ Visual design
✤ Prototypes
✤ Liaise with engineering and marketing teams
Friday, May 24, 13
7. The UX research team
✤ Research planning
✤ In depth research
✤ Usability studies
✤ Liaise with engineering and customer-facing teams
Friday, May 24, 13
8. Design feedback in the design
process
✤ Verbal or written feedback
✤ In a group or 1:1
✤ Stakeholders, peers, or users
Friday, May 24, 13
9. What you can learn from feedback
Friday, May 24, 13
12. Content
✤ Purpose for being there
✤ Too little? Too much? Too much!
✤ Message and brand
Friday, May 24, 13
13. “How has design feedback
helped your work?”
9 different people*, 9 different answers
* 7 designers, 2 product managers
Friday, May 24, 13
14. Wisdom from Matt Edmunds
“The difference between art and design: design is a feedback driven
process. Design is serving a purpose.”
- Matt Edmunds
Friday, May 24, 13
21. People tend to fancy themselves a
designer
Friday, May 24, 13
22. Rein in the
“designers”
✤ They probably haven’t taken
into account existing research
or other info.
✤ They’re unaware of existing
patterns.
✤ A flat design still needs all the
interactions worked out.
✤ They could have found 5 other
problems instead.
http://www.flickr.com/photos/lloydyweb/162608725/
Friday, May 24, 13
24. Let’s make a thing!
(A homepage redesign, for example)
Friday, May 24, 13
25. “Everyone wants to be part of the design process, and if it's
successful they want to say they had a hand in it. It's the human
condition to say you're part of something successful.”
- Matt Edmunds
Friday, May 24, 13
29. Success criteria = SMART
✤ Good: Increase effectiveness rating of signing up from 2.5 to 4 for
Task A by Q4
✤ Less good: Make it easier for users to sign up.
✤ Good: Increase conversion rate from 2% to 5% by Q4
✤ Less good: Higher conversion rate than the current process
✤ Good: Have at least 1 blog post written about us a month after
launch
✤ Less good: Greater visibility
Friday, May 24, 13
33. Who do you need to make happy?
Friday, May 24, 13
34. Client centric approach
✤ Focus on making the client happy
✤ Business objectives come first
✤ Clients pay you to deal with them changing their mind
Paul Boag
http://boagworld.com
Friday, May 24, 13
35. User centric approach
✤ Focus on making the user love your site/app
✤ User goals come first
✤ If a user is satisfied, they will stick around, recommend to friends,
profit
Friday, May 24, 13
40. Stakeholder feedback
✤ Stakeholders need the design to meet project / business goals
✤ Frequent feedback is better
✤ Use Design reviews, Design Checkins, and/or commenting tools
Friday, May 24, 13
41. Design reviews
✤ Stakeholders together
✤ You facilitate and take notes
✤ Designer presents his vision
“Most non designers feel the solution
is to over communicate their
feedback. An experienced designer
will bubble up the useful data and
filter out the noise.”
-- Matt Edmunds
Friday, May 24, 13
42. Get actionable feedback
✤ Ask them to focus on the problem, not the solution*
✤ Remind them to focus on the central experience and goals
✤ Ask them “why” a lot
Friday, May 24, 13
45. “The best way to understand users’ goals, attitudes, and pain
points is to watch people using your products. After observing
users, product teams come away with a rich understanding of what
users really need.”
- Christine Perfetti
Friday, May 24, 13
46. User feedback
✤ Don’t be afraid to talk to users.*
✤ Users are coming to your site with a purpose. What is it, really?
✤ Find out how users will love using your site.
*or a close approximation
Friday, May 24, 13
47. Finding people to talk to
✤ Ask in person, ideally
✤ Offer incentives
✤ Emphasize the benefit of helping
Friday, May 24, 13
48. Feedback in person
✤ Pros:
✤ Build rapport
✤ Better communication (+ nonverbal)
✤ Easier to deal with interruptions
✤ Cons:
✤ Logistics
Friday, May 24, 13
51. ✤ Don’t try to prove things right or wrong.
✤ Focus on the user goals are, and how the design enables them to
complete those goals
✤ Use measurable metrics
✤ Communicate findings visually or with videos
Usability studies
Friday, May 24, 13
52. Setting up repeatable studies
✤ Repeat studies to see how tasks fare after changes.
✤ Complete Drupal site on a multi-environment hosting provider, such
as Acquia Cloud or Pantheon. Revert the database after each study.
✤ Use drush to reset all modules back to default state.
Friday, May 24, 13
53. #protip
✤ Get stakeholders involved.
✤ Don’t gather research alone.
✤ Record conversations.
Friday, May 24, 13
54. Reading and watching
✤ Reading:
✤ Undercover User Experience Design
✤ Rocket Surgery Made Easy: The Do-It-Yourself Guide to Finding
and Fixing Usability Problems
✤ Watching:
✤ http://www.youtube.com/user/squareweave
✤ http://vimeo.com/65242833
Friday, May 24, 13
55. Processing the feedback
✤ Gather the feedback
✤ Look for high level themes
✤ Show these to stakeholders
✤ Decide what to act on
Friday, May 24, 13
57. Product name
Dave the Developer Journey Map 1
Phase 3Phase 2Phase 1
5
4
3
1
2
Usable
Meh
Frustration
The Journey Map
Friday, May 24, 13
58. Acting on the design feedback
✤ Commit to % of time to incorporate feedback
✤ Translate the feedback to chunks of work
✤ Run a “KJ” session to prioritize
✤ Add these to the development schedule
Friday, May 24, 13
59. Your turn
✤ Do design validation. And then tell me what you learned.
✤ Apply to be an Acquia research participant: http://bit.ly/Xqc5Pg
Friday, May 24, 13
61. Building Bridges, Connecting Communities
Evaluate this session at:
http://portland2013.drupal.org/node/1278.
Thank you!
What did you think?
Friday, May 24, 13
