We scan new podcasts and send you the top 5 insights daily.
Gusto's CTO recognized his team's "no docs" method succeeded because his co-founder status gave him implicit permission to break rules. To scale this, leaders can't just allow new methods; they must explicitly forbid old ones, telling teams, "you will get a slap on the wrist if you produce a doc."
As startups hire and add structure, they create a natural pull towards slower, more organized processes—a 'slowness gravity'. This is the default state. Founders must consciously and continuously fight this tendency to maintain the high-velocity iteration that led to their initial success.
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.
Actively encouraging employees to 'break things' risks normalizing the violation of fundamental rules. A safer and more productive approach is to encourage employees to reflect on and challenge existing rules. This creates a space to identify and improve rules that are no longer fit for purpose without promoting chaos.
Pendo's CPO warns that scaling isn't just about replicating processes for more teams. Leaders must simultaneously build coordination systems (design reviews, clear communication) while fighting to maintain the "maniacal focus on the customer" and rapid innovation that characterize small teams.
To maintain the agility of acquired startups, Amplitude's CEO implemented a top-down ban on "decisions by committee." This empowers individual PMs to make decisions quickly without getting bogged down in universal alignment, protecting the fast-moving culture that made the startups valuable.
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.
True innovation cannot be delegated to new hires. The core founding team, with its deep context and high-pressure tolerance, must personally lead and execute critical new ventures. Success comes from pointing the "Eye of Sauron" of the original team at the next big problem.
Companies often fail by promoting high-performing individual contributors into leadership without teaching them how to scale their judgment. The new leader's job is not to solve problems directly but to define what "good" looks like and enable their teams to get there.
To match the pace of AI startups, large companies require explicit, top-down cultural mandates. At Amplitude, the CEO banned 'decisions by committee' to empower individuals and accelerate shipping. This leadership action is crucial because ICs cannot unilaterally adopt such a culture.
The 'move fast and break things' mantra is often counterproductive to scalable growth. True innovation and experimentation require a structured framework with clear guardrails, standards, and measurable outcomes. Governance enables scale; chaos prevents it.