When a business gets high visibility but low conversions, the impulse is to blame the platform or marketing tactic (the 'sink'). However, the real issue is often the core offering—the product, pricing, or value proposition (the 'well'). People obsess over front-end fixes when the back-end is the actual problem.

True accountability extends beyond your own direct mistakes. Even when someone else is the cause of a problem, hold yourself responsible for having put yourself in that situation. This mindset empowers you to learn from the experience and avoid similar issues in the future by analyzing your choices.

To de-risk innovation, teams must avoid the trap of building easy foundational parts (the "pedestal") first. Drawing on Alphabet X's model, they should instead tackle the hardest, most uncertain challenge (the "monkey"). If the core problem is unsolvable, the pedestal is worthless.

A platform's immediate user is the developer. However, to demonstrate true value, you must also understand and solve for the developer's end customer. This "two-hop" thinking is essential for connecting platform work to tangible business outcomes, not just internal technical improvements.

When revenue stalled, Roblox wasted months on small fixes. The real solution was a difficult strategic shift: creating the Robux virtual currency. This aligned creator incentives with platform growth and solved the root problem instead of tinkering with symptoms.

Figma learned that removing issues preventing users from adopting the product was as important as adding new features. They systematically tackled these blockers—often table stakes features—and saw a direct, measurable improvement in retention and activation after fixing each one.

Avoid the trap of building features for a single customer, which grinds products to a halt. When a high-stakes customer makes a specific request, the goal is to reframe and build it in a way that benefits the entire customer base, turning a one-off demand into a strategic win-win.

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.

The biggest blind spot for new managers is the temptation to fix individual problems themselves (e.g., a piece of bad code). This doesn't scale. They must elevate their thinking to solve the system that creates the problems (e.g., why bad code is being written in the first place).