Square's public roadmap serves a dual purpose. While it informs customers, its primary internal function is to create accountability. Committing to features publicly forces the organization to deliver on its promises with speed and quality, preventing internal delays.

There's often a massive gap between a company's strategic goals and where development teams actually spend time. In one case, only 2% of capacity was spent on the top strategic goal because teams are "magnets for requests" that derail progress on the big picture.

Leaders in large companies often lack visibility into the day-to-day workflows that drive results. They see inputs like salaries and outputs like KPIs, but the actual process of how work gets done—the institutional know-how—is a black box that walks out the door every day.

Innovation leaders struggle to secure resources. A powerful tactic is to have VPs align on their long-term strategic goals, identify overlaps, and then dedicate cross-functional teams to these shared priorities. This creates executive buy-in and carves out protected capacity for innovation.

Having a centralized internal system where every project, goal, and update is tracked—like Shopify's GSD—sounds too simple to be a game-changer. However, it's a surprisingly effective foundation for organizational legibility and alignment at scale.

PhonePe practices radical transparency by sharing its board decks, complete with financial data like P&L and burn rates, across the entire company. Unrestricted, cross-departmental data access fosters high engagement, ownership, and unexpected innovation.

Managing innovative teams requires a balancing act. While sharing resources like software improves efficiency, it creates blind spots. Leaders should intentionally foster independent 'splinter groups' to work on the same problem, ensuring critical comparisons can be made to uncover hidden errors.

IBM uses a visual artifact called the "Golden Thread"—a living document showing product vision, value, and a feedback loop. This low-cost tool aligns diverse stakeholders, from the boardroom to developers, around outcomes instead of features, thereby de-risking innovation.

When a product team is busy but their impact is minimal or hard to quantify, the root cause is often not poor execution but a lack of clarity in the overarching company strategy. Fixing the high-level strategy provides the focus necessary for product work to create meaningful value.