Lived experience is frequently invited into organisations as a story.
Someone stands at the front of a room and describes their life. They explain what happened, how it felt and what they learned. The audience listens. Some people are moved. Others are challenged. The feedback forms describe the session as powerful, authentic or thought-provoking.
Then everybody returns to work.
The policy remains unchanged. The manager facing a real situation is no better equipped. Nobody has been given responsibility for acting on what was heard, and the organisation has no way of knowing whether the experience influenced a single subsequent decision.
That is the central problem.
Hearing a story is an activity. It is not an outcome.
Lived experience earns its place in organisational decision-making not simply because it is personal or emotionally compelling, but because it can reveal the consequences of systems that policies, dashboards and formal complaints often fail to show.
It is evidence of impact.
But evidence is only useful when somebody is prepared to do something with it.
The hum a policy cannot hear
For much of my life, I misunderstood my own experience.
Not through dishonesty, but because I did not have the language to describe it.
As a transgender woman, I spent years knowing that something within me was different without having the words, examples or visible possibilities that might have helped me understand it. What followed was confusion, denial, doubt and a persistent feeling that I might somehow be an imposter in my own life.
I learned to mask, cover and carry on.
There was not always one dramatic event I could point towards. It was more like a quiet hum in the background: the awareness that something could be discovered, that I might be judged or shamed, and that every conversation required a calculation about how much of myself it was safe to reveal.
My formative adult years were spent in the Royal Air Force during an era in which LGBT people could not serve openly without risk to their careers. The culture did not need to confront me personally every day. The surrounding rules and assumptions had already communicated what was expected.
Repression became ordinary.
That is one of the things lived experience can reveal: harm is not always a single reportable incident.
Sometimes it is the cumulative cost of vigilance.
It is the energy spent reading a room, editing a sentence, anticipating a reaction or deciding not to ask for something that should have been available. It is the opportunity never pursued, the support never requested and the concern never formally reported because the person has already concluded that disclosure is unsafe.
Most organisational systems are poor at detecting that quiet hum.
They tend to count what becomes visible: complaints, grievances, absence, attrition, tribunal claims or employee survey responses. By the time those measures show a pattern, people may have been carrying its effects for years.
The gap between intention and experience
A policy describes what an organisation intends to happen.
Lived experience can help establish what is actually happening.
Those two things are not necessarily the same.
An organisation may have an inclusion policy, a reporting procedure and a statement about dignity at work. None of those documents proves that an employee trusts the process enough to use it.
A training programme may have reached every manager. That does not prove that a manager can handle a disclosure conversation respectfully, recognise when a decision requires escalation or apply the policy consistently under pressure.
A staff survey may report no serious concerns. That does not prove there are none. It may instead mean that the people most affected do not believe speaking will improve anything.
This does not make formal evidence irrelevant. Policy, law, operational data and properly designed research all matter.
But each has a boundary.
Lived experience can illuminate what sits outside that boundary: the informal culture around the procedure, the behaviour people have normalised, the workarounds required to make a system function and the human cost created by apparently neutral decisions.
It closes part of the distance between institutional intention and individual impact.
That makes it organisational intelligence—not an optional emotional addition once the supposedly serious evidence has been considered.
When the story becomes the product
There is a particular risk when organisations engage people primarily to tell their stories.
The person sharing may revisit painful, intimate or complicated experiences. They may be expected to answer highly personal questions, remain calm when challenged and somehow represent an entire community whose experiences are far from uniform.
The organisation receives an engaging event.
The storyteller carries the emotional labour.
When no practical action follows, lived experience has been consumed rather than used.
The audience may leave saying:
That was moving.
I learned a great deal.
What an inspirational person.
Those reactions are not worthless, but they are not evidence of change.
The relevant questions are harder:
- Which assumption was challenged?
- Which decision will now be made differently?
- What does a manager know how to do that they could not do before?
- Who owns the next action?
- How will the organisation establish whether the action improved people’s experience?
Without those questions, the story itself becomes the outcome.
It creates a memorable hour without altering the conditions the speaker described.
Respectful engagement therefore begins before the person is invited to speak. The organisation should know why it is seeking lived experience, which decisions it may inform and what will happen after it has been heard.
People should not be required to expose their pain merely to make a subject feel real to someone else.
Evidence, not a trump card
Treating lived experience seriously does not mean treating every individual account as complete, universally representative or beyond examination.
No single trans person speaks for all trans people.
My experience is shaped by my age, background, career, relationships and the period in which I grew up. Another transgender person may have encountered an entirely different world and reached different conclusions.
Experiences can also conflict.
One employee may describe a process as affirming; another may experience the same process as intrusive. One person may welcome visible public support; another may consider it unwanted attention. Neither account can simply cancel the other.
The correct response is not to discard lived experience because it is subjective.
It is to use it with discipline.
That means:
- listening to more than one voice;
- seeking experiences from people with different identities, roles and circumstances;
- testing individual accounts against wider patterns and operational evidence;
- distinguishing impact from assumed cause;
- considering current law, policy and organisational duties alongside personal testimony;
- and resisting the temptation to select only the voices that confirm the organisation’s preferred position.
Lived experience is not the entire evidence base.
It is part of the evidence base—and excluding it leaves the analysis incomplete.
From testimony to action
The practical value of lived experience lies in the route from hearing to doing.
That route has four stages.
1. Develop the drive
The first step is not expertise. It is willingness.
Someone has to decide that the experience matters enough to explore rather than defend against. That means resisting the urge to explain why the policy was well intentioned, why the situation was difficult or why the person may have misunderstood what was supposed to happen.
Curiosity comes before correction.
The useful initial response is:
What does this tell us that we did not previously understand?
2. Build the knowledge
One account can identify a question. It should then lead to further examination.
Are other people encountering something similar? Does the experience align with complaints, exit interviews, absence data, engagement findings or informal feedback? What does current law require? What does the organisation’s policy say should have happened? Where did actual practice diverge?
The aim is not to prove or disprove the person’s humanity.
It is to understand the system around their experience.
3. Form a strategy
Knowledge without application leaves an organisation informed but unchanged.
The next step is to identify the decision, behaviour or process that needs attention.
That might involve manager guidance, a reporting mechanism, onboarding, facilities, data handling, language, escalation routes or the way consultation itself is conducted.
A strategy should identify:
- the issue revealed;
- the evidence that will be considered;
- the person accountable for responding;
- the options available;
- the action selected;
- and the point at which its impact will be reviewed.
This converts a story into a structured organisational response.
4. Take action
Action is where confidence becomes competence.
It is where a passive ally becomes an active one, where a listener becomes a participant and where an organisation demonstrates that consultation was not simply theatre.
Action does not require every person to achieve perfect understanding or agreement.
It requires them to be capable of making a better decision, holding a more competent conversation, challenging harmful behaviour or escalating something they are not equipped to resolve alone.
The standard is not whether everybody felt comfortable.
The standard is whether the organisation is now better able to act.
The test is what changed
Lived experience should create an empathy bridge between people.
It allows someone to connect another person’s reality with their own understanding of fear, dignity, safety, uncertainty or belonging. That human connection matters, particularly in a climate where public discussion is routinely reduced to opposing positions and demands that one side defeat the other.
We do not always need to meet around a table to establish who is right and who is wrong.
Sometimes we need to meet in order to see the human being sitting opposite us.
But humanity cannot stop at sentiment.
After hearing somebody’s lived experience, ask:
What will we do differently?
Whose experience have we overlooked because it did not fit our existing understanding?
What conversation have we been avoiding?
Which process looks adequate on paper but feels very different to the people required to use it?
What is one decision we can improve now—and who will be accountable for doing it?
If there is no answer, the organisation may have listened, but it has not yet learned.
Lived experience does not create change on its own.
People do.
And the evidence that you listened is not what you say afterwards.
It is what you do next.