By Yvonne Winkel on October 27 2018 15:25:49
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.
Well, flowcharts can be used to analyze, design, document or manage a process in a wide variety of fields. Examples could include a Recruitment or Accounting process, the logical procedure within a piece of software, or a process in an organization such as Health & Safety, Equal Opportunities, Conciliation & Arbitration or Social Services. There are several derivatives of the basic flowchart including the Workflow Diagram,
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).
Each flowchart should ideally begin with a Terminator shape, from which the next step should be linked. Each shape should be indicative of a specific stage in the process and there are conventions for each of these, the most common being the rectangular "Process" shape. Many others exist, however, including shapes representing Data, Documents and Decisions. Decision shapes are diamonds, each of the four corners (or nodes) being either a link from the preceding shape or action to be taken in the next stage depending on the decision.
This is not easily done, especially in a large room with multiple experts who know only a small portion of the entire process. Each contributor who works within the team can identify their specific areas they deal with on a daily basis, but do not necessarily understand or know the linkages and dependencies that exist outside of their general areas.