By jimgris on Oct 29, 2009
Failure as a springboard to success. Nice piece there from Jono Bacon on how to fail gracefully, recover, and move on -- learning all along the way. I like it. Very practical advice for managing projects -- or doing anything, really -- in a community environment where credibility can be earned and/or lost rapidly and publicly. Much of the issue involves just recognizing your mistakes, apologizing, and fixing things so your actions support your words. Works for me. But I think many people struggle with this concept because they wait too long and the issue gets too big and complex. Then they feel they can't back down. Too much has already been said. So, they spin. What I have found is that if you get out there fast and correct things early -- whether it's your fault or your company's or someone else's in the community -- it's much more casual and normal and most people will engage pretty well. Early apologies on the small stuff tend to be more understated and easier to deliver than those bigger ones later on.
Also, Jono utters this gem in the article: "In my experience of working with communities, successes provide an incredible opportunity to learn about our strengths, but failures provide the inverse opportunity to learn about our weaknesses." I totally agree. People have always told me that you have to fail because "that's the only way you ever learn anything" or words to that effect. I never agreed with that. Actually, that notion always pretty much made me sick to my stomach. The truth is that you learn just as much from success as you do from failure -- it's just that you learn different lessons, that's all. You need a balance of both. That's obvious, right?