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.

To create a cohesive product across multiple teams, GitHub uses a framework that forces alignment upfront. By ensuring all teams first deeply understand the problem and collectively identify solutions, the final execution is naturally integrated, preventing a disjointed experience that mirrors the org structure.

Eliminate one-size-fits-all reviews. Small, self-contained features ship rapidly on a fast track with only lightweight checks. Major, systemic changes require a separate, rigorous product strategy review to ensure alignment before development begins.

When a stakeholder proposes a specific feature (a "form factor"), don't debate it directly. Instead, "ladder up" the conversation by asking a series of "why" questions to uncover the user behavior, desired outcome, and ultimately, the root problem being solved.

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.

Just as PMs are warned against solution-bias, the same discipline applies to problems. The goal is not just to find one problem, but to find multiple, then assess which is most valuable, strategically aligned, and worth pursuing for the right audience before committing resources.

Borrowing from design's critique ritual, product teams can present works-in-progress to peers, stating the problem stage, solutions tried, and specific feedback needed. This fosters knowledge sharing and cross-pollination of ideas with low overhead.

When handed a specific solution to build, don't just execute. Reverse-engineer the intended customer behavior and outcome. This creates an opportunity to define better success metrics, pressure-test the underlying problem, and potentially propose more effective solutions in the future.

When pursuing a long-term strategic solution, dedicate product management time to high-level discovery and partner alignment first. This doesn't consume engineering resources, allowing the dev team to remain focused on mitigating the immediate, more visceral aspects of the problem.