By Elizabeth Spain at November 18 2018 10:38:43
According to the U.S. Department of Labor, the average salary for technical writers is $60,380. Freelance technical writers can make from $30 to $70 per hour. The field of technical writing is like a golden city. It's filled with wealth, rewards and opportunities. After learning technical writing you can branch out into business writing, marketing writing and communications writing. All of these can become additional income streams. But to succeed you must learn how to market yourself to clients. You have to prove to them that you are an invaluable asset. That's where ProTech - Your Fast Track to Becoming a Successful Technical Writer can help. It's a technical writing course that does two equally important things :
Define the starting point of the process of project. This is the first step that starts of the process. For example, the first step could be project planning or research. Write down the starting point and the end result. Both of these should be in boxes with some space in between them. Adjust this space according to the number of steps and sub-steps involved in the process. Draw an arrow from the starting point to the end result. Along this arrow, list the various steps in order that are needed to go from the starting point to the end result. Include any sub-steps as needed.
Diagrams : A diagram can show a process, hierarchy, or other relationships. You can use AutoShapes and arrows, the flowchart shapes with connectors (in the Lines category in PowerPoint 2007; otherwise in the Connectors category), or the SmartArt feature of 2007. Charts/Graphs : Charts (also known as graphs) visually display data, especially data showing a trend. Use only the data that supports your point, not all the data in the Excel spreadsheet where you got the data. If the data is too complex, it won't be comprehensible on a slide. What to do? Print it out and give it to the audience as a handout.
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.