How to Avoid Information Overload in Technical Writing
Too much information can be as bad as too little information in technical writing. Too little information prevents us from understanding the context and relationships. For example: “The motherboard failed the temperature test.” Yes, but in what way? Did it fail in the lower temperature zone or the high end of it? How long did…
Read More
How not to Sacrifice Clarity to Simplicity in Technical Writing
Introduction Simplicity in technical writing is a mantra frequently repeated by trainers and writing instructors. You’ve heard it many times and in general, it’s true: “Write simply. Eliminate all unnecessary words and facts from your technical writing.” Plain language is of course what we all like. But there are always exceptions in life, including this…
Read MoreHow to Write an "Architectural and Engineering Specifications (A&E)" Document
If you think A&E stands for “Arts and Entertainment” TV channel you’re correct. But it also stands for a frequently used technical document: “Architectural and Engineering Specifications (A&E)“. The adjective “architectural” here of course has nothing to do with buildings. It denotes the way something is designed and structured. It’s used in the generic sense…
Read MorePostmortem Analysis of a Technical Writing Project
© Ugur Akinci A postmortem analysis of any technical writing project is a crucial part of the whole project. It’s the closure that reveals the strengths and weaknesses. After we finish a project we should make a habit of analyzing what went wrong during the project and what didn’t, and how we can improve our…
Read More