By Jett Alcock at October 02 2018 07:31:46
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.
Knowledge workers carry out these processes by taking into account multiple inputs (generally a wide set of unstructured data and information) to perform difficult tasks and make complex decisions among multiple possible ways of doing the work, each one implying different levels of risk and possible benefits. They are dependent on individuals and it is not possible to automate them. One example of a knowledge process is "Marketing a new product". The same steps are followed each time a new product is launched (benchmarking competitors, deciding pricing strategy, planning promotion, etc...), but it is the experience, knowledge and intuition of the people that drive the process to success.
Perhaps you feel some shyness. That is understandable. According to shyness researchers, more than 80% of those surveyed have said that they have felt shy at some point in their lives, and 40% label them selves as currently shy! So to win your ex back, you must overcome some shyness. You must re-master the art of conversation. You must get out there and meet new people and become more popular. But if you flex and work out your social muscles, you will definitely strengthen them!
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.