By Liam Simcha at January 07 2019 20:04:58
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.
In the Tell 'n' Show method of creating effective presentations, you tell you point, then you show it. So, each point requires some validation, some evidence. Which validation you choose may depend on your audience. Some people want hard data, others want to know what the competition is doing, and still others may want the advice of an expert. A story that conveys a poignant situation may be effective. Sometimes, all you need is an image to show what you're telling. If you say that the copier you sell fits on a small table, a photograph will suffice.
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.
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.
Multiple inputs to the process exist : Some of them would be competition, lifecycle stage of the market, brand image, budget, etc... ; Complex decisions are made : There are many possible ways to achieve the process objectives (reach planned sales, leverage brand image, etc...) ; Each decision implies different levels of risk and potential benefits : It is the responsibility of the worker to choose the best one (low price strategy, aggressive advertising campaign, etc...) ; There are three main characteristics that make knowledge processes different from highly structured processes: Focus is on communication instead of automation.
Here are the types of evidence you can use: Images ; A photo is often a great way to show a point. You can use a photo in three ways: * Literally: If you're talking about a piece of equipment, show a photo of it rather than describe its specifications in bulleted text. You can use callouts that point to the various features and label them. * Metaphorically: Sometimes a point you're making is a concept, rather than a fact. For example, you may be talking about tough times ahead, so you could show a photo of a rocky road or a steep staircase. * Schematically: If you're talking about a process, you can show it with a diagram or add arrows to point out parts of a photo.