Documentation that conforms to the expectations of genre (often including goals, prerequisite states, action and reaction, and troubleshooting information) makes it easier for people to understand and use.
Reading the competitor's documentation can provide illuminating insights about standard terminology in the industry.
Publishing the docs should kick off the start of an iterative agile approach to docs that mimics a similar process followed with agile software development.
Which information usability principles do you find most compelling or useful?
Do you have any experiences or insights about any of these topics that you'd like to share? 
Powered by QuestionPro Report Abuse
Create Your First Online Survey