By Vanessa Richter on October 20 2018 20:47:32
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.
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.
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,
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.
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).
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.