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.”
When This Archetype Applies¶
Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.
Diagnostic problem
A system, policy, product, process, or evaluation is being designed or judged through external indicators, expert abstractions, institutional categories, or aggregate metrics while the lived experience of affected people remains invisible, distorted, unsafe to express, or disconnected from decisions.
What this problem means
The structural problem is an evidence asymmetry between external observation and first-person experience. A dashboard may show completion rate, but not dread. A policy file may show eligibility, but not the fear of applying. A workflow may show that a tool is available, but not that using it creates surveillance risk or hidden coordination work. An expert schema may classify a case correctly from the institution's perspective while misdescribing what the person is actually living through.
This asymmetry matters because decisions based only on the external view can optimize the wrong thing. A service can become faster but less dignified. A model can become more accurate but harder to contest. A classroom can improve average performance while leaving a subgroup feeling excluded or unsafe. Lived Experience Capture interrupts that failure by making the experienced reality inspectable before action is taken.
Show the applicability expression
Applicability expression5 distinct conditions
groundedpartly groundedopen
Equivalent to the 4 condition sets it replaces, with 2 duplicate condition cards removed.
4At least one of theselettered A–E
Any one of these groups completes the pattern; conditions inside a group are required together.
Irreducible lived experience · grounded
The target includes experience-as-experienced whose structure is not recoverable from external outcome metrics alone.
The source archetype describes the situation as follows: External metrics show what happened but not how people experienced it. The normalized requirement above isolates the load-bearing portion used in this condition set.
Participant-category divergence · grounded
Expert or institutional categories diverge from participants' own sense-making categories.
The source archetype describes the situation as follows: Expert categories or institutional vocabulary do not match how people make sense of their own situation. The normalized requirement above isolates the load-bearing portion used in this condition set.
Irreducible lived experience · also required in this branch
Same condition as A above — stated once.
Unheard affected people · grounded
People affected by a design or policy were not meaningfully heard during its creation or evaluation.
The source archetype describes the situation as follows: A design or policy affects people who were not meaningfully heard during design, evaluation, or revision. The normalized requirement above isolates the load-bearing portion used in this condition set.
Irreducible lived experience · also required in this branch
Same condition as A above — stated once.
Unknown experienced cause · open
Complaints, churn, avoidance, nonuse, attrition, or workarounds reveal a problem whose experienced cause remains unknown.
The source archetype describes the situation as follows: A problem is known through complaints, churn, avoidance, nonuse, attrition, or informal workarounds, but the experienced cause is unclear. The normalized requirement above isolates the load-bearing portion used in this condition set.
First-third person distinction · grounded
Decision-makers must distinguish first-person experience from third-person observation of the same phenomenon.
The source archetype describes the situation as follows: Decision-makers risk confusing observation from the outside with experience from the inside. The normalized requirement above isolates the load-bearing portion used in this condition set.
Other requirements and context (1)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Supporting contextThe stakes include harm, exclusion, stigma, dignity, trust, access, or safety.
Coverage
4 of 5 conditions grounded · 1 open.
None of the 1 open conditions sit in the shared core — each falls inside one alternative branch, so grounding any one of them closes only that branch.
Mechanisms / Implementations¶
- Co-Interpretation Workshop
- Contextual Inquiry: Studies users in the actual setting where the work happens — watching and asking at the same time — so the situated constraints and workarounds that never surface in a lab become visible.
- Diary Study: Has users log their own experience in the moment, repeatedly over days or weeks, so recurring friction and delayed consequences that no single session can reach come into view.
- Ethnographic Observation: Embeds a researcher in the setting for a prolonged stretch, reading lived practice against the material and social conditions around it, so meaning is inferred from how life is actually conducted rather than from what people say about it.
- Experience Sampling: Pings people at signal-contingent moments across days to capture their state right then, building a picture of how experience varies across moments, contexts, and moods rather than what it averages to.
- Journey Map: Lays a user's end-to-end path out as a single picture — touchpoints, handoffs, delays, and emotional lows — so scattered findings become a prioritized map of where the design fails.
- Lived-Experience Panel
- Narrative Account Collection: Invites people to tell the whole of what happened as a story, in their own sequence and words, and preserves that account intact rather than breaking it into answers to the researcher's questions.
- Participatory Research Session: Brings experience holders into the room as co-analysts, not just sources — they help interpret the accounts, decide what the findings mean, and shape the action, so authority over meaning is shared.
- Semi-Structured Interview: Runs a one-on-one conversation from a prepared guide of open questions, covering the decision-relevant ground while leaving room to follow the unexpected — with a deliberate choice of whom to talk to.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (1)
- Phenomenology: Study of subjective experience.
Also references 7 related abstractions
- Boundary: Defines system limits.
- Epistemic Justice: Fair knowledge production.
- Feedback: Outputs influence inputs.
- Observability: Infer internal state externally.
- Representation: Model complex ideas.
- Sociotechnical Systems: Social + technical interaction.
- Stakeholder Analysis: Identify involved parties.
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.
Editorial Notes¶
Problem Classification¶
Classification: Exclusion, Inequality & Distributional Harm → Epistemic Voice & Stakeholder Exclusion
Problem kernel: external abstractions exclude situated lived experience
Rationale: Earliest causal condition: A system, policy, product, process, or evaluation is being designed or judged through external indicators, expert abstractions, institutional categories, or aggregate metrics while the lived experience of affected people remains invisible, distorted, unsafe to express, or disconnected from decisions.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A system, policy, product, process, or evaluation is being designed or judged through external indicators, expert abstractions, institutional categories, or aggregate metrics while the lived experience of affected people remains invisible, distorted, unsafe to express, or disconnected from decisions. That is a epistemic voice and stakeholder exclusion problem because A decision or knowledge surface omits affected parties, situated evidence, or filtered-out perspectives and then mistakes the surviving inputs for reality.
Review outcome: Independent reviewer agreement; high confidence.