Write clearly, using words the audience understands.
She talked about the fundamentals that lay at the core of Technical Writing. The focus was on what process is followed, what are the right questions to be raised, how well the information is analyzed rather than any particular tools or domain.
She discussed 10 Golden rules that work for all types of TC projects and provide a practical methodology. So its important to write correctly, proof read and edit the documents properly and provide a proper structure to the content.
Lets see why is it so important…. Quality states the measure of accuracy absence of errorslike typos, spellings, punctuations, incorrect data.
Usability defines clear and accurate information. Is the content standalone? Do you understand what you are writing? Is the information misleading or ambiguous? Get your grammar and punctuation rules correct so as to give logical explanations to developers.
Know you Audience Who is the user, its essential to know who is going to use the document, include demographics, take into consideration the technical and product knowledge of the users, analyse the language skills of the users.
Ask yourself Are you communicating to existing users, experienced users, novice users. How users are consuming the content, online, printed, and so on.
Does the documentation takes care of special needs of a percentage of audience, such as color blindness? Are you adapting yourself to the type of audience. It tells you how good or bad is your writing and does it match the learning level of your audience.
Check out FOGG Index Do you engage with tech support to find out the pain points, how good is the content, what is working for the user what is not working. Are you taping other internal resources like marketing team to get feedback on the user docs. Engage with the customer. Highlight Hazards Watchout for things that need special attention of the user, Figure out the pain points, high risk things and use proper means to clearly specify the hazard.
As a Technical Writer your job includes: Finding hidden hazards through scenarios. Use a ranking mechanism to differentiate types of severities Danger Warning or Caution or Attention Note Make hazard visually clear by placing it at the right place.
Break it Out Do you know 7 years ago it was known that users spend 30 secs on a page to look for information.
What can you do? Keep the sentences short. Think visually and reduce the text, use graphical illustrations if useful Provide structure to documents, use headings, bullets, Include tables, Steps, Flowcharts for decision making and branching options in a process.
Think about the way people need information text, non-text. Important to know the product you are writing about.
Do not rely on second hand information. Explore the product, see it, use it, touch it because if you cannot perform the action you are writing you cannot explain it correctly. Ask open ended questions to get the right information from the SME.New Look at Grammar Basics for Technical Writing Fraser Hannah - 01/30/ - 1 Comment Of all the arguments technical writers enjoy having, few beat the ones about grammar for .
Here are some general rules in tech writing: Tech Writing is Correct. This is the most important (but not the only) characteristics of technical writing. No matter what else it is, a technical document first of all needs to be CORRECT and ACCURATE. If it’s not correct, nothing else matters.
Technical writing is any written form of technical communication used in a variety of technical and occupational fields, such as computer hardware and software, engineering, chemistry, aeronautics, robotics, finance, consumer electronics, and biotechnology.
Rules in RULES IN TECHNICAL WRITING Capitalization * Capitalize the first word in declarative, interrogative, imperative and exclamatory sentences. * Capitalize the first word in interjections and incomplete sentences. * Capitalize the first word in a quotation if the quotation is a complete sentence.
Feb 03, · Filed Under Communication, Golden Rule, Technical Communication, Technical writer, Technical writing, technology, videogames, Writing and Editing It was a refresher to spend a friday evening listening to Leah Guren sharing her insights acquired from a 30 year old career in Technical communication.
Write clearly  |George Orwell's general writing rules work for technical writing. Never use a metaphor, simile, or other figure of speech you are used to seeing in print. Never use a long word where a short one works.