Most designers are good at making things look right. Far fewer are good at making things get built. That gap — between the beautiful Figma file and the deployed product — is where most design careers quietly stall out, and where the ones who actually matter separate themselves from the ones who don’t.
Figma is a frictionless environment. You can make anything look polished in an afternoon. Shadows, gradients, auto-layout, perfectly nested components — the tool rewards visual precision and punishes nothing. Pixels don’t push back. Engineers do. The result is a whole generation of designers who have optimized their process for the portfolio screenshot: the hero screen, the perfect hover state, the one flow where everything lines up just right. What they haven’t optimized for is the thing that actually has to ship.
Real product design is mostly unglamorous. It’s the empty state when there’s no data yet. It’s the error message when the API times out. It’s the loading skeleton, the disabled button with a tooltip that actually explains why it’s disabled, the form that still makes sense when a user’s name is forty characters long. None of this ends up on Dribbble. All of it determines whether people trust the product or quietly lose confidence in it. The designers who understand this don’t treat those details as afterthoughts. They design the edge cases before anyone asks.
The relationship with engineers is where most designers lose the plot entirely. I’ve seen it enough times to know the pattern: designer throws screens over the fence, engineer builds the closest approximation they can manage, designer is quietly disappointed, product is worse for it. The designers who ship don’t work that way. They talk to engineers before they design anything significant — not to ask for permission, but to understand what’s actually buildable in the time available. They show up to standups. They ask what’s been scoped, what the technical constraints are, where there’s flexibility and where there isn’t. Then they design inside that reality instead of around it.
What a founder actually needs from a designer is different from what most designers are selling. They don’t need a brand exploration or a mood board or a three-week discovery phase. They need someone who can read a messy product brief, identify what’s actually being asked, and come back with screens that are ready to hand to an engineer on Monday. They need speed without sloppiness. They need someone who asks sharp questions upfront so there are no expensive surprises later. They need a collaborator who makes the whole process feel less chaotic, not more.
I’ve been doing this for ten years across SaaS products, fintech tools, and Web3 platforms. The work I’m proudest of isn’t the work that looked the best — it’s the work that got built, that people used, that solved the problem it was supposed to solve. That’s the only measure that matters. The Figma file is a means to an end, not the end itself. I’d rather ship something imperfect than perfect something that never ships.
