Six Essential Guidelines to Failing Forward — Relishing Failure (Even When it Tastes Disgusting)
Posted by Plish on April 26, 2016
In the span of a couple seconds a wonderful orange, blackberry fragrance turned caramely, then malty, then char…
I quickly turned around and saw that my blackberry sauce had become a gooey burning mess. Taking it off the heat I scraped it into a container and set it on the garbage can to cool. I then promptly washed the pan and started another batch of my sauce – after all, the French Toast was already done.
As I went to throw away the failure, I grabbed a spoon and tasted this mess. Who knows, maybe something good came out of it…
Sample your #failures! When something goes wrong, don't just throw it out and start over. #Taste, #experience what it is that you've made. You might find that there's something that's worth keeping. You also know what your #mistake actually did to the product. That will give you knowledge for how that mistake changes the qualities of your product- in this case the #food. If something is good, then you'll know that you can keep some aspect of your #failure. Of course, as in this case, nothing was worth keeping and I threw it out and started over.:) #design #cooking #innovation #experimentation #learnfromfailure #failforward #productdesign #servicedesign #experiencedesign #fooddesign
Carbonized berries with a hint of charred honey – bitter and brown – there really was nothing redeemable from this. My takeaway? Perhaps use a little more liquid, a little less sugars, or more importantly, just pay attention better!!
People always talk about failing fast, failing forward, etc. But failing is only beneficial if we take the time to analyze, or in this case taste, our failures.
What’s needed first when we analyze?
A willingness to look! If I was simply interested in making the French Toast and plating it; or if I was only interested in getting rid of a smoky mess and throwing it out, I wouldn’t have found out what the gooey stuff tasted, looked, smelled and felt/acted like.
Be curious about the failures no matter how mundane or common they may appear. As noted in the classic, “The Art of Scientific Investigation“:
The trick then is to look and really question whatever you can’t explain (and sometimes even questioning the things you (think you) can explain can be very useful!) Multiple people can see the same phenomenon and yet see different things.
Some years back, a veteran engineer was convinced that a plastic part was failing because of something happening in the mold. I was brought in to take a look at the situation as they were short on resources. Not taking the veteran engineer’s word, I looked more closely under a microscope. Something didn’t seem right. After looking at the part, and the entire manufacturing and testing process more closely, I realized that the failure was actually due to a testing fixture applied to the part after it was molded. Good parts were being made bad! A change in the testing procedure resulted in weeks of saved time and the product was able to launch on time.
So, while fruitful failing starts with observation, there are actually six points you should think about next time you burn a berry sauce, or something fails. Pay attention to these six points and you’ll be guaranteed to be failing-forward:
- Practice being curious about why things fail. Ask questions, observe, taste, feel, smell. If you can’t explain something, if something seems odd, follow up!
- Can this failure actually be used? In other words, is it truly a failure? The charred goop may have tasted good – maybe I could’ve used it in its new form? (I couldn’t but I asked this question :) )
- Can some aspect of the failure be used? Okay, so maybe it tastes disgusting, but does this mean that it’s totally a loss? Maybe charred, seasoned berry goo is good for digestion? (I don’t know if it is, but I’d venture it isn’t.) Maybe the sticky sugar is a biofriendly adhesive?
- What did I do? How did I get here? Understand the full width and breadth of what was done to create the failure. Look at the ingredients that went into the failure, the tools and fixtures, the timing, the context/environment. Understand what truly caused the failure.
- Document it! Jot it down, put it into your phone, take pictures, make recordings. At the very minimum, commit what you can to memory. Be conscious about remembering what happened so that it doesn’t happen again.
- Can you recreate the failure? At the end of the day, we should be able to recreate the failure (I am quite confident I could burn my sauce again and create the same brown goop). If we can’t recreate it, we didn’t understand it.
Failing is the easy part. Turning it into something to build upon takes a conscious, concerted effort. However, the more you are cognizant of these six points, the more fruitful and the more repeatable your product development efforts will become.
Then the fun REALLY starts!
~~~The second batch of blackberry sauce was sublime ~~~