Skip to content

Lived Experience Capture

Capture first-person lived experience so systems are not designed, evaluated, or governed only from external metrics, expert categories, or institutional assumptions.

The Diagnostic Story

Symptom: Measured compliance is high, but trust and resentment sit at opposite ends of the scale. Persistent workarounds, avoidance, and informal nonuse coexist with formal availability. Expert explanations repeatedly miss what affected people say is central, and satisfaction scores fail to explain the sharp differences visible across groups. Stakeholders feel consulted but not heard, and design changes solve visible tasks while leaving felt burden unchanged.

Pivot: Create a disciplined evidence pathway from first-person experience to decision-relevant insight. Identify whose experience matters, establish safe elicitation conditions, gather accounts in people's own terms, preserve contextual meaning through synthesis, check interpretations against participants, and translate findings into action while documenting the limits of subjective evidence.

Resolution: Design requirements become more accurate, policy and governance fit improves, and hidden harm and exclusion are reduced. Evaluation gains validity because it includes the dimension that aggregate metrics missed. The pathway is non-extractive: people's accounts contribute to accountable action rather than disappearing into a report.

Reach for this when you hear…

[product design] “The task completion rate looked great in the usability test, but every single participant mentioned feeling stupid while they completed it -- that is not a metric I had, and it matters enormously for retention.”

[public health] “The uptake numbers do not explain why the clinic in one neighborhood is empty and the one two miles away is overbooked -- I have to go talk to people and find out what the experience of walking through the door actually feels like.”

[organizational change] “We ran the engagement survey and got a 74, and then two senior people left in the same month citing the same thing the survey buried in a verbatim comment -- the number hid the signal.”

Mechanisms / Implementations

  • Co-Interpretation Workshop
  • Contextual Inquiry
  • Diary Study
  • Ethnographic Observation
  • Experience Sampling
  • Journey Map
  • Lived-Experience Panel
  • Narrative Account Collection
  • Participatory Research Session
  • Semi-Structured Interview

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

Also references 7 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

User Experience Capture · domain variant · recognized

Captures first-person experience of using, adopting, avoiding, or working around a product, service, interface, or process.

Patient Experience Capture · domain variant · recognized

Captures first-person accounts of illness, care access, treatment burden, communication, dignity, and system navigation.

Employee Experience Capture · domain variant · recognized

Captures workers' first-person experience of roles, processes, incentives, culture, workload, safety, and constraints.

Community Lived Experience Capture · governance variant · recognized

Captures community members' lived experience of a policy, institution, environment, service, risk, or exclusion pattern.

Harm Experience Capture · risk or failure variant · candidate

Captures first-person accounts of experienced harm, burden, stigma, exclusion, fear, or unsafe conditions with elevated safeguards.