By Jett Alcock at September 15 2018 02:31:16
It is usual that knowledge processes take the form of projects to manage their execution. If the output of the process is a unique product, managing work as a project will result in obvious advantages. There are certain guidelines that can help an organization willing to improve their knowledge processes: Provide process description on how to approach work Try to figure out the best way to carry out a knowledge process, by making the best practices existing in your organization (or in your industry) explicit. Publish process definitions in a format that is easy to consult and understand. Provide tools that facilitate and standardize work Decide which tools are best to help knowledge workers carry out their work. Involving all affected knowledge workers in the process of deciding which tools will be used is very convenient, in order to obtain user buy in.
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.
In all cases, however, the task that the algorithm is to accomplish must be definable. That is, the definition may involve mathematical or logic terms or a compilation of data or written instructions, but the task itself must be one that can be stated in some way. In terms of ordinary computer usage, this means that algorithms must be programmable, even if the tasks themselves turn out to have no solution. In computational devices with a built-in microcomputer logic, this logic is a form of algorithm. As computers increase in complexity, more and more software-program algorithms are taking the form of what is called hard software.
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.