This was my initial reaction during a recent discussion with a colleague on process development. During our conversation she advised that they are moving away from flowcharts in favour of text based instructions in table format. I was stunned for a while.
I asked what drove this decision. The answer was that the users of the process found it easier to read a table format instead of a flow diagram.
Although I don't support this approach, I am looking to see if anyone else has tried this method and what the end results were. Also, I would be interested in views of what people could see as problems with this approach. My main concern was around how do you measure the process and how will you know where to start for CI purposes.
Thanks in Advance
Saving Changes...
Sort By:
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
Kendall, Indeed I have found that at certain levels of process analysis and design a tabulature format is far more easy to use than flow charts. They are easier for lay people to read and understand which improves communication. They can depict the phases of the process more easily and can be much easier to notate and diagnose proper obect transformations, labor vs lapse time and process critical path steps. Since a tabulature format does not reflect alternation it must be bound by an assumption (ie. Sales order processing when the customer's credit is okay, inventory is in stock, etc.). These assumptions allow the group mapping the workflow to keep their feet firmly planted in a path and not get confused. With each assumption point identifies the decision points in the process thus also enhancing the ability to quickly understand process variations based on CORE object conditions (good credit / bad credit - in stock / out of stock). Finally, the tabulature format of a process usually fits nicely on a singe page which makes it easy to work with.
For detail process analysis I have found Process Logic Diagrams (Bracket Structures) to be far superior to flow charts. They support all logic constructs (sequence, alternation, repitition and hierarchy, allow for large amounts of text bound by logic, flow right to left & top to bottom enhancing readability and allow for consitant locations for the indexing of exhibits. They have an extremely simple syntax and promote structured thinking. I have been using these presentations for decades with great results and acceptance from CEOs to programmers.
Saving Changes...
Anonymous
My methods & procedures team has been struggling with alternatives to flow diagrams as well. Can you direct me to a template, sample, or source for the tablature format? Saving Changes...
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
I would be happy to send you a complimentary copy of my book "The Helix Factor". Chapters 5 & 6 present some sample models that use this type of format. Just email me your address. Saving Changes...
Michael WoodProject Manager / Business Analyst / Business Process Improvement Guru| Independent ContractorGig Harbor, Wa, United States
I would be happy to send you a complimentary copy of my book "The Helix Factor". Chapters 5 & 6 present some sample models that use this type of format. Just email me your address. Saving Changes...
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Hi Kendall, your experience is similar to the experience our company had 6 years ago in Japan. While we thought we had a very good graphical process for a two year project effort to double-byte enable and then implement a complex application, the participants and user's insisted on having multiple views of the process. We jointly concluded (that means our Japanese client demanded) that for every process, we needed four views of the process; 1) a graphical view, 2) a text-based tabular view, 2) a step by step view with management guidance and resource suggestions, and 4) and an artifact view that listed such things as tool templates, forms, and checklists for each step of the process. The process owners maintain these views with input and suggestions coming from users via the CI process steps. We housed the processes on the intranet, so users can easily access them, (tabular, graphic, etc.) simply from their browser, rather than having to search for department files and open desktop applications such as Word, Excel, or Visio. We learned a lot from the Japanese regarding how to setup, use, and continuously improve processes. Of course, they learned it from Deming..! This early experience birthed for us what is now a solution that we develop, sell, and support called Processes On Demand, an HTML-based software solution for workplace processes, best practices, and standard operating procedures. Hope this helps. -- Mark Perry, VP Customer Care, BOT International Saving Changes...
Ben GrahamPresident| The Ben Graham CorporationTipp City, Oh, United States
Hi Kendall.
For process analysis, no tool is better than a detail process chart.
Unfortunately, too often flowcharts are prepared haphazardly (not following the structure of a proven methodology), they are prepared at a fairly high level (some distance from reality) and they really don't provide a lot of direct value -- unless the analysts diligently dig into each step.
My guess is that the flowcharts your colleague was using were poorly prepared.
For training, general understanding and otherwise contributing to CI; text, table and high level graphical presentations may be appropriate -- but for detailed anaysis, a summary view or partial view doesn't cut it.
Saving Changes...
Anonymous
Using swimlane diagram to represent business process map is a good alternative to flowcharts. It not only shows the flow of the process, it shows who is the owner and the time dimension at once glance. It can be easily understood by both the IT professions and the users. It allows clear visibility of the process and hence make optimisation easy. If it is detailed to a proper granularity, it can be used as an orientation tool for new staff.
Saving Changes...
We are extensively using swimlane diagrams, rather than flowcharts, for organization redesign. It allows us to streamline each business process and associated procedures, and can compile all the operations, procedures and processes associated with each org-unit (i.e., everything in its swimlane on all diagrams) to evaluate workload etc. The intention is to expand to the level of detail required to generate individual Position Work Descriptions, documentation for the quality process manual, even assist the preparation of support contracts. Saving Changes...
Anonymous
As Ben mentioned, process mapping is particularly problematic when diagrams are poorly or incorrectly constructed. There is a tool that automatically generates UML activity and responsibility diagrams from plain English text. Check out the flash demo at www.ravenflow.com.
Not only does it generate the diagrams for you, RAVEN also directs you to errors (i.e. gaps, flow-breaks, inconsistencies) in the text.
Pretty amazing. Saving Changes...
