Description
Model the distinct relationships users have with a system as roles, map how roles relate, rank them and choose focal roles to design for.
User role modelling is Constantine and Lockwood's usage-centred alternative to personas. It starts from all actors, separates system actors from user actors, splits user actors into direct and indirect, and identifies each role a direct actor can play, naming it by its core responsibility. Each role is described by context, characteristics and criteria, often on one index card, and described by difference from other roles. A context map shows roles around the system, and for complex systems a role map records specialisation, inclusion and precedence. Roles are ranked by frequency and business importance to choose focal roles, and personas may then be written for focal roles only. Roles also guide architecture, since parts serving one role cluster together. Its strength is coverage and traceability rather than empathy.
Attributes
- Discipline
- Task Analysis & Cognitive Modelling
- Loss type
- Siloed
- Stage
- Discovery, Definition
- Data
- Analytical / expert
- Effort
- Days
Steps
- List all actors and separate system actors from user actors.
- Split user actors into direct and indirect users.
- Identify every role a direct actor can play and name each by its core responsibility.
- Describe each role on a card by context, characteristics and criteria, emphasising how it differs from others.
- Draw a context map, and for complex systems a role map with specialisation, inclusion and precedence.
- Rank roles by frequency and business importance and select focal roles.
- Optionally write personas for focal roles only and use role clusters to organise the architecture.
Sources
- The Persona Lifecycle (Pruitt & Adlin, 2006)
Also known as
- User role modelling (usage-centred design)
- Role model
- User roles
- Role map
Categories
- User Research
- Task Analysis & Cognitive Modelling