To de-risk ambitious projects, identify the most challenging sub-problem. If your team can prove that part is solvable, the rest of the project becomes a manageable operational task. This validates the entire moonshot's feasibility early on.
To justify risky, chasm-crossing bets, the entire leadership team must agree that inaction is an existential threat. This alignment is the most difficult step; once achieved, the organization can focus on finding the right solution, knowing the risk is necessary.
Before pursuing moonshots, assess execution fundamentals. A key indicator of readiness is the ability to reliably forecast a launch's impact and then see that impact materialize. If predictions are consistently wrong, the underlying measurement capabilities are not mature enough for bigger risks.
A product change that seems universally positive, like increasing partner revenue, can have unforeseen consequences. At Google, the sales team's involvement was crucial for managing partner communications and mitigating risks, proving alignment is needed even for "no-brainer" launches.
When scaling in operational companies like Walmart or Lyft, product leaders must analyze the entire P&L, not just revenue. The cost of training millions of employees on a new feature can outweigh its benefits, making frictionless, self-adopted solutions essential.
A common leadership mistake is setting impossible goals. This often stems from a flawed planning process that doesn't clearly distinguish between aspirational "stretch" goals and committed "planned" goals. Without this clarity, especially in financial planning, teams are set up for failure.
Allocate resources strategically to ensure both short-term stability and long-term innovation. Dedicate 70% of effort to the core business (1-2 year impact), 20% to riskier medium-term bets (3-5 years), and 10% to high-risk moonshots.
When transitioning between companies, even within the same industry, don't assume shared vocabulary. At Pinterest, the speaker found Facebook's ad terminology (e.g., "pacing") differed from Google's ("budget throttle"). Effective leadership requires first acclimatizing to the new environment's language.