During my eight years working in agile product development, I have watched sprints move quickly while real understanding of user problems lagged. Backlogs fill with paraphrased feedback. Interview notes sit in shared folders collecting dust. Teams make decisions based on partial memories of what users actually said. Even when the code is clean, those habits slow delivery and make it harder to build software that genuinely helps people.
It's a debate I've been dragged into so many times, I've lost track: UX vs. Market Research? Qual vs. Quant? Who owns the insights? Who make the decisions? Who drives the strategy? Who makes the "real" impact? I've been a UX Researcher for over 20 years and my thinking is deeply rooted in building meaningful products and services that solve real human problems... (As opposed to fake problems... you know, the kinds of problems that we invent in order to justify the product we're building-alas, I digress).
I used to leave design presentations with a stack of changes and a heavy heart. Over 20 points to revise was normal. Most of the feedback wasn't from users; it was subjective opinions from stakeholders. Nothing felt anchored. I'd rush through the screens, hoping the room wouldn't ask hard questions. Then I learned to stop just showing screens and start telling the story behind them. The result was immediate: clearer conversations, fewer rounds of rework, faster buy-in, and designs that actually reflected user needs.
Behind every seamless user interface, stylish wearable, or smart home device you love is a carefully crafted product design process-built through iteration, research, and hours of fine-tuning by product designers obsessing over every detail, right down to the last pixel. But, too often, teams jump from idea to execution, skipping the critical groundwork. The result? Products that look good on paper but fall flat in the real world.
