Think about the last time something in your organisation quietly didn't work. Not a crisis, just a task that was slower than it should have been, or a responsibility that sat awkwardly, or a piece of work that somehow ended up with the same person every time. Nobody complained. It got done. But something felt slightly off.
In most organisations, that feeling points to a process that was never actually designed. It evolved. Someone did something once, it worked, and it became the way things are done. Now it's infrastructure, and nobody's quite sure who's responsible for it.
Purpose-led organisations are full of committed, conscientious people. That's often exactly the problem. When a process has a gap, when the bookings don't get managed, the handover doesn't happen, the follow-up falls through, someone fills it. Usually the person who cares most, or the one who's least able to say no.
The work gets done. The gap stays invisible. And the person filling it carries an unofficial role that appears on nobody's job description and in nobody's supervision.
This isn't a staffing problem. It's a design problem. The process is making a decision about who carries the load. It just hasn't been made consciously.
The Process lens asks a different question about the work your organisation does. Not "is the process documented?" but "who ends up carrying what, and was that a conscious choice?"
That reframe matters because it moves the conversation away from individual performance and towards structural conditions. When something goes wrong, the instinctive response is to look for the person who dropped the ball. But if the system was set up in a way that made dropping the ball almost inevitable, holding an individual accountable doesn't fix anything. It just makes the next person more anxious.
When organisations start looking at their processes through this lens, several things shift:
- Hidden load becomes visible: you can see who's carrying what, and decide whether that's intentional
- Reviews become more honest: you're asking what the work actually requires, not defending what's already documented
- Succession becomes less fragile: when processes have named owners, handovers are planned rather than panicked
- Burnout signals become earlier: intolerable demands stop being personal failures and start being data about system design
The process is always making a decision. The question is whether you're making it too.
If you're thinking about AI adoption and want to understand your governance readiness first, our AI Governance Diagnostic is a good place to start: https://www.jannaways.co.uk/ai-governance-diagnostic
Continue reading...click the button below to read the full version.