Unorthodox PM wisdom: Automating user insights, unselling job candidates, logging every decision, more

Kevin Yien leads merchant experiences at Stripe and previously built restaurant products at Square and led product and design at Mutiny. In this conversation with Lenny Rachitsky he shares unconventional PM advice spanning career entry paths, writing, PM-engineer-designer collaboration, decision logs, hiring, automating customer research, and AI.

01Key learnings

• Consider entering product management from engineering, design, or sales, since those roles teach you the front-line work a PM would otherwise take on.
• Treat product management as converting a team's potential energy into realized customer value, and only add PMs where that work actually needs doing.
• Write clearly and compellingly enough that others can act on it; Kevin argues a PM who cannot sell or support their own product should not be trusted to build it.
• Draw the problem perimeter with explicit constraints (target customer, jobs to be done, platforms, principles) so designers and engineers can be creative within bounds.
• Get better feedback by putting a concrete draft in front of people and holding a focused silent-review session rather than asking for async comments.
• Keep a decision log: record the rationale behind decisions, then revisit outcomes later to build product sense through repeated reps.
• Before finalizing a hire, send a candid 'unsell' email listing likely pain points; candidates who stay excited are strong hires, and those who back out early save painful mismatches.
• Automate customer research by routing relevant call-recording mentions (e.g., via Gong and Zapier) to scheduling links, and ensure PMs talk to raw customers rather than only reading summaries.

02Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.