Investing early in tokens and primitives paid back across every feature shipped after.
Snap Automation
Enterprise Device Booking
- Role
- UI/UX Designer
- Tools
- Figma · Storybook · Jira

The friction we needed to solve.
Engineering teams booked physical test devices across spreadsheets, Slack threads and legacy tools — leading to conflicts and lost time.
Five lenses on a single product problem.
Each lens explores one dimension — history, geography, physics, chemistry, biology. Expand to read the working.
Honest metrics.
Real numbers where I have them. Where validation is pending, I say so.
Metrics marked “to be validated” are pending live measurement.
How the work came together.
- 01Research
- 02Journey Mapping
- 03Wireframes
- 04Information Architecture
- 05UI Exploration
- 06Design System
- 07Prototype
- 08Usability Testing
- 09Iteration
- 10Final Design
Scan in 30 seconds.
Engineers wasted hours coordinating device access across siloed tools.
Design a scalable booking experience and a system that supports many device classes.
Audited workflows, built a token-driven design system, designed booking, scheduling and inventory surfaces.
A consistent booking experience with a reusable component library adopted across multiple internal products.
What changed for users.
- Spreadsheets & Slack
- Inconsistent UI per tool
- No central availability view
- Unified booking surface
- Shared design system
- Real-time availability
The shipped design.



What I'd take into the next one.
Tighter loop with platform engineering would have caught permission edge cases sooner.
Open the system to partner teams as a shared internal product surface.
Want the long version of Snap Automation?
Happy to walk through process, decisions and trade-offs in detail — say hello and I'll send a deep-dive.
