Triage your backlog with LNO - product-minded engineering with Sam Julien - Become an Epic Product Engineer

If you only get asked about feasibility, this episode is for you. Kent talks with Sam Julien - Director of Product at CopilotKit, author of Agentic GraphRAG - about moving past ticket-taking, collaborative product-engineering dialogue, and frameworks that help you push back with vocabulary.

They cover leverage / neutral / overhead triage, Kagan's four big risks, communicating intent with AI agents, and why engineers need product models even when they have a PM.

(00:00) - Meet Sam Julien
(01:26) - Dev to DevRel to product
(03:37) - Product, design, and engineering overlap
(06:00) - Durable skills as agents write code
(12:01) - Get closer to customers
(15:34) - Building a product-minded engineering team
(18:46) - When technical work was the whole job
(25:28) - Talk through the problem first
(33:26) - Sales-driven development and gatekeeping
(36:26) - Beyond feasibility
(39:35) - LNO, RICE, and friends
(42:42) - Continuous discovery and agents
(46:44) - Communicating intent to AI
(51:27) - Homework: triage your backlog

Sam Julien went from self-taught web developer to developer relations to product. He is Director of Product at CopilotKit (generative UI across front ends, Slack, Teams) and author of the O'Reilly book Agentic GraphRAG.

The through-line is product-minded engineering as a durable skill. Implementation-only careers are getting thinner as agents take more code work. Sam's article on building a product-minded engineering team name-drops jobs-to-be-done, Kagan's four big risks, continuous delivery, LNO (leverage / neutral / overhead), DHM, RICE, and North Star - and he lands on LNO as especially practical for backlog triage.

Leverage work: small effort, outsized outcome. Neutral: necessary, so scope it. Overhead: automate or drop - often a fit for AI. Engineers need these models so they can push back with shared vocabulary, especially when the PM is checked out. Feasibility alone is not enough; value, usability, and business viability belong in the dialogue.

They also talk collaborative product-engineering conversations, gatekeeping sales-driven development, and communicating intent clearly when agents execute.

Homework: spend ten minutes on your backlog and apply at least one triage framework (LNO or similar). Extra credit: watch something recent from Teresa Torres.

Homework

Open your backlog once this week.
Spend about ten minutes sorting items with a triage lens (LNO - leverage, neutral, overhead - or another framework from the episode).
For each item, ask why you are doing it, what the effort is, and what the value or impact is.

Resources

Guest: Sam Julien

Host: Kent C. Dodds

See on Epic Product Engineer

Triage your backlog with LNO - product-minded engineering with Sam Julien

Om avsnittet

Fler avsnitt

Get five people talking about your product - iterative feedback with Ben Vinegar

Start with curiosity and talk to a customer - continuous discovery with Teresa Torres

Lead with empathy and listen without defense - product sense with Mark Techson

Keep a friction log and read a sales book - product ownership with Joyce Er

Use the product yourself - empathy, architecture, and PM partnership with Rita Kozlov

Ask why in every PR - product engineering with Erin Fox

AI is a tool, not a silver bullet - product discovery with Peppe Silletti

Curiosity, micro-sales, and AI as a supplement with Shaundai Person

Talk to users, ship live demos, and build durable products with Michael Grinich

Write it down: process, benchmarking, and product judgment with Ronan Berder