Context and purpose.
Shipment and operational work had to live inside one platform even though different people needed different tools, information, and actions. The experience needed to reduce irrelevant complexity without fragmenting the product into separate role-specific systems.
What the project needed to achieve.
Create a coherent shipment-management experience across three organizational levels and 17 user roles, with permissions and task context shaping the information and actions available to each person. Reuse shared workflows rather than building 17 disconnected interfaces, and define responsive desktop and tablet states for shipment creation, tracking, administration, and operational tasks. Evaluate the design-stage work through documented role and workflow coverage, not unverified claims about live adoption or operational efficiency.
The problem, constraints and competing priorities.
Three organizational levels and 17 distinct user roles created a permissions and workflow problem, not simply a screen-design problem. The system had to support different actions and information across shipment management, user administration, tracking, and operations while preserving shared interaction logic and responsive behaviour.
The competing priorities were tailoring permissions and workflows to 17 roles while maintaining a shared, maintainable experience across the platform.
My responsibilities, ownership and collaboration.
I led discovery and product design for core platform workflows. I mapped role and permission differences, designed responsive interaction patterns and detailed Figma flows, and worked with product and engineering to turn operational rules and edge cases into implementation-ready behaviour.
The options, trade-offs and reasoning behind the key choice.
I treated permissions and role context as product architecture, then reused shared workflow patterns underneath that structure. This avoided two weak extremes: 17 disconnected experiences or one overloaded universal interface. The trade-off was more explicit system logic in exchange for clearer, task-relevant experiences and a more maintainable product model.
What was delivered and the impact it made.
The client publicly announced the launch of its connected logistics platform on February 2, 2026, providing independent confirmation that the broader platform reached market. The announcement describes unified shipment creation, tracking, and operations; these are platform-level claims, not measured outcomes attributed solely to my work.
The work produced reusable role-based workflows, responsive states, and a shared design-system foundation across major platform areas, creating one coherent product model across different responsibilities.
What I learned and what comes next.
The greatest challenge in designing for 17 distinct user roles was determining where the experience needed to adapt and where consistency mattered more. Solving that problem required looking beyond individual screens and treating permissions, workflows and information architecture as interconnected product decisions.
This project reinforced the value of establishing a clear system-level direction before scaling interface design. By approaching the experience as one connected platform rather than a collection of role-specific applications, I could make design decisions that considered both immediate user needs and the long-term maintainability of the product.
The experience continues to inform how I approach enterprise product design: identifying the decisions that have the greatest downstream impact, creating clarity across complex requirements, and building foundations that allow products and teams to evolve without unnecessary fragmentation.
Email required to receive your login code.
INSTANT ACCESSInstant access lasts 7 days and includes all Controlled case studies.
