As Lead UI/UX Designer, I helped transform a fragmented logistics stack into one scalable web product and a reusable design system.
Client
Bofrost
Duration
2 years
Role
Lead UX Designer
Tools
Figma
Planning and field operations depended on a fragmented desktop stack: the same data lived in multiple programs, people constantly switched tools and re-entered information, and handoffs between roles stayed manual and error-prone—with no shared navigation model or consistent patterns for dense logistics and tour workflows.
Legacy software excerpts
Business Impact Goals
01
Faster onboarding for new staff.
02
Higher planning efficiency in parallel workflows.
03
Fewer human errors from manual handoffs.
Before I moved into full concept execution, I aligned on a practical rollout plan that connected research, UX concept work, and delivery cadence with the client team.
First phase
Second phase
Early work was deliberately wide: one-to-one interviews with people across the organisation, plus guided walkthroughs of the legacy software—each time from the stance of a specific role. That combination made it possible to hear how strategy, planning, coaching, field execution, and engineering talked past each other inside the same tool.
I spoke with management, planners, coaches, regional leads, drivers, developers, and others. Each group brought different success metrics, time pressure, and blind spots—so the picture of “what planning work is” could not be reduced to a single persona or department.
Beyond talk, I stepped through the live system with those same roles. Watching planners, coaches, or drivers drive the UI exposed where labels, flows, and handoffs meant one thing in headquarters and something else in the field—and where workarounds had become normal.
Shared components reduced duplicate UI work and made regressions easier to spot.
Tables, filters, and primary actions followed one system—critical for dense logistics data.
I mapped logistics journeys as sequences of decisions—not pages—so I could see where planners lost context, re-entered data, or escalated to workarounds. Below are the original wide-format journey maps—step through them with the controls to keep each map at full width and readable scale.
1 / 3
Pain points and friction from journey maps were combined with signals from interviews and software walkthroughs, then sorted into recurring themes so UX and engineering could argue from shared evidence, not scattered anecdotes.
I turned the critical themes from research and validation into a UX concept with six pillars—Interfaces, Automation, Architecture, User guidance, System feedback, and Customizability—aligned with the concept map.
Principle
Data should reach every place it is needed via explicit interfaces and technical foundations—not ad hoc copies or manual bridges.
Principle
Planned integrations should place data where it is needed automatically, removing repeated manual steps and reducing bad input.
Principle
Strong search reaches deep hierarchy fast (e.g. customers, drivers) without long navigation paths.
Principle
Each step shows what is done, what is pending, and what comes next.
Principle
System copy (including errors): short words and terms planners already use.
Principle
Keep role-critical programs, data, and actions visible; hide what is rare or not allowed for that role.
Management requirements were mapped into screens, flow logic, and navigation structure.
Von Use-Case-Unterlagen zur Umsetzung im System
These representative bo*flex screens show how the information architecture translated into day-to-day planner interfaces, balancing navigation clarity, operational density, and quick access to critical actions.
Boflex is a complex enterprise system with many modules and dozens of screens. The views shown here are selected excerpts that represent key interaction patterns and core operational contexts.
Interactive prototypes replaced assumptions with evidence, and remote testing with planners and stakeholder feedback loops continuously improved flow quality.
I built a UI component library that covered the full product surface: buttons, inputs, responsive grids, and—most critically—complex table logic for scanning, sorting, and bulk operations. The library became the contract between design and engineering: predictable specs, fewer edge-case surprises, and a coherent experience across every module.
A contract between design and engineering based on Material Design principles, ensuring predictable specs and a coherent experience.
Roboto / Title, Label, Body
Legacy planning
Modern, system-backed UI
Average time to complete recurring planning tasks improved dramatically after replacing 80+ legacy programs with one web product: IA from real use cases and mapped flows, plus a shared component library aligned with engineering, cut tool-switching and duplicate data entry—so planners finished routine work noticeably faster day to day.