Explore it yourself
Practical starting points for exploring service evolution - individually, in a one-to-one, or with a team.
These are starting points, not a structured programme. Use whichever feels right for where you are - individually, in a one-to-one, or with a team.
A question to sit with
When did what you deliver last change because of something you learned from the people you serve?
If the answer comes quickly, notice what made that learning possible. If it takes a while, notice what's in the way. Both tell you something important about how alive the evolution loop is.
A conversation to have
Ask three people who deliver your service directly: What do the people we serve need that we're not quite getting right yet? Don't ask for evidence or business cases. Just ask what they see. People close to service delivery carry an extraordinary amount of insight that has nowhere to go. This conversation gives it somewhere. The themes will be consistent, and they'll almost certainly point to things no survey has surfaced.
Something to observe this week
Follow a piece of feedback from the people you serve. Not a complaint - just a piece of genuine insight about their experience. Trace what happens to it. Where does it go? Who sees it? Does it reach anyone with the authority to act on it? How long does the journey take? You're not auditing the feedback system. You're seeing the distance between hearing and acting. That distance determines how quickly your service can evolve.
A useful tension to name
Think about a moment where what the people you serve were asking for and what the organisation was offering were pulling in different directions. What happened? Did the organisation adapt, or did it explain why it couldn't? And how was that experienced by the people on the other side? These tension points are where evolution either happens or stalls. How your organisation handles them tells you a great deal about whether service is genuinely evolving or just being maintained.
One thing to try
At your next team meeting, bring one real story from the people you serve. Not data - a story. Something specific that happened to someone as a result of your service. Then ask the team: What does this tell us? And is there something we could do differently? Keep it concrete. Keep it human. You're not launching a review. You're reconnecting the team to the experience their work creates - and opening the door to one small evolution.