TL;DR: When a designer doesn't understand how things are built, they design for an idealized product that engineers then have to quietly water down. Understanding engineering — and understanding the business — changes your decisions upstream, so you design for what can actually be built, maintained, and grown. That combination of design, code, and business is where real product impact lives.

The fantasy product problem

Beautiful mockups often describe a product that can't exist on time or on budget. The designer hands off a vision; engineering trims it to fit reality; the user gets the leftovers. Nobody decided this on purpose — it's the natural outcome of designing without knowing the cost of what you're drawing.

Why building things changes your decisions

I write code, work hands-on with AI tools, and ship things myself. That doesn't make me a better visual designer — it makes me a better decision-maker. When you know what's cheap and what's expensive to build, you spend your design effort where it actually moves the product, and you stop burning team time on details that won't survive contact with production.

Design, engineering, and business are one decision

An MBA taught me to ask “does this make money?” Engineering taught me “can we build and maintain this?” Design taught me “will people love it?” The strongest products answer all three at once. Treating them as separate disciplines — handed between separate people — is where most products lose their edge.

What this means for hiring

If you're a founder, the highest-leverage designer isn't the one with the prettiest dribbble shots. It's the one who understands your business goals, can reason about what's buildable, and makes data-informed decisions that actually convert. One person holding all three lenses removes entire rounds of translation loss.

FAQ

Does every designer need to code? No — but they need enough fluency to understand cost, constraints, and feasibility, so their decisions hold up in the real product.

Why does business context matter for design? Because design that ignores the business model produces experiences users like but companies can't sustain. Great design serves both.

Carlos Lastres is an MBA, Apple Design Award–winning product designer, and software engineer based in Tokyo. He works at the intersection of design, engineering, and business, shipping conversion-focused products to millions of users.