You start with

one small decision.

Then you build.



01

Step 1

The Atom

Interfaces, icons, characters, logos. The smallest pieces of the work.

Step 1: The Atom. A collection of 17 design artifacts showing breadth across product interfaces, VR environments, 3D modeling, brand identity, illustration, and interaction design. Work spans RITIS transportation platform, Away-sis VR meditation, Ssongs food ordering, Bao Festival, Cloudlytics, and PDA Suite.

02

Step 2

The Pattern

Every popup on the platform was built ad-hoc. Different layouts per layer. Inconsistent data hierarchies. No shared components. Users screenshot these popups for their reports.

I identified common elements across fifty types, built a coherent system across nine data layers, and established patterns that made every new data source faster to ship.

Legacy RITIS popup showing ad-hoc layout with inconsistent data hierarchy and spacing
Redesigned RITIS popup with standardized layout, consistent typography, and structured data hierarchy

Compare

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

RITIS, DMS popup displaying the dynamic message sign content
RITIS weather station popup displaying precipitation and wind data
RITIS incident popup with vehicle details and road closure status
RITIS transit popup showing Metro train arrival and next stops
RITIS fleets popup showing information about reported issues with images, videos and notes
RITIS flights popup showing the flight type and trip details
RITIS maritime popup showing the boats type and trip details
RITIS dangerous slowdown alert popup with speed differential
Scuba diving underwater with coral and marine life visible
Playing Sunday league football on a grass pitch
Pencil sketch in a notebook of traditional milestone flags in Himalayas, drawn while trekking in the mountains
Sitting on a mountain ridge at sunset, looking out at the landscape

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

03

Step 3

The Feature

Legacy RITIS CCTV viewer showing camera feeds opened as separate browser windows in a popup player with no layout organization
Legacy RITIS camera map showing camera locations as dots on a map with a sidebar listing feeds, no way to group or save selections

Two tools. No connection between them.

Two tools for 2,340 cameras. Neither saved your layout. I watched operators work, then designed the wall they could build, name, and keep.

Saved camera walls with their names, camera counts, and last updated dates

Build a wall. Name it. Come back to it tomorrow.

Layout picker showing camera arrangement options from two to eighteen cameras

Same wall, different density. Six cameras or sixty.

Map view showing camera locations across multiple US states

List. Search. Map. Find any camera three ways.

CCTV Camera Wall showing a grid of traffic camera feeds with a search sidebar listing 2,340 cameras

04

Step 4

The Product

Vessel data existed but no one could see the full picture. Port authorities needed real-time movement patterns, dwell times, and throughput in a single view.

I designed the analytics dashboard they use today. Live in production. Presented at TRB 2025.

Analytics for vessel movement: where ships go, where they wait, and what they pay to avoid a queue.

Maritime Trip Analytics, 2024

01

Hex bins, not route lines

Roads give traffic a fixed width; ships follow currents and common paths. I pushed for hex bins over route lines, and the team adopted them. They hold up from a single port to the whole globe.

02

Bin size, separate from zoom

Our tools clustered by zoom: zoom out for the big picture, zoom in for detail. I made bin size its own control, so at the same zoom analysts see both the overall routes and the detail inside them.

03

Filter the result, don't re-run the query

Our tools had you describe a query, then run it. Adding one day meant starting over. I pushed the PM and stakeholders for live filtering, which maritime needs and other datasets can use too.

04

A "through" filter

The job is finding the best route, and chokepoints decide it. If the Panama queue runs 5 to 10 days, a ship might arrive sooner another way. "Through" finds every vessel that passed a region, so analysts can spot delays and compare alternatives.

Tradeoff

[Tradeoff tile]

[What it cost, one line]

Outcome

The first tool in our suite with live filtering

It's now in 5 more. The dashboard I designed now serves other datasets, from truck parking to land vehicles. Presented at TRB 2025.

Built for water, not roads

Four design decisions behind a maritime analytics tool

Ssongs

Browser-based ordering that removes the queue and adds a weekly game. No download. 84% of testers preferred it.

Away-sis

HoloLens meditation for ChristianaCare caregivers, designed for the way out as much as the way in. Stress measured through biosignals, not surveys.

