Remember Me
forgot your password?

Great Technical Writing: Improve your Readers' Access With a Visual Index

OVERVIEW

People are visual creatures. They look at your product, and see, for example, a button or display. They want to find out about that control or indicator. A Visual Index is a simple but powerful document access tool that enables your Readers to find the information that they want.

This article describes the Visual Index concept and tells how to create one for your document.

A VISUAL INDEX

A Visual Index is a picture of your product or process with links to the relevant information in the related document. Using a Visual Index, your Readers can look at the picture, and quickly jump to the place in your document that describes the item of interest.

Your document may include several Visual Indexes (the plural of "index' is "indexes" not "indices").

STARTS WITH A PICTURE

The Visual Index starts with a picture of your product or process. There are various kinds of pictures to use, based on the product type:

* Physical Product (for example, a barbecue or video disk recorder)
Pictures of the product (all relevant views).

* A Procedure or Process: A flowchart of the steps and decisions in the procedure or process.

* Software Product 1: Screenshots of the software.

* Software Product 2: Before and after images of the work that the product does.

* Organization: An organization chart.

LABEL THE PICTURE

Label all the User-Product Interaction Points (U-PIP) on the picture. A U-PIP is anywhere that your User and the product may interact. U-PIP's include controls, displays, and relevant physical features of the product (such as handles, latches, etc.). Provide a meaningful (to your Reader) label (name) for the U-PIP. (Use that same exact label everywhere you refer to that U-PIP.)

Aside: If your product uses sounds to inform the User, then include a table of those sounds, what they mean, and a link into the relevant area of your document (describing the sound).

LINK THE U-PIP's TO YOUR DOCUMENT

Up to this point, the Visual Index is just like any well-labeled picture of your product or process. However, when you add links into your document, the well-labeled picture becomes a Visual Index.

The link should be to a section of your document that you believe your reader would most want to reach to get the information about that U-PIP. (This is a fundamental question whenever you create an index: "does my reader want to come to this place in my document for this item?")

Your method of adding links to the picture depends upon the publishing mechanism for the document. If the document is published as:

* A Printed document, then use page numbers for the links;

* An Electronic Document, then use hyperlinks that a Reader can click on to follow. If the document is published as HTML, then the visual index can be an image map.

EXAMPLE 1: A PAIN IN MY FOOT

I have a pain in my foot when I walk. If I go to a website about feet, it would be very efficient for finding out about my pain, if I could see a picture of a foot with various areas where the pain could be. Links from the foot areas to specific web pages would enable me to find the information about my specific foot pain quickly.

EXAMPLE 2: PHOTO CORRECTING SOFTWARE

Show a picture with the errors that your software can handle, before and after correction. Here the U-PIP's are each of the photo errors.

EXAMPLE 3: A COURSE ON WRITING USER DOCUMENTATION

The Visual Index is a flowchart for creating the User Document. Since the Course is presented in HTML, the Visual Index is made from an image map, with hyperlinks into the sections of the Course relevant to each item in the flowchart.

BOTTOM LINE

A Visual Index is a simple concept. But like many simple concepts it is very powerful. Try to include one in your next document. You'll be doing your Reader a great service.

Barry Millman

Barry Millman, Ph.D., has a Bachelor of Science in Electrical Engineering (1966, Carnegie Institute of Technology) and an M.Sc. and Ph.D. in Psychology (Human Information Processing, University of Calgary). He has been a consultant for over 25 years, an instructor, course developer, and award-winning speaker. For the past seven years he has been researching and creating resources to help organizations create great User Documents.

Visit: http://www.greatuserdocs.com/ for resources to help you create the User Documents that your Product needs and your Users deserve.

Visit http://www.greatuserdocs.com/ReadingRoom.htm for more articles like this one.

Rate this Article: 0 / 5 stars - 0 vote(s)
Print Email Re-Publish

Add new Comment



Captcha

  • Latest Non-Fiction Articles
  • More from Barry Millman

In Bible versus Quran: Nehemiah was cruel with those who married foreign women?

By: Prof.dr. Ibrahim Khalil | 03/01/2010
In the Bible, Nehemiah said: And I contended with them, cursed them and made them swear by God, saying, ye shall not give your daughters unto their sons, nor take their daughters for your sons, or for yourselves. In the whole Quran, the expression "foreign woman" is not mentioned therein; all women are equal in their rights regardless of race, color, location etc.

“Well, to be Honest, I threw It Away”

By: John J Souza | 03/01/2010
The importance of getting a good education.

Confessions of an Elevator

By: ANANT BAIJAL *VIT | 01/01/2010
The article is on what our university Elevator (Lift) would have to say about its life.

"Trains"

By: John J Souza | 29/12/2009
About a boy growing up around trains and fond memories of time spent with his mother.

In Bible versus Quran: All had married foreign wives and had children by them

By: Prof.dr. Ibrahim Khalil | 27/12/2009
Upon citing the Tribes even the Levi, 15 families and group of people even the singers and of the porters and 111 men, the Bible says that all these had married foreign women, and some of them had children by these wives. This story and statistics in addition to the term "foreign women" are not mentioned therein in the entire Quran.

Writing for the passion of writing

By: Cheryl Barnette | 25/12/2009
My interpretation of a life beginning from early years about being in love with the written word and writing.

USMAN DAN FODIO AND THE BIRTH OF GOMBE

By: AYOOLA AKINKUNMI OLAMIDE | 24/12/2009
This article is one of the topical issues in Nigeria.The Fulani Jihad of 1804 that led to the placement of Fulani hegemony in the northern Nigeria, as well as the birth of Gombe, one of the Northern States in Nigeria of today.

Christmas Jokes, Games & Best Xmas Party Ideas - Guaranteed Laughter With This Festive Antic

By: Brent Blackwell | 24/12/2009
Why is it so important to tell jokes or crack a gag for laughs at Christmas? Is this not already a time where folk jolly themselves and laughter naturally fills the air? Yes indeed it is, and does, but what harm can it possibly do to add more fun to your festive agenda you have planned for family and friends. Although Christmas is a known time for telling jokes, it is also a time when you could offend with your ...

Great Technical Writing: the User-product Life Cycle - a Documentation Tool

By: Barry Millman | 29/10/2007 | Non-Fiction
The User-Product Life Cycle (U-PLC) is a powerful tool for the User Document writer. Use the U-PLC to generate the high-level topics for your User Document.

How Poor In-house User Documents Cost you Twice & What to Do About it

By: Barry Millman | 31/07/2007 | Writing
Many organizations produce in-house tools or modify commercially-available tools for their own use. These tools should get documented so they are of use to others in the organization. If this documentation is not created or is poorly written, it costs you twice.

Great Technical Writing: User Document Headings Should be Guideposts, not Advertisements

By: Barry Millman | 28/06/2007 | Non-Fiction
Most heading are designed to entice us to read further. Headings in User Documents should enable your Reader to decide whether or not to continue reading that section. Use effective headings to make it easy for your Reader to access and understand your User Document.

Great Technical Writing: Improve your Readers' Access With a Visual Index

By: Barry Millman | 06/06/2007 | Non-Fiction
People are visual creatures. They look at your product, and see, for example, a button or display. They want to find out about that control or indicator. A Visual Index is a simple but powerful document access tool that enables your Readers to find the information that they want. This article describes the Visual Index concept and tells how to create one for your document.

Benefits of Creating User Documents In-house

By: Barry Millman | 09/05/2007 | Non-Fiction
For small companies, creating their product's User Documentation in-house, provides benefits to the company, to (idle) staff, and to the product. This article describes the benefits and some downsides of producing User Documents in-house.

New Technical Writer: Avoiding the Interview-writing Disconnect

By: Barry Millman | 16/04/2007 | Interviews
Lost or garbled information is a terrible waste. Especially if it's the information you gathered from an interview and must now write into your User Document. Here's how to prevent that waste.

New Technical Writer: Don't Confuse your Reader With your Words

By: Barry Millman | 23/03/2007 | Writing
Stop confusing your Reader with the words you use. Your Reader is trying his/her best to understand how your product works without having to figure out your writing. Here are some writing guidelines to help you stop baffling your Reader.

Submit Your Articles Free: Signup
Article Categories




Use of this web site constitutes acceptance of the Terms Of Use and Privacy Policy | User published content is licensed under a Creative Commons License.
Copyright © 2005-2008 Free Articles by ArticlesBase.com, All rights reserved. (0.21, 6, w3)