Things You'll Need:
- Pencil
- Paper
- Computer
- Software, such as Microsot Power Point or Visio
-
Step 1
Mistake 1: Documenting what management thinks is happening.
Many times management wants to know what’s happening but they go about finding how in the wrong manner. Second level managers, wanting to pacify upper management, throw together a process map documenting what management thinks is occurring. The end result is not reality. How does it benefit the organization? It doesn’t. -
Step 2
Mistake 2: Documenting what should be happening.
Another common mistake is to document how something should be happening. This may have value in the proposed improved phase, but documenting how it should be is a far cry from documenting what’s really going on. -
Step 3
Mistake 3: Documenting by taking someone’s word for it.
This mistake is akin to documenting what should be happening. If you only write down what someone thinks is going on, how can that explain the truth? It can’t. -
Step 4
Mistake 4: Asking the wrong people about it.
Another mistake is asking those who appear to know what’s going on, but really don’t. Taking someone’s word for without validating it is real, it not wise. -
Step 5
Mistake 5: Documenting too much detail.
This is a common mistake. If too much detail is put into the process map, it can be too complicated and busy to see what needs to be improved. The trick is to document the only elements of the process being investigated. Save the other detail for other process maps. -
Step 6
Mistake 6: Begin at the start of the process.
While it seems logical to start at the beginning of a process, it can lead you in the wrong direction. For example, steps of a routine process can be overlooked.











