Learn Sigma has come up with a nice pocket guide to process mapping. This is actually quite a good article for a number of reasons. Firstly, process mapping, done well, is a great way of expressing complex information in an accessible and understandable way. Secondly, for every good process map we see, we'll see five bad ones. Top marks for effort, but zero marks for execution, you could say. Check out the image at the foot of this article for an example of "not quite getting it". So it's the techniques of execution are not always well applied
Here are some of our own tips
- Map between two clear points, start by defining the start and end of the process to be mapped
- Map the existing situation warts and all (NOT the desired, OR the required)
- Describe at each stage what happens and who does it (i.e. not "file" "check" or "complaint in")
- A diamond is a decision point and should take no actual process time
- Use "post-it" notes to rough it out on a wall (you can move things around till you get it right)
- Involve the people in the process in the mapping exercise - they know what actually happens, you might not
Anyway, here's a link to Rob's article

If anyone wants any more formal tuition, you know where to find us, obviously