
How to capture a business process: Step 5
When sketching out a process it helps to start with the most straightforward case. The one where everything goes right, or at least goes as expected. Once you have this laid out, you can identify exceptions.
I find it helps to think of the whole process as a river. The straightforward case is the main, well-worn channel, but there may be parts that break off and loop round before coming back into the main flow.
So, for example, your straightforward case for preparing a set of annual accounts for a client assumes you have all the information already, the client approves your draft immediately and you can go straight on to filing them. But what happens if you don’t have all the information? Or the client doesn’t bother to get back to you with approval? The process needs to deal with these too. These are alternative routes through the process – loops in your process river if you like. And that’s exactly how I like to represent them.
Here’s another example. For a maintenance business, the ‘straightforward’ case is the typical reactive, unscheduled job: