Skip to main content
Tranzport · 2020ux

Tranzport Cards: Optimizing Dashboard Table

Enhancing user experience for dispatchers

Roles
UX Engineer · UX Research
Duration
6 weeks
Year
2020
UXUICSSResearch
Tools
  • Adobe Illustrator
  • Google Docs
  • Miro
  • Slack
Tranzport Cards: Optimizing Dashboard Table
The problem
Help dispatchers scan a dense dashboard without assembling related information across distant columns.
My contribution
Workflow research, interaction design, and responsive interface design.
A key decision
Group load information around lane, status, and actions rather than database column order.

Current evidence: Related load information and actions grouped so dispatchers can scan status and next action in one place.

The problem

The table was unstable, slow to load, and had a horizontal scroll. The original team built the app on Material Design to ship fast and stay focused on profitability. As features and customization piled up, the table slowed down and got harder to navigate — most of the pain was the horizontal scroll. Dispatchers had to scroll down and sideways to check a single load, which slowed them to a crawl.

Old-school dashboards: the industry standard we were working against
The pain: horizontal scrolling made the dashboard slow and hard to scan

The solution

Custom problem, custom solution. A custom lane component packed about 3× more information into the same space, organized in a way that made sense to dispatchers. Notifications consolidated into one part of the table. Fully responsive, so dispatchers can keep eyes on loads from any device.

The cards scale gracefully to mobile — no horizontal scroll

Redesigning the dashboard

I ran a survey with five dispatchers — their process, where it hurt, and what they wanted the next version to do.

Research questions

Understanding the dispatcher day

Six questions guided every interview — surfacing what mattered, not what was convenient.

  1. Daily routines

    Describe daily routines?

  2. Driver interaction

    How is a typical driver interaction?

  3. Exceptions

    Tell me about a time when the load had exceptions?

  4. Non-responsive drivers

    How is your process when the driver is non-responsive?

  5. Critical dashboard elements

    What are the critical elements in the dashboard to keep track of?

  6. Most important information

    What is the most important information in the dashboard?

Takeaways

  • Dispatchers always multitask, always against the clock
  • The load ID and the lane (pickup, dropoff, dates) are what dispatchers actually scan for
  • They need status updates constantly
  • The competitor apps are decades old and pack too much into too little space

“The market is old-school, and the dashboards look like Excel sheets.”

DanielDispatcher

The first attempt: prioritize parts of the table

The first idea was to keep the table and just freeze a few key columns. That gave dispatchers a visual anchor for the load ID and the available actions. Next step was putting it in front of dispatchers to see if it actually helped.

First concept: static columns with scroll area
First attempt: freezing columns kept the load ID visible but scrolling remained painful

Validating the idea: it was a bandaid

I went back to the dispatchers with the design. It helped a little, but they still struggled to scan the dashboard, and the horizontal scroll was still painful. The problem wasn't going to be solved by tweaking the table.

Out-of-the-box thinking

The developers, CTO, product manager, and I argued about whether the interface should change at all. Their position was that the dashboard had been there a long time and didn't need a big rewrite. I was sure we could build something better and more useful, even if it meant accepting some risk. We took the risk.

Explorations: variations and progress

I needed to group information more aggressively, and do it in a way that worked across screen sizes. The groups had to make sense for how dispatchers scan: around the lane (pickup, dropoff, dates, miles) — the fields they actually rely on.

We validated again with stakeholders and dispatchers, getting fantastic feedback and excitement.

Worth the risk: custom components made it easy to scan

The dispatchers were on board. The developers and stakeholders could see my vision and the benefits of taking the long road.

Final design: expanded card view showing all load details without horizontal scroll

Decisions & tradeoffs

  1. Tweak the table vs. replace it

    Frozen columns were the cheap fix — we built them, tested them, and watched dispatchers still struggle. Killing our own first solution is what earned the team's trust for the expensive one.

  2. Custom lane component vs. Material table

    Material shipped fast in 2018 but could not express how dispatchers actually scan: lane first, then status, then actions. We accepted the rebuild risk — the leadership argued against it — and the custom component paid it back in scan speed and load time.

  3. Grouping by dispatcher mental model vs. by data model

    The card groups fields the way dispatchers think (lane · status · actions), not the way the API returns them. The grouping makes the scanning strategy visible in the layout.

What I'd do differently: instrument scan time and mis-click rate from day one. The original records do not support publishing a numerical improvement here. I would establish comparable tasks, baseline timings, and error rates before making that claim.

The impact

A layout organized for scanning

The redesigned cards bring lane, status, and actions together so dispatchers can inspect a load in one place. No quantified scanning improvement is claimed.

Organization

Information grouped by how dispatchers think

Lane fields, status, and actions cluster the way dispatchers actually use them, instead of in column order.

Faster dashboard load

The custom layout reduced the interface’s reliance on the original table structure. A comparable performance benchmark is not available.

Phone view

Works on any screen

The cards collapse cleanly to mobile. Dispatchers can keep an eye on loads from a phone without losing the dashboard layout.

Eye tracking

Loads identifiable at a glance

Visual anchors on load ID and lane mean dispatchers spot the right row without reading the table cell by cell.

The custom-component card layout has been in production since 2020. This case study documents the research and layout decisions; it does not claim a quantified productivity result.

Other work

Explore more case studies