ain't no backseat driver

44
Management & Technology Ain’t no backseat driver! A tale about user-centred design, storyboards and prototyping M tth Hd Matthew Hodgson ACT Regional-lead, Web and Information Management SMS Management & Technology SMS Management & Technology 3 June 2008

Upload: matthew-hodgson

Post on 02-Nov-2014

2.037 views

Category:

Technology


2 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Ain't no backseat driver

Management & Technology

Ain’t no backseat driver!A tale about user-centred design, storyboards and prototyping

M tth H dMatthew HodgsonACT Regional-lead, Web and Information ManagementSMS Management & TechnologySMS Management & Technology

3 June 2008

Page 2: Ain't no backseat driver
Page 3: Ain't no backseat driver
Page 4: Ain't no backseat driver
Page 5: Ain't no backseat driver
Page 6: Ain't no backseat driver

Systems for expertsSystems for experts

“It’s time we face reality, my friends …We’re not exactly rocket scientists”

Page 7: Ain't no backseat driver

What about systems for these people?What about systems for these people?

Page 8: Ain't no backseat driver

Web 2.0 designed‐systems for ‘normal’ peopleWeb 2.0 designed systems for  normal  people

Page 9: Ain't no backseat driver

Systems ‘we’ buildSystems  we  build

A i d b hAs envisaged by the Business Owner

As specified in the requirements

As designed by the Senior Analyst

What the UserAs finally As produced by 

actually neededimplementedthe Developers

Page 10: Ain't no backseat driver

Our projects and processes …Our projects and processes …

Page 11: Ain't no backseat driver

… squeeze out the design phase… squeeze out the design phase

Page 12: Ain't no backseat driver

Leaving users til last has a high costLeaving users til last has a high cost

Page 13: Ain't no backseat driver
Page 14: Ain't no backseat driver

How can we capture the intent of the system?How can we capture the intent of the system?

Page 15: Ain't no backseat driver

User‐centred design!User centred design!

Page 16: Ain't no backseat driver

User‐centred designUser centred design

Engages users:Engages users:• From the beginning to the end of a project

Understands:• How users want to use the system• How users think about their workHow users think about their work

Identifies:Identifies:• Needs and wants• Interaction preferences

Page 17: Ain't no backseat driver

ISO:13407 Human‐centred design fprocesses for interactive systems

Page 18: Ain't no backseat driver

User‐centred design frameworksUser centred design frameworks

Source: Jessee James Garrett: www.jjg.net/ia

Page 19: Ain't no backseat driver

How do we ‘do’ user centred design?How do we  do  user‐centred design?

a look at how other disciplines …a look at how other disciplines employ this philosophyemploy this philosophy…

http://www.youtube.com/watch?v=t3mAHQuBqQI

Page 20: Ain't no backseat driver

StoryboardingStoryboarding

Movie Directors use storyboarding to:Movie Directors use storyboarding to:

• Plan the movie as early as possible• Put themselves into the shoes of the audience• Put themselves into the shoes of the audience• Make the movie better for the audience• Conceive of the movie early

Id tif fl i th l t• Identify flaws in the plot• Work out difficult conceptsWork out difficult concepts• Save time and money

Page 21: Ain't no backseat driver

Using storyboarding in our projectsUsing storyboarding in our projects

Helps us understand: Helps us understand: • User’s wants and needs• User-interaction preferences

Clarify:y• Business processes

Identify:Identify:• Flaws in business & system logic• Points for system support

Page 22: Ain't no backseat driver

Storyboarding @ IA Summit 08, MiamiStoryboarding @ IA Summit 08, Miami

Page 23: Ain't no backseat driver

Storyboards with process maps, use‐cases and irequirements

storyboards

use case reference

user experience

business processuser-profiles

(actors) system objectsrequirements lists

Page 24: Ain't no backseat driver

Storyboarding (cont.)Storyboarding (cont.)

Benefits:Benefits:• Light-weight – use at a minutes notice• Low cost – just grab pen & paper• User buy-in for change managementUser buy in for change management• Gets users involved

