Back to Work
Case Study - Product Design

From Figma to shipped: a UX career evolves in the age of AI

I spent my career mastering the tools that defined UX - Adobe XD, Sketch, Protopie, Figma. Then, about a year ago, I made a deliberate shift. Not away from design, but deeper into it, using AI to close the gap between what I could imagine and what I could actually ship.

Career-long UX foundationLed teams of 3-30AI-native workflow for 1+ yearLaid off January 2025v0 - Claude Code - GitHub - VS Code3 shipped apps
Background

A deliberate evolution, not a pivot

My whole career as a UX designer was built on the tools of the craft. Adobe XD in the early days, Sketch for years after that, Protopie for high-fidelity interaction design, and Figma most recently - a tool I still use fluently today. These shaped how I think about interfaces, systems, and the relationship between design decisions and user outcomes.

Throughout that time I stayed an individual contributor by choice, while also directly leading creative teams ranging from 3 to 30 people - product designers, copywriters, and researchers. That combination of doing the work and guiding others through it gave me a perspective on design quality that's hard to get any other way. You learn what good looks like when you're accountable for it at both levels.

About a year ago, I started integrating AI tools into that foundation. Not to replace the design thinking those years had built, but to extend what I could do with it. v0 and Claude Code became the bridge between a design decision and a working component. What used to require a full engineering sprint to validate could now be tested in an afternoon.

When a layoff hit in January, I didn't have to find a new way of working - I already had one. The products here are the result of that workflow put to the test.

"The tools changed completely. The design thinking that makes them useful didn't."

Yes, this case study was authored with the help of Claude. That's exactly the point.


Tools & Workflow

The shift in my stack

The transition wasn't about abandoning craft. Figma is still where ideas take shape. But over the past year, the tools I reach for when it's time to build and validate have fundamentally changed.

Design-tool era
Adobe XD
Sketch
Protopie
Figma (still active)
AI-native era
v0 by Vercel
Claude Code
GitHub
VS Code
v0 by Vercel
Rapid UI scaffolding and validating ideas with real components before handoff
Claude Code
Primary AI coding partner for logic, debugging, and iterating on complex interactions
GitHub
Version control and repository management throughout every project
VS Code
Local development environment for reviewing, editing, and running code

Work

What we built

These three projects were built in close collaboration with an engineer partner. AI changed how we worked together - not who did what, but how fluidly we could move between idea and implementation.

Renovation app
App 01
Renovation app
Consumer web app - Home renovation platform

A platform for homeowners to visualize renovation projects, price out products, connect with local contractors, and track progress from first idea to final build.

v0Claude Code
File manager
App 02
File manager
Internal tool - File transfer visualization and management

A real-time dashboard for teams to visualize, track, and manage file transfers across SFTP pipelines, with full status visibility from queued to delivered.

v0Claude Code
Customer search
App 03
Customer search
Enterprise SaaS - Unified financial customer intelligence

A "Google" for financial services teams - search across customer records, accounts, and connections from a single interface, unified across all core systems.

v0Claude Code

Reflection

What a year of building actually taught me

01
AI is just another tool. The craft is the foundation. Every year spent in Figma, Sketch, and XD sharpened the design judgment that now drives better AI output. The tools changed. The thinking that guides them didn't.
02
AI made collaboration better and more actionable. When both sides of a design-engineering partnership are AI-fluent, the feedback loop gets faster and the gaps in translation between design intent and implementation get smaller.
03
Prompting is a design skill. Writing a good prompt is structurally similar to writing a good design brief. Constraints, context, and clarity of outcome are what separate useful AI output from generic noise.
04
Iteration speed changes your judgment. What used to take a sprint now takes an afternoon. That compression doesn't eliminate the need for good process - it amplifies the cost of skipping it.
05
The best outcomes come from the best partnerships. The goal was never to work alone. It was to bring so much more to the collaboration that the whole team could ship something neither of us could have built the old way.
What's next

Looking for a team where design and engineering genuinely build together

I'm a Lead Product Designer with a career-long UX foundation, a track record of leading creative teams of 3 to 30 across design, copy, and research, and 1+ year of hands-on AI-augmented product experience. I've stayed an individual contributor by choice - and built some of my best work that way. I'm looking for a full-time role at a company where design and engineering are deeply collaborative and AI-fluent on both sides.

hellokylegoe@gmail.com - LinkedIn