Welcome back to our ongoing series that explores how Agile practices and Accessibility principles converge to create products and systems that serve everyone. So far, we’ve explored foundational definitions, inclusive story writing, and accessibility testing in CI.
Today’s focus? A tool Agile teams often rely on, but rarely challenge: personas.
What Are Personas in Agile?
In Agile and user-centered design, personas are fictional but research-informed representations of your users. They help teams visualize needs, constraints, and goals in a relatable way.
Typical personas might include:
- A tech-savvy millennial using mobile apps
- A small business owner tracking inventory
- A busy parent shopping on-the-go
These personas help humanize development priorities, but they often miss access needs, systemic barriers, and overlooked perspectives.
Why Inclusive Personas Matter
When personas don’t reflect users with disabilities, teams risk designing products that exclude by default.
Inclusive personas go beyond demographics:
- They reflect differences in how users interact with products
- They highlight barriers caused by design choices
- They promote empathy, not just efficiency
- They elevate equity as a design outcome
Instead of assuming typical use, inclusive personas ask: “What if this user interacts differently?”
How to Create Inclusive Personas
Here’s a framework Agile teams can follow:
1. Include Diverse Abilities
Go beyond visual or auditory disabilities, include cognitive, motor, and situational constraints.
Example: Anna, 27, graphic designer with ADHD Needs: Clear navigation, focus-friendly interface, consistent structure
Example: Jenny, 52, warehouse manager who lost vision Needs: Screen reader compatibility, alt-text on images, keyboard navigation
2. Contextualize Use Cases
Design personas based on scenarios users encounter:
- Noisy environments (caption reliance)
- Glare on screens outdoors (contrast needs)
- Time-sensitive actions (simplified flows)
- High emotion moments (clear feedback)
3. Co-create with Real Users
Whenever possible, build personas with input from individuals with lived experience. This avoids tokenism and strengthens usability insights.
Invite feedback, use interviews, leverage advocacy networks.
4. Integrate Personas into Agile Rituals
- Use inclusive personas during backlog refinement
- Reference them in story writing and testing scenarios
- Include accessibility criteria that reflect persona needs
- Track which personas are supported, and which are underserved
Persona-Driven Empathy Leads to Equitable Design
Personas aren’t just planning tools, they’re storytelling tools. And stories shape outcomes.
Inclusive personas invite teams to imagine beyond default users. They help you design features that remove friction and empower everyone, not just the majority.
So ask your team today: Whose story are we not telling yet, and how can we make space for it?
Next up in the series: Measuring Accessibility as a Team KPI We’ll discuss how Agile teams can hold themselves accountable using metrics that track impact, not just compliance.
See you in the next episode Want help building inclusive persona templates or workshop kits? I’d be glad to create some!
