Process design document
When we start the RPA project, the first step we perform is to try to understand the existing process by reading through the documentation available, process maps, and other artifacts related to that project. Only after reviewing these documents and processes do we engage with the SMEs to understand any nuances within the process. Though this is an ideal scenario, most of the time it doesn’t happen. In reality, we are directly introduced to the SMEs and given a walk-through of the process verbally. As you know, this is not a very efficient way of analyzing any process that is lengthier than 15 minutes. The question is: how do we overcome this challenge?
The best way to handle the situation is to create documents. This is where the PDD comes into the picture. Most of the time, a solution architect is accompanied by a business analyst to these meetings. A business analyst is considered an expert in understanding the process, retaining that knowledge...
