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.
- Audiences are static
- Avoid repetition
- Be careful about having a blog, because all employers will read it
- Design doesn't matter
- Different floats should be numbered independently
- Documentation review can wait (until after more important tasks)
- Everyone will need to move over to the DITA XML standard
- Foreign language terms should be italicized
- If we put our manuals on the web, we'll lose Support revenues
- If we put out manuals on the Web, our competitors will have an advantage over us
- It is better to omit information about any product limitations from technical documents
- It is better to put all technical information about a product into one document
- Minimalism means using as little text as possible
- Myths aren't always false
- Never use citations as nouns
- On an Agile project, you'll save time by doing the documentation last
- Only key features of the product need documentation
- Paper structure is rigid
- Print layouts don't work on screen
- Product features must be listed in order of importance
- Programmers can't write
- Providing documentation in English is sufficient
- Readers don't use the table of contents, they just search
- Sans serif fonts are always more legible online
- Sentences should be kept short
- Single-sourcing means publishing your print documents online
- Single-sourcing success just requires the right tool or technology
- Software products are documented like hardware products
- Technical Authors want to write too much
- Technical documentation is an insignificant part of product development
- Technical writers are not necessary because the SMEs can write
- Technical writers are not necessary during the product development phase
- Technical writers are not paid well
- Technical writers just write
- Technical writers only write about highly technical, scientific, technological, medical, or systematic topics
- Technical writers should type quickly
- Technical writers write only user manuals
- Technical writing academics are disconnected with the profession
- Technical writing has a very rigid structure
- Technical writing is just listing product features
- Technical writing must be objective
- The passive voice is to be avoided
- There is no career growth for a technical writer
- Today’s younger generation doesn't read
- Two columns are better than one
- Usability testing is prohibitively expensive and difficult
- We can design away the need for a user manual and online Help
- Writers can't code
- Writing happens as fast as reading
- You must have a bachelor's degree to become a technical writer
- You need a high command of English
- You need inspiration to write
- You need technical writing samples to get a job in technical writing
To view the comments, you must first consent to participate in our study.