When scaling rapidly, companies naturally develop departmental silos and a tendency towards small, incremental improvements. These two forces actively work against the bold, cross-functional bets required to reach the next revenue milestone and must be actively fought.

Related Insights

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.

Processes that work at $30M are inadequate at $45M. Leaders in hyper-growth environments (30-50% YoY) must accept that their playbooks have a short shelf-life and require constant redesign. This necessitates hiring leaders who can build for the next level, not just manage the current one.

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.

If a company creates a siloed "innovation team," it's a sign the main product organization is stuck in "business as usual" maintenance. Innovation should be a mindset embedded across all teams, not an isolated function delegated to a select few.

Companies fail at collaboration due to behavioral issues, not a shortage of good ideas. When teams operate in silos, believing "I know better," and are not open to challenging themselves or embracing "crazy ideas," progress stalls. Breaking down these habitual, protective behaviors is essential for creating a fluid and truly innovative environment.

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.

Every change introduces a temporary performance decrease as the team adapts—an 'implementation dip.' This guaranteed loss often outweighs the uncertain potential gain from minor tweaks. Real growth comes from compounding skill through repetition of a working system, not from perpetual optimization.

Contrary to the popular bottoms-up startup ethos, a top-down approach is crucial for speed in a large organization. It prevents fragmentation that arises from hundreds of teams pursuing separate initiatives, aligning everyone towards unified missions for faster, more coherent progress.

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.

Organizing by function (e.g., all sales together) seems efficient but incentivizes teams to optimize their individual metrics, not the company's success. This sub-optimization prevents cross-functional learning and leads to blame games, ultimately harming the entire customer value stream and creating a non-learning organization.