By Lisa Werner on December 04 2018 12:07:55
A flowchart could be defined as a pictorial representation of a process in which the steps are symbolized by shapes - in other words a diagram that explains the steps in a procedure. Each shape should link to its neighbour by a connector line, and often these have arrow heads to describe the direction of flow.
Once the team recognizes the problem areas, they can easily adjust the map to a future state version that can dramatically affect performance and turnaround time of the purchase order process.
Helping an organization map out processes can be a challenging task unless you know how to create sample flowcharts. When attempting to get subject matter experts to redefine their business processes, it is imperative to help them identify gaps or redundancies in their current as-is process.
Creating purchase requisitions is a standard function in every business. Unfortunately, the manual paper purchase order or requisition is one of the most frustrating areas of every business because the constant approval issues and long turnaround times that can occur.
I guess what I`m driving at is that despite all of this peripheral activity, and to refute my Business Analyst friend, the principal thrust of the engineer or architect is to produce and maintain a reliable set of drawings. It all comes down to boxes and lines. Interestingly, today`s analysts and programmers think drawings are "old-hat" or passé. I don`t care whether you draw it with pencil and paper or by computer, documentation is an inherent part of the design process. Failure to recognize this is to deny reality.
A flowchart can enable the process analyst to effectively document the information given to them by the subject matter experts. With a defined list of symbols, directional arrows and flow diagrams, flowcharts can help the team find gaps and or problem areas that have been known for awhile but have never been visually mapped out in an as-is process map.