By Liam Simcha at October 28 2018 01:20:18
For a technical writer a flowchart can be a very useful tool to illustrate various operations and processes. Before you start your next project, see if you can illustrate the process via a flowchart. It will make life easier for you and your manager or client. The end result will be a better project which is good for your target audience. Note: Microsoft Visio is a good software for creating flowcharts. If you can write a simple sentence in English and organize your thoughts then technical writing may be a rewarding field. You can easily make it a second income stream in your spare time.
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.
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.
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).