The app
I led product design end-to-end across garden, from early product definition to a mature system processing billions in volume.
The work focused less on visual novelty and more on building a predictable, low-friction experience that users could trust under real financial and operational constraints.
In a space dominated by themed, high-noise interfaces,
I deliberately set a more understated design direction:
reduce surface area, minimize cognitive load, and align product decisions tightly with business priorities.
As a result, core interaction patterns stayed stable across multiple product generations.
Years in production
3+
Total volume processed
$2B+
Design principles were intentionally simple: less, but better, clarity over cleverness, and confidence over spectacle.
The interfacte is so intuitive
- Niko Kampouris , Unichain
The explorer is just gorgeous
- Chase Chapman, Unichain
This is a delight to use.
Kyall Walker, Persistence Capital
Best BTC bridge I ever used.
- @BlurCrypto
The website
The landing page evolved alongside the product, serving as a practical way to learn what holds up and what doesn’t.
all that on a real, high-traffic corporate website.
Each iteration refined not just messaging, but the underlying system: enabling faster updates, clearer communication, and reliable handoffs as the team and product matured.
Homepage strategy resets
3
Major live versions
3
Learning what works & building systems around it.
The system
A major challenge on this project was handling the complexity of a Bitcoin interoperability system without pushing that complexity onto the user.
Garden serves very different needs across its surface area, from simple swaps and transaction tracking to solver infrastructure and API tooling. Reducing mental load meant splitting the product into specialized tools, while keeping them visually coherent and intuitive within a single system.
This required a flexible design system that could scale across user-facing products and internal infrastructure, stay consistent over time, and adapt as the product matured.
Distinct user roles
4
Product surfaces
7
One system, multiple mental models.
The team
As garden scaled from a small founding group into a multi-disciplinary organization, design work extended beyond the product into how the team itself was built and operated.
I took an active role in shaping how designers were recruited, onboarded, and evaluated.
from running a focused two-week recruitment drive in India to defining expectations around performance, ownership, and craft.
Beyond day-to-day team building, I explored ways to scale design culture itself, including the concept for a recuring design hackathon initiative (frame25), aimed at attracting talent and stress-testing our systems.
Major product phases
3
Design team size at peak
6
Design as an organizational system, not just a visual one.