We Have a Policy Problem, Not a People Problem
We Have a Policy Problem, Not a People Problem
A non-fiction record on what happens when systems follow rules perfectly—and still fail
If a system needs more policy to fix a problem it created with policy,
you don’t have a staffing issue.
You have an obsession.
Context
This is not a complaint.
This is not performance.
This is a record.
We are told, repeatedly, that systems are improving.
More guidance.
More frameworks.
More procedures.
More layers.
On paper, it looks like progress.
In reality, it often looks like this:
- no reply
- no clarity
- no ownership
- no movement
And yet somehow, everything is still “within policy.”
The Pattern
Here is the uncomfortable truth.
Systems are not short on policy.
They are drowning in it.
Every problem gets the same solution:
write another rule
create another pathway
define another boundary
And what happens?
Responsibility doesn’t increase.
It gets diluted.
Passed.
Redirected.
Packaged neatly and sent somewhere else like a parcel nobody wants to sign for.
Personal Truth
I’ve seen this up close.
You send correspondence.
Nothing.
You follow up.
Still nothing.
You escalate.
You’re told:
- it’s judicial
- it’s out of time
- it’s not specific enough
- it’s not within remit
At no point does anyone say:
“Right. That’s ours. We’ll sort it.”
That’s the issue.
Not one person taking ownership.
But a system perfectly designed to avoid it.
The Kitchen Test
Let’s bring this back to reality.
If I ran a kitchen like that:
- orders ignored
- no acknowledgement
- plates delayed
- no one responsible
And then I said:
“Don’t worry, we’re fully compliant with kitchen policy”
I’d be shut by the end of the night.
No debate.
Because in the real world:
Outcome beats policy. Every time.
The Buck Passing Machine
Here’s how it actually works:
- You raise an issue
- It’s assessed against policy
- It’s redirected
- It’s narrowed
- It’s delayed
- It disappears
And if you push?
You get a better-worded version of:
“Not our department.”
That’s not governance.
That’s organised buck passing.
The Real Risk
Let’s call it properly.
When systems become obsessed with policy:
- clarity drops
- accountability blurs
- people get lost
- outcomes stall
And the most dangerous part?
Everything still looks correct on paper.
That’s how failure hides.
Not through chaos.
Through structure.
The Gap (Because It’s Always There)
This is where people end up:
Not ignored.
Not resolved.
Held.
In process.
In review.
In limbo.
That’s The Gap.
And policy doesn’t close it.
In many cases, it builds it.
Wider Lesson
You cannot fix structural failure with more structure.
You fix it by:
- owning decisions
- simplifying communication
- making responsibility visible
- measuring outcomes, not wording
Anything else is just rearranging paperwork.
Mindspire Position
Mindspire is not therapy.
It is not diagnosis.
It is not legal advice.
It is a non-clinical lived-experience platform.
It records what actually happens.
Not what policy says should happen.
Because when there is a gap between the two:
That gap matters.
And it needs to be seen.
The Clear Takeaway
The clear takeaway is this:
If you are inside a system:
- do not rely on it to track your case for you
- keep your own record
- document everything
- follow up clearly and consistently
And if something feels wrong:
Say it.
Early.
If you are struggling:
Speak to your GP, NHS 111, emergency services, or someone you trust.
Do not sit in silence while a system hides behind process.
Ending
Policies are meant to guide action.
Not replace it.
If the system needs ten policies to avoid one decision,
the problem is not complexity.
It’s avoidance.
And once you see that, you cannot unsee it.
Operation Buzzard
What it is:
Operation Buzzard is a non-clinical observation framework that records lived experience as structured evidence — not opinion, not therapy, not noise.
What it does:
It tracks where systems break down at the joins:
handovers
delays
resets of responsibility
“in progress” with no movement
How it works:
Like a buzzard overhead — it doesn’t interfere, it observes patterns over time:
logs events chronologically
fixes them to evidence
maps cause → effect
identifies repeatable failure patterns
Standard applied:
HACCP-style thinking:
identify risk points
monitor control failures
record deviations
build a clean audit trail
Core position:
This isn’t about blaming people.
It’s about exposing structural misalignment.
Why it matters:
Because systems rarely fail loudly.
They drift quietly — and the record proves it.
Michael P. Lennon Jr
Mindspire | Where Lived Experience Finds Its Voice in Mental Health
HMW-AI-LIC-1984-NC-GOV
#Mindspire #TheGap #OperationBuzzard #MH84
Comments