Exception paths
ENGLISH A request is submitted. The approver is unavailable. What happens next? That exception belongs in the workflow before the solution goes live. Consider a simple approval process: submit, review, approve. Now consider what can interrupt it: • Required information is missing • The approver is unavailable • The request is rejected • The same request is submitted twice Each situation needs an agreed response. For an unavailable approver, stakeholders need to decide: • Who is authorized to take over? • When should escalation begin? • What status should the requester see? • How should the request data and history be preserved? As a Senior Business Analyst, I would walk stakeholders through these situations alongside the normal flow, then document the agreed business rules and acceptance criteria. Process owners define who can act and when. Delivery teams know which behaviour to implement and test. This is where Business Analysis connects with Systems Analysis, Data Management and project delivery: making sure an exception has a clear owner, a defined response and a testable outcome. A workflow is ready for daily use when people know what to do when the usual path is interrupted. Which exception would you add to an approval workflow review? #BusinessAnalysis #RequirementsManagement #ProcessAnalysis #SystemsAnalysis
Read on LinkedIn