Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Dick Costolo drew a direct line between a messy office kitchen and site instability. A culture where employees leave dirty dishes thinking "someone else will clean it up" is the same one that leads to engineering problems being ignored, causing crashes.

Related Insights

Fast-growing companies operate with internal chaos ("backstage") as they constantly rebuild systems. The key is to shield customers from this dysfunction, presenting a polished, reliable product experience ("onstage") no matter how turbulent things are internally.

Exceptional people in flawed systems will produce subpar results. Before focusing on individual performance, leaders must ensure the underlying systems are reliable and resilient. As shown by the Southwest Airlines software meltdown, blaming employees for systemic failures masks the root cause and prevents meaningful improvement.

Costolo argues against the common reaction to add process steps to prevent future mistakes, which leads to bloat like 17-page launch checklists. Instead, he advises assigning a clear DRI and managing for outcomes, not adherence to processes.

Deep tech startups don't have unique interpersonal problems. The same human OS bugs—communication breakdowns, ego, avoiding hard conversations—that sink a restaurant or a marriage will also sink a highly technical venture. The context changes, but the core human errors do not.

Focusing on "bad to great" is more effective than "good to great" when scaling. Bad behaviors and destructive norms are so corrosive that they make it impossible for excellence to take root. A leader's first job in a turnaround or scaling effort is to eliminate the bad—like dirty bathrooms or incompetent employees—before trying to implement the good.

The actual standards of your organization are not set by posters or mission statements, but by the negative behaviors you permit. If you allow chronic tardiness or underperformance to continue without consequence, you are signaling that this is an acceptable standard for the entire team.

The value 'seek pain' encourages employees to proactively find what's broken and have difficult conversations. This counterintuitively minimizes pain by preventing it from accumulating over time, such as delaying a necessary pivot or firing.

Menlo's culture operates on the principle that when mistakes happen, the system is at fault, not the individual. This approach removes fear and blame, encouraging the team to analyze and improve the processes that allowed the error to occur, fostering a culture of continuous improvement.

Expedia received 20 million support calls for itineraries because each department (marketing, tech, product) focused only on its own metrics. No single silo owned the cross-functional problem of preventing calls, so the problem festered despite its massive scale. True ownership must transcend departmental lines.

To gauge if an engineering team can move faster, listen for specific 'smells.' Constant complaints about broken builds, flaky tests, overly long processes for provisioning environments, and high friction when switching projects are clear signals of significant, addressable bottlenecks.