A process map is valuable when it explains why work is slow, unreliable or expensive. A perfect diagram that shows only the intended procedure will not do that.

Choose a clear start and finish

Define the trigger and the completed outcome. “Sales process” is too broad. “From qualified enquiry to signed proposal” gives the mapping session boundaries.

Select two or three recent cases, including one that went wrong.

Map what happened, not what should happen

Ask the people doing the work to describe each action, handover, decision and wait. Include email approvals, personal trackers and steps performed outside the main system.

For every step capture:

  • owner
  • input and output
  • task time
  • waiting time
  • system or file used
  • common exception

Mark four types of friction

Look for queues, rework, unnecessary handovers and unclear decisions. Use evidence where possible. Ten minutes of data entry may attract attention, but a two-day wait for approval could be the real constraint.

Also note failure demand: work created because something was incomplete or incorrect earlier, such as chasing information, correcting records or answering the same question repeatedly.

Find the constraint

The bottleneck is the point that limits the performance of the whole flow. It may be a person, a policy, missing information or a batch review that happens only once a week.

Improving a non-constraint can make one team look busier without improving the end-to-end result.

Test the cause before designing the future

Ask why the constraint exists. A slow approval may reflect unclear limits, low confidence in the data or a senior leader carrying accountability that should sit elsewhere.

Run a small test. Change the approval threshold, improve the input or redistribute a decision. Measure the effect on lead time, quality and exceptions.

Turn the map into ownership

End with a short improvement backlog. Name the owner, expected operational result and first experiment for each item. Keep the map updated only if teams will use it to manage the process.

LUKiN’s process improvement consulting follows work as it really happens, then helps teams implement and test a better flow.