Product Rebels

The episode contains a handful of genuinely useful practitioner tactics - pre-selling via adoption lists before a line of code is written, assumptive interviewing technique, and AI-assisted PRDs enabling engineer-led prototyping - but these are interspersed with substantial filler: leadership platitudes about conviction, 'it's just you,' and the usual 'don't build what they tell you' advice that adds no density.

“we built a following and we built an adoption list before we ever started coding”

“I see that you are doing this or I think you are doing this. And that way it gives them an opportunity to object in a much better fashion.”

The outside-in, jobs-to-be-done framing and 'watch behavior, not stated preferences' insight are well-worn product management orthodoxy; the assumptive interviewing technique is the most novel element, and the AI-to-PRD-to-production-ready-engineer pipeline has some freshness, but nothing here is genuinely contrarian or first-principles.

“don't fall into the trap of build what they tell you to build and instead watch what they're doing, listen to what they're trying to solve for and build solutions for the problems”

“the worst thing that I have seen so far is somebody builds a wonderful automation and it creates this great deliverable, but the team that's supposed to then use it tries. At one time, doesn't really get it fully”

Jared is a genuine senior practitioner who has operated at real scale - CPTO at Booknook with verifiable turnaround results and 17 years at a major ed-tech publisher reaching millions of users - not a career podcast guest, and the transcript reflects lived experience rather than polished thought-leadership.

“taking customer attention from 27 to 70% and driving the company to its first profitable quarter within a year of joining”

“In a 17-year career, early part of my career at a single company, I never vacated a position that wasn't refilled by somebody that I brought up and coached up into a position”

The episode punches above its weight on specificity: hard numbers appear repeatedly (27→70% retention, 25% YoY revenue growth, $700 build vs. $60k licensing offset, 6-7M learners, 10 percentile-point RCT outcome, math product launched 4 months after reading), giving the abstract claims real grounding, though some passages remain anecdotal and vague about organizational context.

“a zero-to-one replacement of a tool that we're licensing right now cost me$700 to build over the last six days. And so I know exactly what the reward is there. That's a$60,000 offset.”

“we've proven that our intervention can drive outcomes to the tune of 10% telepoint improvement on standardized assessments”

The hosts show some craft - pulling back to an offhand remark about time pressure and pressing for specifics on AI ROI - but the conversation is overall warm and validating, with no meaningful pushback on any claim and a closing 'what can we brag about you' softball that signals a PR-friendly dynamic rather than a genuinely interrogative one.

“I want to go actually back to something that you said just a few minutes ago. And you said it in passing.”

“What's one thing we can brag about you right now?”