By Olivia Giles at November 08 2018 02:02:30
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.
In the last few years a lot has been written about Business Process Management, and about technologies supporting it such as BPMS, SOAP and Web Services. Most of these theories, tools and techniques refer to processes of a highly structured nature. Typically, BPM theorists and practitioners have focused on highly structured processes, like back-office processes of industrial or administrative nature. These processes are highly standardized and repeatable, produce a consistent output and are likely to be automated in part or end-to-end (STP).
It is extremely important to continuously improve knowledge processes, by creating an environment through which they can evolve. This can only be achieved through coordination of diverse disciplines such as knowledge management, change management, expectations management, etc... It is crucial to establish an adequate process context (the combination of technologies, procedures, people, etc... that support the processes). The process context must incorporate feedback mechanisms, change evaluation procedures, process improvement methods and techniques and must be flexible, in order to be able to incorporate enhancements in an agile but controlled way.
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.