Why the same problems keep coming back when staff ask to work flexibly. It carries on from the service map: every part rests on its boxes and stories. Start with what the map is and where it comes from. Then walk through it, see where each part sits on the journey, see what pushes most, try a change, see who’s connected, or open the whole thing. Every link is a hypothesis for Brightwater’s people to correct.
Brightwater is a made-up trust: every part, link and quote here is invented for this demo.When something goes wrong, the natural fix is to patch that step: chase the email, type it in again, add a line to the policy. Often the problem comes back, or moves somewhere else. That is because the steps are connected. What happens in one place pushes on another, and some of those pushes come back round to where they started.
“I spent a morning emailing round to find out what others had done.”
An HR adviser, notes, day 4
A systems map draws those connections. It shows why a pattern repeats, so leaders can choose together where a change would shift it, rather than patch one more step.
Things there can be more or less of. Not people, and not steps: “Heads deciding alone”, “Reasons written down”.
One part pushes another. + they move together: more typing by hand, more mistakes. − they move opposite ways: more admin for HR, less HR time to advise. Read each arrow as “because…, so…”.
Follow the arrows and some come back to where they started. Barrier loops make a problem worse each time round. Enabler loops make something good grow. Checks hold things steady for a while, often a quick fix that works at first.
The quotes are people’s own words, from the stories and notes on the service map. The parts, arrows and loops are our reading of them (Blended AI): a first draft for Brightwater’s people to correct.
It follows a simple sequence: people’s own experience first, then a service map, then a systems map, then choosing together where to act, and trying it small.
The service map shows one service, stage by stage: a request to work flexibly, from asking to looking back. We matched each of its boxes to the parts of this map. The matching is ours, for you to check. When the service map changes, we match it again.
One service, in order, on paper and in practice. It shows where it hurts, stage by stage.
Why what hurts keeps coming back, across the whole journey. It shows where to act.
The people behind the patterns: who turned to whom in the stories, who everything goes through, and which conversations people wished had happened.
The service map follows a request through seven stages, from asking to looking back. Here is where each part of the systems map sits on that journey, and which loops pass through each stage.
Click a stage to light its parts and loops. Click a part on the map to open it in the whole map, with where it comes from.
Each dot is a part of the system. The further up, the more it pushes the rest of the system; the further right, the more the rest pushes it. Click a dot to see what it pushes and what pushes it.
Pick a part and push it up or down. The ripple follows the arrows, three steps out, and shows where the change helps, where it hurts, and where it pulls both ways.
The systems map is about patterns, not people. This view shows the people behind them: who turned to whom in the sixteen stories, who everything goes through, who is on the edge, and which conversations people wished had happened. Roles, never names.
Our reading of where a small change could weaken several barrier loops at once, or feed an enabler. Click one to see it on the map.