About me
Designer, AI tinkerer,
illustrator, curious cook.
👋 I'm Suhee Lee, a Senior Product Designer with 7+ years across enterprise platforms, crypto wallets, and IoT dashboards. These days I sit at the boundary between design and engineering: prototyping with AI, shipping pixel fixes directly to production via Claude Code, and rebuilding how my team handles design-to-dev handoff.
How I think
- I bias toward shipping. A scrappy v1 in production beats a polished v2 in Figma.
- Design systems are infrastructure, not artifacts. I treat them like a product: versioned, tokenized, with a roadmap.
- Designers belong closer to code. AI finally made this realistic, and I lean in hard.
- My best work is cross-functional. I'd rather pair with an engineer to ship a fix than write a spec doc about it.
Tools & platforms
Beyond work
I cook 🍲, illustrate on Instagram, and stay on the bleeding edge of AI tooling, partly out of curiosity, partly because it keeps reshaping what a designer's job even is.
A new design→dev workflow
How I ship UX upgrades with AI.
Small UX upgrades (tooltips, alignment, microcopy, accessibility fixes) used to sit in the backlog waiting for engineering capacity. I built a loop that lets me ship them myself, then rolled it out as a workflow for the broader design team.
- 01
Design audit
I find the gap or rough edge, sometimes from user feedback, sometimes from my own crit.
- 02
Ticket
Written up like any product issue, with screenshots and acceptance criteria.
- 03
Implement with Claude Code
In our local env, against our Storybook, using the team's component library.
- 04
Open MR
Goes through normal code review with engineering, same bar as any other PR.
- 05
Iterate & ship
Address feedback, merge, deploy. The loop closes faster than a backlog ticket ever would.