By Randkin Paul on September 07 2019 16:51:41
There is a reason for this, as it has been found by psychologists, researchers, and neurologists that such graphics are much easier to remember when they are done this way. This means that the human reading the text book, manual, or technical paper will indeed remember the step-by-step process long after he has reviewed the material.
When writing technical papers, manuals, e-books, or research papers we often try to explain procedures, processes, and the proper way to make decisions based on that data or the task at hand. In explaining these processes it makes sense to use flowcharts, something that is very popular with academia, and business management gurus.
The first task in developing a procedure is to prepare a flowchart of the current practice. This is done with the active contribution of staff who do the task or know most about the task. The procedure author/facilitator leads the group and prepares a rough flowchart of the current process. The flowchart emerging in the meeting should be rich in detail through the contributions of all participants, but will also be a mess -- marked up with deletions, changes, and notes added as a result of the groups inputs. Seldom can this be done in one meeting unless the process is simple. All participants should bring any work instructions and check sheets that they use or have concerning the process to the meeting for reference and use in the discussion and to be included in the project file for future reference.
The author and team should consider whether it may be beneficial to cover some of the tasks in multiple separate procedures - there are no hard and fast rules. The best approach is to assure a clear and easy understanding of the process. All that can be said is that a flow chart generally is easier to use if it less complex. Also, if a flow chart focuses on one process or functional area it provides easier future change and control.