Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To prevent review meetings from becoming about personal opinions, enforce a rule: all criticism must be linked to a testable hypothesis or a clear gap in existing data. This transforms subjective feedback into an objective, evidence-based discussion about what needs to be validated next.

Related Insights

To evaluate ideas without getting bogged down, use a simple framework: What is the idea? Why is it important? Who will it impact? Explicitly avoiding the 'how' prevents premature criticism and focuses the discussion on strategic value.

A three-step structure for feedback: state a neutral observation ("What"), explain its impact ("So What"), and suggest a collaborative next step ("Now What"). This focuses on the work, not the person, making the feedback more likely to be received well and acted upon.

Effective review boards don't just say yes or no. They ask, "What is the next experiment needed to secure the next round of funding?" This approach relies on micro-budgeting for specific tests and regularly rotating board members to prevent political capture and groupthink.

Product managers frequently receive solutions, not problems, from stakeholders. Instead of saying no, the effective approach is to reframe the solution as a set of assumptions and build a discovery backlog to systematically test them. This builds alignment and leads to better outcomes.

The "IKEA Check" is a three-question framework to fight personal bias. 1) Does my conviction come from my work or from evidence? 2) Would I fund this if it weren't my idea? 3) What is my confidence level before and after feedback? This forces a more objective assessment.

Early-stage ideas are easily killed by practical objections. To prevent this, implement a rule where feedback must begin with "Yes, and...". This forces critics to be additive and constructive, building upon the initial concept rather than immediately shutting it down. It creates space for a bold idea to develop before facing harsh reality checks.

To prevent a culture of complaining, Coinbase requires employees to document issues using a "Problem, Proposed Solution" framework. This forces individuals to move beyond simple criticism and contribute constructively, ensuring that dissent is paired with a thoughtful potential solution.

To foster a culture of candid feedback, use physical objects like ice hockey pucks in meetings. A team member can use a 'straight puck' to signal disagreement, which separates the critique from the person. This makes feedback feel less personal and encourages honest, constructive debate.

When giving feedback, structure it in three parts. "What" is the specific observation. "So what" explains its impact on you or the situation. "Now what" provides a clear, forward-looking suggestion for change. This framework ensures feedback is understood and actionable.

Counteract the tendency for the highest-paid person's opinion (HIPPO) to dominate decisions. Position all stakeholder ideas, regardless of seniority, as valid hypotheses to be tested. This makes objective data, not job titles, the ultimate arbiter for website changes, fostering a more effective culture.