Entringo Traffic

Automated digital traffic management system for logistics facilities (stealth alpha-to-beta).

Design inconsistency was blocking beta launch and scalability. Ran a full UX/UI audit, built the design system from scratch, and redesigned core user flows—reducing task complexity and unblocking development cycles.

Files Client

Problem

  • 50-60 inconsistent UI patterns across product from ad-hoc decisions

  • critical user flows required multiple tabs, mental linking, and extensive steps

  • no design system → developers lacked clear implementation guidelines

  • blocking beta launch and market expansion

Approach

  • full UX/UI audit identifying flow bottlenecks and pattern inconsistencies

  • prioritized 3 highest-impact user flows based on frequency and friction points

  • created comprehensive design system (components, patterns, documentation)

  • iterative redesign within technical constraints (minimal dev lift, preserve navigation logic)

  • developer handoff with annotated specs and state documentation

High-impact user flows before
Visual sitemap of the platform
UX/UI audit results documented
Alternative take on the dashboard
Design system file for new website
Navigation component documentation
Improved session overview page

1 / 7

Impact

User (high-impact flows) *

  • permit creation: 50-60 steps → 20-30 (50% reduction)

  • event investigation: unified scattered data across interface (50% faster completion)*

  • gate troubleshooting: eliminated dual-tab workflow (50% faster, removed operator cognitive strain)*

In-house

  • design system with component library and implementation guidelines

  • 30-40% faster design-to-development handoff*

  • enabled consistent implementation patterns across product

* Estimates based on measured workflow changes and step reductions

Files

  • Jiwambe

    Established the design function from the ground up (design system, file architecture, cross-functional processes) and currently designing the customer-facing product surface, in active build.

    Case study

  • Polar Explorer

    Streamlined to 14 steps (~40% reduction) and improved information hierarchy — aimed at reducing repetitive support load.

    Case study

Working with startup teams, remote and across time zones. Based in CET. 

Book a call Connect