By Vanessa Richter on October 18 2018 02:14:52
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.
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.
I recently overheard a Business Analyst say there was more to systems architecture than drawing boxes and arrows on a piece of paper. This may be true to a degree, but the ultimate deliverable of any engineering/architectural practice is a set of drawings from which to build a product. Architects and engineers do not spend all of their time drawing diagrams; for example, they have to specify requirements and analyze such things as the stress of components to determine the suitability of materials for use in design. But aside from this, the end result of engineering or architecture, their deliverable, is a set of drawings, be it a blueprint, a floor plan, wiring diagram, plumbing, or a set of flowcharts.
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.
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.
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.