Every child welfare agency in the country now says it values “lived experience.” It’s in strategic plans, grant applications, conference panels. Say it enough times and it starts to sound like a value the system already has, rather than a resource it mostly still doesn’t know what to do with.
That gap is the problem. Lived experience gets invited into the room and then handed a chair with no table in front of it — asked to share a story, thanked for their courage, and sent home while the actual decisions get made by people who never have to live inside the system they’re deciding about. That’s not inclusion. It’s a photo op with a worse aftertaste.
Here’s the case for something different: lived experience isn’t a perspective to be represented. It’s diagnostic capability the system doesn’t have anywhere else — and if it isn’t built into the actual infrastructure of reform, it isn’t being used. It’s being displayed.
What lived experience actually knows that data doesn’t
Administrative data tells you what happened in aggregate. Lived experience tells you what happened at the point where policy met a real family, and why the gap between the two exists.
A caseworker’s file might show a referral was “diverted” or a case was “closed, services not needed.” Someone who lived through that process knows what actually happened in the fifteen minutes that determined the outcome — what question wasn’t asked, what form didn’t get filled out correctly, what a worker assumed because of a zip code or a tone of voice. That’s not anecdote. That’s the specific mechanism by which a policy fails or succeeds, and it’s usually invisible to the people who wrote the policy.
This matters because most reform efforts fail at implementation, not intent. Nobody drafts a bad child welfare statute on purpose. It goes wrong in the translation — in the protocol that doesn’t account for how caseworkers are actually trained, in the reporting requirement nobody built the infrastructure to fulfill, in the “structured decision making” tool that structures the decision around the wrong variables. Lived experience is the fastest, cheapest way to find that translation failure before it produces another decade of harm. Ignoring it doesn’t just cost equity. It costs effectiveness.
Where this actually breaks down
To be honest about this, rather than encouraging: most systems that claim to value lived experience are running one of a few patterns, and it’s worth naming them plainly.
Tokenism dressed as engagement. One advisory seat, one storytelling panel, one advocate quoted in the annual report — with zero mechanism for that input to change a protocol, a budget line, or a training curriculum. The advocate becomes proof the agency listens, without the agency having to act.
Extraction without infrastructure. An agency will happily take a written complaint, a policy analysis, or a working prototype from an outside advocate — and then quietly incorporate the thinking into internal work without funding, crediting, or partnering with the person who built it. This isn’t hypothetical caution; it is a documented risk for anyone doing this work independently and outside an institutional contract. Building something valuable does not, by itself, guarantee acknowledgment or the actual authority to see it through.
Credentialism as gatekeeping. Lived experience gets treated as a supplement to “real” expertise (a degree, a title, a tenure inside the agency) rather than as expertise in its own right. This shows up as advocates being asked to present findings to the very officials whose staff will later interview them for a job — and reject them, sometimes with a timeline that doesn’t add up — with no acknowledgment of the conflict.
No standing. Lived experience advocates are frequently unpaid, undercontracted, and without any formal decision rights. That’s not a moral failing on the advocate’s part to fix by working harder or being more diplomatic. It’s a structural design choice by the institution, and it will not resolve itself through good will.
None of this is an argument against doing the work. It’s an argument for doing it with clear eyes about what “valuing lived experience” costs an institution to actually mean, versus what it costs to just say.
What using it for real looks like
If an agency, legislature, or reform coalition actually wants to use lived experience rather than display it, here’s what that requires structurally — not sentimentally.
1. Put it on the payroll, not the panel. If lived experience expertise is valuable enough to ask for, it’s valuable enough to contract. Advisory seats without compensation or formal authority are a signal, not a partnership. A reform effort that wants credibility should be able to point to a paid role, a defined scope, and a deliverable — the same structure it would use for any other consultant.
2. Give it a decision point, not just a data point. Lived experience input should sit at a specific stage in the process — reviewing a draft protocol before it’s finalized, auditing a reporting requirement against what frontline staff can actually produce, stress-testing a “structured decision making” tool against real case scenarios — with actual authority to send something back for revision. If the only role is to be interviewed for a report that’s already been outlined, it’s not shaping the reform. It’s illustrating a decision made elsewhere.
3. Route it through oversight, not just partnership. Agencies are slow to self-correct, and internal engagement can quietly become internal containment. Lived experience advocacy gains real leverage when it’s also visible to people with independent oversight authority — legislators, inspectors general, committee staff — not only to the agency being asked to change. A complaint or analysis that goes only to the agency it concerns can sit in a drawer indefinitely. One that also reaches an elected office creates a record and a second party with reason to ask what happened to it.
4. Build the artifact, not just the testimony. A story is powerful, but a story is also easy to file away once the meeting ends. A working prototype, a data integrity audit, a mapped protocol gap — something concrete that exists independent of the telling — is harder to dismiss and harder to lose. Lived experience paired with a deliverable changes the conversation from “thank you for sharing” to “here’s what has to happen next.”
5. Track your own trail. Anyone doing this work independently should assume institutional memory is short and self-serving. Keep dated records of every submission, every meeting, every verbal commitment. Follow up in writing after verbal conversations, even friendly ones. This isn’t paranoia; it’s the only way to later demonstrate what was said, what was promised, and what happened instead — which matters enormously if the relationship with the institution turns adversarial, and sometimes even if it doesn’t.
6. Separate the mission from the institution. The goal is the reform, not the relationship with any single office, director, or program. An agency that stalls, appropriates the work without credit, or quietly closes the door doesn’t end the effort — it just removes one avenue. Legislative offices, oversight bodies, coalitions, and public documentation are all separate paths to the same outcome, and no single one of them owes the advocate anything just because the work is good.
The honest version of the argument
Lived experience is valuable specifically because it’s inconvenient. It surfaces the parts of a system that were never designed to be looked at directly — the gap between the protocol on paper and what happens when a real, exhausted caseworker applies it to a real, terrified family at 11pm on a Friday. Institutions that manage lived experience well get better outcomes. Institutions that manage it as a PR function get better optics and the same outcomes they already had.
There is no shortcut where an agency values lived experience without giving it authority, pays it without contracting it, or protects it without also protecting itself from being embarrassed by what it says. If a reform effort isn’t willing to build the infrastructure — payment, decision rights, oversight visibility, documentation — then it isn’t using lived experience. It’s borrowing it for the length of a meeting.
You cannot reform what was never built. And you cannot claim to have built something on lived experience if lived experience was never given the structural power to change it.
Leave a Reply