Your SlideShare is downloading. ×
Technical  tien
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Technical tien

70
views

Published on

Published in: Business, Education

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
70
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Technical Writing Tips and Tricks Technical writing is a fabulous career for anyone who loves research and writing. If you have a degree in accounting, engineering, biotechnology, or computer technology, consider becoming a technical writer (technical author in the UK). You don't necessarily need a degree to become a technical writer but it doesn't hurt. The alternative is to get a technical writing certificate. It's imperative to know how to write for technical and non-technical audiences. If you're able to convey information to both of these audiences, you'll have a successful career as a technical writer. Tech notes Tech notes Blog Technical Writing Tips and Tricks Know your target audience. Are you writing for a technical or non-technical audience? These are two different audiences. One will understand 'technical jargon' and the other won't. Make sure you use verbiage that the end user will understand. What is your writing goal? You can write the most comprehensive manual or users guide but if you get lost in the details, your goal will be lost in translation! Don't get lost in the details. Step back from your work and look at the big picture. Does your writing make sense? Will the target audience understand what you wrote? If focus solely on the details your message will get lost. Review your writing now and again to make sure you're on track with your writing goal. Use examples. Help the end user out by using examples. You may understand the information back and forwards but don't assume the end user will. Provide examples within your writing, especially if you're technical writing is for computer software. Make sure the examples are relevant and the audience can understand them. Give credit to your resources. Do you remember when you had to write research papers and were required to quote sources and provide a bibliography? Make sure you reference any resources you use. Give credit whenever you can. Use visuals. Most people are visual and will appreciate a table of contents, graph, or chart. Use these whenever you can because it will help the end user understand the information quickly. Proofread your work. If you don't have an editor or manager proofreading your work, make sure you proofread. It can be embarrassing for a company to send out a manual or guide that's filled with errors. You'd be surprised by the amount of errors found in newspapers, magazines, newsletters, books, brochures, and other writings. Ask someone to proofread your work to make sure all errors are found and corrected. Have someone review your work. Constructive criticism can improve your technical writing skills. Don't be afraid to get a second opinion. It's good to have a different perspective because you may have missed something or discover a new way of presenting information. Use headers. Headers are a great way to break up your writing and it will make reading a long manual or report easier. Use headers that are relevant to the topic; summarize each section. Stay present. Use present instead of future tense -- it's clear and concise. For example, if you're writing a manual for a TV, write, "Press the Menu Button and Select Language. Choose your language." This sentence gets to the point and the end user immediately knows and understands what to do. Return to Event