Design Impact

138%

Customer Satisfaction Score

90.8

System Usability
Score

4.8

Overall Efficiency
& Speed

From Idea

  • For System Inventory, the UX team analyzed the user requirements and combined system and device inventory in one view.

  • Motorola's design system Cobalt doesn't support master grid view. The need was to design a top-level grid for System Inventory, having rows that expand. When expanded, the device grid is displayed with other details related to the expanded devices' row.

  • UX team explored different concepts and searched for open-source design systems to save development cost & effort.


To Design Hand-off

  • The team decided the use AG Grid's Master Grid view solution. We explored ways to merge complex structure of system and device data base.

  • UX team internally evaluated concepts and decided to merge both Master Grid (System & Device Integration) and Simple Grid (Device information) in one view.

  • We documented details such as specification, user flows and interaction in Figma as ready for development.

Role: UX Lead

Collaborated with: Research Product Owners, Engineering, Program Manager

Duration: October 2023 - August 2024

From idea

  • For System Inventory, UX team analyzed the user requirements and combined system and device inventory in one view

  • MSI's design system Cobalt does not support master grid view. The need was to design a top level grid for System inventory having rows that expand. When the System row is expanded, device grid is displayed with other details related to the expanded devices' row.

  • UX team explored different concepts and searched for open source design systems to save development cost & effort.


To Design Hand-off

  • The team decided the use AG Grid's Master Grid view solution. We explored ways to merge complex structure of system and device data base.

  • UX team internally evaluated concepts and decided to merge both Master Grid (System & Device Integration) and Simple Grid (Device information) in one view.

  • We documented details such as specification, user flows and interaction in Figma as ready for development

View More

Testing & Feedback Summary

Testing breakdown: Our pre-launch phase consisted of high-touch collaboration and rigorous testing cycles to ensure product readiness.

  • VOP Sessions: 13 sessions conducted across 5 rounds with 3 key partners.

  • Usability Testing: 5 Pre-launch Usability sessions completed.

  • Alpha Testing: 3 dedicated Alpha testing phases.

Feedback Implementation: We prioritized high-impact adjustments based on direct user input:

  • Total Actionable Feedback Received: 65 items

  • Pre-launch Implementation Rate: 68% (44 items resolved prior to go-live)

Research Integration

Testing breakdown: Our pre-launch phase consisted of high-touch collaboration and rigorous testing cycles to ensure product readiness.

  • VOP Sessions: 13 sessions conducted across 5 rounds with 3 key partners.

  • Usability Testing: 5 Pre-launch Usability sessions completed.

  • Alpha Testing: 3 dedicated Alpha testing phases.

Feedback Implementation: We prioritized high-impact adjustments based on direct user input:

  • Total Actionable Feedback Received: 65 items

  • Pre-launch Implementation Rate: 68% (44 items resolved prior to go-live)

Testing & Feedback Summary

Testing breakdown: Our pre-launch phase consisted of high-touch collaboration and rigorous testing cycles to ensure product readiness.

  • VOP Sessions: 13 sessions conducted across 5 rounds with 3 key partners.

  • Usability Testing: 5 Pre-launch Usability sessions completed.

  • Alpha Testing: 3 dedicated Alpha testing phases.

Feedback Implementation: We prioritized high-impact adjustments based on direct user input:

  • Total Actionable Feedback Received: 65 items

  • Pre-launch Implementation Rate: 68% (44 items resolved prior to go-live)

Inventory View

1- As a user, I need to see all the systems and their devices.

2- As a user, I need to all the devices in one list.

Side Panel

Side Panel

As a user, I need to see status, upgrade, device and license details for each device.

As a user, I need to see status, upgrade, device and license details for each device.

Inventory View

1- As a user, I need to see all the systems and their devices.

2- As a user, I need to all the devices in one list.

Side Panel

As a user, I need to see status, upgrade, device and license details for each device.

Job View

As a user, I need view to the job logs with all upgrades (in progress, completed or failed).

Abnormalities

