Case Study · 01
A comprehensive redesign of the Actions dashboard for an automotive IoT platform — improving usability, reducing errors, and scaling for enterprise device management.
4+
Major Features Redesigned
6
Design Changes Shipped
B2B
Enterprise IoT Platform
∞
Connected Vehicles
The Project
Bytebeam is a comprehensive platform designed to optimize connectivity and data management for connected vehicles. It serves fleet management, vehicle health monitoring, predictive maintenance, battery monitoring, driver monitoring, and over-the-air (OTA) updates.
Key capabilities include remote diagnostics, data analytics and visualization, and error analysis for efficient troubleshooting — all within a single cloud dashboard used by engineering teams.
Fleet Management
Real-time monitoring and control across large connected vehicle fleets and devices.
OTA Updates
Over-the-air firmware deployment with phased rollout and version controls.
Predictive Maintenance
Analytics-driven alerting before device failures occur in the field.
Remote Diagnostics
Deep error analysis and live device state visualization in the cloud.
The Problem
With a growing number of active devices on the platform, the Actions tab required an upgrade — to handle load, incorporate new features, and eliminate user errors that were becoming increasingly costly.
01
Insufficient Action Overview
Users were only notified of executed actions — with no visibility into current status or ongoing operations.
02
Broken New Action Workflow
Multiple stages involving numerous stakeholders, with no structured approach — creating operational chaos.
03
Errors in Rolling Updates
Different vendors for different tasks made tracking progress across device groups extremely difficult.
04
Basic Filter Criteria
Limited filtering forced users to manually search and note down each device — a slow, error-prone process.
Discovery
We began by gathering structured feedback from existing users — engineers and fleet managers who relied on the platform daily. These questions guided our research sessions:
Design Changes
Action Overview
Enhanced Action Summary
The action view was restructured to give users a complete picture of ongoing and completed operations — not just what ran, but what's happening now and what failed.
Before
After
Before → After: Action Overview redesign
Phased Roll-out
Dynamic Icon Integration
The phased roll-out feature introduced additional segmented information. Dynamic icons were implemented to draw attention and provide immediate visual feedback on current status — making the interface intuitive at a glance.
Dynamic icon system for phased rollout status
New Action Form
Progressive Disclosure
When initiating a new action, users configure multiple parameters. Progressive disclosure maintains user focus by presenting information in a structured, manageable sequence — left to right, simple to complex.
Advanced features like Phased Rollout, Advanced Trigger, and Auto-Retry are hidden until the user opts in — reducing cognitive load without sacrificing capability.
Progressive disclosure form — simple → advanced
New Action Form
Summary Screen
The length and complexity of the form increases the risk of user error. A summary screen at the end allows users to review all inputs before final submission — acting as a last checkpoint before fleet-wide operations are triggered.
Review & confirm before final submission
Error Handling
Minimizing User Errors
Running actions across large device fleets often creates overlaps with devices already engaged in other operations — leading to system errors. An 'Undone' action state was introduced, allowing users to defer conflicting devices. A button opens conflicting action details in a new tab for informed decision-making.
Conflict resolution dialog with 'Undone' state
Filter & View
Advanced Filter Function & View Options
Managing thousands of devices requires smart filtering. Each device has two identification parameter sets — Metadata and Device Shadow. A percentage-based filter lets users select subsets of devices for bulk operations. Filters are context-sensitive across sections of the interface.
1

2

3

4

5

Steps 1–4: Filter selection flow. Step 5: View options panel.
↳ Let's connect