Tying a PM's success to getting their project approved creates perverse incentives. Instead, frame discovery as a team effort to find the right opportunities. This encourages rigorous, unbiased investigation and celebrates killing bad ideas, not just launching new ones.

Don't make high-stakes decisions in a silo. Involve stakeholders throughout the discovery and analysis process. Having finance review your P&L or sales weigh in on customer pain builds shared context and turns your recommendation from 'your bet' into 'our bet.'

When teams repeatedly debate the same trade-off (e.g., "job seeker vs. recruiter focus"), it's a signal to create a principle. By making a definitive choice and codifying it (e.g., "Always focus on the job seeker"), you eliminate future arguments and empower teams to make faster, consistent decisions.

To move beyond static playbooks, treat your team's ways of working (e.g., meetings, frameworks) as a product. Define the problem they solve, for whom, and what success looks like. This approach allows for public reflection and iterative improvement based on whether the process is achieving its goal.

Not all decisions are equal, and treating them the same causes micromanagement. Frame decisions at three levels: Level 1 for strategic bets (owned by the CEO), Level 2 for product bets (owned by product leaders), and Level 3 for daily execution (owned by teams).

Leaders forfeit their right to be frustrated by subpar work if their quality bar is subjective and hasn't been explicitly communicated. To hold a team to a high standard, particularly one based on 'gut feeling,' you must document those expectations in specific detail. This transforms a subjective bar into an objective, referenceable standard.

To avoid bias and misalignment, collaboratively create a weighted decision-making rubric with stakeholders *before* evaluating options. This ensures everyone agrees on the evaluation criteria, making the final decision easier to accept and implement.

When using a 1-5 scale for evaluations, managers often default to the safe middle option (e.g., '3'), which provides ambiguous feedback. By removing the middle number, you force a choice between a positive or negative leaning score, leading to more honest, clear, and actionable assessments.

Don't fall into the trap of believing a scored rubric provides an objective, mathematical truth. Its primary value is forcing alignment on what criteria matter and ensuring a consistent data-gathering process, not spitting out an infallible answer.