When pivoting from a product with existing revenue, avoid the binary choice of killing it or splitting focus. Blue Jay successfully transitioned by putting their V1 product into "maintenance mode"—servicing existing customers but halting all new feature development—and committing the entire team to building the V2 for a defined six-month period.

Business leaders respond to the language of risk and money, not 'clean code' or 'developer happiness.' Rebranding technical debt work as a necessary step to mitigate future business risks is a more effective way to get projects approved and funded.

To combat over-dependence on Google and escape the local maxima of conversion optimization, TripAdvisor's product team took a full quarter off from shipping new features. They instead created a detailed strategy document with wireframes for a new North Star vision, which guided product development for years to come.

Treat your product and engineering teams as stewards of the company's most precious capital: their time. A capital allocation framework forces leadership to ask if this "investment" is being spent on the initiatives with the highest strategic return, not just fulfilling requests.

To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.

To get executive buy-in for technical debt work, visually demonstrate how it blocks high-value future features. Present it as a choice: we can do this necessary refactor now, or we forfeit the ability to build the things that will make us money later.

Don't let technical debt accumulate until it cripples your ability to innovate. Product should proactively treat it as a feature to be prioritized. Use natural lulls in the product cycle to pay down debt, ensuring you can move fast when the next big market opportunity arises.

To prevent engineers from focusing internally on technical purity (e.g., unnecessary refactoring), leaders must consistently frame all work in terms of its value to the customer. Even tech debt should be justified by its external impact, such as improving security or enabling future features.

The pivot from Arc to Dia was also a cultural and technical reset. The Browser Company gave their team a "blank page," allowing engineers to build a new, faster architecture and designers to rethink the experience. This chance to fix old problems and pursue new ideas was key to getting team buy-in.