By Vanessa Richter on October 26 2018 22:10:12
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?
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.
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.
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.
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).
This is where simple process mapping can be used as an effective tool. Developing sample flowcharts that focus on specific areas or duties can help each subject matter expert define their areas of knowledge and communicate to others in the room. Linking each area together with inter-dependencies and business rules is where the real power of this technique comes in.