Lived experience is systems knowledge

Why It Matters

The person navigating a system every day knows things about it that no theory can capture. This knowing is not raw material waiting to be analyzed by experts. It is already analysis—partial, situated, and legitimate. The host's role is not just to collect these accounts, but to treat them as authoritative. To lift them up. To let them shape what comes next.

This means noticing whose testimony actually influences decisions—and whose gets gathered but never used. It means resisting the habit of translating lived experience into "data" that professionals then interpret. It means asking: Are we treating this as knowledge, or as illustration?

What This Looks Like

The Red Teapot Collective positions community members experiencing the opioid crisis as holders of wisdom–not as research subjects.  Mothers raising children who lost parents to overdose understand intergenerational trauma, policy failure, and community resilience in ways no external expert can capture. Rather than "gathering data" from communities to be interpreted by professionals, the work treats these accounts as already-complete analysis. Stories aren't raw material—they're authoritative knowledge that shapes the work.

Try This

Audit your process: Where does lived experience enter? At the beginning, shaping direction? In the middle, informing analysis? Or at the end, illustrating conclusions already reached? Move it earlier. Let it lead.

  • Pitfalls and Mitigations (particularly "Trauma Exploitation" and "Missing Power Analysis")

Watch For

Using phrases like "powerful story" or "compelling narrative" in ways that reduce lived experience to emotional appeal rather than recognizing its analytic value. Also watch for processes that collect many stories but only let a few "representative" ones shape outcomes.