Adobe Experience manager

Get new posts delivered straight to your inbox.

Subscriber count: 4,300

Stitcher radio

Search results

Adobe Experience manager

Simplicity in a 550 page manual?

Dec 9, 2010 • general

Simplicity in a 550 page manual?One of my readers, Shweta, asks the following question:

I am a Technical Communicator working in a software services company in India. I have been reading your posts daily from a long time now.

I am developing end-user documentation for an access control product. The current application that I have is huge and so is the user manual (550 pages, which I am sure not even 55 users will read). It also has an over exhaustive online help (not context sensitive, unfortunately). A Quick Reference Guide (prepared for each of the applications; there are 5) is still not sufficient to let the user know everything.

Was wondering if you can guide me on reaching best to the users with simple documents.

I'm opening this up this question to the community for response. You can add your thoughts in the comments below.

Here's my take on this situation.You have the right approach in creating several quick reference guides to accompany the longer, 550 page user manual.

However, don't expect the quick reference guide to cover the same scope as the long manual. There's no way that you'll teach users all they need to know from a 550 page manual in a few quick reference guides. That's not the point of quick reference guides. The point is to help get the user started, to introduce the user to the content in an approachable way. Learning takes place primarily from doing, so the key is to get the user exploring the application quickly. Give them some direction and guidance to begin. That's all a quick reference guide needs to do. See more from me about quick reference guides.

follow us in feedly

Get new posts delivered straight to your inbox.

Subscriber count: 4,300

About Tom Johnson

Tom Johnson

I'm a technical writer based in the California San Francisco Bay area. In this blog, I write about topics related to technical communication — Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, academics, and more. I'm interested in simplifying complexity, API documentation, visual communication, information architecture and findability, and more. If you're a technical writer of any kind (progressional, transitioning, student), be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.