Involving users - Why is it so hard to do the right thing?


Published on

Why is user involvement in projects the exception rather than the rule, despite the fact we know it is the ‘right’ thing to do? Taking a practical standpoint and without the boring and irrelevant theory, this presentation discusses the role of user involvement in web projects covering:

- What types of projects need (and do not need) to involve users
- Determine the value of involving users or the risks of not involving them
- Methods and techniques appropriate for different situations
- Low-contact, quick methods you can use to learn about users with little effort
- Tips to help other people understand the value of user involvement

Published in: Design, Technology, Business
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Involving users - Why is it so hard to do the right thing?

    1. 1. Involving Users - Why Is It So Hard To Do The Right Thing? Donna Spencer Maadmob
    2. 2. About me <ul><li>Freelance information architect/interaction designer </li></ul><ul><ul><li>8 yrs </li></ul></ul><ul><ul><li>Complex websites, intranets, business applications </li></ul></ul><ul><ul><li>Design, strategy, mentoring, training </li></ul></ul><ul><li>Conducted loads of user research </li></ul><ul><li>Writing a book about card sorting - due soon </li></ul>
    3. 3. Key points <ul><li>Images – veggies, exercise, alcohol </li></ul>
    4. 4. But first, what is user research
    5. 5. What is user research
    6. 6. Why would we do it? <ul><li>Your users may have different: </li></ul><ul><ul><li>experience with computers </li></ul></ul><ul><ul><li>understanding of the domain </li></ul></ul><ul><ul><li>working patterns and working arrangements </li></ul></ul><ul><ul><li>ways of describing their tasks </li></ul></ul><ul><ul><li>contexts in which they will use the product </li></ul></ul><ul><ul><li>goals for using the product </li></ul></ul><ul><li>You will learn interesting things! </li></ul>
    7. 7. How we do it
    8. 8. Why don’t we do it? No money We are the users Too hard The outcome really doesn’t matter The client actually doesn’t care We already know what users need Someone already ‘gathered requirements’ Don’t know who our users are No time
    9. 9. What helps us do it Included it in proposal budget Team have the skills to Client cared about doing well Acknowledged that we don’t know the users Explained that requirements weren’t enough Have easy access to users Made it fast
    10. 10. How to decide...
    11. 11. How to decide <ul><li>How important is it to the organisation </li></ul><ul><li>Risk if we get it wrong </li></ul><ul><ul><li>Impact on the users </li></ul></ul><ul><ul><li>Money spent </li></ul></ul><ul><ul><li>Profile </li></ul></ul><ul><li>Need to convince others </li></ul><ul><li>Existing knowledge of users </li></ul><ul><li>Ability to iterate </li></ul><ul><li>Ability to collect feedback </li></ul>
    12. 12. How to decide
    13. 13. Personal blog
    14. 14. Conference website
    15. 15. E-commerce system
    16. 16. Big internal business app
    17. 17. Making it easier…
    18. 18. Making it easier <ul><li>Start with existing materials </li></ul><ul><ul><li>Staff who have contact with users </li></ul></ul><ul><ul><li>Website analytics </li></ul></ul><ul><ul><li>Search terms </li></ul></ul><ul><li>Small research, not huge </li></ul><ul><li>Focus your research – don’t try to learn everything </li></ul>
    19. 19. Share it! <ul><li>Personas/scenarios </li></ul>
    20. 20. Personas
    21. 21. Share it! <ul><li>Personas/scenarios </li></ul><ul><li>Analytics reports </li></ul><ul><li>Analysis of feedback </li></ul>
    22. 22. Questions & thanks <ul><li> </li></ul><ul><li>0409-778-693 </li></ul><ul><li>[email_address] </li></ul><ul><li>Twitter etc: maadonna </li></ul>