Inclusive Design (Guest Lecture) February 2012 iPersonas | Inclusive requirements for your Personas Caleb Tang @calebtang UX Consultant | Foolproof Accessibility | UK Usability Professionals’ Association
Jan 27, 2015
Inclusive Design (Guest Lecture) February 2012
iPersonas | Inclusive requirements for your Personas
Caleb Tang @calebtang UX Consultant | Foolproof
Accessibility | UK Usability Professionals’ Association
Contents
1. What are Personas? 2. Why Inclusive Personas? 3. Extending the persona development process 4. References
2 © 2012 Foolproof Limited
“A persona is a user archetype you can use to help guide decisions about product features, navigation, interactions, and even visual design”
– Kim Goodwin
“
What are Personas?
A typical Persona may include: § Profile (name, age, job etc) § Goals (life goals, experience goals and end
goals) § Motivations (triggers, rewards etc) § Frustrations (barrier, things to avoid etc) § Context of use (desk, mobile, on-the-go etc) § Skills (domain knowledge, use of technology
etc) § Decision making process (behaviours,
preference etc)
© 2012 Foolproof Limited 4
Contents
1. What are Personas? 2. Why inclusive Personas? 3. Extending the persona development process 4. References
6 © 2012 Foolproof Limited
There are One Billion people in the world currently currently living with a disability
Many people do not consider their condition as a disability
Why Inclusive Persona?
8 © 2012 Foolproof Limited
Disabilities can be invisible, temporary or acquired
Why Inclusive Persona?
9 © 2012 Foolproof Limited
I’m sorry but we are all going to experience disability at some point!
Why Inclusive Persona?
10 © 2012 Foolproof Limited
Contents
1. What are Personas? 2. Why Inclusive Personas? 3. Extending the persona development process 4. References
11 © 2012 Foolproof Limited
“
12 © 2012 Foolproof Limited
Inclusive Thinking + UCD
Personas = Inclusive Personas
Extending UCD Personas process
© 2012 Foolproof Limited 13
Desk-‐based research
Contextual research
Analysis
Workshop Write up personas
Hypothesis ObservaCons and findings
Behavioural segments
Skeleton personas
1. Desk-based research
Where to find data? § Customer service/support logs § Previous research § Available analytics and statistics § Disability related organisations § Standards and guidelines § Good old Web
© 2012 Foolproof Limited 14
Involve an Accessibility Expert early in the process
2. Contextual research
Research tools you could use § Home or workplace visits § Coffee shop interviews § One-to-one lab interviews § Focus groups § Co-design
How many people and who to include? § It depends…. § 6-8 from each disability group § Rule of third (e.g. 12 users + 6 with disabilities) § Different disability groups through iterations § Include those with invisible disabilities,
temporary disabilities and older people © 2012 Foolproof Limited 15
Involve users with disabilities as much as you can
2. Contextual research
Where to find them? § Employees or customers panel § Disability organisations § Specialised recruitments § Friends of friends or social media § They have already responded to your
recruitment What to gather? § Stories of themselves and friends § Adaptive/Assistive technologies and tools used
as well as their level of expertise § Condition related frustrations, barriers,
motivations and preferences
© 2012 Foolproof Limited 16
Involve users with disabilities as much as you can
3. Analysis
How to analyse § Map data to behavioural axis § Identify patterns of user groups § Prioritise disability conditions § Consider personal vs. condition specific
preference
© 2012 Foolproof Limited 17
Inclusive requirements are just better design requirements
4. Workshop
What to discuss? § Identify overlapping and conflicting behaviours § Stretch personas to a manageable number
(normally between three and seven) § Identify primary, secondary and negative
personas
© 2012 Foolproof Limited 18
Find the sweet spot between the requirements
5. Write up personas
Inclusive requirements can be in form of § Previous experiences § Future needs § Friends or family of persona § Secondary personas § Age related needs § Context specific needs § Behavioural characteristics § Preferred touch points § Preferred interaction styles
© 2012 Foolproof Limited 19
Personas don’t design, designers do
Contents
1. What are Personas? 2. Why inclusive Personas? 3. Extending the persona development process 4. References
20 © 2012 Foolproof Limited
References
Personas § AEGIS
http://www.aegis-project.eu/index.php?option=com_content&view=article&id=63&Itemid=53
§ W3C http://www.w3.org/WAI/redesign/personas
§ Just Ask http://www.uiaccess.com/accessucd/personas_eg.html
Inclusive Design § Inclusive Design Toolkit
http://www.inclusivedesigntoolkit.com/
Standards § BS 8878 Web Accessibility code of practice § Web Content Accessibility Guidelines (WCAG2) © 2012 Foolproof Limited 21
Thank you