Rsa Gujnsdttir, CID, rosagkth.se

1
User-Centred Design Process and Visualisation
of Requirements

• Rósa Guðjónsdóttir, CID, rosag_at_kth.se

2
Usability

• Utility
• The product meets the users needs and goals
• The product respects the users culture
• User friendliness
• The product is easy to use
• The products functions are easy to remember

3
User-centred design

• User centered design is a structured,
  comprehensive product development methodology
  which
• Involves users
• Is iterative and tests are performed to control
  that users needs are met
• Integrates different disciplines
• Is driven by clearly specified business
  objectives
• User-centered design is about understanding the
  users and their needs and designing an
  interactive system to meet those needs

4
Benefits of usability

• Positive perception of the company and its brand
• Increased customer loyalty
• Better quality
• Higher accessibility
• Increased participation
• More content employees

5
Benefits of usability

• Increased number of visits and return visits
• Almost 50 of users dont come back if they find
  it hard to find relevant information on a web
  site (Forrester research, 1999)
• Increased productivity
• 10 minutes x 50 employees x 5 workdays 42 hours
  per week

6
Benefits of usability

• Decreased number of failed products/projects
• Decreased costs for development and maintenance
• 1x -gt 10x -gt 100x
• Decreased costs for user support
• Decreased costs for education and training

7
User-centred design process
5
6
1
2
3
4

• Who are the users?
• What are their needs and goals? What are their
  attitudes and values?
• Which content and functionality meets their
  needs?
• How should the content be structured and
  visualised?
• Prototypes and evaluation
• Implementation and follow-up

8
Users
5
6
1
2
3
4

• 1 Who are the users?
• Online surveys
• Review of documentation

9
Utility
5
6
1
2
3
4

• What are their needs and goals? What are their
  attitudes and values?
• Ethnographic field studies
• Contextual interviews
• Focus groups
• Interviews

10
Functionality
5
6
1
2
3
4

• 3 Which content and functionality meets their
  needs?
• Ethnographic field studies
• Interviews
• Focus groups
• Contextual interviews
• Workshops with client

11
Results
5
6
1
2
3
4

• When we know what the users need and how to
  meet those needs we communicate the results to
  project stakeholders
• Report
• Persona
• Scenario
• Video

12
Structure
5
6
1
2
3
4

• 4 How should the content be structured and
  visualised?
• How to structure the navigation
• Terminology for buttons and links
• How to structure the content
• Card sorting exercises with users

13
Prototype and evaluation
5
6
1
2
3
4

• 5 Prototypes and evaluation
• Prototypes produced (Paper, PowerPoint, Html)
• User tests on members from the target groups
• Prototypes improved
• New iteration of user tests
• Parallell to this the requirement specifications
  are written

14
Implementation
5
6
1
2
3
4

• 6 Implementation and follow-up

15
Personas
25
28
25-30
Lorem ipsum dolor sit amet, consectetuer
adipiscing elit. Vestibulum lobortis mi non quam.
Vivamus lorem. Vestibulum pretium. Ut faucibus
ultrices leo. Proin eu arcu. Duis sapien tortor,
varius nec, pellentesque ut, eleifend vitae, leo.
Integer mauris eros, tincidunt ut, dignissim ac,
ultricies eu, nunc. Maecenas sit amet libero non
orci consectetuer ultricies. Nulla purus.
Vestibulum ante ipsum primis in faucibus orci
luctus et ultrices posuere cubilia Curae Integer
dapibus odio a ipsum. Donec porta, mi at pulvinar
mollis, metus justo porttitor lorem, sed suscipit
lacus urna in enim. Vestibulum ac nunc.
Pellentesque placerat nisl a diam. Nulla sed
erat. Aliquam sit amet justo. Suspendisse lectus
sapien, dignissim sit amet, aliquam id, sagittis
vitae, nulla.
16
Personas

• A personas are a fictitious persons who represent
  a target group
• They have a name, a life
• They have specific needs and requirements
• They have a goal
• Their live is exemplified through a scenario
  where they perform certain tasks and fulfill
  their goal
• It is more important to be specific than to be
  accurate in the persona description

17
Personas

• Personas make it easier to communicate the
  results of a pre-study
• To project group
• Between different competence groups in the
  project
• To the client

18
Personas

• A primary persona and a secondary persona
• A design tool that visualizes the users needs and
  requirements
• A persona is sometimes more effective than real
  users
• Real users can sometimes behave very strangely
• A persona can not participate in a user test
• Personas create a more and substantial user
  awareness in the project
• Personas do not replace users participation!

19
How to use personas

• All members of the project group have to know the
  personas
• To know who the user is
• To know the users needs and requirements
• Personas are used to
• Prioritize functionality
• Discuss different solutions
• Personas work during the whole project
• Look over our shoulders while we are designing
  and producing the system

20
How to create personas
21
How to create personas

• You give them a name
• Patrik
• You give them a life
• Patrik is a positive and energetic guy who is
  just recovering from the thirty-something crisis.
  He is educated in political science, and is
  almost finished with his Masters thesis
• Patrik has worked for over six years as
  sakkunnig for the party in the Swedish
  parliament. He is mostly active within the
  healthcare sector.
• You give them a face

22
How to create personas

• You give them a goal
• Patrik wants to do a good job in the healthcare
  committee by influencing the policymaking

23
How to create scenarios

• You write a scenario where the persona realizes
  the goal
• It is Tuesday morning and it is still early, but
  Patrik is already at the office. He starts his
  day by reading the news on online newspapers and
  starts with DN, SVD and Aftonbladet, and then he
  reads the news on his partys Intranet. When hes
  finished he resumes his work on

24
How to create personas
Life-size personas literally look over our
shoulder while designing and producing the system
25
User-centred design process
5
6
1
2
3
4

• Who are the users?
• What are their needs and goals? What are their
  attitudes and values?
• Which content and functionality meets their
  needs?
• How should the content be structured and
  visualised?
• Prototypes and evaluation
• Implementation and follow-up