By Katrin Freeh on December 05 2018 07:32:04
Many departments have established business rules based on guiding principles and philosophies that may have been created years before. Because there has been no initiative in documenting these procedures, chances are that there are many rules still in place that are causing unnecessary barriers and redundancies that add to the purchase order cycle time.A flowchart is a sequence of graphical symbols and shapes that can be used to help subject matter experts visually walk through their processes and validate those rules for accuracy and relevancy based on current business needs.
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.
As a process mapping consultant, it is imperative to get everyone to see not only their own procedures, but how they interconnect into the organizational structure. Once in place and agreed upon by all the contributors, you begin to be able to challenge the current way of doing business and assist them in finding inefficiencies that could be costing the business thousands of dollars.
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.
In addition to diagramming techniques, engineers and architects have found it useful to develop models and prototypes to evaluate the overall physical aspects of their design. These are useful but let us not forget they are all ultimately based on a design of some kind (boxes and lines). From the models and prototypes, designs can be adjusted as required.
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.