Design & Iterations
Interaction design
With an understanding of agents’ daily work and priorities, I designed the interaction of each kind of notifications, presented as cards, within each location of navigation. I made major decisions around:
• How each type of notification works and behaves.
• How notifications interaction impacts other Dashboard and the Bell dropdown (notification history) UI elements.
• How to show a limited number of notifications and the logic for when they get refreshed.
• How notifications get dismissed.
Individual notification templates
Next step is to design modular templates for each type of notifications. I first designed a few versions of each notification card, then fit multiple of them into the dedicated space on Dashboard (both desktop and mobile) to assess their appearance.
When agents log in to the portal dashboard, I aimed to prevent cluttering the space above the fold, ensuring visibility of other vital sections like data tables and snapshots. Consequently, the space allotted for each notification is limited. The primary design challenge was making notifications easy to skim in this confined space across various viewports, demanding each card to deliver key information and call-to-action concisely to fit its space.
1. Updates
Iteration: The notification card is full of information and links asked by the PM, which can be distractive to users to find real important things; it also didn’t help to reduce the size of each card, which can end up cluttering the dashboard.
(iterations)
To improve these issues, I decided to only include info and links that are closely relevant to the type of notification, adjusted font size and weights to show better information hierarchy and tried more ways to reduce the space each UI element takes.
Shipped version:
• This section shows all auto-generated alerts triggered by updates in the system.
• This section only shows 3 alerts at a time. Prioritize showing critical rated alerts, once they are all dismissed, show less critical - non critical alerts.
• Users can choose to click any links / buttons to check specific info related to the alert or take actions.
2. News
Iteration: The goal in designing this section was to maintain a similar height as the Updates section while displaying as many news tiles as possible. After experimenting with various design patterns and getting inspirations from news websites, I found that the carousel pattern does the best job.
(iterations)
Shipped version:
• This section shows all auto-generated alerts triggered by updates in the system.
• This section only shows 3 alerts at a time. Prioritize showing critical rated alerts, once they are all dismissed, show less critical - non critical alerts.
• Users can choose to click any links / buttons to check specific info related to the alert or take actions.
3. Announcements
Iteration: Initially, I placed this section above Updates and News, considering the importance of these announcements for users. However, after consulting with stakeholders, I received advice to make it less prominent since the information doesn’t directly contribute to the agent’s work. Taking inspiration from e-commerce websites, I created a top banner for these announcements, ensuring visibility at all times without disrupting users' workflow.
(iterations)
Shipped version:
• Top bar of the page holds 3 types of notifications : Emergency alert, 3rd party Maintenance updates, Office closures / Holiday Hours.
• When user log into the portal, these alerts will show up first in Override format. When the override is closed the alert will show up here.
4. Notification history dropdown
Iteration: This is where users can view all past notifications. Given the time-sensitive nature of notifications and to keep the feature simple, I decided to retain notifications for the last 30 days only. This ensures the dropdown has ample space to accommodate all notifications, eliminating the need for users to manually clear or delete old ones.
(iterations)
Shipped version:
• The section is divided into 3 categories: Book of Business; General Notices; Agent specific.
• Unread notifications will be indicated. Users can also filter out messages that have been read.