Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I'm building an event notification system for a PC browser. The events queue up on screen on top of each other, until you "acknowledge" or "dismiss" them.

The information I need to display is:

  1. Ok Button
  2. Acknowledge Button
  3. Category of event
  4. Time
  5. Event Description

Here's what I have so far:

What I have so far

I'm not really sure how I should layout or present this information within the boxes.

Do you have any suggestions - or are there any precedents I could imitate?

--UPDATE--

Your comments are all MUCH appreciated. A little more context:

  • The notification system will be used by a small number of system admins for a real time business system, and possibly also be displayed on a tv somewhere, like a "system status" sort of thing. They will typically need immediate attention.
  • The categories will be quite fine grained, there will be maybe 20 or 30 of them, so that whole categories can easily be ignored by going to the settings page.
  • "Acknowledge" will turn the message orange and sink it to the bottom (or something like that maybe?). Just so they know someone has seen the message and is working on it. "Ok" will remove the notification.
share|improve this question
4  
How is behaviour different between acknowledgement and OK? –  Aadaam Aug 10 '12 at 7:40
1  
most sysops are used to familiar layouts such as unix/linux/webserver logs. structured usually like date, time, short descriptor, longer message, event code. Then your buttons can follow. You're on the right track. –  Chris Aug 10 '12 at 7:47
3  
I don't think making the messages all red helps. It makes the whole thing scream, but harder to read. You could make the signalling much more subtle without loosing it completely, for instance by using a red dot in front of the row. Also sorting failure events before warning events will already make them more noticable. –  André Aug 10 '12 at 7:56
1  
You really need to give us context. What's the type of issues you're reporting on? When will people be seeing them? How do they go about diagnosing them? etc. etc. –  Jimmy Breck-McKye Aug 10 '12 at 9:55
    
I'm with Jimmy on this one. Are those notification all critical and important? Do they need immediate attention from users, if not, then red color is not the best choice for background. –  Michael P. Aug 10 '12 at 15:35
add comment

1 Answer 1

up vote 4 down vote accepted

Without knowing more about the context, here are a few tips to get you started.

  1. Ok/Acknowledge button. Having both is confusing. What is the difference?
  2. Buttons. Alight to the right. This assumes that the user would want to take in the details before acknowledging the item. Also, it is a commonly used practice.
  3. Category. It depends on what they are. However you could group by category. E.g. All urgent items on top. Alternatively you could display the category after the title. What does the category add to the information given?
  4. Description. This is often good to place on the left. This allows the user to scan through the items more easily. This assumes that the description is the core differentiator. If you placed the category to the left you will have a lot of messages that look the same initially until they read more of the the details. e.g. Instead of starting each with 'Event failure, event failure, event failure' you could have a label before the group of 3 or start with the description then a more subtle suggestion that this is an event failure.
  5. Time If the sequence is important the user might want to scan through the times to see when each happened (or how close etc). Therefore they should be aligned to allow this. Right aligned seems to be a trend. You may have this with less emphasis than the description though.

I've had a go at wireframing one of these options:

Alert list

  • You could save space by having the icon within the alerts and getting rid of the category titles.
  • The checkbox on the right is a guess at the functionality where the user is required to acknowledge the alert.

This example shows a more compact approach. The second part demonstrates a more subtle approach to categories (but beware of what needs attention - see the 2nd item in the list!)

Alerts 2

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.