To avoid stifling teams with bureaucracy, leaders should provide slightly less structure than seems necessary. This approach, described as "give ground grudgingly," forces teams to think actively and prevents the feeling of "walking in the muck" that comes from excessive process. It's a sign of a healthy system when people feel they need a bit more structure, not less.

A key, often overlooked, function of leaders in high-growth groups is to act as a shield against internal company interference. This allows their teams to focus on innovation and execution rather than navigating organizational friction, which is a primary driver of top talent attrition.

To innovate quickly without being bogged down by technical debt, portfolio companies should ring-fence new AI development. By outsourcing it and treating it as a separate "skunk works" project, the core tech team can focus on existing systems while the new initiative succeeds or fails on its own merits.

Contrary to the remote-first trend, Crisp.ai's founder advises against a fully distributed model for initial product development. He argues for gathering the core team in one physical location to harness the energy and efficiency of in-person collaboration. Distributed teams are better suited for iterating on an already established product.

Prioritize projects that promise significant impact but face minimal resistance. High-friction projects, even if impactful, drain energy on battles rather than building. The sweet spot is in areas most people don't see yet, thus avoiding pre-emptive opposition.

Afeyan advises against making breakthrough innovation everyone's responsibility, as it's unsustainable and disruptive to daily jobs. Instead, companies should create a separate group with different motivations, composition, and rewards, focused solely on discontinuous leaps.

In siloed government environments, pushing for change fails. The effective strategy is to involve agency leaders directly in the process. By presenting data, establishing a common goal (serving the citizen), and giving them a voice in what gets built, they transition from roadblocks to champions.

Stripe's Experimental Projects Team discovered that embedding its members directly within existing product and infrastructure teams leads to higher success rates. These "embedded projects" are more likely to reach escape velocity and be successfully adopted by the business, contrasting with the common model of an isolated R&D or innovation lab.

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.