Comment on Macro and Micro Processes by Paul
Blog: BPTrends - Harmon on BPM
Brad, I’ve never made fine distinctions about the lower end of the process size scale, except to distinguish atomic activities — which refer to things people or systems actually do. In essence, activities can actually be observed. People greet customers, software applications check if a credit card is acceptable. Everything above the level of activity is a name given to one or more activities. As you progress upward, the process names refer to larger and larger groups of activities. The names help us understand how groups of activities work together to accomplish outcomes.
The issue of reuse is more complex. The idea of standardizing processes (activities) is focused on reuse. We want the Record Customer Information to be the same, no matter what process the activity occurs in, so we get the same customer information each time. Similarly we want larger processes to be the same so we can switch employees and managers and support materials from the Support Sales process in the US to the same process in England with a minimum of fuss.