Professional Business Analysts / Writing it down

Process maps are for arguments, not archives

Their value is produced while drawing them, and mostly spent.

A process map earns its cost in the room where it is drawn, when two people who have worked adjacently for years discover they believe different things about what happens between them. That discovery is the deliverable. The resulting diagram is a record of a conversation and it begins going out of date immediately.

Treating the diagram as the asset leads to the familiar outcome: an elaborate repository of maps, maintained by somebody, consulted by nobody, describing an operation as it was during a project two years ago. The maintenance cost is real and the return is close to zero, because anybody who needs to know how the process works asks a person.

The practical position is to draw them freely, keep them rough, and keep only the ones that answer a live question. A map that exists to support a decision has a lifespan tied to that decision. One that exists because a methodology lists it as an artefact has no natural end and will be maintained forever.

Where a durable record genuinely is needed, usually for a regulated process or a handover, that is a different artefact with a different level of rigour, and it should be identified as such rather than being every map by default.

There is a further use for a map that justifies keeping some of them, which is handover to whoever operates the process afterwards. A person joining a team needs to know how the work flows in a way that no amount of watching individual tasks conveys quickly, and a single clear diagram does that better than prose. That is a different artefact from the analysis map, drawn to a different standard, and it is worth producing deliberately rather than hoping a working sketch will serve.