summary

Simon Sinek - Is Failure Necessary? | Simon Sinek

Thumbnail of the video “Simon Sinek - Is Failure Necessary? | Simon Sinek”
Community upload. AI output has not been independently verified.

Short Summary

Main recommendation: Stop calling setbacks "failure" and instead treat them as falls you recover from quickly, because innovation requires experimentation and experimentation requires falling. Sinek argues that teams should challenge calcified processes by asking why they exist, then pilot changes in small groups before scaling them, drawing on an exchange with an interviewer about a 95,000-person team.

Key Points

  • Innovation is inherently inefficient because it requires experimentation, and experimentation requires failure; Sinek says a team not failing is probably "not pushing very hard."
  • Sinek dislikes the phrase "fail fast" because "failure" is too broad, like "cancer," and people hear it as catastrophe.
  • Judge innovation less by whether someone fell and more by how quickly they get back up and try again.
  • Processes often outlive their reasons; one person asking "Can somebody explain why we do it this way?" can expose a rule that should change.
  • Questioning should come with a proposed solution, and people who challenge a process should be heard and allowed to pilot alternatives in their own group.
  • After the pandemic, Sinek argues some in-person habits, such as brainstorming and the commute, are worth relearning, along with turning off constant connection.

Details Worth Noting

  • Concrete instructions:
    • Replace the word "failure" with "fell" when describing setbacks, and encourage people to "get back up and try again."
    • When a process seems unexplained, ask directly why it exists; if nobody can give a good reason, challenge or change it.
    • Before changing a process company-wide, let a team test the new approach in its own group; if it works, scale it, and if it doesn't, treat the test as useful.
    • When someone raises a problem, ask "What should we do differently?" so the critique comes with an idea.
    • Start pilots with early adopters, since they tolerate imperfections.
    • Schedule in-person brainstorming and interrupt-friendly meetings, which Sinek says are harder to do over Zoom.
    • Deliberately create a transition ritual, since the commute helped people start and end the workday.
  • The example given is a company with 14 approvals required to hire one person, which Sinek uses to show how unexamined checks can fall apart when questioned.
  • Sinek describes a "culture circles" effort in which people address their subculture by piloting ideas, which he links to "love diffusion."
  • He recalls once meeting a CFO who named efficiency and innovation as company priorities, and jokingly told him 'good luck with that,' since innovation is inherently inefficient.

Bottom Line

Progress depends on tolerating small, recoverable falls and making it safe to question unexplained processes, provided challengers bring a workable alternative.