Sketch the user journey and review systems - product-minded engineering with Drew Hoskins

If you jump straight to implementation before you can explain the user journey, this episode is for you. Kent talks with **Drew Hoskins** - author of The Product-Minded Engineer, Senior Staff engineer at Stripe - about the otter metaphor, avoiding the Cthulhu effect in user interviews, and reviewing systems instead of diffs. They cover Facebook product-hybrid archetypes, Temporal and Stripe loops, the rule of three for generalization, and homework: sketch one feature's journey and hunt for plot holes. - (00:00) - Meet Drew Hoskins - (00:33) - The Product-Minded Engineer - (03:21) - Stripe and developer products - (06:11) - From compilers to product hybrid - (08:34) - Facebook archetypes and career turn - (10:57) - Temporal PM, then back to Stripe - (13:51) - Sketch the user journey - (16:13) - Balancing systems and users - (21:05) - Fire-and-forget codegen risks - (25:00) - Avoiding the Cthulhu effect - (30:43) - Puzzle approach to empathy - (33:28) - Rule of three - (39:43) - Review systems, not only diffs - (46:03) - Homework: sketch one journey Drew Hoskins (he also goes by Andrew) is the author of The Product-Minded Engineer. He started as a compiler engineer at Microsoft, built deep systems at Facebook and Oculus, founded Workflow Engine at Stripe, spent two years as a PM at Temporal, then returned to Stripe engineering after the book shipped - living the product-hybrid path he writes about. The through-line is product-minded engineering as a career shape, not a side hobby. At Facebook, Kent Beck's staff archetypes named "product hybrid" as a real mode. Drew doubled down instead of managing. The otter metaphor from the book frames engineers who play across product and systems. User interviews go wrong when you summon the Cthulhu effect - leading people into agreeing with your idea. Sketching the journey (discovery, understanding, usability, safe usability) exposes plot holes before you ship. They talk balancing systems thinking with user empathy, reviewing systems not diffs as agents write more code, deferred trust and conditional approvals, and the rule of three for when to generalize. Homework: take a feature you are working on, sketch its user journey in detail, and look for plot holes - how users find it, how they understand what it means, where the story breaks. **Homework** - Pick a feature you are working on. - Sketch the user journey in detail (discovery, understanding, usability / safe usability). - Look for plot holes: how does the user find it, understand what it means, and get through without getting stuck? **Resources** - The Product-Minded Engineer (O'Reilly) - The Product-Minded Engineer (Substack) - Drew on LinkedIn - Temporal - Stripe **Guest: Drew Hoskins** - Company: Stripe **Host: Kent C. Dodds** - Website: kentcdodds.com - 𝕏: @kentcdodds - GitHub: @kentcdodds - YouTube: kentcdodds-plus - Podcast: epicproduct.engineer See on Epic Product Engineer