As a user, I need to be notified with any abnormalities and guided to fix the issues.

Before Validation

  • The assumption was view of all devices was more priority than the system view.

  • Connection> License>Status was the priority order.

  • Color code was used to show the difference between active and redundant devices.


The assumption was view of all devices was more priority than the system view

  • Connection> License>Status was the priority order

  • Color code was used to show the difference between active and redundant devices

After Validation

  • Changed default view to Group by System and Devices.

  • Switched the order of the SMA License and Connection columns so users can see the relationship between connection and status.

  • Got rid of the color-coded dots under the Status column to avoid confusion.

From Idea

  • For System Inventory, UX team analyzed the user requirements and combined system and device inventory in one view

  • MSI's design system Cobalt does not support master grid view. The need was to design a top level grid for System inventory having rows that expand. When the System row is expanded, device grid is displayed with other details related to the expanded devices' row.

  • UX team explored different concepts and searched for open source design systems to save development cost & effort.


To Design Hand-off

  • The team decided the use AG Grid's Master Grid view solution. We explored ways to merge complex structure of system and device data base.

  • UX team internally evaluated concepts and decided to merge both Master Grid (System & Device Integration) and Simple Grid (Device information) in one view.

  • We documented details such as specification, user flows and interaction in Figma as ready for development

Before Validation

  • The assumption was view of all devices was more priority than the system view

  • Connection> License>Status was the priority order

  • Color code was used to show the difference between active and redundant devices

After Validation

  • Changed default view to Group by System and Devices.

  • Switched the order of the SMA License and Connection columns so users can see the relationship between connection and status.

  • Got rid of the color-coded dots under the Status column to avoid confusion.

From Idea

  • For System Inventory, UX team analyzed the user requirements and combined system and device inventory in one view

  • MSI's design system Cobalt does not support master grid view. The need was to design a top level grid for System inventory having rows that expand. When the System row is expanded, device grid is displayed with other details related to the expanded devices' row.

  • UX team explored different concepts and searched for open source design systems to save development cost & effort.


To Design Hand-off

  • The team decided the use AG Grid's Master Grid view solution. We explored ways to merge complex structure of system and device data base.

  • UX team internally evaluated concepts and decided to merge both Master Grid (System & Device Integration) and Simple Grid (Device information) in one view.

  • We documented details such as specification, user flows and interaction in Figma as ready for development

IT Technicians

Sarah is the IT Technician who is responsible for 5 customers' systems and their hundreds of infrastructure components. Regularly she:

1- Checks the health of the systems and components.
2- Makes onsite upgrades if the components are outdated.
3- Fixes and resolves issues.

Systems & Components

One IT Technician can be responsible for multiple systems. Each system have types, IDs, IP Addresses, Names, Network Status and RM Connection Status.

Each system includes components:
1- CapMax System Server (CMSS)
2- Repeater
3- Subscriber
These servers are responsible for managing the presence and mobility information of radios in the system over the air.

Today

The backbone of Mototrbo's 2-way communication system is made up of Repeaters, Capacity Max Servers, and Gateways. These components work together to make sure that the radio network is always available and that communication is secure, and clear across an enterprise. In summary, Mototrbo infrastructure components need to be set up, well-maintained, and upgraded regularly to keep the robust and reliable communication system supporting various industries and applications.

Today

The backbone of Mototrbo's 2-way communication system is made up of Repeaters, Capacity Max Servers, and Gateways. Mototrbo infrastructure components need to be set up, well-maintained, and upgraded regularly to keep the robust and reliable communication system supporting various industries and applications.

Today

The backbone of Mototrbo's 2-way communication system is made up of Repeaters, Capacity Max Servers, and Gateways. These components work together to make sure that the radio network is always available and that communication is secure, and clear across an enterprise. In summary, Mototrbo infrastructure components need to be set up, well-maintained, and upgraded regularly to keep the robust and reliable communication system supporting various industries and applications.

Target User

