Nine myths about technical writing

• Nobody reads the manuals
      in No one reads technical docs
• Research shows you must use the 7+-2 rule for lists and arranging your information (i.e. if you have more than nine items, split it into two lists)
      in There is an optimum number of steps
• We can design away the need for a user manual and online Help
      in We can design away the need for a user manual and online Help
• If you’re working on an Agile project, you’ll avoid wasted time and effort by leaving the documentation to the end
      in On an Agile project, you’ll save time by doing the documentation last
• If we put out manuals on the Web, our competitors will have an advantage over us
      in If we put out manuals on the Web, our competitors will have an advantage over us
• If we put our manuals on the web, we’ll lose Support revenues
      in If we put our manuals on the web, we’ll lose Support revenues
• Technical Authors want to write too much
      in Technical Authors want to write too much
• Print layouts don’t work on screen
      in Print layouts don’t work on screen
• Everyone will need to move over to the DITA XML standard
      in Everyone will need to move over to the DITA XML standard

Source

Pratt, E. (2012, October 26). Nine myths about technical writing. Retrieved August 9, 2017, from https://www.cherryleaf.com/blog/2012/10/nine-myths-about-technical-writing/