Forty tons, highway speed, six inches of screen.

Designing for limited attention where the cost of a mistake is real miles and real money.

Designing for limited attention where the cost of a mistake is real miles and real money.

Role

UX/UI designer

Team

5, dedicated product

Platform

iOS · Android

Timeline

Dec. 2025 – Mar. 2026 (3 months)

Role

UX/UI designer

Team

5, dedicated product

Platform

iOS · Android

Timeline

Dec. 2025 – Mar. 2026 (3 months)

4

Friction points

4

Friction points

24

Screens

24

Screens

8

User flows

8

User flows

2

Shipped to production

2

Shipped to production

  1. Context

The user is driving

The user of this product works sitting down. An eighteen-wheeler, forty tons of freight, highway speed, a schedule that has to hold and a six-inch phone somewhere on the dashboard. CDL drivers spend most of their working lives in the cab. Navigation and route control aren’t app features for them. They’re part of the job.

The user of this product works sitting down. An eighteen-wheeler, forty tons of freight, highway speed, a schedule that has to hold and a six‑inch phone somewhere on the dashboard. CDL drivers spend most of their working lives in the cab. Navigation and route control aren’t app features for them. They’re part of the job.

Route One GO is mobile navigation built for those users. It routes around restrictions based on vehicle dimensions and weight, so a driver doesn’t meet a low bridge, a banned turn or an axle-load limit at the worst possible moment. A mistake here costs more than irritation: a hundred-kilometre detour, a late delivery or a fine.

Route One GO is mobile navigation built for those users. It routes around restrictions based on vehicle dimensions and weight, so a driver doesn’t meet a low bridge, a banned turn or an axle-load limit at the worst possible moment. A mistake here costs more than irritation: a hundred-kilometre detour, a late delivery or a fine.

The business model is B2B2C. The product was already live: a five-person team working on iteration and improvement, not a launch. Each change had to fit into what already ran.

The business model is B2B2C. The product was already live: a five-person team working on iteration and improvement, not a launch. Each change had to fit into what already ran.

  1. Problem

Where the flow broke down

The app got in the driver’s way in four places.

Sign-in

A driver signs in, and the app accepts only the account on his phone.

Sign-in

A driver signs in, and the app accepts only the account on his phone.

Feedback

A driver wants to report a problem, and the app pushes him out into a mail client.

Feedback

A driver wants to report a problem, and the app pushes him out into a mail client.

Place corrections

A driver sees wrong data about a place, and the app asks him to describe it in words.

Weigh Stations

A driver approaches a weigh station, and the app shows where it is, but nothing he can use.

Weigh Stations

A driver approaches a weigh station, and the app shows where it is, but nothing he can use.

  1. Constraints

Everyone but the driver

Everything below was decided inside these:

  • Not one conversation with an end user. Everything I knew about drivers came through experts and open sources.

  • No metrics before or after. Every number on this page counts work done, not its effect.

  • Three months — the entire engagement, including learning the industry.

The first two aren't an excuse, they're the terms of the job. A designer who says "we can't work without research" doesn't work; a designer who passes their own guesses off as user needs works badly. What follows is the third option.

  1. Method

Someone you can't ask

Three independent layers that check each other

The layers were chosen so the sources wouldn't depend on each other: where conclusions overlapped, confidence went up; where they diverged, that was the signal to check.

Three transparent layers stacked one over another; the area where all three overlap is the darkest.
Three transparent layers stacked one over another; the area where all three overlap is the darkest.
Three transparent layers stacked one over another; the area where all three overlap is the darkest.

Domain expertise

Former drivers

Team knowledge

A mental model of how trucking operates

Domain expertise

Former drivers

Team knowledge

A mental model of how trucking operates

Competitor analysis

Direct

Trucker Path

TruckMap

Indirect

Waze

Google Maps

Benchmark and opportunity map

Proxy research

YouTube

Reddit driver forums

GPT

Behavioural patterns and pain points

Proxy research

YouTube

Reddit driver forums

GPT

Behavioural patterns and pain points

The former drivers among the stakeholders weren’t only a source. They were the review gate: solutions went through them as domain experts. I call this a working method. There was no formal study — there were three ways to get closer to a user who can’t be brought into the room. The limits of what that proves haven’t gone anywhere, and they’re stated plainly below.

The former drivers among the stakeholders weren’t only a source. They were the review gate: solutions went through them as domain experts. I call this a working method. There was no formal study — there were three ways to get closer to a user who can’t be brought into the room. The limits of what that proves haven’t gone anywhere, and they’re stated plainly below.

What I had to learn first

The domain was studied across all three months, in doses, alongside the work. I started on tasks two weeks in. What had to be learned from zero:

a concept new to anyone from Moldova

How US highway exits actually work

a concept new to anyone from Moldova;

How US highway exits actually work

Drivewyze, PrePass: what they are, how they work, what they save a driver

