BEES

Modernizing the analyst experience

Modernizing the analyst experience

Modernizing the analyst experience

This project was a spiritual successor to the Routing Tool I worked on at Lowe’s, carrying over many lessons that directly influenced the design and direction of the Routes page at BEES.


This was a design-driven project with the goal of creating a more intuitive solution for Deliver Portal's fleet management functionality.

This project was a spiritual successor to the Routing Tool I worked on at Lowe’s, carrying over many lessons that directly influenced the design and direction of the Routes page at BEES.


This was a design-driven project with the goal of creating a more intuitive solution for Deliver Portal's fleet management functionality.

This project was a spiritual successor to the Routing Tool I worked on at Lowe’s, carrying over many lessons that directly influenced the design and direction of the Routes page at BEES.


This was a design-driven project with the goal of creating a more intuitive solution for Deliver Portal's fleet management functionality.

Role

Role

UX Product Designer

UX Product Designer

Application

Application

Deliver Portal

Deliver Portal

Tools

Tools

Figma, Sketch, Adobe Xd

Figma, Sketch, Adobe Xd

But, first…

But, first…

But, first…

But, first…

Meet Jonotan.

Meet Jonotan.

Meet Jonotan.

He's a route analyst.

He's a route analyst.

He's a route analyst.

Every day, Jonotan relies on Deliver Portal to track trucks and delivery statuses.

Every day, Jonotan relies on Deliver Portal to track trucks and delivery statuses.

Every day, Jonotan relies on Deliver Portal to track trucks and delivery statuses.

This is the experience he knew before the redesign.

This is the experience he knew before the redesign.

This is the experience he knew before the redesign.

The original routes page was a disjointed experience.

The original routes page was a disjointed experience.

The original routes page was a disjointed experience.

The table view focused on displaying visit statuses for each route...

The table view focused on displaying visit statuses for each route...

The table view focused on displaying visit statuses for each route...

...While a separate map view would show truck location and POC information.

...While a separate map view would show truck location and POC information.

...While a separate map view would show truck location and POC information.

Ultimately…

Ultimately…

Ultimately…

Ultimately…

The initial design had

-

.

The initial design had

-

.

The initial design had

-

.

The initial design had:

-

Problem statement

Problem

statement

Problem

statement

Based on the heuristic evaluation and team insights, analysts struggled to optimize workflows. Limited route visibility, unclear navigation, inconsistent visuals and poor scalability made critical data hard to access and workflows difficult to improve. These issues increased cognitive load and hindered effective fleet management.

Based on the heuristic evaluation and team insights, analysts struggled to optimize workflows. Limited route visibility, unclear navigation, inconsistent visuals and poor scalability made critical data hard to access and workflows difficult to improve. These issues increased cognitive load and hindered effective fleet management.

Based on the heuristic evaluation and team insights, analysts struggled to optimize workflows. Limited route visibility, unclear navigation, inconsistent visuals and poor scalability made critical data hard to access and workflows difficult to improve. These issues increased cognitive load and hindered effective fleet management.

Design objectives

Scalable structure

Create a flexible information architecture that supports growth in routes, trucks and new features without needing to reinvent patterns.

Intuitive navigation

Enable seamless movement across the entire dataset from entire routes to individual products.

Live data & status clarity

Present real-time route updates and clear visual indicators for route and delivery statuses.

Design objectives

Scalable structure

Create a flexible information architecture that supports growth in routes, trucks and new features without needing to reinvent patterns.

Intuitive navigation

Enable seamless movement across the entire dataset from entire routes to individual products.

Live data & status clarity

Present real-time route updates and clear visual indicators for route and delivery statuses.

Design

objectives

Scalable structure

Create a flexible information architecture that supports growth in routes, trucks and new features without needing to reinvent patterns.

Intuitive navigation

Enable seamless movement across the entire dataset from entire routes to individual products.

Live data & status clarity

Present real-time route updates and clear visual indicators for route and delivery statuses.

Design

objectives

Scalable structure

Create a flexible information architecture that supports growth in routes, trucks and new features without needing to reinvent patterns.

Intuitive navigation

Enable seamless movement across the entire dataset from entire routes to individual products.

Live data & status clarity

Present real-time route updates and clear visual indicators for route and delivery statuses.

Competitive research

Competitive research

Competitive

research

