By Summer Gatenby at January 03 2019 13:06:52
Linear Programming, mathematical and operations-research technique, used in administrative and economic planning to maximize the linear functions of a large number of variables, subject to certain constraints. The development of high-speed electronic computers and data-processing techniques has brought about many recent advances in linear programming, and the technique is now widely used in industrial and military operations. Linear programming is basically used to find a set of values, chosen from a prescribed set of numbers, that will maximize or minimize a given polynomial form and this is illustrated by the finished; the manufacturer knows that as many articles as are produced can be sold.
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.
Flowcharts can be very useful for a technical writer. If you're working on a complex process, a flowchart can show you the various steps involved in that process. For example, you could be working on a manual on how to troubleshoot the Autopilot Flight Director system for the Boeing 747 aircraft. There are various steps involved in troubleshooting this system. Each step has multiple sub-steps. By creating a flowchart, you can quickly see which step takes place at what stage in the process.
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.
The key to process improvement is to clearly communicate process definitions (the way in which the company wants the processes to be carried out) to the people in charge of their execution (through training, process descriptions publication, etc...). The better process participants understand the process definition, the higher the probability that the process is carried out according to it. They are better implemented through obtaining buy-in than through imposing directives.
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.