Three Screens
One Flow
Consolidating a fragmented non-compliance receiving workflow — from three disconnected Nulogy screens into a single INTRA module, solo, in roughly four weeks.
Three Systems.
Zero Alignment.
The company ran non-compliance receiving inside Nulogy, a third-party logistics tool. Filing a single chargeback took three separate screens, the tool didn’t share data with INTRA — the company’s own internal platform — and the experience was built for a desk, not a warehouse floor. I designed and shipped a dedicated module inside INTRA in roughly one month.
Filing a Chargeback
Took Three Screens
Disconnected from INTRA
Nulogy held its own data, invisible to the internal platform teams actually relied on for day-to-day operations.
Desk-oriented UX
The interface assumed a mouse, a keyboard, and a desk — none of which exist on a working dock.
Ongoing license cost
Every seat on Nulogy was a recurring cost for functionality that, at its core, was a single data-entry workflow.
Three-screen detour
Filing one chargeback meant navigating three separate Nulogy screens before the job was actually done.
Screenshot pending — will slot in once uploaded to Media Library.
Solo, Four Weeks,
Live Angular Codebase
As the sole designer on this project, every decision had to earn its place inside a live Angular platform with an existing design system, on a four-week clock. There was no room for a wholesale redesign — only for the smallest change that would fully solve the problem.
One Inspection,
Top to Bottom, on the Dock
The new INTRA module was designed mobile-first, for a worker standing at the dock next to the pallet — not sitting at a desk reviewing it after the fact.
Outcomes
Consolidating three Nulogy screens into one INTRA flow didn’t just save clicks — it removed an entire third-party dependency from a daily operational task.
What I
Learned
Working solo against a four-week deadline meant every design decision had to earn its place. The clearest lesson: for warehouse-floor tools, replacing three desk-oriented screens with one mobile-first flow mattered far more than any visual polish. Respecting how and where the work actually happens is the design.
It also reinforced the value of designing out a dependency, not just around it — the win here wasn’t a nicer Nulogy wrapper, it was removing Nulogy from the workflow entirely.