The Product Science Podcast

The episode has genuine substance in the value-vs-usability distinction and the Amex call-center case study, but significant runtime is consumed by career biography, the guest's ETA business pivot, and a self-promotional lab notes segment from the host's own team. Insights arrive in bursts rather than consistently.

“you have to basically go out and test for value. You have to get them to react to words or to experiences or other types of things. You have to observe them in their environment”

“they had done the spreadsheet analysis out the yin yang, like, look, if you just move 20% of calls, look how much money we save and everything. And I said, but what do customers want? And they had no idea”

The functional/emotional/social value trifecta is a restatement of well-worn frameworks (Jobs-to-Be-Done, basic marketing theory), and the 'it's not about the technology' lesson is a podcast cliché. The ETA/SMB acquisition angle is fresher but underdeveloped.

“logically, there's no reason for people to buy luxury brands, luxury products, right? There's no reason to buy a Porsche over a Chevy”

“those are almost never the reason people make a product decision”

Andy Breen is a genuine practitioner - engineering roots, ran product at American Express, grew a commercial insurance digital channel from zero to $300M, and now operates acquired businesses as CEO. This is real operator experience at scale, not a thought-leadership circuit rider.

“basically went from zero digital revenue when I joined to uh, over 300 million in a few years”

“did a stint to running product, uh, for American Express's services division”

There are meaningful specifics - 150M calls/year at Amex, $300M digital revenue, 4,000+ designer partners, 8-10x return on first acquisition - but much of the evidence is qualitative and anecdotal; the 20-customer interview insight is presented as conclusive without methodological detail.

“we get 150 million phone calls a year”

“we've partnered with 4,000 or over 4,000 now, um, independent designers”

The host asks reasonable follow-up questions about internal change management and value-testing mechanics, but never pushes back on vague claims or challenges the guest. The lab notes segment at the end is essentially the host's team validating their own methodology using the guest's words.

“So uh, I just love everything you had to say there. It aligns so well with a lot of the things that, that I think and teach as well”

“how did you shift mindset inside the company to understand and get on board with the direction”