Personas in Agile: AI-enabled Qualitative Research

Personas can be integrated into Agile sprints if treated as living, lightweight artifacts tied to measurable outcomes, according to the Interaction Design Foundation.

• The Interaction Design Foundation article published on August 8, 2025 warns that Agile teams running two-week sprints often sideline persona research unless personas are built as minimal, versioned artifacts.
• Alan Cooper's advice quoted in the article on August 8, 2025 recommends front-loading foundational research: "Long before Day Zero, when features and interface are on the table, bigger questions need to be answered about who, exactly, is the user, and what, exactly, will make him happy."
• The UK Government Digital Service case study published on December 5, 2017 shows embedding researchers and using collaborative workshops produced faster insight delivery and actionable backlog items in sprints.

The Interaction Design Foundation article published on August 8, 2025 documents why personas are forgotten in fast Agile cycles and prescribes specific fixes: minimal viable personas, cross-functional research, living documents, and sprint-tied visibility.

The Interaction Design Foundation identifies the core problem as schedule pressure: many teams operate in two-week sprints and treat persona research as a months-long, one-off activity, which creates a mismatch between research cadence and delivery cadence.

The Interaction Design Foundation recommends three concrete remedies: (1) create minimal viable personas that emphasize needs and scenarios over demographics, (2) involve engineers and stakeholders early in interviews and synthesis, and (3) version-control personas and review them after each sprint to keep them current.

Treating personas as living documents changes team decisions and priorities, according to the Interaction Design Foundation.

• Decision: Create minimal viable personas before your first sprint, per the Interaction Design Foundation recommendation on August 8, 2025; implication: faster sprint planning and clearer acceptance criteria.
• Decision: Embed researchers in cross-functional teams, as shown in the UK Government Digital Service case study on December 5, 2017; implication: research insights become actionable backlog items rather than slide decks.
• Decision: Make personas visible in tickets, standups, and demos, following the Interaction Design Foundation guidance; implication: measure persona mentions and feature usage each quarter to keep artifacts relevant.

Personas can thrive in Agile when teams make them minimal, visible, versioned, and tied to sprint outcomes, as argued by the Interaction Design Foundation on August 8, 2025 and demonstrated by the UK Government Digital Service case study from December 5, 2017.

Start by creating one minimal viable persona, embedding a researcher in your team for one sprint, and measuring persona mentions in tickets over the next quarter.

If you want to accelerate persona creation and keep them current across sprints, try Evidano to transcribe, code, and generate persona stories that attach directly to your backlog items; learn more on our features page.

Get hands-on: Try Evidano for free.