Why does one vivid customer story outweigh months of research? This week on the Cognition Catalog, we break down the anecdotal fallacy — our tendency to let a single experience override real evidence. Learn why stories hijack decisions, how this shows up on product teams, and what you can do about it.

Have you ever watched weeks of solid research get sidelined by one person saying, "Yeah, but I talked to a customer who hated it"?

We've all been in that meeting. The team has done the work—research is solid, the data points in a clear direction—and then someone shares a single story that shifts the entire conversation. A stakeholder mentions one piece of feedback from a sales call, or an engineer pushes back on a technology choice because of a bad experience three jobs ago. Suddenly, the energy in the room changes, and the data fades into the background. That's the anecdotal fallacy at work, and it's one of the quietest ways teams get pulled off course.

In this episode of the Cognition Catalog, I'm breaking down why our brains are wired to favor stories over statistics, and how this bias shows up constantly on product teams, from design critiques to sprint planning to roadmap discussions. We'll look at the research behind why personal narratives outperform aggregate data in persuasion (hint: it's not because people reject evidence, it's because stories are just easier to process and remember). And we'll talk about the HiPPO effect — when the highest paid person's opinion carries disproportionate weight simply because of who's telling the story.

But here's the thing... the goal isn't to eliminate anecdotes. Stories surface edge cases, highlight blind spots, and humanize insights. The key is learning to treat them as hypotheses, not proof. I'm sharing five practical takeaways your team can start using right away to keep one person's experience from becoming the whole team's strategy. Give it a listen.

Topics:• 01:50 - When one story derails the team• 03:49 - What the Anecdotal Fallacy is• 04:21 - Why stories feel true• 06:03 - How it hurts our team• 07:36 - Fixes and team habits

Mahnaz has lived with volatility, uncertainty, complexity, and ambiguity in ways most product teams never will. In this episode, we talk about what happens when VUCA isn’t theoretical, how to avoid becoming an order taker, and how courage, empathy, and initiative can reshape your role as a designer.

What if the volatility, uncertainty, complexity, and ambiguity you’re facing at work feel overwhelming only because you’ve never had to live through it in your everyday life?

I throw the word VUCA around like it’s a trendy framework. Volatility. Uncertainty. Complexity. Ambiguity. But for Mahnaz Hajesmaeili, those aren’t abstract concepts; they’re lived experience.

Originally from Iran, before becoming a product designer, she built a life in China, knowing she could never fully belong there. When COVID hit, borders closed, savings ran out, and the life she had carefully constructed disappeared almost overnight. She returned to Iran, started over, taught herself UX, and eventually rebuilt her career in the United States.

That’s not “roadmap volatility.” That’s real volatility.

This week, I chat with Mahnaz to explore how living through that level of instability reshaped her approach to work. Why rejected designs don’t shake her. Why unclear strategy doesn’t rattle her and why she doesn’t default to being an order taker.

If you’ve ever felt overwhelmed by shifting priorities or frustrated by leaders who “don’t know what they want,” this episode offers perspective—and practical lessons.

Give it a listen. It might change how you define uncertainty.

Helpful Links:
• Connect with Mahnaz on LinkedIn