By Yvonne Winkel on October 22 2018 06:06:09
Many of us use flowcharts in our daily work - indeed the creation and deployment of a flowchart is one of the most common tasks in business today. But what do we mean by a flowchart, and what is it supposed to do?
Usually, this exercise takes place during an e-procurement project as part of the analysis phase, but can be done at any time. As long as there is a resource who has the proper skills and knows how to draw a flowchart to help the various departments identify their current procedures and potential problem areas within the purchase order approval process.
If your organization is looking for ways to reduce costs, the purchase order chain is one area that can be made more efficient. If the purchasing department learns how to draw a flowchart depicting the as is for each department, the overall effort could help reduce costs by eliminating redundant approval processes and mistakes.
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.
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.
Such drawings basically consist of boxes and arrows. Boxes (be it squares, rectangles, polygons, circles, etc.) represent tangible objects and lines represent relationships between such objects. Flowcharts are similar; here, boxes represent specific types of processes or decisions or objects such as inputs/outputs/files, and lines represent dependencies between them (comes from/goes to).