‘What is UCD?’ presentation

February 6, 2009 (over a year ago)

Transcript

1. User-Centred Design:

   Building an effective, efficient and engaging user experience

2. What is User-Centred Design?
   An approach that involves the user throughout the design and development process
3. Understanding users’ needs
   By understanding user’s needs we can design products that are:
   • Usable: Effective, efficient and satisfying to use
   • Desirable: If a product is desirable to a user, they will be motivated to learn how to use it
4. Involve users early
   By involving users early in the process we aim to ensure we build the ‘right’ things and minimise the need for high cost changes late in the project
   Build the right thing. Build the thing right.
5. What are the benefits?
   • Development: Reduce time and costs
   • Usability: Improve efficiency and effectiveness
   • Conversions: Increase benefits to agents
   • Overall value: Improve user experience

6. How do we ‘do’ UCD?

   How will we test? When will we test? Who will we test with?

7. Make sure we’ve got the right tools
   There are various methods we can use to talk to, observe and interact with users throughout the design process.
8. [Picture of UCD methods list]
   We’ll talk about some of these methods at the end. A full list of methods and their application is on the Design Twiki
9. Which methods do we choose? 
   The recommendation engine allows us to create recommendations for your project
   Working with BAs and BOs we’ll generate two options with costings and timeframes
10. [Picture of recommendation engine]
11. How do we find users?
    • Internal users: Marketing, CST
    • Existing users: Rightmove Improvement Program
    • New users: Trade shows, cafes, external agency
12. Who’s involved?
    • Design
    • Marketing
    • Business Analysts
    • Analytics & Optimisation
13. How do we measure success?
    • Conversion rates
    • Development time & cost
    • Confidence (Are we certain the product works well?)
    • Customer feedback
    • System Usability Scale (SUS)
14. So, what are we actually doing?
    • Bunnyfoot: Usability testing on main flows with eyetracking
    • Beta feedback: Analyse comments to inform future projects 
    • Trialling recommendations and methods on upcoming projects

15. Preparing for UCD

    How we’re getting Rightmove ready for UCD

16. Training programme
    • 1-hour intro to User-Centred Design
    • Weekly practical sessions on methods for user testing: Paper prototyping, user observation (including Silverback), interviews, surveys, multivariate testing
17. Rightmove Improvement Programme
    • We’ve contacted registered or active users in 12 key locations
    • As part of the programme they will help us with surveys, usability tests and preview beta functionality
    • If successful, we’ll widen the net to include non-Rightmove users

18. Let’s look at methods

    A quick overview of key methods, their strengths and weaknesses

19. Paper prototyping
    • Lo-fi mockups on paper with key interactions
    • User interacts with the paper mockups, verbalising their thoughts and what they’re looking for
    • Used early in design phase as quick changes can be made with minimal development
    • Users feel they can still have input into the design
20. User observation
    • Otherwise known as ‘usability testing’
    • Users interact with a working version of the site using the ‘think aloud’ protocol
    • Used during or after development phase
    • Users are interacting with real data and can use real tasks
21. Cognitive walkthroughs
    • After compiling a task analysis, tasks are broken down into sub-tasks and the project team questions each step
    • Used in the research phase to compile potential issues 
    • Generates results quickly for very low cost
22. Expert reviews
    • Measure each page against accepted heuristics (rules of thumb)
    • Conducted by ‘expert’ not working on the project
    • Used in design or development phase
    • Very cost-effective but users are not directly involved
23. Multivariate testing
    • Develop multiple versions of the same page or interaction and measure key metrics to see which is most effective
    • Used in release phase but must be developed in design and development phases
    • Absolute, quantitative data on usage
24. Build the right thing. Build the thing right.