Petro Dudchenko

How I work

The job of a designer has changed a lot. Here's how I actually work today — what I still do by hand, where AI does the heavy lifting, and the roles I step into when a product needs them. Less about one project, more about how I operate.

The short version

I'm a designer who doesn't stop at the mockup. I design the thing, build a lot of it, use AI to move fast, and step into product and team roles when that's what moves the work forward.

  • Design, hands-on — UI, brand, and the design systems that hold them together.
  • Design to code — I build in the real stack, so nothing gets lost in handoff.
  • AI as leverage — prototypes in hours, and systems that scale without me.
  • The people side — customers, stakeholders, and design teams.
⬚ image · to capture

How the work fits together

A simple workflow diagram: design → code → AI → product/team. Or one unified page visual. Placeholder — to be replaced later.

/how-i-work/overview.webp
WEBP · wide ~2400px

Design, hands-on

The craft is still the core. I'm in Figma every day — interface design, brand, and design systems: tokens, components, and the rules that keep a product consistent as it grows. This part hasn't gone away; it's the foundation everything else builds on.

Design to code, no handoff

I don't just hand off mockups. I work in the product repos — defining tokens, shaping component APIs, and writing the components themselves (web, iOS, Android, or Framer). When the same person designs it and ships it, nothing gets lost in translation, and the design system is the real, running code — not a Figma library that drifts away from the product.

contributions · last 12 monthsJun 2025Jun 2026
560 contributions in the last yearLessMore

AI as leverage

AI changed how fast I can move and how much one person can hold. Two ways I lean on it:

  • Prototypes in hours, not weeks. I build clickable, real-feeling prototypes with AI tools and take them straight to customers — so feedback lands on the real thing, not a static mock, before engineering commits.
  • Systems that extend themselves. I set up repos with machine-readable rules and AI agents that scaffold new components on-spec — typed, tokenised, on-brand — so the system stays consistent without me policing every change.

The point isn't novelty — it's leverage: ship more, keep quality high, and spend my time on the hard parts instead of the repetitive ones.

Claude Code · last 12 monthsJun 2025Jun 2026
Sessions
40
Messages
31,223
Total tokens
43.1M
Active days
34
Current streak
1d
Longest streak
6d
Peak hour
4 PM
Favorite model
Opus 4.8
LessMore

The people side

Design isn't only the screen. Depending on what a product needs, I step into:

  • Customer & stakeholder work — I take demos and prototypes to customers, gather feedback first-hand, and start those conversations myself rather than wait for a brief.
  • Design leadership — I've built and led a 20+ person design org: structure, hiring, a fair career-leveling system, and the standards that keep quality high at scale.

I'm comfortable as the maker — and as the person who builds the function around the making.

What stays constant

Tools change fast; the approach doesn't. Show up, do the repetitive work well, and play the long game — the same discipline I bring to triathlon. Whatever the tool, the goal is the same: a product that feels simple, stays consistent, and gets better over time.

Work with me

If that's the kind of designer your team or product needs, let's talk.