Get your free personalized podcast brief

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

To enforce relentless operational simplification, Bending Spoons requires that anyone proposing added complexity—such as a new feature, process, team, or headcount—bears the full burden of proving its necessity. Opponents need no proof. Furthermore, additions must be clearly successful or promptly reverted, and teams must continually question and dismantle historical complexity that employees have become blind to.

Related Insights

Saying 'no' to product ideas is often contentious. At GitHub, the process is simplified by first 'seeking the truth'—rigorously assessing if an initiative aligns with the team's definition of success. If it doesn't, the 'no' becomes an objective, logical conclusion rather than a subjective or political decision.

Incremental process improvement is insufficient for true simplification. Drawing on Elon Musk's method, the goal should be to aggressively delete steps until you remove one that is actually necessary and must be re-added. This counter-intuitive approach ensures you have identified the absolute minimum viable process with no superfluous elements.

To ruthlessly simplify processes, Tesla uses a powerful filter: any rule or requirement not based on safety, law, or physics is considered a "dumb rule" by default. This forces teams to justify complexity rather than accept it as a given, as demonstrated when they discovered their 12-page auto loan document was almost entirely legally unnecessary.

Complexity is a silent killer of growth. To combat this, adopt an aggressive simplification algorithm: systematically remove steps, features, or processes. The rule is that if you don't break things during this removal process, you haven't removed enough. This forces you to operate with only the bare minimum required for success, reducing complexity and costs.

When implementing new processes to prevent errors, the new way of working must be demonstrably easier than the old one. If it adds complexity, employees will inevitably revert to the path of least resistance, negating the change.

To enforce its "the best part is no part" philosophy, SpaceX has a rule: if you aren't adding back at least 10% of the requirements you previously deleted, you aren't being aggressive enough. This counter-intuitive metric ensures engineers continuously question and simplify designs.

To harness new ideas without causing chaos, mandate that new employees first learn and execute tasks the established way. This forces them to understand hidden dependencies and workflows they can't see initially. Only after mastering the current system can they suggest meaningful, context-aware improvements.

Jacobs's team uses the acronym WOTWOM—Waste Of Time, Waste Of Money—as a rapid check on new ideas. Any suggestion can be challenged with this label if it doesn't clearly contribute to organic revenue growth or margin expansion. This simple tool creates a culture focused on high-leverage activities.

Leaders default to adding more—more features, more goals, more meetings. This 'addition bias' creates friction and exhausts teams, leading one employee to say she only has 'scraps of myself for my family.' The solution is for leaders to act as 'editors-in-chief,' relentlessly subtracting tasks and complexity.

Mature software products often accumulate unnecessary features that increase complexity. The Bending Spoons playbook involves ruthless simplification: eliminating tangential projects and refocusing R&D exclusively on what power users "painfully needed." This leads to a better, more resilient product with a lower cost base.