In the last ten years, I've been in hundreds of boardrooms. I've seen strategy maps, balanced scorecards, OKR dashboards, and SWOT analyses pinned to walls in every combination. I've almost never seen a process map. This is a mistake.
Process maps are treated as an operational artefact — something the efficiency team produces and the operations director files away. The board sees the outcomes (cost ratios, cycle times, error rates) but not the mechanism. This creates a peculiar situation in which the people with the most power to change an organisation have the least direct view of how it actually works.
What executives see and what they don't
Senior leaders typically receive dashboards: red, amber, green. The dashboard tells them that the loan-processing time is 14 days. It does not tell them why — that five of those days are a credit committee that meets only on Tuesdays, and three of them are waiting for a physical signature that could be digital.
A process map tells them why. It is, in that sense, a different category of information — not a metric but a mechanism. And mechanism is what you need when you want to change something rather than simply monitor it.
A metric tells you what is happening. A process map tells you what to do about it.
The objection: too much detail for the boardroom
The standard objection is that process maps are too detailed for senior audiences — that a 40-swim-lane Visio diagram causes eyes to glaze over. This is correct, and it is also a reason to make better process maps, not to abandon them.
The process maps that belong in boardrooms are not the same as the ones that belong in operations manuals. A boardroom process map has three properties: it covers the entire value chain at one level of abstraction; it annotates where decisions happen and who makes them; and it marks where time and money are consumed disproportionately. A good one fits on a single slide. A bad one contains every sub-step and exception path.
Process maps as a diagnostic instrument
We typically use process maps in two ways with leadership teams. The first is at the start of a programme, when we walk the executive team through the current state. The usual reaction when the map goes up is: "I didn't know it worked like that." Not because the operations team was hiding anything — but because nobody had ever put it on a wall in front of them before.
The second use is as a decision-making tool in redesign. When you're deciding whether to add a new product or service, the question "what process does this require, and what does that process cost?" is answered much faster by a current-state map than by a gap analysis document.
We build process maps by observing, not by interviewing. Interviews produce the process as people think it works. Observation produces the process as it actually works. The gap between the two is usually where the cost is.
Process maps as change instruments
The most underused application of process maps is in change management. When you're restructuring a function, the question your staff want answered is: "how does my job change?" An updated process map answers that question precisely, in a way that a PowerPoint deck about transformation strategy does not.
We've found that organisations which present the before-and-after process maps to affected staff (not just the rationale for change) see meaningfully higher adoption rates. The staff can see concretely what their role looks like, what disappears, and what is new. Ambiguity is the enemy of adoption — the process map is its remedy.
One thing to avoid
A process map is a description of how work is done, not a prescription of how it should feel. The most common error we see is organisations that produce elaborate process maps at the end of a transformation, as documentation, and then file them. Eighteen months later, the process has drifted and the map is wrong.
The organisations that get sustained value from process maps treat them as living documents — updated quarterly, owned by a named individual, and referenced in leadership meetings when performance metrics move. That sounds simple. It is. Very few organisations do it.
Drawn from operations improvement work across financial services, manufacturing, and public sector in East Africa, 2019–2026.