Unisyn
About Project
ROLE
Product Designer
TIMELINE
November 2023 – Present
LOCATION
Remote
Overview
Meet Unisyn — One Platform, Four Powers Working as One
Unisyn is an enterprise platform built to help businesses run their operations smoothly, all from one place. Instead of juggling separate tools, Unisyn brings everything together through four connected apps — each handling a key part of the daily grind.
Fleetra keeps deliveries and logistics on track, from routes to roundtrips.
Ordexa takes care of every order — placing, tracking, and managing it with ease.
Stocko makes sure you know exactly what’s in stock, where it is, and what’s running low.
Resorsly brings all the people stuff together — managing employees across the board.
Each app is powerful on its own, but the real magic happens when they work together. A driver scheduled in Fleetra is also managed in Resorsly. An order in Ordexa checks available items through Stocko. It’s a tight, smooth ecosystem — and I was responsible for shaping that experience end to end.
The Challenge
Before Unisyn, businesses were juggling disconnected tools that didn’t talk to each other. Drivers were managed in one app, stock tracked in another, orders lived in spreadsheets, and HR was off in its own world. It slowed everything down and opened the door to constant errors and miscommunication.
Internally, things weren’t much smoother. The team was still forming, roles weren’t clearly defined, and the design work that existed was scattered — no components, no shared patterns, and no design system to bring things together.
Unisyn is a complex system, so I had to dive deep into the business logic and understand why things worked the way they did before making any design decisions. And because the roadmap kept shifting, I had to stay flexible and constantly adapt — balancing strategy, speed, and usability in a moving environment.
A few more challenges I had to navigate:
Design feedback loops were unclear, which made it hard to know when a design was “final” or ready for handoff.
Developers were using different UI styles, often rebuilding components from scratch because there wasn’t a shared library.
User flows stretched across multiple platforms, so ensuring consistency and reducing friction required thinking at a system level, not just screen-by-screen.
My Approach: Designing for Clarity in a Moving System
With four interconnected platforms, no design system, and shifting priorities, I knew I couldn’t fix everything at once. So instead of jumping straight into screens, I took a step back and focused on making sense of the bigger picture.
I started by mapping how each platform functioned on its own — and more importantly, how they depended on each other. My goal was to bring consistency, reduce friction between apps, and make sure the design was scalable for the team and developers.
To move fast without breaking things, I focused on three core strategies:
1. Design with the system in mind
I mapped the flows across Fleetra, Ordexa, Stocko, and Resorsly to understand how users moved between them — and where things were breaking down. This helped me identify patterns we could reuse and design shared experiences that felt unified, not fragmented.
2. Build foundations before polishing
There was no proper design system, so I started building one as I went — creating reusable components, documenting decisions, and aligning visuals across platforms. This made collaboration with developers smoother and helped avoid reinventing the wheel with every screen.
3. Stay adaptive and collaborative
With shifting priorities and no solid roadmap, I worked closely with PMs and devs to constantly re-align. Instead of waiting for things to “settle,” I designed in loops: rapid iteration, feedback, and real-time adjustments. It wasn’t always perfect, but it kept us moving.
This approach helped me bring structure to the chaos — and set the stage for deeper work on each platform. Next, I’ll walk you through one of them: Fleetra, and how we reimagined logistics for the teams who rely on it every day.
challenge
process
Outcome