For this project, I looked into routing and fleet management software such as Samsara, Here, and Fleet Complete, along with a few others to identify the most important features to consider. I chose these applications for their data visualization and scalable architecture.

For this project, I looked into routing and fleet management software such as Samsara, Here, and Fleet Complete, along with a few others to identify the most important features to consider. I chose these applications for their data visualization and scalable architecture.

For this project, I looked into routing and fleet management software such as Samsara, Here, and Fleet Complete, along with a few others to identify the most important features to consider. I chose these applications for their data visualization and scalable architecture.

From this research…

From this research…

From this research…

From this research…

route map

Because fleet management is spatial at its core, a live map needs to be the foundation. It gives analysts immediate awareness of trucks, stops and routes, anchoring all the other features.

route map

Because fleet management is spatial at its core, a live map needs to be the foundation. It gives analysts immediate awareness of trucks, stops and routes, anchoring all the other features.

route map

Because fleet management is spatial at its core, a live map needs to be the foundation. It gives analysts immediate awareness of trucks, stops and routes, anchoring all the other features.

route map

Because fleet management is spatial at its core, a live map needs to be the foundation. It gives analysts immediate awareness of trucks, stops and routes, anchoring all the other features.

route map

Because fleet management is spatial at its core, a live map needs to be the foundation. It gives analysts immediate awareness of trucks, stops and routes, anchoring all the other features.

Over a few months…

Over a few months…

Over a few months…

Over a few months…

Validating the foundation

Validating the foundation

The dual-layout framework was well-received, with the side panel improving clarity around routes and delivery history.

The dual-layout framework was well-received, with the side panel improving clarity around routes and delivery history.

The right side panel is clearer on what is going on with the routes and what happened in the past deliveries.

The right side panel is clearer on what is going on with the routes and what happened in the past deliveries.

Identifying the gaps

Identifying the gaps

Testing surfaced several new user needs as well.

Testing surfaced several new user needs as well.

I didn't see any info on unplanned stops.

I didn't see any info on unplanned stops.

Can we show latitude and longitude for each client?

Can we show latitude and longitude for each client?

It would be good to download spreadsheets with all this.

It would be good to download spreadsheets with all this.

Confirming the improvements

Confirming the improvements

In the second round, streamlined navigation and richer status details made the tool feel more powerful, yet easier to use.

In the second round, streamlined navigation and richer status details made the tool feel more powerful, yet easier to use.

I really like it. There are more details. It's better than what we use today.

I really like it. There are more details. It's better than what we use today.

Validating the foundation

The dual-layout framework was well-received, with the side panel improving clarity around routes and delivery history.

The right side panel is clearer on what is going on with the routes and what happened in the past deliveries.

The right side panel is clearer on what is going on with the routes and what happened in the past deliveries.

Identifying the gaps

Identifying the gaps

Testing surfaced several new user needs as well.

Testing surfaced several new user needs as well.

I didn't see any info on unplanned stops.

I didn't see any info on unplanned stops.

Can we show latitude and longitude for each client?

Can we show latitude and longitude for each client?

It would be good to download spreadsheets with all this.

It would be good to download spreadsheets with all this.

Confirming the improvements

Confirming the improvements

In the second round, streamlined navigation and richer status details made the tool feel more powerful, yet easier to use.

In the second round, streamlined navigation and richer status details made the tool feel more powerful, yet easier to use.

I really like it. There are more details. It's better than what we use today.

I really like it. There are more details. It's better than what we use today.

And finally…

And finally…

And finally…

And finally…

Final thoughts

Final

thoughts

Final

thoughts

Even without quantitative data early on, we leaned on heuristic evaluations to identify usability gaps and make informed design choices. This process reinforced how structured principles can guide realistic, user-centered solutions, ensuring that analysts received a tool grounded in clarity, scalability and efficiency.

Even without quantitative data early on, we leaned on heuristic evaluations to identify usability gaps and make informed design choices. This process reinforced how structured principles can guide realistic, user-centered solutions, ensuring that analysts received a tool grounded in clarity, scalability and efficiency.

The original routes page was a disjointed experience.

The original routes page was a disjointed experience.

The table view focused on displaying visit statuses for each route...

The table view focused on displaying visit statuses for each route...

...While a separate map view would show truck location and POC information.

...While a separate map view would show truck location and POC information.