Motorola collaborates with a network of authorized dealers and system integrators. These experts work closely with customers to design, deploy, and maintain the infrastructure tailored into specific needs. They provide expertise in system planning, installation, configuration, and ongoing support. These experts are responsible for regular health checks and upgrades of the components such as servers. Everything is handled manually. It takes up to 2 days for them to make an upgrade to a specific device with a lack of guidance. Upgrade can take up to 1 month if any error occurs during any upgrade step.


Target User

Technicians/administrators are responsible for health check and upgrades of Mototrbo system and devices (servers & repeaters) today. Everything is handled manually. It takes up to 2 days for them to make an upgrade to a specific device with a lack of guidance. Upgrade can take up to 1 month if any error occurs during any upgrade step.

Design Process

As the lead UX designer on this project, I collaborated closely with the RM, Cloud Gateway, Front-End Development, and Product teams. The project followed two-week sprints for both design and development. Our team included two UX designers and one researcher. I also participated in Voice of Partner sessions every two sprints to gather design feedback and ensure alignment with user needs.

Design Process

As the lead UX designer on this project, I collaborated closely with the RM, Cloud Gateway, Front-End Development, and Product teams. The project followed two-week sprints for both design and development. Our team included two UX designers and one researcher. I also participated in Voice of Partner sessions every two sprints to gather design feedback and ensure alignment with user needs.

Job View

As a user I need to view the job logs with all upgrades (in progress, completed or failed)

Abnormalities

As a user, I need to be notified with any abnormalities and guided to fix the issues

IT Technicians

Sarah is the IT Technician who is responsible for 5 agencies' systems and their hundreds of devices. Regularly she:

1- Checks the health of the systems and devices
2- Makes onsite upgrades if the devices are outdated
3- Fixes and resolves issues

Systems & Devices

One IT Technician can be responsible for multiple systems. Systems have types, IDs, IP Addresses, Names, Network Status and RM Connection Status. Each system can include devices:
1- CMSS (CapMax System Server)
2- Repeater
3- Subcsriber

Overview

Mototrbo Service Toolkit is a cloud-based management portal that allows technicians to remotely monitor, license, and update the software of MOTOTRBO radio infrastructure.  It allows technicians to push software updates to the CMSS and other infrastructure components remotely via the cloud, reducing the need for on-site visits.

Role: UX Lead

Collaborated with: Research Product Owners, Engineering, Program Manager

Duration: October 2023 - August 2024

Overview

Mototrbo Service Toolkit is a cloud-based management portal that allows technicians to remotely monitor, license, and update the software of MOTOTRBO radio infrastructure.  It allows technicians to push software updates to the CMSS and other infrastructure components remotely via the cloud, reducing the need for on-site visits.

Role: UX Lead

Collaborated with: Research Product Owners, Engineering, Program Manager

Duration: October 2023 - August 2024

Overview

Mototrbo Service Toolkit is a cloud-based management portal that allows technicians to remotely monitor, license, and update the software of MOTOTRBO radio infrastructure.  It allows technicians to push software updates to the CMSS and other infrastructure components remotely via the cloud, reducing the need for on-site visits.

Solution Highlights

  • Remote Software Upgrades: It allows technicians to push software updates to the CMSS and other infrastructure components remotely via the cloud, reducing the need for on-site visits.

  • Inventory & License Management: It provides a centralized dashboard to track all system components, including repeaters, servers, and radios. Serial   numbers, current software versions, and—crucially—when licenses or service contracts are expiring.

  • Predictive Planning: The toolkit can "pre-validate" an upgrade. It checks if your hardware is eligible for a new version and estimates exactly how much system downtime the update will cause.

  • Automated Backups: If a remote upgrade fails, the toolkit can automatically roll back the system to the previous version to prevent a downtime.



Design Impact

138%

Customer Satisfaction Score

4.8

Overall Efficiency & Speed

90.8

System Usability Score

Design Impact

138%

Customer Satisfaction Score

4.8

Overall Efficiency & Speed

90.8

System Usability Score