Regulatederror-intolerant domain
Densedata-heavy screens
Workflowclassification & docs
Livein design now
The domain
Customs classification and documentation. Getting a code wrong isn't a bad user experience — it's a fine, a delay, a held shipment. The design constraint is unusual: the interface's main job is to make the wrong entry hard to make.
How I approach it
Progressive disclosure over dense tables, validation at the point of entry rather than on submit, and empty and error states treated as primary screens instead of afterthoughts.
Note — client work in progress; screens are under restriction. Happy to walk through the thinking and the flows live.