Recognising patterns

When did what you deliver last change because of something you learned from the people you serve?

Evolution shows up in the distance between what the people you serve actually experience and what the organisation does about it. These prompts help you see whether that distance is closing or quietly growing.

Listen for

• When people talk about what they deliver, do they talk about the people on the receiving end - or about the process of delivering it?
• When a frontline team knows something isn't working for the people they serve, what happens to that knowledge? Does it reach someone who can act on it?
• When someone suggests doing something differently, is the instinct curiosity or defensiveness? "That's interesting, tell me more" - or "we've tried that before"?
• Is the definition of "good" owned by the organisation or shaped by those it serves? Who gets to say whether the service is working?

Watch for

• When a service change is proposed, is the first question "what do the people we serve need?" or "what's feasible within our current setup?"
• Do investment decisions reference real evidence from those you serve - or are they driven by internal assumptions about what they want?
• Are there services or approaches the organisation is clearly attached to beyond their usefulness - things that persist because "that's what we do"?
• When feedback contradicts an internal assumption, which wins?

Measure

• How recently has what you deliver changed in a substantive way - not cosmetic, but meaningfully different?
• Of the changes made in the last year, how many were proactive versus reactive? Improving something working versus fixing something broken tells you very different things.
• Can you trace specific improvements back to specific insights from the people you serve? If you can't, the feedback loop may not be real.

Notice

• Is improvement continuous or episodic? A steady stream of adjustments suggests a living feedback loop. Occasional big changes suggest improvement only happens when it's forced.
• Do the people you serve feel like partners in shaping what happens next - or like recipients who occasionally get surveyed?
• How far is the person who designs the service from the person who receives it? Every layer of distance is a place where the signal can fade.

Feedback collected but never acted on is worse than no feedback at all. It teaches the people you serve that their voice doesn't matter - and teaches the organisation that listening is a box to tick.