Documentation takeaways from the Boeing disaster

Exit Survey
100%
These two questions -- (1) How does this product differ from other products? and (2) What does the customer need to know? -- are often applicable to my own documentation projects.
I often include comparisons to competitor products in my docs.
I am usually familiar with how competitor's products work and how they are similar or different to the product I'm documenting.
I often describe how the product I'm documenting is similar or different to other products within my same company (not competitor's products).
It's rare that I actually experiment with or use competitor products as I'm documenting my company's products.
Product managers often do not want me to speak plainly about a product's limitations in the docs.
I include a section that addresses product limitations in my docs (e.g., "Known Limitations").
I often spin negatives in more positive ways in docs.
I regularly ask the question, "What does the customer really need to know?" when writing documentation.
I decide what the customer needs to know by evaluating whether the information is necessary for performing a task.
When I have extra information that I want to include, but which I don't think is really necessary, I stuff this in an appendix, collapsed section, less visible folder, etc.
My documentation takeaways from the Boeing disasters are different. Questions I asked were the following:
Powered by QuestionPro Report Abuse
Create Your First Online Survey