Contribute in GitHub:
Open doc issue|Edit online
Content Quality
Content Standards
Introduction
Standards driving the quality characteristics for IBM content contributors and professionals.
IBM Quality Standards Slack
Join us on the IBM Content Quality Slack channel: #content-quality
Note: Content quality for technical information spans a wide range of topics. A substantial portion of this section provides an abridged version and excepts from Developing Quality Technical Information: A Handbook for Writers and Editors. This book, published by IBM Press, was written by IBM content design experts, published by IBM Press, and also available from major retail and online bookstores (ISBN-13: 978-0-13-311897-1 and ISBN 10: 0-13-311897-5). An electronic copy is available online from Safari Books. To access Safari Books Online, log in with your IBM intranet user ID.
Quality Standards Overview
Quality is ultimately determined by users. When users have questions and quickly find the exact information they need, they perceive the product (and the information, though they don't distinguish between the two) as being of high quality. In fact, an overwhelming majority of customers report that information quality both affects their view of the product quality and their overall product satisfaction. Information quality also has a significant impact on customers’ buying decisions.
Almost always, users seek answers to specific questions and don't want to read a book from beginning to end to find those answers. Quality information addresses users where they are, for example, in the user interface. That quality helps them accomplish real goals rather than forcing them to figure out how to accomplish their goals in the product.
Content that focuses on domain expertise, provided by experts in the field based on their experience and judgement, is the most highly valued content today. We can already see the beginning of another technical communication transition toward artificial intelligence, and our role in gathering real domain expertise for users becomes critical. Think of voice-driven assistance that provides real-world information about proximity to gas stations with the lowest prices or guidance for how to choose the right app from an online store. In these situations, the writer is the trusted colleague or the concierge, directing users to exactly what they need at that moment.
Technical writers must be the users’ advocate throughout the product development process. Ideally, writers have access to users throughout that process, but user engagement alone cannot ensure information quality. Writers must apply their own skills and expertise based on solid research and proven methods.
Quality characteristics for technical information must reflect what users expect and want from the information. Based on comments from users and on experience in writing and editing technical information, the authors of this book have found that quality technical information has the following characteristics.
Easy to Use
| Category | Description |
|---|---|
| Task orientation | In the context of a product, a focus on helping users do tasks that support their goals |
| Accuracy | Freedom from mistake or error; adherence to fact or truth |
| Completeness | The inclusion of all necessary parts—and only those parts |
Easy to Understand
| Category | Description |
|---|---|
| Clarity | Freedom from ambiguity or obscurity; using language in such a way that users understand it the first time that they read it |
| Style | Correctness and appropriateness of writing conventions and of words and phrases |
Easy to Find
| Category | Description |
|---|---|
| Organization | A coherent arrangement of parts that makes sense to the user |
| Retrievability | The presentation of information in a way that enables users to find specific items quickly and easily |