Questions one should ask while mapping the process are:
- what is the purpose of process being mapped?
- what is the boundary of the process being mapped, i.e. the start and the end of the process?
- what triggers the process?
- what is the Level 0 process? what are the inputs, and outputs (product/service/decision)?
- do I drill down to the next level?
- what are the sub-processes within the next level?
- what activities are carried out as part of the process being mapped?
- when is this activity carried out?
- why is this activity carried out?
- what are the inputs and outputs (prodct/service/decision) of this activity?
- what are the tools/resources required to carry-out this activity?
- who is the performer of this activity?
- what is the next activity?
- are there multiple activities possible as a result of this current activity?
- can the follower activities of this activity be one or many of the multiple activities identified? in case of many, can they be parallel?
- what are the business rules for each of the possible options?
- is this activity without any predecessor or follower?
- are all activities connected with each other? is the inter-relationship completely mapped?
- can i simplify the representation of the process? is it really so complex?
- has the process been verified or signed-off by the user?
Ensure that user / person whom you are intervieweing is either the process owner or an expereinced user. Also ensure that you are clear of the process mapping convention / notation that you will follow to map the process. Always communicate / carry a sample process map to the user / process owner ahead of the process mapping interview or workshop and explain the same to the user. Try and visualise the process.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment