Discover the process before automating it

Start with actual requests Compare a completed request with one returned for correction. Who started the work? Which information was available initially, and what was added later? These examples reveal more than a feature wish list.

Agree the boundary A process needs a recognisable trigger and a defined result. “Customer operations” is too broad for a first implementation; “reviewing application documents” is easier to scope and test. Identify a person responsible for the outcome.

Include exceptions Missing documents, an unavailable approver and cancellation are normal operating conditions. Decide who receives the request, which data remains and how work resumes.

Review before configuration Walk through the model with the people doing the work and those approving it. Explore our process analysis service and the BPMS design guide, or describe your process.