Process Mapping for a better visibility !!
The process mapping is a representation that shows the whole picture of any processes of the company. Process mapping is used to represent activities of the company through a single or multiple scheme. so why companies should proceed to map their process?
- Get a bird’s-eye view on your process : The process mapping provides a large-scale view of how your process works. With an “AS IS” version, a detailed graphic description can help to understand the way your processes deliver an output. The process mapping also helps to define responsibilities and clarify which activity is done and by which person.
- Keep the knowledge inside : Mapping your process will help the companies' owners to improve knowledge retention and meet everyday challenges as your employees retire, leave their positions. Using a standard for drawing your process map as UML or BMPN will make your chart understandable, leading to a better understand by anyone in your company. You can use your process map to train your employees.
- “ah-ha” moment! : Process mapping presents all the details of the process, putting the process under inspection. Just like under a microscope, it reveals areas that need to be worked on. Once your process is mapped, you usually discover unnecessary steps or wasted time, bottlenecks, unwantedscenarios and other problems. Here comes your” Ah-HA” moment that allows you to figure out a better way to get the job done.
- A Jump into the Future : The process map provides a clear vision of the future. Once you finish mapping how the current process works in the present, you have the opportunity to redesign the process on what it should be. The “TO-BE” version of your process are made after identifying problems and proposing solutions. now, with the big picture in hand, employees can make improvements with a shared vision.
Wholeheartedly agree! Often process mapping in itself has uncovered key issues, outlined solutions and, importantly, generated urgency for change with teams struggling to complete mapping , itching to act. Great tool.
Great summary, Maher! Some rules of thumb that I use when developing process maps: - Process boxes should always start with a verb and describe the main activity of the process - Arrows that connect process boxes should be labelled with nouns and represent the output of the process boxes - A process box can have several inputs from other processes, but only one output - Processes should be built in levels, with fewer than a dozen boxes per page. Use numbering to drill down into subprocesses within each process box. That way, you don't end up overwhelmed with 100 boxes on a page and arrows everywhere. - No mention of systems! You should be able to describe a business process as a series of activities that is system agnostic. There's nothing stopping you from doing a system overlay after the fact for context, but process maps describe the 'what' not the 'how'. Nicely done!
When you map the process you need to value steam map to really understand some of the context to what you may have eloquently drawn up, and here, it is essential in gaining profound knowledge, to undertake gemba walks to confirm the accuracy and identify management failures in design, goals and communication. Just my thoughts
Process Mapping is a great tool contributing to increase Operational Efficiency and Profitability. JGM
I fully endorse this approach. Great article and something to foster in our day-to-day work.