Track

Improving a fleet tracking system adopted by over 1,000 clients*

*The name of the application and the screens design has been changed due to NDA

*The name of the application and the screens design has been changed due to NDA

*The name of the application and the screens design has been changed due to NDA

UX

UI

BtoB

Timeline

Jan. 2024
— Early 2026

Scope

North America, South America,
Europe and Oceania

Platform

iOS & Android App, Web

Context

Context

Track is a cable reel fleet management application designed for industrial clients to track, secure and manage their cable reels.

Originally developed by Nexans R&D and released in 2020, the platform includes real-time anti-theft monitoring, return management to optimize reel lifecycle, and order visibility.

Industrial SaaS

Asset tracking

Real-time

Usability

Growth focus

Retention

IoT

International rollout

Mobile experience

Local food artisans

Mobile exp.

My role

My role

One of the most complex B2B products I worked on.

Worked closely with PMs and engineers to align UX with business priorities. I led the UX redesign, defined key product improvements and contributed to the evolution of the design system. I focused on:

• simplifying complex workflows

• improving product consistency

• supporting product clarity and structure

Experience gaps

Experience gaps

A review of the existing product revealed several experience gaps affecting usability, consistency and accessibility.

No relevancy


The product surfaces many features and pages, but most are not aligned with real user needs — leading to low engagement and underused functionality.

Limited guidance during decision

Users received little contextual support during browsing and checkout. Higher cognitive load, smaller baskets, and fewer repeat orders.

Low contextual relevance

The platform lacked seasonal or event-based content tied to real-life moments. Missed emotional and commercial opportunities, limiting engagement.

Limited guidance during decision

Users received little contextual support during browsing and checkout. Higher cognitive load, smaller baskets, and fewer repeat orders.

Low contextual relevance

The platform lacked seasonal or event-based content tied to real-life moments. Missed emotional and commercial opportunities, limiting engagement.

Inconsistent experience

The lack of consistent design rules and navigation patterns creates confusion, increases cognitive load and makes the product harder to use.

No defined journey


Key actions are difficult to identify, leaving users unsure of what to do next and reducing overall product adoption.

Our users

Our users

Before any design, we deep dive into existing behavioral and data of our users to understand them better. We also conducted a series of customer interviews.

What is 
the job that our customers hire our product for?

User research

User research

To understand how Track was used across markets, we conducted a mixed-method research combining a user survey and remote interviews with operational and business stakeholders. This research helped identify key pain points around reliability, information hierarchy and product adoption.

30 survey responses

30 survey responses

30 survey responses

6 user interviews

6 user interviews

6 user interviews

Multiple regions

Multiple regions

Multiple regions

Interview participants
Interview participants

Participants included operational, logistics and business stakeholders involved in cable reel tracking and asset management across different markets.

Affinity mapping from interviews
Affinity mapping from interviews
Key user needs
Key user needs

Real-time reel location

Remaining cable length

Clear operational status

Clear operational status

Remaining cable length

Clear operational status

Core user expectations
Core user expectations
Reliability

Accurate and up-to-date tracking

Simplicity

Clear information hierarchy

Security

Alerts for abnormal reel movements

Circularity

Better visibility on reel returns and recycling

Defining the problem

Defining the problem

How might we help users gain full visibility and control
across an entire lifecycle, from deployment to return?

How might we help users gain full visibility and control across an entire lifecycle, from deployment to return?

Goals

Goals

Business

Strengthen the value proposition of core offerings

Operational efficiency

Tailor services to individual user needs

Users

Increase content relevancy

Add a delightful, consistent consumer experience

Update key offers

Key product decisions
Key product decisions

Prioritized clarity over feature accumulation

Simplified workflows instead of adding new features

Simplified workflows instead of new features

Standardized navigation patterns for scalability

Reduced cognitive load on critical operations

Standardized navigation patterns for scalability

Impact

Impact

As it’s a huge product, the project design enhancements have been released in phases by business priority.

For confidentiality reasons, I have omitted the actual values for these metrics.

The redesigned features rolled out in business-priority phases over the year. Web and mobile releases were coordinated in parallel, ensuring both platforms evolved together for a seamless cross-device experience.

The redesign focused on measurable retention and engagement improvements.

+44%

+44%

Operational visibility

+72%

Improved network monitoring

+50%

Reduced investigation time

Approach

Approach

Collaboration

To ensure maximum value delivery with minimal waste, we adopted a Lean Design approach throughout the project. By prioritizing user feedback loops, lightweight documentation, and rapid prototyping, we were able to align closely with real user needs and iterate quickly. This allowed us to test assumptions early, focus on what truly mattered, and deliver meaningful outcomes without overinvesting in unnecessary features.

Define

User research and ideation

Design

Prototypes and value proposition

Prototypes
and value proposition

Validate

Testing with users

Userflows

Userflows

We mapped each archetype to their user journey on the app, with their respective success metrics.

On the left, we have an example of the previously used user flow for all app. On the right, we have the newly improved user flow for each routine.

Final designs

Final designs

From feature overload
to task-focused experience

Consistent interface
for complex workflows

Clear navigation
to guide key user actions

Better data visibility
for confident decisions

Product outcomes
Product outcomes

Clearer product structure

Improved usability across complex workflows

Better foundations for future features

Stronger UX consistency across the platform

Improved usability across complex workflows

Stronger UX consistency across the platform

What we learned

What we learned

This project reinforced three key lessons:

Focus on a specific market rather than trying to serve everyone

Trying to design for multiple international markets proved counterproductive. Aligning the product with the needs of a clearly defined professional user group brought much more clarity and relevance to the service.

What you sell matters as much as how you present it

The product worked well, but its value was not clearly communicated. As a result, many clients were unaware of what Track could actually do for them.

Design also means choosing what not to show

Designing for users does not mean exposing every option. Prioritizing the most relevant information and limiting visible choices helps create a clearer and more usable experience.

Track was a demanding and complex project that pushed me to navigate international product challenges and work on one of the most feature-rich platforms of my career. It strenghtened both my product thinking and my ability to simplify complex systems.

Thank you for reading. Don’t hesitate to take a look at my other works!