CHI-WEB Archives

ACM SIGCHI WWW Human Factors (Open Discussion)


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
1.0 (Apple Message framework v752.3)
"ACM SIGCHI WWW Human Factors (Open Discussion)" <[log in to unmask]>
Cindy Lu <[log in to unmask]>
Sat, 9 Jun 2007 14:26:32 -0400
"Jared M. Spool" <[log in to unmask]>
"Jared M. Spool" <[log in to unmask]>
text/plain; charset=US-ASCII; delsp=yes; format=flowed
text/plain (69 lines)
On Jun 9, 2007, at 1:32 PM, Cindy Lu wrote:

> The key question is how the users scan the data.
> If the data appears with the most likely candidates at the top, the  
> user is likely to scan slowly. In cases like this, the dynamic  
> loading and presentation of subsequent data in the live model can  
> keep up.
> If the user searches a specific item and it happens to be  
> positioned above screen fold, then the user does not have to scroll  
> the table.
> If the user scans items starting from the top and gratually move  
> down, live scroll will help.
> If the user is going to grab the scroll bar to quickly get further  
> into the data set, skipping the initial items without even scanning  
> them, the live model will likely struggle. This would be a scenario  
> where the user is jumping into the data set (say, starting at a  
> specific letter further into the data,) and therefore not  
> interested in the stuff that is initially loaded. In this case,  
> you'd be better off offering an indexed approach to the data.
> I agree.
> However, the struggle we have is that the users' needs of doing  
> tasks on each table is different. For example,
> 1. Search for a specific item by browsing - then view detail, drill  
> down or take an action
> 2. Scan the table to identify the trend or pattern. May view detail  
> on a specific item during the process. If they do it every day,  
> they want to do it quickly
> The challenges are:
> How to meet all the needs, make the table component consistent and  
> make sure the system can respond quickly.

Hi Cindy,

It feels to me, just on what you've written, that you might be trying  
to do too much with a single table. How would you attack the design  
if you had the freedom to come up with completely different solutions  
for each goal of your users? If you could have 'n' designs instead of  
1, what would each of the 'n' designs look like?

By answering that question, you might see a way to produce the  
designs you need with 1 or 2 elements, the table being one of them.

Just a thought,


Jared M. Spool
User Interface Engineering
510 Turnpike St., Suite 102, North Andover, MA 01845
e: [log in to unmask] p: +1 978 327 5561  Blog:

    Tip of the Day: Quote only what you need from earlier postings
     CHI-WEB: POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]