The Innovation Engine Podcast

The episode surfaces a handful of genuinely useful frameworks - the behavioral definition of outcomes, the three magic questions, and the layered roadmap structure - but the ideas are spread thin across a 46-minute runtime dominated by host anecdotes and warm affirmation. Most of the conceptual content is a light oral summary of a short book rather than novel thinking unpacked in depth.

“An outcome is a change in behavior that creates business value.”

“What are the user and customer behaviors that create value?...How do we get people to do more of those?...How do we know we're right?”

The outcomes-over-outputs framing is well-established in agile/lean product circles, and the book itself predates this recording; there is little here that challenges or extends the prevailing consensus. The sales-led vs. product-led tension and the 'products are hypotheses' idea both circulate widely, and the episode adds no contrarian edge.

“you have to make a choice if you're going to be sales led or product led”

“the three Bs of, of scientific innovation are, are bed, bath and bus. That's where all the great breakthroughs happen”

Seiden is a credible practitioner - co-author of a widely-read UX book, multi-book author, and consultant to large financial institutions - which places him above thought-leader-only guests. However, he is primarily a consultant and author rather than a founder or product executive who scaled a company, and his examples are drawn from client engagements rather than personal operating history at scale.

“I worked with a small nonprofit that uh, a few years ago that did a really good job. They came to the consulting company uh, I was a partner in at that point”

“I do a lot of um, like training in methods and process and stuff like that”

The nonprofit marketplace case study is the episode's one concrete, detailed example - with a timeline, transaction targets, and a manual-before-digital sequencing decision - but it is the sole substantive data point in the episode. The rest of the discussion stays at the level of principle and analogy, with no metrics, no named client outcomes, and no quantified before/after results from the guest's broader portfolio.

“we launched the marketplace, they wanted it launched in 20 weeks. We had it launched in three weeks but it was operating manually. And then we had something that was appropriate at their 20 week deadline.”

“we need to have this many companies registered on this side. We have need this many people registered on that side. That's an outcome.”

The host is knowledgeable but repeatedly redirects the conversation toward his own lengthy anecdotes (Pearson, the CEO quota story), leaving the guest in a reactive role rather than being drawn out. Crowdsourcing questions to ChatGPT and ending with an off-topic photography speed round consume significant runtime that could have been used to probe specifics, stress-test claims, or surface implementation failures.

“we actually turned to ChatGPT to generate some, some questions for our, uh, our uh, episode today. And we selected the top two.”

“I got to run identity and access management for Pearson, uh, back when we had Financial, uh, Times and Economist and Penguin Books”