User-centred design and prototyping

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    12 Favorites & 1 Group

    User-centred design and prototyping - Presentation Transcript

    1. User-Centred Design & P rototyping Matthew 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 the business owner As specified in the requirements As designed by the senior 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 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
    10. User-centred design frameworks Jessee James Garrett: www.jjg.net/ia
    11. How do we do user-centred design?
      • A look at how other disciplines employ this philosophy…
      • http://www.youtube.com/watch?v=t3mAHQuBqQI
    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 movie better for the audience
      • Conceive of the movie early
      • Identify flaws in the plot
      • Work out difficult concepts
      • Save time and money
    13. BAs using storyboarding
      • Helps us understand:
      • User’s 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 users again, and again and again
      • Refining concepts until they’re bullet-proof
      • Includes:
      • Interaction design
      • Navigation design
      • Information design
    17. Case study
      • ‘ Previz’ as an example of iterative prototyping
      • http://www.youtube.com/watch?v=zMgoIwA_oQM
    18. Evolution through iteration with users
    19. What does iterative prototyping involve?
      • Emphasise:
      • User involvement – they’re 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
      • Conceptual or detailed
      • Communicates the intent of the system to the developers
      • Find problems in system interactions early
      • Solve information architecture problems early
      • Cheaper than building the system
      • Disadvantages
      • Need good software – Axure (www.axure.com)
      • Prototyping is more than 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: magia3e.wordpress.com
      • Slideshare: www.slideshare.net/magia3e
      • E: mhodgson@smsmt.com
      • W: www.smsmt.com

    + Matthew HodgsonMatthew Hodgson, 2 years ago

    custom

    2448 views, 12 favs, 1 embeds more stats

    Often, we forget that we build systems the way the more

    More info about this document

    CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

    Go to text version

    • Total Views 2448
      • 2365 on SlideShare
      • 83 from embeds
    • Comments 0
    • Favorites 12
    • Downloads 158
    Most viewed embeds
    • 83 views on http://magia3e.wordpress.com

    more

    All embeds
    • 83 views on http://magia3e.wordpress.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Groups / Events