TC Myths TEST

All technical communication myths in place.

These myths have been identified, but they do not have a complete description, yet.

If you’d like to contribute to an unfinished myth, go to that myth topic and leave a comment.

If you don’t see your favorite myth listed here or on the home page, add a new myth.

  1. Design doesn't matter
  2. Everyone will need to move over to the DITA XML standard
  3. Foreign language terms should be italicized
  4. High school or college English class is enough
  5. If we put our manuals on the web, we'll lose Support revenues
  6. If we put out manuals on the Web, our competitors will have an advantage over us
  7. It is better to omit information about any product limitations from technical documents
  8. It is better to put all technical information about a product into one document
  9. Minimalism means using as little text as possible
  10. Myths aren't always false
  11. Never use citations as nouns
  12. On an Agile project, you'll save time by doing the documentation last
  13. Only key features of the product need documentation
  14. Paper structure is rigid
  15. Print layouts don't work on screen
  16. Product features must be listed in order of importance
  17. Programmers can't write
  18. Providing documentation in English is sufficient
  19. Readers don't use the table of contents, they just search
  20. Sans serif fonts are always more legible online
  21. Sentences should be kept short
  22. Single-sourcing means publishing your print documents online
  23. Single-sourcing success just requires the right tool or technology
  24. Software products are documented like hardware products
  25. Technical authors want to write too much
  26. Technical documentation is an insignificant part of product development
  27. Technical writers are loners
  28. Technical writers are not necessary because the SMEs can write
  29. Technical writers are not necessary during the product development phase
  30. Technical writers are not paid well
  31. Technical writers just write
  32. Technical writers only write about highly technical, scientific, technological, medical, or systematic topics
  33. Technical writers should type quickly
  34. Technical writers write only user manuals
  35. Technical writing academics are disconnected with the profession
  36. Technical writing has a very rigid structure
  37. Technical writing is just listing product features
  38. Technical writing must be objective
  39. The passive voice is to be avoided
  40. There is no career growth for a technical writer
  41. Today’s younger generation doesn't read
  42. Two columns are better than one
  43. Usability testing is prohibitively expensive and difficult
  44. We can design away the need for a user manual and online Help
  45. Writers can't code
  46. Writing happens as fast as reading
  47. Writing style doesn’t matter as long as the content is accurate
  48. You must have a bachelor's degree to become a technical writer
  49. You need a high command of English
  50. You need inspiration to write
  51. You need technical writing samples to get a job in technical writing

Comments are not currently enabled on this site.