[Maritime overline]

[Thesis hook, 20 to 30 words]

Maritime Trip Analytics dashboard showing OD Zone Map with hexbin vessel density visualization, query parameters for vessel type and country flag filtering, cross-filtered charts for trip count by category, day of week, hour of day, and distance, with display options panel for map and chart configuration

Problem. [About 50 words]

Decisions.
[Decision 1] [one line]
[Decision 2] [one line]
[Decision 3] [one line]
[Decision 4] [one line]

Tradeoff. [About 40 words]

Outcome. [About 30 words]

Ssongs · Ordering for a Korean hotdog shop

A browser-based ordering app that removes the queue and gives the wait a purpose: a weekly game with rankings and rewards. No download.

Problem. At a food court you queue to order, struggle to find a seat, and have nothing to do while you wait. Tablets at the counter don't fix that.

Decisions.
Scan, don't install. QR ordering in the browser. Nobody wants to download a hundred food apps.
A weekly game. Three games rotate each week, with rankings and rewards for the top 3. The team made three; I made one myself: Red Light Green Light, themed on Squid Game, which was everywhere at the time and fit a Korean shop.
Customization you can see. Picking options visually instead of from words made custom orders easier.

Tradeoff. A game that holds your attention can make you miss your order. So the live order timer and a ready notification stay on top of the game.

Outcome. 84% of 19 test participants preferred it over the existing process. 31 heuristic issues found across 5 sprints in 7 months. Delivered with a style guide and component library.

Browser-based · 7 months, 5 sprints · Usability tested with 19 participants

Away-sis · HoloLens meditation for ChristianaCare

Most meditation apps focus on getting in and staying in. Away-sis also designs the way out.

Problem. Guided meditations open with a relaxing voice or sound that fades away, then end with an abrupt voice announcing it's over.

Decisions.
A sequence for every sense. Day slows into night, then into a state with all color removed. Sound starts natural, gains birdsong, then instruments.
Breathing you can see. In the colorless state, a colored breathing cue gradually brings the respiratory rate down.
A way back. Sound fades in and out as color and night birds return, then morning birds bring you out.
Start with a look. The first version needed a controller to begin. We replaced it with a bubble you look at for a few seconds.
Measured live. The HoloLens tracked respiratory rate, heart rate and other signals, and showed a live graph of the wearer's cognitive load as it changed.

Tradeoff. It was a short project: a home space and one meditation space. We modelled everything in the meditation space and some of the home space, and took the rest from online libraries, so the two share a theme but not an identical style. I modelled a panda spirit animal in Blender, but its interaction didn't make it in.

Outcome. Tested with 40 caregivers, including doctors and nurses. Most liked it, but not everyone was ready to adopt it straight away; gradual exposure would have helped. Over 20 days of our own recordings, cognitive load dropped gradually.

Unity + HoloLens · Built for ChristianaCare, one of the largest health systems in the US

05

Step 5

The Invisible Layer

The previous four steps showed work you can see. This is the work you'd miss. The thinking behind shipped products, the case made for new ones, the systems that let other people build.

made the work estimable

gave the product a face

turned a prototype into a funded project

engineers shipped without me in the room

SJ
A letter to my next team

You started with one small decision.

SJ

To my next team

Most enterprise software isn't designed. It accumulates.

Ten years of patches. New datasets bolted onto old screens. Every feature request answered with one more button, one more toggle, one more column.

I design for the people who use those tools. Traffic operators, analysts, freight planners. Six years of this work, four of them at a research lab building for state agencies across the US.

The portfolio is a sample. Most of what I've shipped isn't here. The platforms are behind logins, the data is operational, a lot of screens just can't live on a public site.

Here's how I approach it.

I sit with operators before I design. I push on information architecture when a screen feels crowded. I read API docs to find what the spec missed. I draw journey maps when product managers think they don't need one. I prototype to secure funding. I stay through shipping.

An engineering background helps. I know what's cheap to build and what isn't, and I don't hand off work I can't defend in a technical review.

Small team. Hard problems. If that's you, let's talk.

Shwetank Jain
Product Designer