From Flow Charts To Process Maps

Business process mapping techniques have existed for more than a few years and a lot of companies make use of the tools. Surely, flow charts, data flow diagrams or IDEF0 will bring something good, however these tools were intended for a diverse idea and it is barely astonishing that they do not explain business processes very well. The techniques involve some stages and an initial vital first step is to define the process that is to be mapped. It is decisive to take a process and not a functional view and it is also essential to define the scope of the process to be mapped, its start and end points as well as any key areas that are out-of-scope.

For the reason that the process should by definition be cross functional, then the teams put the job of producing the detailed maps require to be cross functional as well. The model team size is around five or six, plus a facilitator and larger teams might also be put to use but tend to slow the mapping process down. It is useful to sub divide the general process into smaller sections and allocate each sub-process to a divide team where large and intricate business processes are being mapped. It is vital to uphold sufficient communication between the teams where this is done.

Maps made in RAD sessions are typically hand drawn and for publication and change control purposes, they are redrawn in Visio and standard templates subsist for this. We usually anticipate a single sub process to cover somewhere between five and seven roles and to cover between two and six pages.

If they go down faint of these wide limits they are either not big and are possibly maps of functional activities rather than processes. And altering the maps into Visio format lets them to be extensively dispersed for review and comment. For the reason that Visio supports dynamic links to Excel, it is likely to assign metrics to individual activities, such as frequency, cost, resource, duration, and data requirement.

Process Mapping Techniques also involve consolidation as it defines the job of reducing the maps to more manageable proportions. It is restricted to the actions that take place between interactions, though; it does offer a shorter and simpler presentation of the process and is usually made use for presentation and approval purposes. Interactions have also a great role to play in describing processes in realistic and easily understood terms.