Ain't no backseat driver


Published on

A presentation on user-centred design methods, tools and techniques

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ain't no backseat driver

  1. 1. Management & Technology Ain’t no backseat driver! A tale about user-centred design, storyboards and prototyping Matthew H d M tth Hodgson ACT Regional-lead, Web and Information Management SMS Management & Technology 3 June 2008
  2. 2. Systems for experts Systems for experts “It’s time we face reality, my friends … We’re not exactly rocket scientists”
  3. 3. What about systems for these people? What about systems for these people?
  4. 4. Web 2.0 designed systems for  normal people Web 2.0 designed‐systems for ‘normal’ people
  5. 5. Systems ‘we’ build Systems  we build As envisaged by the  A i db h As specified in the  As designed by the  Business Owner requirements Senior Analyst As produced by  As finally  What the User the Developers implemented actually needed
  6. 6. Our projects and processes … Our projects and processes …
  7. 7. … squeeze out the design phase … squeeze out the design phase
  8. 8. Leaving users til last has a high cost Leaving users til last has a high cost
  9. 9. How can we capture the intent of the system? How can we capture the intent of the system?
  10. 10. User‐centred design! User centred design!
  11. 11. User‐centred design User centred design Engages users: • From the beginning to the end of a project Understands: • How users want to use the system • How users think about their work Identifies: • Needs and wants • Interaction preferences
  12. 12. ISO:13407 Human‐centred design  processes for interactive systems f
  13. 13. User‐centred design frameworks User centred design frameworks Source: Jessee James Garrett:
  14. 14. How do we ‘do’ user‐centred design? How do we  do user centred design? …a look at how other disciplines a employ this philosophy philosophy…
  15. 15. Storyboarding Movie Directors use storyboarding to: Plan the movie as early as possible • Put themselves into the shoes of the audience • Make the movie better for the audience • Conceive of the movie early • Id tif flaws iin th plot Identify fl the l t • Work out difficult concepts • Save time and money •
  16. 16. Using storyboarding in our projects Using storyboarding in our projects Helps us understand: • User’s wants and needs • User-interaction preferences Clarify: y • Business processes Identify: • Flaws in business & system logic • Points for system support
  17. 17. Storyboarding @ IA Summit 08, Miami Storyboarding @ IA Summit 08, Miami
  18. 18. Storyboards with process maps, use‐cases and  requirements i storyboards use case reference user experience business process user-profiles (actors) system objects requirements lists
  19. 19. Storyboarding (cont.) Storyboarding (cont.) Benefits: • Light-weight – use at a minutes notice • Low cost – just grab pen & paper • User buy-in for change management buy in • Gets users involved • S users’ expectations Sets • Increases users’ understanding of the system users Disadvantages: Di d t • Need to be able draw to convey the concept ☺
  20. 20. Other tools for user centred design? Other tools for user‐centred design? ‘Previz’ - prototyping the solution •
  21. 21. What does prototyping systems involve? What does prototyping systems involve? Emphasise: • User involvement – they’re the ones going to use the system! Improve: • Design concepts in rapid iterations Refine: R fi • User interactions (UXD) • Information design • N i ti modell Navigation d
  22. 22. Evolution through iteration with users Evolution through iteration with users
  23. 23. Why use prototyping? Why use prototyping? Benefits • E l design solution Evolve d i l ti • Involves users – sets expectations, increases understanding • Conceptual or detailed • Communicate intent of system to developers • Find problems in system interactions early • Solve information architecture problems early • Cheaper than building the system Disadvantages g ( ) • Need good software – Axure ( • It’s more than just screens! – need an IA to help with the tricky bits
  24. 24. ‘Conceptual’ design in project methodology Conceptual design in project methodology
  25. 25. Case study: User‐centred design in action!
  26. 26. Case study Case study Client: • Large government agency • Business critical system redevelopment Business-critical • Included business process improvement Problem: • Silos’ expectations to manage • No documented processes • “I don’t know what I want, but I’ll know it when I see it” • Vendor suffered from ‘the dreaded analysis spiral’!
  27. 27. The dreaded analysis spiral The dreaded analysis spiral
  28. 28. New Information Understand Users Storyboard Analysis Wants & Needs possibilities Prototype interactions Design Refine & Document concepts solution Solution • Adopt a user centred user-centred design approach • Reinforce role clarity Build
  29. 29. Understand your users thru Personas Understand your users thru Personas
  30. 30. Storyboard possibilities Storyboard possibilities
  31. 31. Prototype users system interactions Prototype users’ system interactions
  32. 32. Outcomes Increased user-acceptance of change: • Created a single vision of what we were doing • Helped managed expectations • Wider understanding of everyone’s needs Better system adoption: y p • User-involvement meant system was ‘designed’ for them to use Saved ti S d time: • Kept us on-track and the vendor less distracted p • Worked through difficult concepts before development
  33. 33. Conclusions
  34. 34. User‐centred design User centred design Benefits: • Improved vision – we can all see up front where we’re going •IImproved change management capability dh t bilit • Visible iterations – no hidden end-game solution • Best-practice agile environment methodology Disadvantages: More up-front analysis required • Role definition – requires good communication • Power-shift to front-end of project • Some d l S developers d ’t lik b i llast don’t like being t •
  35. 35. The goal The goal As envisaged by  As specified in the  As designed by  the business  project request the senior  owner analyst THE SWEET SPOT As produced by  What the user  What the user As finally  As finally the programmers actually needed implemented
  36. 36. Management & Technology Fin Questions? Q
  37. 37. Management & Technology Ain t no backseat driver! Ain’t no backseat driver! A tale about user-centred design, g, storyboards and prototyping
  38. 38. Management & Technology Matthew Hodgson ACT Regional-lead, Web and Information Management SMS Management & Technology Blog: Twitter: magia3e Slideshare: Email: g@ Mobile: 0404 006695