By Gabrielle Button at October 12 2018 18:28:55
In the last years some organizations have emerged with the aim of creating professional communities around specific disciplines such as Software Development (SEI, ESI, etc...), Project Management (PMI), Business Process Management (BPMI), IT Service Management (ITSMF), etc... One of the objectives of these groups is to develop a body of knowledge that compiles the discipline's best practices in the form of reference frameworks, methodologies and maturity models. These assets should be considered by any organization interested in knowledge process management.
If the process is instantiated frequently and the instances are homegeneous, it is possible to create great process models that dramatically increase the efficiency of the process. The best way to ensure process improvement is to generate an environment in which people are motivated, enthusiastic and passionate about process management. Most of the time, knowledge processes are collaborative. By performing a process collaboratively it is possible that each task is carried out by the most specialised, experienced and knowledgeable worker in that specific area. Having a net of relations within the organization is a very important asset for people executing knowledge processes.
What's a flowchart? A flowchart can be defined as a graphical representation of a sequence of operations or steps. In other words, it's an illustration of the various steps involved in a project or process. Typically, a flowchart consists of a number of boxes, arrows, and text that combine to form a sequence. Why create a flowchart? The purpose of a flowchart is to show the various steps of a process in a snapshot. By looking at the flowchart, the viewer should be able to identify the various steps involved in the process.
How to create a flowchart When you're working on a complex project, creating the flowchart itself may be a time-consuming task. Here are six simple steps you can follow to create even complex flowcharts: Start by defining the end result of the process or project. The end result could be anything such as completing a user manual, writing a complex software process, installing a new part, or performing a test. List the various steps involved to achieve the end result. This will take some research. In complex processes, each step could have a series of sub steps. The steps involved to create a user manual could be: a. Meet with SME ; b. Research existing documentation ; c. Videotape the procedure ; d. Take photographs ; e. Create illustrations ; f. Develop the user guide ; g. Test the user guide ; h. Make changes/adjustments ; i. Deliver final product.