To avoid decline, managers of mature 'cash cow' products must operate on two tracks. They should rapidly test solution-based iterations to optimize the existing product, while simultaneously dedicating resources to high-level problem discovery to identify the company's next source of growth.

Related Insights

Founders waste time seeking tactical solutions for growth plateaus. The real breakthrough comes from correctly diagnosing the root cause. Once the specific reason for the plateau is identified—of which there are only a handful—the necessary actions become clear.

The old product leadership model was a "rat race" of adding features and specs. The new model prioritizes deep user understanding and data to solve the core problem, even if it results in fewer features on the box.

The tension between growth and profitability is best resolved by understanding your product's "runway" (be it 6 months or 6 years). This single piece of information, often misaligned between teams and leadership, should dictate your strategic focus. The key task is to uncover this true runway.

The idea that startups find product-market fit and then simply scale is a myth. Great companies like Microsoft and Google continuously evolve and reinvent themselves. Lasting success requires ongoing adaptation, not resting on an initial achievement.

To grow an established product, introduce new formats (e.g., Instagram Stories, Google AI Mode) as separate but integrated experiences. This allows you to tap into new user behaviors without disrupting the expectations and mental models users have for the core product, avoiding confusion and accelerating adoption.

Pivoting isn't just for failing startups; it's a requirement for massive success. Ambitious companies often face 're-founding moments' when their initial product, even if successful, proves insufficient for market-defining scale. This may require risky moves, like competing against your own customers.

A product leader should actively manage development by allocating effort into three buckets: future big bets, core foundation (stability/tech debt), and growth/optimization. The resource allocation isn't fixed; it must dynamically shift based on the product's maturity and immediate business goals.

Success often leads businesses to replace winning strategies with corporate formalism and an over-reliance on acronyms like ROAS and LTV. Re-embracing the initial, more intuitive and less metric-obsessed "Day 1" mindset can be the key to breaking through plateaus.

For net-new products, begin with deep problem discovery. Once a product is introduced, shift to rapid, solution-based iteration and feedback. As the product matures, revert back to problem discovery to find the next growth engine while optimizing the current product.

Mature software products often accumulate unnecessary features that increase complexity. The Bending Spoons playbook involves ruthless simplification: eliminating tangential projects and refocusing R&D exclusively on what power users "painfully needed." This leads to a better, more resilient product with a lower cost base.