Product Thinking

The episode delivers several actionable insights - experimentation as a cultural practice requiring persistent leadership reinforcement, the 70-20-10 portfolio allocation framework, and learning through iteration velocity - but the format of stitching together short clips limits depth. Most insights are compressed into single sentences or brief anecdotes rather than explored rigorously, and the host's summarization adds commentary rather than new substance.

“It was in our bloodstream, but it wasn't in our DNA”

“if you feel like you're being too repetitive or, oh, well, people got this, now I'm just going to move on. Don't, uh, keep repeating it”

The portfolio allocation framework (70-20-10 or adjusted by disruption level) and the bloodstream/DNA distinction around culture are useful reframes, but the core thesis - that experimentation requires leadership commitment and iterative failure - is well-established in product management. The Copilot acceptance rate insight (30% acceptance can drive value) is interesting but underexplored, and most other advice mirrors standard product playbooks.

“It was in our bloodstream, but it wasn't in our DNA, which meant it was something that was happening. Right. But it wasn't really a part of how they worked.”

“70% of the time that we suggested something to you, you did not accept it... it was completely different”

The guest roster is genuinely strong: David Bland (author of Testing Business Ideas, deep practitioner experience); Monica Lewis (VP of Product at LinkedIn, tier-1 operator); Mario Rodriguez (CPO at GitHub, leader on a high-stakes AI product). These are not career podcast guests - they are practitioners at serious scale who have shipped real products and made hard organizational decisions. However, they appear only in short clips (estimated 3-5 minutes each), limiting depth of access.

“Monica Lewis, VP of Product at LinkedIn”

“Mario Rodriguez, Chief product officer at, uh, GitHub, who takes us inside how Copilot was built through failures, high iteration, velocity”

Some concrete details appear: Monica's move from 'create clarity first' to 'skeleton doc' approach, Copilot's 20-30% acceptance rates, the 70-20-10 resource allocation split, and references to GitHub's outcome-driven principles. But many claims lack specifics - no metrics on actual experimentation velocity gains, no named examples of failed experiments, no company names from David's anecdotes, and no concrete numbers on experimentation ROI. The 14-minute format works against depth.

“acceptance rates were like in the 20%, 30%... 70% of the time that we suggested something to you, you did not accept it”

“roughly we want whatever, 60, 30, 10 or 70, 2010 across those categories”

The host (Melissa Perry) asks reasonable opening questions and provides useful transitions, but does not probe deeply or push back on claims. Follow-ups are soft (e.g., "That's really cool" after the Copilot insight), and the format - short clips stitched together - prevents the extended back-and-forth that would reveal tensions or test ideas. The host summarizes and editorializes rather than deepening the inquiry.

“That's really cool.”

“Monica showed what the answer looks like in practice. Owning mistakes publicly, sharing unfinished thinking early, giving teams room to do discovery before the plan is locked.”