By Anya Petersen-Frey, Regional Director, MBA, PhD (abd), Certified Global Business Professional
What exactly is process mapping? Bob, Torrington
This is a great question, and timely, since I just finished a process mapping project with a local organization. Here is a very brief overview.
Process mapping is usually considered a quality management tool with an overall goal of improving a process by looking for gaps in service, waste (time or product) or other issues. You may have heard terms such as "Six Sigma", "Lean Six Sigma" or the Malcolm Baldrige National Quality Program all which provide tools geared toward maximizing efficiency while maintaining control over a process - be it manufacturing or service related.
Process mapping provides business leaders the opportunity to clarify how processes are actually being performed. It reveals problems such as bottlenecks or variations in how the process is carried out by different groups or individuals. Put simply, process mapping strives to improve business performance by optimizing the efficiency of connecting activities in the creation of a product or service.
A process map is a tool - a means to an end, not an outcome in its own right.
The final output will, hopefully, be an improvement in the way that the business process works.
There are two main process models:
- The "current" model which outlines the current process as it is performed now
- The "future" state model which defines the way the process will look when changes or modifications have been implemented - or the way it is desired to be.
The goals of completing this process are to create value for the customer and to reduce costs for the company
There are many ways to approach creating a process map. Optimal is to have people at all levels of the organization involved, even in a very small firm. The starting point is to identify and map out a particular process for a "current" state. If you don't know where the gaps or delays in a process are it can be difficult to identify and correct them.
For example: Imagine you own a carpet store that sells carpet as well as offers delivery and installation. What is the process, from the customer perspective, of purchasing and having carpet installed? The starting point might be "customer comes into store to look at carpet". Then what? What questions are asked that direct the next step? Walk the steps as though you are a customer including communication, time involved, etc. Note where delays occur, or where decisions have to be made. This can be a messy process as different input creates a map with many divergent paths. That is ok.
This may be a simplified example but can give you a hint of how to take a step back and objectively view your business process. It is important to understand what each person does - so ask them. The map should have no personal names but rather only list the processes and the differences in how different people handle them.
There are many flow chart and process map examples on the Web as well as software to help you build your final map. You will notice some standard symbols used to delineate "decisions", or "delays" - these can be helpful but the map can be created in a way that meets the needs of your organization.
It can help to have an objective facilitator guide the original data collection using input from various people in the particular process to get an accurate view of what is actually happening, but again, a business owner can begin the process on his own.
The key goal in using this type of tool is to maintain a competitive edge. Don't become complacent and fall into the age-old "this is the way it has always been done" trap. There are times when the an original method is still the best; but many times it is time to re-evaluate and institute more efficient processes.
Recent Comments