no-code
Glossary ↗Process Mapping
Process mapping is writing down how work actually gets done before you automate any of it: the steps, who performs each one, what triggers them, what information moves between them, and where the work waits. It is the least fashionable part of any automation project and the one whose absence explains most of the disappointing ones. The reason it matters is that the documented process and the real process are rarely the same. The version in the handbook describes the intended path; the real one contains the spreadsheet somebody maintains privately, the exception that a senior colleague handles by messaging a supplier directly, the approval that is granted verbally and recorded later, and the step everyone skips because it stopped being necessary two years ago. Automating the documented version produces a system that works on the cases that were never the problem. A useful map records a few unglamorous things per step: what starts it, what decision is being made, what the person needs in front of them to make it, what happens when the answer is unusual, and how long the step waits before someone picks it up. Exception paths deserve more attention than the happy path, because they are where the time goes and where automation most often fails. Mapping also does the sorting an AI project needs. It separates the steps that are deterministic rules — which should be code, not a model — from the steps that need judgement over unstructured input, which is the narrow place a model genuinely earns its cost. Teams that skip this reach for a model for the whole process and end up with something expensive and unpredictable where a set of conditions would have done. The most common finding is that the process should change rather than be automated. Queues that exist because two systems do not talk, approvals nobody can justify, rework caused by a form that asks the wrong question — automating these preserves them at higher speed and makes them harder to remove afterwards, because now there is an integration built on top.
Related terms