2024
Designing a Controlled Notification Architecture for Multi-Source Fleet Ecosystems
Reducing notification fatigue while helping users focus on what matters most
A leading truck and bus manufacturer wanted to improve how notifications were managed within its fleet management platform. As the platform grew, notifications started arriving from multiple systems and vehicles, making it harder for fleet managers to distinguish critical alerts from routine updates. The opportunity was to create a notification experience that improved visibility, reduced information overload, and gave users more control over how and when they receive updates.
This project focused on transforming notifications from a simple alert list into a more structured and manageable communication system.
Project: Fleet Management Platform
Role: UX Designer (Interaction Design)
Focus Area: Fleet Vehicle Details Experience
Duration: 2.5 weeks
Heading / Headline
Business Goal
The primary objective was to increase operational efficiency and safety by reducing notification fatigue for fleet managers. By transforming a cluttered alert system into a streamlined communication hub. The project aimed to improve response times to critical vehicle updates, minimize the risk of missed information, and enhance overall user engagement with the mobile platform.
The Challenge & My Role
Fleet managers were experiencing "information overload," struggling to distinguish between routine updates and high-priority alerts. With no existing way to filter or manage the influx of data, critical vehicle notifications were frequently overlooked. The challenge was to design a sophisticated notification architecture that balanced high-volume data delivery with user control and visual clarity.
As the UX Designer, my responsibilities included:
-
Collecting and consolidating interviews results of fleet managers and truck drivers to identify pain points in the current alert workflow.
-
Redesigning the notification panel to introduce a clear visual hierarchy and distinct categorization.
-
Developing a "Notification Setup Channel" to empower users with granular control over their alert preferences.
-
Ensuring the new system effectively highlighted critical updates while reducing overall cognitive load.
How it started
Analyzing Existing Notification Trigger Points
To understand the current notification landscape, I interviewed an experienced technical architect to identify all existing system communication trigger points. Subsequently, I conducted an open card sort with the Product Manager and Tech Lead to categorize these diverse trigger points originating from multiple sources.
Heading or headline
SUB HEAD
Where to start? - Strategy & Rapid Execution
With a high-stakes, two-week deadline, we chose a "Music App" concept to demonstrate the system's versatility across Web, Native, and HMI platforms.
Caption text
SUB HEAD
Analyzing Existing Notification Trigger Points
General Research says that frequent notifications significantly increase cognitive load (by 37%) and reduce task completion efficiency (by 28%).
To address this, I proposed a system to control and categorize incoming notifications, delivering them to the user's platform in a timely manner. This system empowers users with control over their notification preferences, ultimately reducing cognitive burden and improving efficiency.
For non-time-sensitive alerts, we implemented a batching technique
to consolidate them into a single, digestible summary, reducing notification fatigue.
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
SUB HEAD
Understanding and Designing Notification Patterns
Analyzing notification patterns across major operating systems (iOS, Android, Windows, macOS) and popular applications (social media, communication, productivity) revealed significant complexities. Initially it looked simple, but digging deep into its patterns wasn't that easy, each platform exhibits unique communication patterns.
Caption text
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
Caption text
SUB HEAD
Notification Placement
Previously, the notification list was located on the mobile tab bar. However, through research into intranet application patterns, I determined that placing a bell icon on the App Bar would offer a more consistent and intuitive user experience, aligning with common web pattern.
Caption text
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
SUB HEAD
Empowering Notification Control
Research says 55% of users found notification overwhelm as a reason for primary digital detoxes and 71% users uninstall apps due to excessive alerts.
Keeping that in mind we implemented granular user controls where users can now customize notification types, channels, and frequency (instant, daily/weekly digest), while ensuring critical alerts, like battery charge failures, remain unskippable
Caption text
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
Caption text
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
SUB HEAD
Communicating Notification Management
To inform users about managing notifications, we chose to highlight options with a tooltip after multiple notifications (Option 2) over onboarding setup (Option 1) This ensures users grasp notification criticality before being prompted for preferences reducing the likelihood of them overlooking crucial information during initial onboarding.
Caption text
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
SUB HEAD
Reusable Component Design
Based on extensive notification pattern research, I designed a simple, reusable component and tried to avoid complex patterns that can save time & money. It helped me focus more on component usage rather than complex pattern variants.
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
Caption text
SUB HEAD
Additionally, I created detailed documentation outlining floating notification patterns for both iOS and Android.
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
Caption text
SUB HEAD
Streamlined Developer Handoff
Recognizing the development team as key users, I created detailed handoff documentation including comprehensive navigation flows. This initiative effectively bridged communication gaps and provided seamless design support to developers. The documentation also served as a valuable reference for Business Analysts, Product Managers, and the Quality Assurance team.
SUB HEAD
Building the base variable/token architecture
The backbone of this project was the token strategy, and multi-brand with device scalability was the key challenge. On researching and studying the big companies design system and their structure, I tried to performed the below activities with team in establishing the base variable-token architecture.
Caption text
As this is still under development, we don't have analytical data yet.
The proposed notification architecture helped establish a more structured and user-centered communication model
-
Better visibility for critical alerts
-
Reduced notification fatigue through categorization and batching
-
Greater user control over notification preferences
-
Improved discoverability of important updates
-
Consistent notification patterns across the platform
-
A scalable foundation for future communication features
Most importantly, the experience helped shift notifications from being a source of distraction to becoming a more meaningful and manageable part of daily fleet operations.
Outcome
We can think of leveraging Generative AI (GenAI) to intelligently summarize incoming alerts, updates, and announcements, prioritizing them based on user-defined importance and real-time context. This will provide fleet managers with highly condensed, actionable insights, further reducing cognitive load and ensuring focus on the most critical information.
What's Next? — Future Enhancements - AI-Powered Notification Summarization
-
Not All Notifications Are Equal: Treating every alert with the same importance creates noise. Categorization helps users focus on what truly matters.
-
Placement Influences Behavior: Even a small decision, such as where a notification icon appears, can impact discoverability and usability.
-
User Control Builds Trust: Giving users control over timing and delivery preferences helps reduce fatigue without sacrificing important information.
-
Simplicity Scales Better: Reusable notification patterns are easier to maintain, document, and expand as products evolve.
-
Context Improves Adoption: Users are more likely to engage with settings and preferences when they understand the value behind them.