Bypass systems

and above all, why drivers dislike them and avoid them whenever they can

Weigh stations

Day four: yellow instead of black

The first test of the method arrived before I had a name for it.

Day four, a small task: change the colour of markers for truck stops with fuel discounts. They were black. I proposed yellow, and argued it not from taste but from what yellow already means to an American driver, twice over. It's the colour of a discount, fixed by retail practice, Walmart among others. And it's the colour of fuel itself — the very thing these stops discount. The app is strictly US-facing and its audience is local drivers.

The task arrived as a visual one. The answer to it turned out to be a product one — not "which shade looks better" but "what does this colour say to the person looking at it".

The task arrived as a visual one. The answer to it turned out to be a product one — not "which shade looks better" but "what does this colour say to the person looking at it".

A map of the US Midwest with a cluster of truck stops; stops with a fuel discount carry yellow price labels next to their brand markers.

Yellow for a fuel discount: the colour of fuel and of a sale.

Yellow for a fuel discount: the colour of fuel and of a sale.

Three months later the same move would give the project its core. Only instead of a price tag in a supermarket, it would be a road sign.

  1. Solution

Removing unnecessary steps

Three separate user flows, each with its own solution: one entry screen for signing in and signing up, feedback sent from inside the app, and place corrections made directly in the place's data. All three were designed alongside the main work on weigh stations.

Shipped to production

One screen instead of two

Shipped to production

Don't push people out of the app

Design complete

Don't describe it — fix it

Design complete

Don't describe it — fix it

01 / 03

Sign-in: one screen instead of two

Before

The task as assigned: add email sign-in. The only way in was the provider the platform put in front of you — on iPhone, Apple ID. No email, no Google. What I saw around it: signing up and signing in were separate flows. Before the app would let a driver anywhere, it asked him to declare which of the two he was. That is a question the system can answer on its own — it knows whether the account exists.

The task as assigned: add email sign-in. The only way in was the provider the platform put in front of you — on iPhone, Apple ID. No email, no Google. What I saw around it: signing up and signing in were separate flows. Before the app would let a driver anywhere, it asked him to declare which of the two he was. That is a question the system can answer on its own — it knows whether the account exists.

Solution

One screen for both, labelled sign in or sign up, with three ways in instead of one: Apple, Google, email. Whether the account already exists became a check on the backend, not a choice the driver makes at the door.

Rejected

Doing exactly what was asked. Adding an email button to the existing split flow — faster, safer, no questions asked of the designer. Rejected because it would have closed the ticket and left the problem.

Before

After

One screen for both, and three ways in instead of one.

02 / 03

Feedback: don't push people out of the app

Before

Profile → Give us feedback → enter email → the mail client opens. To complain about the app, a driver had to leave the app and switch tools.

Profile → Give us feedback → enter email → the mail client opens. To complain about the app, a driver had to leave the app and switch tools.

Solution

Feedback inside the product: three types — suggest a feature, report a problem, share feedback. Plus an optional screenshot or video and two optional contact fields, phone and email, so a report can be acted on rather than merely received.

Rejected

The most interesting edit of the three. The first iteration was sequential: choose the type of report, then land on the input screen. I dropped it for tabs. The reason: in a sequential flow you choose blind, without knowing what will be asked of you, and if the fields aren't what you expected, you go back. With tabs you see what the form wants straight away. The step was removed from the user's head, not from the interface.

The most interesting edit of the three. The first iteration was sequential: choose the type of report, then land on the input screen. I dropped it for tabs. The reason: in a sequential flow you choose blind, without knowing what will be asked of you, and if the fields aren't what you expected, you go back. With tabs you see what the form wants straight away. The step was removed from the user's head, not from the interface.

Before

After

Three report types in tabs — you see what's being asked before you commit.

03 / 03

Place corrections: don't describe it — fix it

Before

Generic checkboxes and a text area. Someone who sees a specific error — wrong opening hours, wrong address — has to translate it into free text. At the other end it becomes a vague report where it’s unclear what to fix.

Solution

Six structured edit types with the current POI data prefilled. You correct the exact field in context instead of describing the problem from scratch. Less typing, more precise edits.

Where six came from

From the structure of the new POI data — what is actually editable — and from the competitor teardown: which corrections they allow and what they call them. The set was derived, not invented.

Hardest place first

I started from the hardest place on the map. A weigh station carries the most data, and some of it exists nowhere else — station type, bypass support. Designing corrections for it produced a template that the simpler places, truck stops and parking, fit into as a reduced version of the same set. This wasn’t about saving time: design from the simple case first and every next place type needs its own pass, until editing spreads into several incompatible mechanics.

Before

After

Five generic place fields became six that only exist in this domain.

Five generic place fields became six that only exist in this domain.

  1. Weigh stations

Reading the road, not the map

The main task of the project. I started with it and came back to it three times:
Stations → Sign-in → Stations → Feedback → Stations → Place corrections.

