User-centred design and prototyping

  • Published on

  • View

  • Download

Embed Size (px)


Often, we forget that we build systems the way the BA, the Systems Architect and the Developer interpret the requirements and not the way that users might envision the system. This means that what we build might not actually be what users want or actually need to help them get their work done.This presentation looks at user-centred design as a way of shifting the focus back toward the user in order to achieve the sweet spot between the business requirements and the user-requirements. It suggests that this process needs to start early, as part of the planning, rather than being left til too late in the process.


  • 1.User-Centred Design& P rototypingMatthew Hodgson Regional-lead, Web and Information Management 4 Nov 2007

2. Systems design What the user actually needed As finally implemented As produced by the developers As envisaged by thebusiness owner As specified in the requirements As designed by thesenior analyst 3. Systems development lifecycle 4. Squeezing out the design-phase 5. Developers as designers 6. The high cost of redevelopment COST INCREASE 7. How do we capture the intent of the system? 8. User-centred design 9. What is user-centred design?

  • Engages users:
  • From thebeginning to the endof a project
  • Understands:
  • How userswantto use the system
  • How usersthinkabout their work
  • Identifies:
  • Needs and wants
  • Interaction preferences

10. User-centred design frameworks Jessee James Garrett: 11. How do we do user-centred design?

  • A look at how other disciplines employ this philosophy

12. Prototyping thru storyboarding

  • Movie-makers use storyboarding to:
  • Plan the movie as early as possible
  • Put themselves into the shoes of the audience
  • Make the moviebetterfor the audience
  • Conceive of the movieearly
  • Identify flaws in the plot
  • Work out difficult concepts
  • Save time and money

13. BAs using storyboarding

  • Helps us understand:
  • Users wants and needs
  • User-interaction preferences
  • Clarify:
  • Business processes
  • Identify:
  • Flaws in business & system logic
  • Points for system support

14. BAs using storyboarding (cont.) 15. Storyboarding (cont.)

  • Benefits:
  • Light-weight use at a minutes notice
  • Low cost just grab pen & paper
  • User buy-in for change management
  • Gets users involved
  • Sets users expectations
  • Increases users understanding of the system
  • Disadvantages:
  • Need to be able draw to convey the concept

16. Iterative prototyping

  • Take your storyboards to the next level
  • Conceive of a system before implementation!
  • Involves:
  • Engaging usersagain, and again and again
  • Refining conceptsuntil theyre bullet-proof
  • Includes:
  • Interaction design
  • Navigation design
  • Information design

17. Case study

  • Previz as an example of iterative prototyping

18. Evolution through iteration with users 19. What does iterative prototyping involve?

  • Emphasise:
  • User involvement theyre the ones going to use the system!
  • Improve:
  • Design concepts
  • Refine:
  • User interactions
  • Information design
  • Navigation model

20. Why use iterative prototyping?

  • Benefits
  • Involves users sets expectations, increases understanding
  • Conceptualordetailed
  • Communicatesthe intent of the system to the developers
  • Find problemsin system interactions early
  • Solveinformation architecture problems early
  • Cheaperthan building the system
  • Disadvantages
  • Need good software Axure (
  • Prototyping ismorethan just screens you might need a UX-designer or an IA to help with the tricky bits

21. Do conceptual design sooner rather than later! 22. User-centred design finding the sweet spot What the user actually needed As finally implemented As produced by the programmers As envisaged by the business owner As specified in the project request As designed by the senior analyst THE SWEET SPOT 23. Fin

  • Questions?
  • Blog:
  • Slideshare:
  • E:
  • W: