Power!
Power user. It’s a term that I don’t like. But there definitely are people out there who are working with the software and hardware that we document who want more than just basic information. Getting them that information can be tricky.

For years, I’ve felt that a manual actually offers very little benefit to power users. Why? Most of them want to quickly and efficiently learn how to carry out an advanced task. Thumbing through a manual or cookbook-like guide slows that process down.

I’ve found that in many cases, documentation for power users should be task based, but also as long or as short as needed. When I say as long or as short as needed, I mean just that. You might have a four or five step procedure. Or, you might have a piece of documentation that contains a considerable amount of overview and expository material interspersed with the procedures.

As for the form that this kind of documentation might take, here are a few suggestions:

  • Knowledge base articles
  • Blog posts
  • Tech notes

If you’re wondering what a tech note is, I define it as a document that’s a cross between a white paper and a knowledge base article. It provides details about an advanced or little-used feature or a function of a technology, along with information on how to use that feature or function.

Regardless of the form that the documentation for a power user takes, you should always keep my one of my favourite and most over-quoted thoughts from Tim O’Reilly in mind:

People are looking for advanced tips and tricks. They’re not looking for the basics. They’re looking for things that will give them more of an edge. And they’re looking for it in a style that’s fun and engaging.

What’s your take on this? Feel free to leave a comment.

Photo credit: dzz from morguefile.com

  • Share/Bookmark

Related posts:

  1. Documentation and its hidden power
  2. Musings on user-generated documentation
  3. Change your writing style to make documentation more usable and user friendly

Related Posts