Persona Spectrum

Purpose

The Persona Spectrum, developed by Microsoft's Inclusive Design team, broadens the definition of disability and context. Instead of designing for a fixed persona, the team maps how an ability gap (e.g., "can use only one arm") applies across a spectrum: permanent (amputee), temporary (broken arm), and situational (holding a baby). This reveals that inclusive design benefits far more people than traditional accessibility thinking suggests.

At a glance

How to run

1. Choose an ability dimension (3 min): Pick a human ability relevant to the product: touch, sight, hearing, speech, cognition, mobility.
2. Define the permanent persona (5 min): Describe a user with a permanent limitation in this dimension.
3. Define the temporary persona (5 min): Who experiences this limitation temporarily?
4. Define the situational persona (5 min): Who experiences it situationally due to context?
5. Quantify the spectrum (5 min): How many people fall into each category? (Microsoft provides global statistics.)
6. Design implications (7 min): How does designing for the permanent persona automatically serve the temporary and situational ones? What features or changes would help all three?

Materials needed

• Persona Spectrum template (three columns: Permanent, Temporary, Situational)
• User ability dimensions list
• Statistics on prevalence (optional but powerful)
• Markers and sticky notes

Pitfalls & common mistakes

• Focusing only on permanent disability: The whole point is to expand the lens.
• Abstract categories: Use real, named personas. "Maria, 67, with arthritis" is more compelling than "elderly user".
• No design action: The spectrum must lead to concrete design decisions.
• Treating it as a checkbox: Inclusive design is a mindset, not a compliance exercise.

Inclusion & accessibility

• Invite people with diverse abilities to contribute their perspectives.
• Use real data and stories, not assumptions about what limitations feel like.
• Provide the template in accessible formats.

Variations

• Exclusion Mapping: Identify where your current product excludes users across the spectrum.
• Multi-dimension Spectrum: Map 2–3 ability dimensions simultaneously for a richer picture.
• Journey + Spectrum: Overlay the Persona Spectrum on a customer journey map.

When NOT to use this

• When the product has no user-facing interface.
• When the team needs to solve a specific usability bug, not rethink the design approach.
• When detailed accessibility auditing (WCAG) is more appropriate than spectrum thinking.

Source & further reading

• Microsoft Inclusive Design Toolkit (inclusive.microsoft.design)
• Kat Holmes, *Mismatch: How Inclusion Shapes Design* (2018)
• W3C Web Accessibility Initiative