Don't expect your organization to adopt a new strategy uniformly. Apply the 'Crossing the Chasm' model internally: identify early adopters to champion the change, then methodically win over the early majority and laggards. This manages expectations and improves strategic alignment across the company.

For internal tools, don't rely solely on product-led growth. A hybrid approach combines a frictionless product experience with a proactive "sales" strategy of advocating for the tool's potential, constantly proving its value to leadership, and removing friction for users.

Directly approaching large organizations is often ineffective. Instead, emulate Slack's growth model by getting individual employees to use and love the product. This creates internal champions who advocate for wider organizational adoption, pulling the product in rather than pushing it from the outside.

Webflow drove weekly Cursor adoption from 0% to 30% in its design team after one 'builder day' where every participant was required to demo a project. This combination of hands-on practice, peer support from champions, and clear expectations creates rapid, tangible adoption of new AI tools.

Forcing innovations to "scale" via top-down mandates often fails by robbing local teams of ownership. A better approach is to let good ideas "spread." If a solution is truly valuable, other teams will naturally adopt it. This pull-based model ensures change sticks and evolves.

Instead of large, multi-year software rollouts, organizations should break down business objectives (e.g., shifting revenue to digital) into functional needs. This enables a modular, agile approach where technology solves specific problems for individual teams, delivering benefits in weeks, not years.

To overcome widespread resistance and inertia, companies should avoid company-wide digital transformation rollouts. Instead, create a small, empowered "tiger team" of top performers. Give them specialized training and incentives to pilot, perfect, and prove the new model before attempting a broader implementation.

The primary obstacle to adopting a shared platform model is cultural resistance. Teams accustomed to controlling their full stack view shared platforms as a loss of autonomy and a forced dependency. Overcoming this requires building a culture of trust and shared goals, not just proving the technological superiority of the platform.

The "Odin" platform, which eventually managed all of Uber's stateful workloads, began as a project to containerize sharded MySQL for a single team. This bottom-up approach allowed them to prove the concept and build a working system before seeking wider, more political adoption.