Enterprise SaaSDevice Booking

Snap Automation

Enterprise Device Booking

Role
UI/UX Designer
Tools
Figma · Storybook · Jira
Snap Automation cover
01 — Problem

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.

02 — Science Framework

Five lenses on a single product problem.

Each lens explores one dimension — history, geography, physics, chemistry, biology. Expand to read the working.

03 — Mathematics

Honest metrics.

Real numbers where I have them. Where validation is pending, I say so.

Research Participants
5
Usability Testing
5
Confidence Rating
4.5 / 5
Business Impact
Metric to be validated
Task Completion
Metric to be validated

Metrics marked “to be validated” are pending live measurement.

04 — Design Engineering

How the work came together.

  1. 01Research
  2. 02Journey Mapping
  3. 03Wireframes
  4. 04Information Architecture
  5. 05UI Exploration
  6. 06Design System
  7. 07Prototype
  8. 08Usability Testing
  9. 09Iteration
  10. 10Final Design
05 — STAR

Scan in 30 seconds.

situation

Engineers wasted hours coordinating device access across siloed tools.

task

Design a scalable booking experience and a system that supports many device classes.

action

Audited workflows, built a token-driven design system, designed booking, scheduling and inventory surfaces.

result

A consistent booking experience with a reusable component library adopted across multiple internal products.

06 — Before & After

What changed for users.

Before
  • Spreadsheets & Slack
  • Inconsistent UI per tool
  • No central availability view
After
  • Unified booking surface
  • Shared design system
  • Real-time availability
07 — Final Screens

The shipped design.

Snap Automation — SNAP Automation — Web Portal
SNAP Automation — Web Portal
Snap Automation — SNAP Automation — Web Portal
SNAP Automation — Web Portal
Snap Automation — SNAP Automation — Web Portal
SNAP Automation — Web Portal
Prototype walkthrough
08 — Learnings

What I'd take into the next one.

What worked

Investing early in tokens and primitives paid back across every feature shipped after.

What I'd improve

Tighter loop with platform engineering would have caught permission edge cases sooner.

Future opportunities

Open the system to partner teams as a shared internal product surface.

Next steps

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.

Next case study
Skyde
Passenger Disruption Platform
Read case study