Why a Designer Who Can’t Code Is Designing for a Product That Doesn’t Exist

When a designer does not understand how things get built, they design a product that cannot exist on the time and budget available.

Engineering then trims it to fit. The user gets whatever survived. Nobody chose that outcome, which is exactly why it keeps happening.

The fantasy product problem

Beautiful mockups routinely describe something nobody can ship.

The designer hands off a vision. Engineering makes the cuts, usually alone and usually under time pressure. The decisions about what the product actually is end up being made by whoever was closest to the deadline.

That is not an engineering failure. It is the natural result of drawing something without knowing what it costs.

Why building changes your decisions

I write code and ship things myself. That has not made me a better visual designer. It has made me a better decider.

Knowing what is cheap and what is expensive means I spend design effort where it moves the product, and stop spending team time on details that will not survive contact with production.

The change happens upstream, before anything is drawn, which is where the expensive decisions live.

Design, engineering and business are one decision

An MBA taught me to ask whether this makes money. Engineering taught me to ask whether we can build and maintain it. Design taught me to ask whether anyone will love it.

Good products answer all three at once. Splitting them across three people who hand work between them is where most products lose their edge, because every handoff drops something and nobody is accountable for what was dropped.

What this means if you are hiring

The most useful designer is rarely the one with the best looking portfolio.

It is the one who understands your business goals, can reason about what is buildable, and makes decisions that hold up when they meet real constraints. One person holding all three lenses removes entire rounds of translation loss, and translation loss is where products get boring.

Questions I get asked

Does every designer need to code? No. They need enough fluency to understand cost, constraints and feasibility, so their decisions survive the real product.

Why does business context matter? Because design that ignores the business model produces experiences people like and companies cannot afford to keep running. That is not a win for anyone, including the users who liked it.