Why this is more than a map point

A weigh station means delay, inspection, a fine and a broken schedule. Understanding why drivers avoid them is half the task.

What the app showed: the station and where it is. Bypass support wasn’t on the map yet, that data was still being collected.

What the driver needs: is it open right now, does it support my bypass provider, is there parking? Whatever was there had to be dug out by tapping. At highway speed a tap isn’t interaction. It’s distraction.

The marker as a decision model

I stopped treating the marker as an icon and started treating it as layers of answers. The goal was to move the most critical signals into the zero-tap layer — what can be read at a glance along the route.

Marker layer

Encodes

Why it matters

1

Border color

Open / Closed / N/A

Is it working right now

1

Border color

Open / Closed / N/A

Is it working right now

2

Center symbol

Weigh station POI

What is this

2

Center symbol

Weigh station POI

What is this

3

Provider badge

Drivewyze / PrePass

Can I bypass it

3

Provider badge

Drivewyze / PrePass

Can I bypass it

4

Parking badge

Parking availability

Can I stop here

4

Parking badge

Parking availability

Can I stop here

The difficulty wasn't inventing the layers. It was fitting four signals into one marker without turning the map into noise. The marker had to stay readable in peripheral vision.

An arrow instead of a scale

The most domain-specific decision of the project, and a direct continuation of the yellow-marker story. On US highways weigh stations are announced by large green signs — "WEIGH STATION →". A driver has been trained for years to read that arrow as an instruction: get ready, slow down, decide whether you're pulling in. The response to it was built long before he opened the app.

I replaced the scale icon with that arrow. The old blue marker denoted a place but not a meaning — it had to be decoded. An arrow is simply recognised on sight, because the person sees it every working day on the road.

That is what reading the environment means: the interface doesn't invent a language, it borrows the one already working outside.

BEFORE

1 dimension

Location only

AFTER

3 dimensions

Status · Provider · Parking

The interface borrows a language drivers already read at highway speed.

Filters with counts

Toggles control which stations appear on the map. Each one carries a count: how many stations along this route support that provider. That stops being a filter and becomes an answer to "how many times will I have to stop on this route" — available before pulling out.

A count next to each toggle answers a route question before departure.

Not shipped. The weigh stations flow as a prototype.

  1. Outcomes

Two of four reached users

On weigh stations. I presented the first iteration to stakeholders — as work in progress, not as a finished solution. The task needed further options and I kept looking for them. The state I stopped at was never presented: the work was cut short when I left the company.

On trip planning. Three concepts for comparing routes, surfacing key indicators earlier — including how many weigh stations sit on each path. None of them won out: the task ran in the background the whole time.

On place corrections. I left and don't know what became of it. I can't find those screens in the published app — I assume backlog, but I won't claim it.

What reached users: two tasks out of four. That part is publicly verifiable — the app is in the App Store and on Google Play.

Where this case study’s evidence ends

Validation with real drivers. Solutions were checked by domain experts — former truckers. They know the industry, but they aren't current users of the product.

A complete picture of the user base. Forums and YouTube represent the drivers who post, not all of them.

  1. Takeaways

The environment is data

The best interface here was the one that required less thought. A six-inch screen in the cab of an eighteen-wheeler isn't a browsing environment, it's a decision-making environment. That changed my approach: instead of adding detail, I subtracted effort. For products where the cost of a mistake is real mileage and real money, reducing mental load matters more than visual richness.

When you can’t ask the user, you can read their environment. Distance from users is a reason to look harder. You can’t bring a trucker into a lab, but you can look at what he sees every day: a green sign on the highway, a yellow price tag in a supermarket. The environment is data that’s already been collected — by someone else.

The method travels. It isn't about trucks. It's about whatever domain I'm dropped into next: find what the audience already knows how to read, and don't make them learn it again.

Thanks for reading

Let’s talk about your product

I design products people use at work under pressure — and I start with structure, not screens. If you’re building one, write to me. I’d rather talk about yours than mine.

I design products people use at work under pressure — and I start with structure, not screens. If you’re building one, write to me. I’d rather talk about yours than mine.

Waiter Jan case study cover: a laptop on a white shelf showing the restaurant admin dashboard

Next case

From one platform to four connected experiences

Waiter Jan · Restaurant Tech · 2025

→

Product Designer

Shaping ideas into user-centric design

© 2026 Alina Sur

Fueled by coffee — designed & built by me

Product Designer

Shaping ideas into user-centric design

© 2026 Alina Sur

Fueled by coffee — designed & built by me

Product
Designer

Shaping ideas into user-centric design

© 2026 Alina Sur

Fueled by coffee — designed & built by me

Product Designer

Shaping ideas into user-centric design

© 2026 Alina Sur

Fueled by coffee — designed & built by me

Create a free website with Framer, the website builder loved by startups, designers and agencies.