By Summer Gatenby at October 20 2018 09:14:22
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.
Current research in information processing deals with programs that enable a computer to understand written or spoken information and to produce summaries, answer specific questions, or redistribute information to users interested in specific areas of this information. Essential to such programs is the ability of the system to generate grammatically correct sentences and to establish linkages between words, ideas, and associations with other ideas. Research has shown that whereas the logic of language structure-its syntax-submits to programming, the problem of meaning, or semantics, lies far deeper, in the direction of true AI.
They are more difficult to implement through discipline than administrative human-centric processes (although some discipline is needed). It is better to focus on obtaining buy-in from the people affected by the processes through early involvement, communication and expectations management. It is a known fact that knowledge workers are reluctant to change their habits. Some say knowledge workers don't like following procedures because they feel it limits their creativity; but most of the time they will be happy to follow a procedure as long as they see value in it, perceiving that it helps them work better and produce a better process output.
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.