original-3afea57044a57bf5338e9790f900ee8e.webp

01. The Challenge: "Design for High Anxiety"

Coinshift is a treasury management suite for DAOs, decentralized organizations managing their funds on-chain.


02. The Process: Getting to the Answer

Understanding the users

Before designing, I needed to understand how treasury managers actually worked and what they were afraid of. I ran interviews with managers directly, and for smaller or more specific questions I used structured forms to gather input at wider scale. I also worked closely with our business development team, who spoke to users constantly and carried a lot of unfiltered insight about where people struggled.

The pivotal insight: a treasury manager signing off on multiple transactions doesn't think in system states. They think in "what needs my attention right now." So the real problem wasn't displaying transactions, it was helping the user triage them.

That reframed everything. We prioritized by amount as the primary signal, the larger the transaction, the more attention it demanded. But amount alone wasn't enough, because sometimes a small transaction was urgent and needed to happen now. So we added an "important" tag that the person requesting approval could apply, letting urgency surface independently of size. On each transaction, the approver could see what genuinely needed their eyes rather than scanning an undifferentiated list.

Designing and validating

I designed the approval flow as a card-based queue, which matched that triage mental model. Rather than committing to it blind, I put prototypes and basic front-end flows in front of real users and advisors, paired with a short form to capture their reactions, and monitored actual behavior with Hotjar once things were live. That loop, prototype, gather direct feedback, watch real usage, let me refine the flow against how people actually behaved rather than how I assumed they would.


03. The Solution: Trust by Design

I led the end-to-end design of the Coinshift v1, v2, and v3 web apps.