To create a cohesive product across multiple teams, GitHub uses a framework that forces alignment upfront. By ensuring all teams first deeply understand the problem and collectively identify solutions, the final execution is naturally integrated, preventing a disjointed experience that mirrors the org structure.

To move beyond static playbooks, treat your team's ways of working (e.g., meetings, frameworks) as a product. Define the problem they solve, for whom, and what success looks like. This approach allows for public reflection and iterative improvement based on whether the process is achieving its goal.

When facing a major technical unknown or skill gap, don't just push forward. Give the engineering team a dedicated timebox, like a full sprint, to research, prototype, and recommend a path forward. This empowers the team, improves the solution, and provides clear data for build-vs-buy decisions.

Companies often have undiscovered IP because technologists don't always communicate their innovations effectively. A simple management practice of regularly talking to engineers and asking "What problem are you facing?" and "How did you overcome it?" can surface valuable, patentable solutions that would otherwise go unnoticed.

To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.

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.

A critical challenge for corporate innovation is a lack of transparency between silos. Executives report teams discovering they've worked on the same project for months, wasting hundreds of thousands of dollars. Simple tools like shared, visible roadmaps are a crucial unlock to prevent redundant efforts.

Instead of arguing for more time, product leaders should get stakeholder buy-in on a standardized decision-making process. The depth and rigor of each step can then be adjusted based on available time, from a two-day workshop to an eight-month study, without skipping agreed-upon stages.

Public company constraints don't kill innovation; they change its nature. Instead of building solutions from scratch, PMs must prioritize reusing existing internal capabilities and tech stacks from other products within the company. This "plugin" approach maintains velocity while managing resources under public scrutiny.