Unorthodox PM tips: Automating user insights, unselling candidates, decision logs, more | Kevin Yien — Lenny's Podcast: Product | Career | Growth Summary

Unorthodox PM tips: Automating user insights, unselling candidates, decision logs, more | Kevin Yien — Lenny's Podcast: Product | Career | Growth Summary | Galaxy of Podcasts

The Conversation Breakdown

Give people something concrete to react to

⏱ Untimed topic

Yien describes presenting a concrete view instead of asking an entirely open question about what others think. A proposal gives the conversation an object to inspect and improve. Treat it as a starting point for feedback rather than a finished answer that others must accept.

Define the problem space

⏱ Untimed topic

He describes product work as drawing the perimeter within which engineering and design can explore. Useful constraints make the conversation productive without prescribing every detail of the solution. Clarify whom the product is for and which problem the team is solving.

Keep attention on the delivered value

⏱ Untimed topic

Yien warns against treating product work as only high-level strategy or kickoff activity. The final deliverable matters because the value must reach the customer. Check the actual result rather than counting completed planning tasks as the outcome.

Audit internal busyness

⏱ Untimed topic

He suggests periodically reviewing what the product manager is doing and how it relates to customer value. As organizations grow, internal processes can consume more attention. The review helps distinguish necessary coordination from activity that no longer serves the result.

Record the decision and its rationale

⏱ Untimed topic

Yien's decision-log practice writes down a choice and why it was made. That record preserves the reasoning available at the time. It is more useful for learning than reconstructing a confident explanation after the outcome is already known.

Return to the outcome

⏱ Untimed topic

He says the log needs later review, not merely more entries. Compare what happened with the original reasoning and expectation. The value is a feedback loop that can reveal where the decision was wrong or where a similar result came from a different cause.

Use practice as a supplement to building

⏱ Untimed topic

Yien suggests additional decision practice by thinking through another team's situation and recording a hypothetical choice. He gives a clear caveat: the log is not a replacement for building products. It adds reflection and repetitions alongside real work, not an excuse to avoid it.

Unorthodox PM tips: Automating user insights, unselling candidates, decision logs, more | Kevin Yien

Executive Summary (TL;DR)

Key Takeaways

Give people something concrete to react to

Define the problem space

Keep attention on the delivered value

Audit internal busyness

Record the decision and its rationale

Return to the outcome

Use practice as a supplement to building

The Conversation Breakdown

Give people something concrete to react to

Define the problem space

Keep attention on the delivered value

Audit internal busyness

Record the decision and its rationale

Return to the outcome

Use practice as a supplement to building

Core Frameworks & Ideas

Problem-space perimeter

Value-focused activity audit

Decision-learning loop

Actionable Next Steps

Notable Quotes

The One Thing to Remember