Why process mapping should happen before you choose any software
There is a sequence that produces good technology implementations, and it is not the sequence most organisations follow. The common approach is to identify a technology, select a vendor, and then figure out how to make the existing process fit the new system. The sequence that works is the reverse: map the existing process in detail, identify where it breaks down, redesign it, and then select the technology that supports the redesigned process.
What process mapping actually involves
Process mapping is not a flowchart exercise. It is an observation and interview exercise that produces a flowchart. The difference matters. A flowchart drawn from memory by a manager describes how the process is supposed to work. A flowchart drawn from observation and interviews with the people doing the work describes how it actually works.
The gap between those two versions is where most implementation problems originate. A system configured to support the official process will encounter the actual process on day one and produce unexpected results.
Common patterns that only appear during mapping
Several patterns appear consistently when a process is mapped carefully for the first time. Handoffs that are assumed to be automatic turn out to depend on a specific person's informal knowledge. Steps that appear sequential in the official process turn out to happen in parallel, or in a different order depending on the day. Workarounds that were introduced years ago have become load-bearing parts of the process that nobody has documented.
Each of these patterns has implications for how a new system should be configured, and for what training will be required. Discovering them after go-live is significantly more expensive than discovering them during the mapping exercise.
How long it takes
For a single operational workflow in a mid-size organisation, a thorough mapping exercise typically takes two to three weeks. That includes scheduling and conducting interviews, observing the process in operation, drafting the map, and reviewing it with the people involved to confirm accuracy.
That timeline feels long when an organisation is eager to move forward with an implementation. It is considerably shorter than the time required to remediate a system that was configured around the wrong assumptions.
Process mapping is not a preliminary step that can be compressed or skipped. It is the work that makes the rest of the project possible.