Wednesday, October 18, 2006

Progressive Disclosure and Hierarchy of Information
I am currently working on a wireframe for an embedded help pane and wrestling with the real estate constraints and information-prioritization issues that come with megabytes of information vying for a surface area roughly the size of an envelope.

The obvious solution is to not show everything at once in the panel, but to use the pane as a gateway into the content. Allow the user to navigate into and through the content by progressively disclosing greater detail or related topics.

The UA architectural issue is how to categorize and prioritize information so it can be appropriately displayed and disclosed. This requires that a taxonomy of presentation tiers be defined and that an ontology of pane elements be defined and mapped to the presentation tiers.

Presentation Tiers
Start first by understanding how many layers of presentation options you will use and rank them into tiers. The following is an example of a presentation tier taxonomy:
Tier 1: Information that is displayed upon initial appearance of the pane without any interaction on the part of the user.
Tier 2: Information that is displayed within the original presentation by expanding the content. In other words, the pane's initial information remains, but new information is inserted. For example, a definition could be tier 2 information; the user clicks on a term in the text and the text expands to include the term's definition.
Tier 3: Information that replaces the information in the original pane. In essence, the pane's content is replaced with new content. One could slice this even finer by having Tier 3A that replaces a entire pane's content and Tier 3B that replaces just a section within the pane.
Tier 4: A new window is opened to display the content; the original embedded help pane stays intact.

Ontology of Elements
I just love having the opportunity to use the word ontology :-) I can only hope that I am using it reasonably correctly. I use it in a broad sense to mean what is the furniture, so to speak, you can put into a user assistance pane. The ontology will contain interaction devices such as search criteria entry fields, navigation devices, such as links, and information elements, such as headings, definitions, procedures, multimedia, etc.

This is the part I am working on now, defining that ontology and mapping the elements to their appropriate presentation tier.

Keep posted.

2 comments:

Jeff said...

I'm not even going to attempt to use Ontology as I'll just get myself in trouble.

From a user interaction perspective, I'd be interested in expanding the role of the panel as an extension of the parent application. This of course leads to needing to understand more about the expectations between interactions that the user may take in the pane and it's updating of the parent application.

For instance, if the parent application is some type of budgeting tool and the user is trying to figure out what to set their spending limit for groceries. The panel would appear providing your Tier 1 information with the option to show "what was my spending last month for groceries. Then it would move to tier 3 with a worksheet with the spending amounts for groceries of different periods in time. At this point the user would be provided with the ability to say 'use this value' for each choice and the parent client is then updated with this information.

So I think it would follow the same pattern that you are developing and complementing the help with data interaction within the panel.

Mike Hughes said...

Wow-that certainly opens up the field. I've been thinking about the embedded user assistance pane merely as an interactive information delivery area, you expand it in your example to be a secondary or support interactions/data-manipulation device. One would have to manage the ambidexterity (the area having two functions) so that its support functionality isn't lost to the user who doesn't "go to the help".