Developing Quality Technical Information: A Handbook for Writers and Editors

by Michelle Carey, Moira McFadden Lanyi, Deirdre Longo

The #1 Guide to Excellence in Technical Communication--Fully Updated for Embedded Assistance, Mobile, Search, Multimedia, and More Direct from IBM's own content design experts, this guide shows you how to design product interfaces and technical information that always place users front and center. This edition has been fully revised to help you consistently deliver the right content at the right time. You'll master today's best practices to apply nine essential characteristics of high-quality technical information: accuracy, clarity, completeness, concreteness, organization, retrievability, style, task orientation, and visual effectiveness. Coverage Includes
Advocating for users throughout the entire product development process Delivering information in an ordered manner by following progressive disclosure techniques Optimizing content so that users can find it from anywhere Streamlining information for mobile delivery Helping users right where they are Whether you're a writer, editor, information architect, user experience professional, or reviewer, this book shows you how to create great technical information, from the product design to the user interface, topics, and other media.
Thoroughly revised and updated Extensive new coverage of self-documenting interfaces and embedded assistance Updated practical guidelines and checklists Hundreds of new examples

Genres: Writing, Reference, Nonfiction, Professional Development, Business

624 pages, Paperback

First published October 1, 1997

Reviews

[Wendy]

One of the best books I've come across at addressing the skills and practices that are particular to good technical writing as opposed to good writing in general. Some of the material will seem a bit obvious to the experienced technical writer, but the many examples will be valuable to writers at all levels.

[Robin]

If you are new to technical writing, it would be hard to find a better primer than this one. Brimming with realistic examples and strong opinions (perhaps occasionally too strong?) about exactly what your content and style rules should be, this book crammed a lot of best practices into 541 pages. Even if "in real life" I'll never be able to apply all this great advice and still make my deadlines, I'm getting closer than I otherwise would have.

The book design and layout made me twitch, but that's just my pre-tech writing publishing maven talking, and I have to learn to ignore her now.

[Joanne Cheek]

Bored me to tears. DNF

[Blair]

I like this book on several levels. This book is the standard for what it is teaches for developing good quality documentation: it is easy to use as a reference, with headings and a table of contents that many other technical books would do well to emulate. It clearly explains how to write or techniques to follow to help improve your writing quality, along with the why. It's recommendations are immediately useful.

If I had to choose only one book to refer to on my bookshelf, I'd toss aside my style guides, and keep this nearby.

[Ember DeBoer]

Though I've read an earlier edition of this book, I recently evaluated this one as a replacement to the textbook I'm currently using in my technical writing class. I'm partial to this particular IBM veteran's work. :)

[Evelyn]

Great reference and tutorial for beginning tech writers to seasoned veterans. My team of senior writers with over 15 years; experience found it as valuable as my junior writers.

[Peter Anderson]

A good book for pedants like me :-)

[Sarah R.]

This is a really good reference book for technical writers. We have used it to build out our review checklists and to get cleaner and clearer with our docs.