Two programmes

If you want to understand how a programme works, read the service specification.

If you want to understand how the programme feels, ask the person receiving it.

They may not talk about the Theory of Change, the intervention model or the intended sequence of programme components.

They may tell you that they had to explain their story three times.

That somebody called when they said they would.

That the first appointment felt like an assessment rather than a conversation.

That one practitioner remembered the name of their daughter.

That another appeared to be reading questions from a screen.

That the group was described as welcoming, but nobody contacted them after they stopped attending.

These details can appear small when viewed from a performance dashboard. But they are often the places where the programme becomes real.

Participants experience our programmes through moments: how they are welcomed, how decisions are explained, how reliably people respond, how safe it feels to tell the truth and what happens when they struggle to engage.

An organisation may believe it delivers one consistent programme while participants are encountering very different versions of it.

Quality improvement therefore requires more than asking whether people were satisfied.

We need to understand the experience beneath the score.

What did participants believe the programme was trying to help them achieve?

Which parts made change possible?

Where did the pathway become confusing, impersonal or difficult to access?

The programme described in our documents matters.

But the programme people experience matters more.