What Architecture Taught Me About Product Design
I came to product design through architecture — I studied it in undergrad and again for my first master's, drawn to shaping the spaces people move through. But over time it felt not quite down-to-earth enough for me. So much of architecture lives in beautiful concepts that never get built, ideas floating free of real context and constraint.
Product design pulled me the opposite way: it's practical. A product has to answer to real markets, budgets, timelines, and the messy work of actually shipping. Those constraints aren't obstacles to the work — they are the work, and they're what turn an idea into something people can actually use.
I left architecture seeing mostly its shortcomings. Only later, deep in product work, did I realize the gift it had given me — its very first lesson: that human feeling matters. I spend my time in highly technical spaces like cybersecurity and complex enterprise tools, where people's real needs often get buried under engineering priorities. Systems meant to make work easier end up heavy — full of jargon and layered steps, asking users to understand the machine before they can decide anything. I think it should be the other way around: we build systems so people don't have to hold every detail in their heads. Whether the material is a building or a screen, my job is the same — to put humans first.