01
Treat state as content
Trading state cannot be relegated to color or a transient toast. Labels, hierarchy, feedback, and timing have to explain what the system knows, what it is doing, and what remains unresolved.
Case01 / 05
Sorella Labs
Making market infrastructure understandable
Angstrom is a DeFi trading and market-infrastructure product. The design problem was not to make complexity disappear. It was to reveal the right state, constraint, and consequence at the moment a person needed to act.
LeadProduct design
Protocol → productCore translation
Flows + statesCore design work
The problem
Trading products compress protocol rules, market movement, account state, and irreversible action into a small number of moments. When those moments are vague, visual polish cannot manufacture trust.
I partnered with founders and engineering to translate protocol and implementation constraints into product flows, information architecture, interface states, and specifications the team could build against.
Working idea
Comprehension before commitment.
How it fits together
A simple model of the system behind the interface.
- A
Intent
Make the action and its object unmistakable.
- B
Constraint
Surface the system rules that can change the result.
- C
Preview
Show expected execution, state change, and uncertainty.
- D
Confirmation
Close the loop with a durable, intelligible record.
Key decisions
The choices that shaped the work.
02
Make confirmation part of the product
A signature request is not the end of the experience. Confirmation needs to reconnect intent, execution, and resulting position so the user can verify what changed.
03
Prototype against engineering reality
I used working prototypes and code-aware tools to test interaction behavior against engineering constraints, then shared decisions in a form the team could inspect.
The work
Original artifacts, cropped and sequenced to show the decisions behind them.
Selected public material from the Angstrom engagement. The identity documents part of the system; it does not stand in for the product work.
A restrained base palette gives functional feedback colors enough contrast to carry meaning.
Display, system, and technical voices are separated so interface information can remain clear under density.
The expressive layer is deliberately distinct from the product’s functional layer.
What this case shows
What the public work can show
The public material does not include adoption, conversion, or revenue data. What it can show is the design work: protocol and engineering constraints turned into clearer flows, detailed states, and specifications.
What the work delivered
Stated plainly, without padding the result.
- 01
Clarified product decisions around order flows, trading states, confirmations, and confidence in high-consequence actions.
- 02
Connected protocol behavior, product language, and the interface.
- 03
Used code and AI tools to prototype, test, and communicate interaction behavior.