How I Operate

I don't see design as a layer on top of a product. Design is how decisions get made. It's how a messy idea becomes something people can understand, trust, and use.

This is how I operate any product, team, or founder I work with.

I start from reality, not from Figma

Before I care about UI, I care about context. What problem are we actually solving? Who is this really for? Where does this sit in their day and in the business? What's already working that we shouldn't break?

I talk to founders and teams first, tools later. I want to understand the tension, the constraint, the stakes. Good design comes from clear reality, not a cool visual direction.

I care about taste and tiny details

I pay close attention to the parts most people ignore. The first five minutes of using a product. The moment someone gets stuck. The tone of an error message. How it feels to use late at night when you're tired.

This is where trust gets built. You can feel when a product was designed by people who actually use it and care. That's the standard I hold myself to.

Taste isn't aesthetics. It's knowing what feels honest versus what feels cheap for this product and this audience.

I think in systems, not screens

I don't design isolated pages. I design systems that scale.

When I look at a product, I'm looking for the core loop. How does someone enter, understand, and keep coming back? How do brand, product, and communication reinforce each other?

I like building structures a team can keep shipping inside. A clear story the whole team can repeat. A visual language that works across product, web, and decks. UX patterns that make new features easier to add, not harder.

If we work together, I'm not giving you a few pretty flows. I'm helping you build a system you can grow inside for a while.

I anchor design to outcomes

I get excited by good visuals, but I measure success in what moves.

Activation. Retention. Trust. Conversion. Better clients. Clearer story.

Every design decision sits on one question: does this make it easier for the right person to understand, start, and stay?

That's how I choose what to work on first, what to simplify, and what to cut.

I like constraints

I don't need perfect conditions. I prefer honest ones.

Limited engineering, tight timelines, unclear data, legacy product. That's normal. Constraints force focus. They force tradeoffs. They make you choose what actually matters.

My instinct is always: what's the smallest thing we can do that meaningfully changes reality? What should we protect? What can we safely ignore for now?

This is how I avoid endless redesigns and help teams actually ship.

I work as a partner, not a decorator

I do my best work close to the founder and the core team.

I want to understand how you think, what keeps you up at night, what you're building beyond the next release.

You're not getting someone who delivers files. You're getting someone who questions assumptions with you, sharpens the story, translates strategy into product and brand moves, and holds the bar for quality without losing momentum.

I'm a design operator sitting next to you, not an external vendor throwing work over the wall.

What makes me different

I think like a founder. I design like someone who ships.

I've been first design hire at a protocol that scaled. I've helped founders raise, launch, and grow. I've seen what works at 0→1 and what falls apart when you're moving fast with limited resources.

I can sit in conversations about product, growth, and roadmap, then turn that into interfaces, stories, and systems that actually move things. I care how it looks. I care more whether it worked.

If you want someone to make things look nicer, there are plenty of options. If you want someone who helps you think clearer, choose better, and design work that matches your ambition, that's where I fit.

Let's Work

Want to build something together? Get in touch at hi@0xdragoon.xyz