|
|
|
|
|
|
|
FlowchartingIn this page we will briefly describe flowcharts and some enhancements that make flowcharts an even more powerful tool for understanding and discussing processes. Objectives At the end of this page you will know how to...
Basic FlowchartsConstruction Flowcharts most often use five basic symbols. At times other sysmbols, usually computer symbols, are also used.
Symbols are connected with arrows pointing in the direction of flow. The convention is for flow to move from left to right, or top bottom if space necessitates. Interpretation
Best done in a brainstorming session. Especially interdisciplinary processes. In this setting use Post-it© Notes and draw the chart later.
Example Example flowchart of Labor, Birth, and Recovery Department Information System
In this flowchart is a very simple version of the flow of information into the LBR computer system. The data is collected on a document known as the 'blue sheet' and sent to the O.R. Management department for data entry. From there the data is electronically passed to the billing system and a reporting and analysis database. Several problem areas are apparent from the flowchart. One is the presence of two 'inspection', or checking, steps in O.R. Management. These steps check the work of the people in LBR; an inefficient and problematic checking process because the steps occur outside of the area where the Blue Sheet was filled in. The second problem is the presence of fog, namely the billing process. Nobody involved in the flowcharting process knows anything about the billing process or its requirements.
Topdown FlowchartsUse Used as a step in constructing detailed flowcharts or to simplify - for presentation purposes - a detailed flowchart. This is a great tool for beginning the flowcharting process; it keeps the team from bogging down in minutiae, at least tooo quickly. It also makes a great presentation tool. It is most useful, however, as a 'process mapping' tool, structuring the entire organization into an integrated flowchart schema. The highest level drawing shows the 'core' (or 'key') business processes and their relationships. The devil is in the details, which the more detailed flowcharts will increasingly iluminate. The following new prescription process presents a topdown flowchart. This high level view has 5 steps, plus an problem feedback step. Construction
Interpretation This flowchart is interpreted in much the same manner as the basic flowchart. What is of interest here, though, is the level of detail. And, the relationships at different levels of detail. "Handoffs" from one workgroup to another are also an important analysis using a topdown flowchart: much easier than with a detailed flowchart. Example This example shows the high level flowchart moving down the page and the details to the right. Each high level step contains a flowchart-within-a-flowchart consisting of the details steps. It is this hierarchical scheme that gives rise to the name, topdown flowchart.
Matrix Flowcharts
Use Shows process responsibilities with process flow. Shows who does what and when. The matrix flowchart is an excellent tool for reviewing and understanding interdepartmental handoffs in a process.
Construction
Example In this example we take the topdown flowchart from the previous pharmacy example and expand it, adding the extra dimension of Who is performing the activity.
Interpretation The central role of the patient as messenger becomes apparent. The patient performs the crucial step of transmitting the presciption to the pharmacy. This causes several problems:
All of these add potential inefficiencies and patient dissatisfaction to the process. The timing of the pharmacist verifying the prescription is very problematic: it will now require someone (either the patient or the pharmacist) reconnecting with the prescribing physician (or nurse) to discuss and resolve the issue. Considerable process disruption is likely if the pharmacist calls the physician (thereby reducing the number of pharmacists available to process prescriptions). The organization also risks patient dissatisfaction is the patient is forced to return to the physician for problem resolution.
Additional Flowchart AnalysisAdditional data enhances flowcharts and their analytic capabilities:
ConclusionFlowcharts are a powerful tool for generating process knowledge. This knowledge of waste, rework, duplication, over-inspection, and inefficiency is a first step in making breakthrough process improvements.
|
Additional Resources On This SiteWe offer OnLine Consulting and OnLine Workshops to help you learn and use cause-effect analysis. Send us your questions or data through our OnLine Consulting page and we'll help you do the analysis.
ReferencesSee our Bookstore for books and references on flowcharting and other quality management tools. |
copyright 2000, Robert Luttman & Associates * 53 Colonial Road * Medfield, MA * 02052 * 508.359.9630 * rluttman@robertluttman.com