S• Sets users’ expectations• Increases users’ understanding of the systemIncreases users understanding of the system

Di d tDisadvantages:• Need to be able draw to convey the concept ☺Need to be able draw to convey the concept ☺

Page 25: Ain't no backseat driver

Other tools for user‐centred design?Other tools for user centred design?

‘Previz’ - prototyping the solution• http://www.youtube.com/watch?v=zMgoIwA_oQM

Page 26: Ain't no backseat driver

What does prototyping systems involve?What does prototyping systems involve?

Emphasise: Emphasise: • User involvement – they’re the ones going to use

the system!the system!

Improve:• Design concepts in rapid iterationsDesign concepts in rapid iterations

R fiRefine:• User interactions (UXD)User interactions (UXD)• Information design

N i ti d l• Navigation model

Page 27: Ain't no backseat driver

Evolution through iteration with usersEvolution through iteration with users

Page 28: Ain't no backseat driver

Why use prototyping?Why use prototyping?Benefits

E l d i l ti• Evolve design solution• 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• Need good software – Axure (www.axure.com)g ( )• It’s more than just screens! – need an IA to help with the tricky

bits

Page 29: Ain't no backseat driver

‘Conceptual’ design in project methodologyConceptual  design in project methodology

Page 30: Ain't no backseat driver

Case study:User‐centred design in action!

Page 31: Ain't no backseat driver

Case studyCase study

Client:Client:• Large government agency• Business critical system redevelopment• Business-critical system redevelopment• Included business process improvement

Problem:Problem:• Silos’ expectations to manage• No documented processes• 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’!

Page 32: Ain't no backseat driver

The dreaded analysis spiralThe dreaded analysis spiral

Page 33: Ain't no backseat driver

NewNew Information

Analysis Storyboardpossibilities

Understand UsersWants & Needs

Prototype

Design

interactions

Design& Document

solution

Refineconcepts

Solution• Adopt a user centred • Adopt a user-centred

design approach• Reinforce role clarity

Build• Reinforce role clarity

Page 34: Ain't no backseat driver

Understand your users thru PersonasUnderstand your users thru Personas

Page 35: Ain't no backseat driver

Storyboard possibilitiesStoryboard possibilities

Page 36: Ain't no backseat driver

Prototype users’ system interactionsPrototype users  system interactions

Page 37: Ain't no backseat driver

OutcomesOutcomesIncreased user-acceptance of change:• Created a single vision of what we were doing• Helped managed expectationsHelped managed expectations• Wider understanding of everyone’s needs

Better system adoption:y p• User-involvement meant system was ‘designed’ for them to

useuse

S d tiSaved time:• Kept us on-track and the vendor less distractedp• Worked through difficult concepts before development

Page 38: Ain't no backseat driver

ConclusionsConclusions

Page 39: Ain't no backseat driver

User‐centred designUser centred design

Benefits:Benefits:• Improved vision – we can all see up front where we’re going

I d h t bilit• Improved change management capability• Visible iterations – no hidden end-game solution• Best-practice agile environment methodology

Disadvantages:• More up-front analysis required• Role definition – requires good communicationRole definition requires good communication• Power-shift to front-end of project

S d l d ’t lik b i l t• Some developers don’t like being last

Page 40: Ain't no backseat driver

The goalThe goal

As envisaged by the business 

owner

As specified in the project request

As designed by the senior analyst

THE SWEET SPOT

What the userAs finallyAs produced by 

What the user actually needed

As finally implemented

the programmers

Page 41: Ain't no backseat driver
Page 42: Ain't no backseat driver

Management & Technology

FinFinQuestions?Q

Page 43: Ain't no backseat driver

Management & Technology

Ain’t no backseat driver!Ain t no backseat driver!

A tale about user-centred design, g ,storyboards and prototyping

Page 44: Ain't no backseat driver

Management & Technology

Matthew HodgsonACT Regional-lead, Web and Information Management

SMS Management & Technology

Blog: magia3e.wordpress.comTwitter: magia3eTwitter: magia3e

Slideshare: www.slideshare.net/magia3e

Email: [email protected] @Mobile: 0404 006695