Nick Perry distinguishes malfunctions, preventable errors in familiar tasks that erode trust, from crashes, failures when attempting something new that teach you something. Treat them differently: eliminate malfunctions, embrace crashes as learning.
The single largest indicator of future success is your ability to know the difference between these two kinds of failure: a malfunction and a crash. See, a malfunction is a failure in a known task, like missing a deadline or being consistently late. These should be avoided because they're preventable and they damage trust. But a crash is what comes when you fail trying a new task, like setting up PPC ads or starting a company. See, treating malfunctions the same as crashes is a big boo-boo because crashes don't decide how the rest of your story is written. So don't avoid crashes because every time your system fails, you give yourself the opportunity to reprogram it for success.
