Guide to writing a classic technical document

Sundaresan Anandan - Sep 20 - - Dev Community

Recently I read some articles ๐Ÿ“ฐ about how organizations are converting boring and dull technical documents ๐Ÿ˜ด into classic ones ๐Ÿค‘.

Here are my takeaways:

1) Identify your right set of audience ๐ŸŽฏ: Think you designed some amazing fashion clothes that look stunning, but you put those advertisements in some restaurants, so youโ€™re trying to reach the wrong set of audience. So always identify your audience and carefully craft a document.

2) If possible, utilize the data ๐Ÿ“Š: There are some applications which can provide numerous numbers of analytical data amounts, like how long the reader reads the document and where exactly he stopped scrolling. Using those data points, identify the interesting part of the document which your audience likes the most.

3) Write simple and clear ๐Ÿ“œ: Try to avoid the use of complex words which are hard to understand by users. Use the standard word format like Time, New Roman, Calibri and avoid the zombie word format.

4) Get it reviewed โœ…: Many articles forget to do this step. As creators of the document, we tend to imagine our article is well crafted and prone to mistakes. So, in reality, there can be something which we are not aware of. So, get that reviewed by some team members.

Let me know your thoughts about this article ๐Ÿค”

Thanks for Reading ๐Ÿ˜€

.
Terabox Video Player