Twitter's CEO Banned Cross-Team Approvals. Here's What Happened Next. #podcast #shorts

Why It Matters

Accelerating product cycles may boost Twitter's competitiveness, but reduced oversight could increase regulatory and quality risks.

Key Takeaways

• Elon Musk eliminated cross‑team approval bottlenecks at Twitter.
• Implemented a 'bias to yes' policy, limiting vetoes to managers.
• Legal can only block actions that violate law or privacy policy.
• Engineers now launch experiments directly, often at 1% scale.
• Speed of product iteration increased dramatically after policy change.

Summary

Twitter CEO Elon Musk scrapped the company's cross‑team approval maze, instituting a "bias to yes" framework that lets only a direct manager—or legal when law or privacy is at stake—to block initiatives. The move mirrors Jeff Bezos' Amazon practice of empowering rapid decision‑making.

Previously, engineers faced a labyrinth of 14‑person sign‑offs, slowing experiments. Under the new rule, any idea approved by a manager can be executed without additional gatekeepers, encouraging teams to prototype and roll out features to a 1% audience instantly.

Musk cited his improv background and Bezos' model, saying, "Only the person you report to is allowed to tell you you're not allowed to do that." Engineers responded by skipping wireframe reviews and launching minimal viable tests, illustrating the cultural shift.

The policy promises faster iteration and could help Twitter regain product momentum, yet it also raises questions about oversight, quality control, and potential regulatory exposure as unchecked experiments proliferate.

Original Description

Ex-Twitter CEO Dick Costolo on how he killed the approval bottleneck with one rule: only your direct manager can tell you no. No other org gets a vote.