Yesterday we looked at the Information Gathering Phase and described different ways you can get that information from Subject Matter Experts and those in the frontline who use the procedures.
Gathering Data For Procedures
In general, Business Analysts gather data through workshops and interviews. Emails work too but I prefer to see the white of their eyes.
You can also collect data from reading historical documents which may give more background to the project. These may include Specifications, Requirements and Flowcharts. Gather all these and hold them in a centralized location.
Does the Process Work?
As mentioned in the previous tutorial, we need to test the procedures (aka SOP) and determine if they work. Your goal at this point is to:
- Determine if the procedure works as documented in the SOP.
- Identify mistakes or anomalies that have crept into the material.
- Determine if the procedure has been updated, version controlled, and also if multiple copies of the same SOP are in circulation. It’s not unusual for multiple copies of the same procedure to be in circulation if there is no known Document Owner or if there are no Version Controls in place.
Once you have captured the existing process, share your notes with the team members.
Looking at Alternatives To The Current Process
The next step is to look at alternative ways of performing this process and contingencies that need to be considered when developing the new process.
At this point, you should understand how the current process works. What you want to do is see:
- Where it can be improved.
- How the process can be streamlined so there are fewer activities, transactions, manual interactions required.
- Who needs to be involved in the revised process.
- What technologies are required to perform these tasks.
- What parallel processes must be performed for the primary process to work correctly.
- What sub-processes need to be developed to support the new process.
There are several ways to approach this. One is to look at the actors in the process, (for example, the Cashier) and see how his role could be streamlined.
- What activities can be removed?
- What activities could be collapsed into a single activity?
- What tasks could be automated?
- What activities could be changed so there are fewer activities later on.
- What security measures need to be considered, for example, sharing information between department and/or with partners.
Here’s an example from the real world.
When I apply to have my credit card limit increased, the process works as follows:
- Ivan contacts his Local Branch.
- Local branch tells me to call another number. They can’t forward me for technical reasons.
- Ivan called the Credit Card office.
- Credit Card Dept ask me to fax in the paperwork, e.g. utility bill. They do not accept documents over the web. Oddly enough, you can apply for a credit card and even a mortgage over the web….
- Credit Card Dept faxes this to Relationship Manager at Local Branch for verification purposes.
- Local Branch forgets to process my application… Relationship Manager may have moved to different office.
- Credit Card Dept don’t follow up.
- Ivan calls Credit Card Dept to remind them to chase up Local Branch.
- Ivan needs to send over the documents again.
- Does Ivan do this? You know the answer, I’m sure.
OK, clearly this process could be improved if I could give the documents to my Local Branch instead and if there was a reminder for the Credit Card Dept to follow-up if they did not hear back from the Local Branch. Otherwise, applications disappear into black hole.
FYI – actually, I did. While re-sending the documents was an inconvenience, I wanted to finish this task and move on to the next thing… which you can read about tomorrow.
