You start with

one small decision.

Then you build.

01

Step 1

The Atom

02

Step 2

The Pattern

Every popup on the platform was built ad-hoc. Different layouts per layer. Inconsistent data hierarchies. No shared components. I redesigned over fifty popup types across nine data layers into a single coherent system.

Inconsistent y-axis

Inconsistent y-axis

Compare

50+ popup types · 9 data layers · One system.

I sketch to think, play football to not think, and measure coffee extraction like it's a design variable.

03

Step 3

The feature

Two tools. No connection between them.

Operators monitored 2,340 cameras through two disconnected tools — one opened feeds in random browser windows, the other couldn't save what you were watching. I sat at their workstations, watched them work, and designed a camera wall system they could build, name, and keep.

Built, named, kept.

List. Search. Map. Three ways to find any camera.

Same wall. Different density.

reading Articulating Design Decisions · watching One Piece (ep 1,089) · brewing Yirgacheffe 15:1 · playing Sunday league, right back

04

Step 4

The product

A Korean hotdog restaurant needed a complete digital identity — ordering, customization, queue management, and a community game to pass the wait. Seven months. Five sprints. 84% of test participants preferred it over the existing process.

84%

preferred

19

participants

5

sprints

7

months

Brand system — type, color, illustration

Component Library

VR environment

The invisible layer

Estimation tools that secured funding. Handoff systems that made engineers faster. Form prototypes that replaced paper workflows. The work that makes the work work.

estimation

Secured funding for feature development

handoff

Made engineering implementation faster

forms

Replaced paper workflows entirely

You started with one small decision.

SJ

To my next team

There's a platform called RITIS that most people have never heard of. It serves over 40 state departments of transportation across the United States. If you've ever checked a traffic app during your commute, some of the data you saw probably flowed through systems I've spent the last three years redesigning.

I've redesigned map legends that organize 179 icons into browseable systems. I've systematized 50 popup types across 9 data layers so that a traffic operator in Virginia sees the same interaction patterns as one in Maryland.

I've sat at a camera operator's workstation, watched them juggle disconnected tools to monitor 2,340 live feeds, and designed a spatial workspace that let them build and save their own monitoring stations.

This is the work I'm drawn to. Dense, layered problems where the interface is the last step in a long chain of decisions about data, hierarchy, and the person on the other end.

I'm not a designer who makes things pretty and hands them off. I dig into analytics to justify killing a tool. I read API documentation to find opportunities the spec didn't mention. I prototype in Figma to secure funding, then stay through implementation.

I'm looking for a small team building something complex. A place where the product problems are genuinely hard and the people solving them take craft seriously. If that sounds like your team, I'd like to talk.

Shwetank Jain
Product Designer