By Summer Gatenby at November 23 2018 11:28:02
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.
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.
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.
How to create a flowchart When you're working on a complex project, creating the flowchart itself may be a time-consuming task. Here are six simple steps you can follow to create even complex flowcharts: Start by defining the end result of the process or project. The end result could be anything such as completing a user manual, writing a complex software process, installing a new part, or performing a test. List the various steps involved to achieve the end result. This will take some research. In complex processes, each step could have a series of sub steps. The steps involved to create a user manual could be: a. Meet with SME ; b. Research existing documentation ; c. Videotape the procedure ; d. Take photographs ; e. Create illustrations ; f. Develop the user guide ; g. Test the user guide ; h. Make changes/adjustments ; i. Deliver final product.