Key Takeaways

  • Luca Ferrari runs Bending Spoons by operating major software acquisitions like Evernote with small, high-agency teams running proprietary internal tools.
  • Internal job titles cause administrative drag and political games, so Bending Spoons abolished them entirely, assigning algorithmic functional roles instead.
  • Ferrari defines extreme ownership as an internal drive to succeed: “caring in your belly tremendously about being the best at what you do about helping the team in the company succeed.”
  • The company fights corporate bloat using the Bending Spoons' Relentless Simplification Rule, which puts the total burden of proof on anyone proposing new processes or features.

The Bending Spoons' Relentless Simplification Rule

Most expanding companies collect process like dust. A single team member makes a mistake, so leadership creates a new review meeting. A manager wants clearer boundaries, so the company invents five new middle-management titles. Over time, administrative weight crushes product velocity.

Luca Ferrari built Bending Spoons to resist this default decay. When the company acquires established products like Evernote, it strips away legacy overhead rather than integrating corporate red tape. Ferrari points out that human psychology naturally protects existing friction: “We tend to assume the status quo is fine and we focus on deltas that happen, new things that are added or changes.”

To break through this inertia bias, Bending Spoons operates under a strict operational standard:

Rule 1: Asymmetric Burden of Proof on Complexity

Anyone proposing to add a part, feature, team member, rule, or process carries 100% of the burden of proof. Anyone objecting to the addition carries no burden of proof: raising a flag is sufficient. Ferrari explains the asymmetry clearly: “Every time someone is suggesting that we should be adding complexity the burden of proof is on those making that suggestion. The people who support the thesis that we shouldn't be adding that complexity don't need to prove it.”

Rule 2: Active Interrogation of the Status Quo

Actively combat inertia and consistency biases by questioning long-standing processes and features; the longer a rule or system has existed, the more aggressively it must be audited for removal.

Rule 3: Complete Removal Over Incrementalism

Seek 10x operational improvements by eliminating entire categories of overhead (such as eliminating formal job titles or entire unused product feature sets) rather than optimizing them incrementally.

Ferrari proved Rule 3 by killing internal job titles across the organization. “And so we just got rid of titles,” Ferrari said. “And we told people, you can pick your title for your CV, LinkedIn, whatever. We don't need to know. We don't want to know. We don't need to approve it. We don't want to see it.”

When This Works (and When It Doesn't)

This framework works when your organization has high talent density and people with extreme ownership who act autonomously. When your team cares about outcomes over politics, stripping out titles and processes speeds up execution. It allows small groups to manage software suites that previously required hundreds of employees.

It breaks down in early-stage startups that lack baseline systems. If you have zero repeatable workflows, placing the burden of proof on creating a basic deployment pipeline or onboarding checklist creates paralysis. It also fails if you hire low-context workers who require explicit guardrails to avoid costly mistakes.

What to Do With This

Run an organizational audit on your team this Thursday. Pick one recurring meeting or mandatory sign-off process that has existed for more than six months.

Tell the team the approval requirement is paused for the next thirty days unless the person who created it can provide written data proving it prevented a measurable loss. If they cannot defend it with numbers, delete the rule permanently.