Seven People, Seven Different Ways: Why a Map Is Not Enough
· 3 min read
In brief
A process map is not enough because it shows the steps but does not make them happen the same way twice; that requires governance. In a story John Sansbury tells, a council housing repairs contact centre had seven agents handling calls seven different ways, a full year after the process was designed, documented, trained and rolled out.
- Four artefacts bridge a map and a governed process: a RACI matrix with one and only one accountable person per activity, a swim-lane process flowchart, measurement on each step, and written procedures.
- Documented accountability is rare. In one analysis, only around 15 per cent of people in a set of departments had any documented accountability at all.
- There is only ever one process owner, accountable for policy, design and continual improvement, while managers run the process day to day. Sansbury found no process at maturity level three in one large university's IT function, because there were no process owners.
- Governance produces control, control produces consistency, and consistency is the prerequisite for optimisation. The book cites 30 per cent of revenue as the cost of putting right what should not have gone wrong. The housing centre's real failure was that the manager never went back to audit the process.
Continue reading on the Exchange
Join or sign in to read the complete article, explore the full knowledge library and record your CPD.
Founder membership is free for life
More from Ian Hughes
Available to members.
Related articles
How should the service desk handle a Microsoft 365 outage it cannot fix?
Treat a supplier cloud outage as your own major incident: log it once, tell people early on a channel that still works, update on a rhythm and review your dependency afterwards.

Deploying AI is the easy part: who runs it once it goes live?
Only a third of large enterprises have met the business case for their main AI programme. New research points to a gap in who runs AI after launch, and what leaders can do.
How do I compare help desk tool pricing before rolling it out across several departments?
Compare help desk tools on a full year's cost for your real agents, approvers and requesters in every department, not on the headline monthly price.
Turning 'not helpful' into a fix
'Not helpful' is free, honest feedback, and most of it goes nowhere. Turn that click into a fix.
When the author leaves, who owns the article?
Articles keep being read after their authors move on. Make sure the care for them does not leave too.
Test after every change, or find out from users
Knowledge changes fail quietly. A short, repeatable test after every change finds the problem before your users do.
