Testimonial

Testimonials

See What Other Said About Us

Read how ‘Design For Your Realities’ helped product managers, designers, developers, and business leaders rethink their approach to building products. These reflections come from people who recognized their own teams in Sarah’s struggles.

I have been a product manager for eight years and saw my team in every mistake Sarah’s team made. We ship features constantly but struggle to show impact. The focus on outcomes over outputs gave me language to explain why we need to change our approach. I shared the opportunity tree concept with my team and it shifted how we prioritize immediately.

Harry

Founder & CEO

As a designer, I often feel pressure to produce mockups before understanding the problem. Sarah’s insistence on research and validation before design resonated deeply. The empathy mapping section gave me practical tools to push back on stakeholders who want solutions before we have defined what we are solving. This book validated my instincts about process.

Jordan

Manager

The reporting feature failure early in the book was painfully familiar. We built an entire analytics dashboard based on what we thought users wanted, only to discover they found it confusing and never used it. Reading about Sarah’s team making the same mistake then learning from it gave me hope that we can recover from our failure too.

Chris

Developer

I manage stakeholders constantly and struggle to say no to feature requests that do not align with user needs. The section on communicating with stakeholders while advocating for research based decisions gave me strategies I used immediately. The book emphasizes that saying no requires offering alternatives and explaining reasoning, which is obvious in hindsight but I was not doing it well.

Sarah

Writer

The concept of humanizing data changed how I look at analytics. I was obsessed with conversion rates and usage metrics but rarely thought about why those numbers were what they were. Now I pair quantitative data with qualitative research to understand the emotional and contextual factors driving user behavior. That combination produces better insights than numbers alone.

Rosie

Designer

As a developer, I appreciated that the book acknowledged the challenge of iterating quickly. Sarah’s team learns to build prototypes and run experiments without massive resource investment, which requires different skills than building production code. The book treats this as a learned capability rather than expecting it to happen naturally, which felt realistic based on my experience.