[IxDA Discuss] Graphical methods for displaying time elapsed

Will Parker wparker at channelingdesign.com
Fri Mar 2 10:52:07 PST 2007


On Mar 2, 2007, at 10:29 AM, dnp607 wrote:
> Hi All,
>
> I'm wondering if there are any references out there that discuss
> different graphical methods for displaying time in UI?
>
> The problem: My users will be presented with many alarms over the
> course of a 30 minute time frame. I need to display the alarms (in
> color) in such a way that it gives them a historical perspective of
> 1- When the alarm occurred and 2- What color the alarm was...
>
> So far, I'm contemplating:
>
> 1_  A histogram/strip chart.
> 	Benefits: It's a common method for displaying two axis. Could be
> used for one axis as well.
> 	Drawbacks: Poor discrimination since most lines are bunched together
> tightly. Usually hard to follow for nontechnical users.
>
> 2_ A progress bar (horizontal).
> 	Benefits: Commonly used for displaying progress
> 	Drawbacks: Perhaps too simple - displaying progress is one thing,
> displaying different colored alarms on a progress bar gets cluttered.
> 	Example, where "A" is an alarm with color:
>
> 	* * * A * * A *
> 	<-----Scrolls
>
> 3_ A timed list (vertical).
> 	Benefits: Reads like a log, simple to interpret.
> 	Drawbacks: ?
> 	Example, where "A" is an alarm with color:
>
> 	A Time/Date
> 	A Time/Date
> 	A Time/Date
> 	A Time/Date
>
> ...Are there more? Any comments or suggestions welcome.

Dan:

You mention "many alarms" in several different classes over a 30- 
minute session, and indicate that the user will probably be required  
to simultaneously track both current alarms and past alarms, using  
only a simple graphical display.

That doesn't sound like a pleasant user experience no matter what how  
you design the data presentation, and quite possibly could lead to a  
large number of user errors while using the application. Frankly, the  
experience you describe can and should be better managed by the  
computer. If we're talking about a teenager playing Halo, sure, we  
can just skip to the visual design layer. If we're talking about a  
NASA flight engineer during a shuttle launch, the first priority is a  
discussion of information architecture, with an eye to computer-aided  
maintenance of error states.

Can you provide a _good deal_ more detail on the application,  
audience and functional goals?

- Will

Will Parker
wparker at ChannelingDesign.com
206-228-3187 (cell-preferred)
206-783-1943 (home office)


"The only people who value your specialist knowledge are the ones who  
already have it." - William Tozier




More information about the discuss mailing list