By Summer Gatenby at October 30 2018 11:23:52
All process instances are executed in a very similar way and it is easy to draw a flowchart detailing the sequence in which tasks are executed. It is also possible to formalize the business rules that guide decisions, normally based on the evaluation of some process variables. But recently other kinds of processes have caught the attention of process management specialists. They are known as knowledge processes, or knowledge-based processes. Knowledge processes can be defined as "high added value processes in which the achievement of goals is highly dependent on the skills, knowledge and experience of the people carrying them out". Some examples could be management, R&D, or new product development processes.
For a technical writer a flowchart can be a very useful tool to illustrate various operations and processes. Before you start your next project, see if you can illustrate the process via a flowchart. It will make life easier for you and your manager or client. The end result will be a better project which is good for your target audience. Note: Microsoft Visio is a good software for creating flowcharts. If you can write a simple sentence in English and organize your thoughts then technical writing may be a rewarding field. You can easily make it a second income stream in your spare time.
It is extremely important to continuously improve knowledge processes, by creating an environment through which they can evolve. This can only be achieved through coordination of diverse disciplines such as knowledge management, change management, expectations management, etc... It is crucial to establish an adequate process context (the combination of technologies, procedures, people, etc... that support the processes). The process context must incorporate feedback mechanisms, change evaluation procedures, process improvement methods and techniques and must be flexible, in order to be able to incorporate enhancements in an agile but controlled way.
Process definitions are high level descriptions instead of rigid workflows : Processes can only be defined up to a certain level of detail, and it is difficult to provide low level work instructions or to automate decisions. Because they cannot be formalised in detail, process simulation is rarely possible. Decisions are highly subjective and too complex to be expressed in a formal language, as they are taken based on intuition and not on rigid business rules.