An End Point represents a terminal state of your process and can be thought of as the opposite of a Start Point. An End Point does not have to be an activity or action taken by a person or system; it can be just a place holder to represent the terminal state. If you are mapping the call flow of an automated phone system, an example End Point might be “Call Ended”. If you are mapping a customer support process, an example End Point might be “Issue Resolved.” If you are not sure what to call it, “Process Ended” can be a fine End Point. You should try to end all pathways through your process with an End Point. If your Process Map represents an intermediary step in a larger process, instead of ending with an End Point, you may end your flow by linking to the higher level Process Map, or the Process Map that represents the next phase of the process. Like Start Points, you should try to keep the number of End Points on single Process Map as low as possible. One Start Point and one End Point per Process Map is ideal, but very often not possible. Many times you will have two End Points, one to represent a successful process termination and one to represent a failure. That is great. If, however, you have multiple End Points and the ends states are not closely related, you may want to think about breaking up your Process Map into multiple smaller maps focused on narrower parts of the overall process.
| « Elements – Process Map | Elements – Decision » |
Elements – End Point
December 8th, 2009Elements
