Process decomposition is the practice of documenting all the sub-processes and tasks that make up a higher-level business process. For example, invoice processing can be decomposed into four sub-processes:
- Receiving an invoice
- Extracting data from that invoice
- Getting approval for payment
- Processing payment
The more complex a process is, the more levels and sub-processes it will contain.
Why is Process Decomposition Important for RPA?
Under a continuous improvement lens, process decomposition is important because it delivers the insight needed to make informed decisions when considering the right process improvement strategies to apply.
Before deciding how best to improve your processes, you need to analyze your business processes and determine where there are inefficiencies, where they are error-prone, and where there might be waste. There is no way to do that without first having a clear and accurate picture of what that process and all of its sub-processes look like.
Automation is one process improvement strategy that an organization may want to apply to improve their workflows in terms of higher efficiency and cost reduction. Process decomposition is so integral to automation because it’s not the end-to-end business processes that are automated—it’s the sub-processes and tasks of those higher-level processes that are converted into bots.
Without process decomposition, finding automation candidates and knowing what to automate is like trying to find a needle in a haystack and will most likely elicit the same success rates.