First, get a handle on your processes. If you are starting from scratch, focus on your Customer interactions first. A familiar example is Order Fulfilment; say your company is a supplier of desired widgets and gadgets of various types that your customers order as they need them. You need to identify the events that can trigger the process, define the ending point of the process, and any other events that can occur during the process.
Trigger Event: Customer places Order
End Point: Order received by Customer
– Customer changes Order
– Customer cancels Order
– Customer asks about Order
Defining a process like this will look similar across companies, but it will not be exactly alike even at this point. For example, you may determine that the real End point is when Payment is received from the Customer. (Looking ahead, what will make your process unique is the decisions and rules you use to guide your process.)
Given the above definition, you need to identify the distinct activities that will always be performed by the process, such as:
– Receive Order
– Record Order
– Pick Products for Order
– Ship Order
The process becomes more complicated when you identify the variations to the process, the things that don’t always happen, but change the flow and potentially the outcome when they do occur.