
Transport Optimisation Dashboard
Overview
Frontend development for Bama’s internal transport planning dashboard, from August to October 2023. Built with Next.js, GraphQL and Tailwind CSS.
I worked on maps, tables and filters that help operators compare routes, stops and assignments.
Bama moves a lot of produce around Norway. From August to October 2023 I worked on the frontend for an internal transport optimisation dashboard — a routing and planning view for logistics operators who need to trust what is on screen before trucks roll.
The interface supported daily logistics decisions. Clear labels, readable data and a consistent relationship between maps and tables were central to the work.
The problem
Bama’s logistics tooling had grown messy over time — different UIs, unclear data ownership, and people doing workarounds in spreadsheets because the software did not show them what they needed in one place. The new dashboard had to pull transport data into a single view operators could actually use during planning.
What I built
- Routing and planning views — map and table layouts tuned for comparing routes, stops, and assignments at a glance.
- GraphQL data layer — typed queries against Bama’s transport API so the UI fetched only what each screen needed.
- Performance-aware tables — large datasets that stay scrollable and readable without turning every row into a wall of numbers.
- Operator-first interaction patterns — filters, drill-down, and hierarchy that assume someone is in a hurry, not browsing.
Stack
Next.js, TypeScript and Tailwind CSS on the frontend, with GraphQL for transport data. I focused on the information hierarchy and interactions operators needed for route planning.
The hard part
Information density is the whole game in logistics UI. Show too little and people reopen Excel. Show too much and nobody trusts the screen. I spent most of the project on hierarchy — which metrics belong above the fold, which details wait for drill-down, and how map and table views stay in sync when the dataset grows.
What I took away
The project reinforced the importance of information hierarchy in internal tools. The screenshots show the delivered dashboard; it has no public URL.