Tom Stewart - If UCD is so great, why are more systems not perfect?

Supporters Sponsors Organiser

1

9.30 Saturday 10 November 2012 Tom Stewart, Founder System Concepts

If UCD is so great, why are more systems not perfect?

User centred design is now mainstream. It's widely accepted as the best way to create

usable systems. Not everyone follows the ISO standard for UCD (ISO 9241-210 previously

known as ISO 13407) but the basic principles seem unarguable. Start by understanding the

users and context. Then set measurable objectives and test potential designs against these

objectives with typical users. Keep refining the design till it meets the objectives. What could

possibly go wrong? In this presentation we discuss a number of real world stumbling blocks

which mean that even when the process is followed properly ( and not doing it properly is

one of the first stumbling blocks), the results are not always what was wanted. Issues

include failing to get management buy-in, testing with the wrong users and fixed project

schedules which preclude fixing known problems.

,

This document and it’s content is Copyright ©2012 [Tom Stewart] and UCD UK Limited.


2

If UCD is so great, why are

more systems not perfect?


3

Actually, IT projects have a

long history of failure


4

Typical reasons for failure

1. The technology didn’t work


5

Me = Mistake edition


6



2. Unrealistic ambitions


7

• Other thoughts “the new system will let everyone be customer facing so customer

service will be great!”


8



2. Unrealistic ambitions

3. Rejected by users


9

User feedback

“in the FCO’s long history of

ineptly implemented IT

initiatives, Prism is the most

badly-designed, ill-

considered one of the lot”


10 10


11

UCD is the solution

but not everyone gets it (Google user centred design)


12


13


14

But most do (Google images for User Centre Design)


15


16

Standards trivia

• Started as ISO 13407

• “Human centred” to

reflect more stakeholders

• Revision is part 210 of

ISO 9241 series

• Part 210 contains “shalls”

ie can claim conformance


17

Warning!

Photos from this point are NOT

from the actual project or client


18

Plan the human-centred

design process


19

Plan the human-centred design process

• What can go wrong?


20


21

Plan the human-centred design process


– Phased development with no time to

incorporate feedback after initial phases

– Organisational changes exposed

‘accidentally’ during design consultation

• Lessons

– Plan for time to incorporate feedback

– Don’t use IT to force organisational change


22

Understand and specify

the context of use


23

Understand and specify the context of use



24


25

Understand and specify the context of use


– Scope and position of new product assumed

by remote teams

• Lesson

– Communicate context of use as early as

possible to as many stakeholders as possible


26

Specify the user

requirements


27

Specify the user requirements



28


29

Specify the user requirements


– Project team “hadn’t decided who would use

system”, planned to install then see “who took

to it best”

• Lesson

– Be absolutely clear about target user

characteristics


30

Produce design solutions

to meet user requirements


31

Produce design solutions to meet user

requirements



32


33

Produce design solutions to meet user

requirements


– Too early focus on detail, users reluctant to

criticise what appear to be fully worked designs

• Lesson

– Keep design concepts simple prior to initial

evaluation


34


35

Evaluate the designs against the

requirements


– Not test at all


36


37


38


39

Evaluate the designs against the

requirements


– Not test at all

– Test with wrong users and tasks – managers

instead of staff

• Lesson

– Test with real users and their tasks


40


41

Iterate where appropriate



42

“Most government IT

therefore remains trapped in

an outdated model, which

attempts to lock project

requirements up-front and

then proceeds at a glacial

pace. The result is repeated

system-wide failure”

Report published by the Institute for

Government, March 2011

www.instituteforgovernment.org.uk


43

Iterate where appropriate


– Not enough time to iterate, made worse by

contractual straightjackets

• Lesson

– Plan better, gain management buy in to

agile/ucd process to minimise risk as part of

organisations IT governance


44 44


45

020 7240 3388

www.system-concepts.com

Tom Stewart

[email protected]


46

“Many forms of Government design process have

been tried, and will be tried in this world of sin and

woe. No one pretends that democracy user

centred design is perfect or all-wise. Indeed, it has

been said that democracy user centred design is

the worst form of Government design process

except for all those other forms that have been

tried from time to time."

‘based’ on a speech by Winston Churchill, 1947

Technology

Tom Stewart - If UCD is so great, why are more systems not perfect?