UX/UI • ONBOARDING FLOW • B2B
Client onboarding and admin platform for a supply chain company
context
A supply chain company was building an internal administration platform to centralize client data and speed up project kickoffs. I joined as the UX/UI Designer in the early stages of the product.
The company already had a brand guide and a website, but no product interface. Starting a new project meant collecting a large amount of client information and documentation in a process that was slow, scattered, and pushed the start of every engagement further back.
problems
Onboarding required 15+ different documents and data points upfront, exactly the kind of ask that makes users abandon the process
Industry-specific documents (SKU matrices, bills of materials, 3PL invoices, freight documents) that not every user would recognize without explanation
Requirements arrived as a raw list, with no defined order or flow
The brand guide was made for marketing, not for a functional product UI
No existing components, everything had to be built from zero
process
1. Understanding the domain
Before designing anything, I studied what each required document actually was and what it was for. That's what made it possible to organize the raw requirement list into 8 steps that follow a logic the user can recognize (company basics first, then products, retailers, tools, operational data) instead of a form that mirrors the company's internal checklist.
2. Structuring the flow in wireframes
I validated wireframe versions of the flow with both the internal team and the client. The hardest part was keeping the process simple while still explaining unfamiliar terms in context, so users were never left guessing what was being asked of them.
3. Removing friction
The flow was designed so a missing document never blocks progress: every step can be skipped and completed later, users can attach alternative files when they don't have the exact one requested, and a persistent step indicator always shows where they are. Nothing gets lost, and nobody gets stuck.
4. UI and design system
After validation, I built the component library on top of the Radix library, following an atomic design approach and translating the brand guide into a functional UI language, around 40 screens in total, covering all states and modals. Using Radix as the base kept the components consistent with what developers would actually implement. The platform was designed for desktop use, with two breakpoints.
outcomes
15+ required documents organized into a single 8-step onboarding flow, replacing an unstructured requirement list
Heavy data collection made manageable: skippable steps, resumable progress, and in-context explanations instead of a wall of fields
~40 screens designed and specified, with a component library built on Radix following atomic design
Flows validated with the client and internal team before high fidelity, no rework on direction
Next project
PRODUCT ARCHITECTURE • DESIGN SYSTEM • AI SEARCH
Replacing dozens of scattered spreadsheets with one AI powered search platform
Product architecture, UX, and a 75 screen design system, built alongside the dev team from day one
UX PROCESS, MOBILE CHECKOUT, HIRING CHALLENGE
Landing a design role by shipping a full checkout journey in 5 days
End-to-end UX process, benchmark to tested prototype for a mobile checkout, built solo in 5 days
END-TO-END • DESIGN SYSTEM • B2C
Getting a product into development after years of failed attempts
End-to-end design for a C2C safety platform with 1,000+ people waiting
DESIGN SYSTEM • COMPONENTIZATION • B2C
A design system for a product being built without a designer
Redesign, component behaviors, and 100+ specified screens, built on the library the developers already used