• Home
  • About
  • Contact
Blue Orange Green Pink Purple

The Importance of Failure for Designers – Part 3

Posted in Interaction Design, User Experience. on Monday, October 26th, 2009 by Brad Tags: Design, failure, methods
Oct 26

In the final part of this series on the importance of failure, I’ll be getting a little philosophical on the subject. Part 1 and Part 2 covered some practical means to take advantage of failure. The final two methods are meant more to change the mindsets of both individuals and organizational leadership to encourage an environment that takes full advantage of failure. Failure always has a negative connotation to it, and these final two approaches are perfect for finally putting a positive spin on the subject.

Embrace Failure

It’s a natural human response to put up our defenses once something goes wrong and we are deemed at fault. This response normally comes out as a series of excuses, attempting to divert the blame to others, or just hanging our head low while the situation steamrolls everyone over. A better response would be taking control, and asking questions like ‘What could I have done differently?’ or ‘What did I miss that lead to this?’ Not only is this the more professional, but it can jump start the conversation towards finding possible solutions.

Conversation Points:

  • What kind of policies should be in place to encourage failure?
  • How serious does a failure need to be before serious action needs to be taken?
  • How does traditional damage control fail to inform project teams and designers on how to avoid the same mistakes again?

Open Minds and Open Ears and Open Hearts

Negatively responding to someone who has made a mistake does nothing to resolve the overall issue. In fact, it makes the whole situation that much worse. Keeping an open mind that everyone screws up every now and then, listening to what lead to the failure, and supporting someone in picking up the pieces greatly is whats need to  improve the situation. This is the keystone to turning everyday design failures into a positive aspect of designing.

Conversation Points:

  • What was the worse project/design review you’ve had that did nothing but point out all the flaws and didn’t offer any tips for improvement?
  • How do you empathize with a peer on their failure, but still maintain a sense of authority?
  • Obviously, there is such thing as failing too much and too often. Where should this line be drawn?

This closes the proposed framework on how to deal with failure as a designer and use our failures to ensure the work we do tomorrow is a vast improvement to the current ‘disaster’ that is causing so much heartache today.

blog comments powered by Disqus

Brad’s Ramblings

  • Tweet Tweet

    Tweet Tweet

      follow me on Twitter
    • Topics
      • Fatherhood
      • Interaction Design
      • Random Noise
      • User Experience
    • What People Are Saying
      • Mark Tattersall on Conversation on Failure
      • Failure and the Agile solution « Budding Business Analyst on About
      • Robert on Prototyping is Like An Onion – It Has Layers
      • Pimpformatn Archtct on Prototyping is Like An Onion – It Has Layers
      • Brad Nunnally on Prototyping is Like An Onion – It Has Layers
    • Blogroll
      • Chris Fahey
      • David Armano
      • Gabby Hon
      • Josh Bokardo
      • Konigi
      • Liv Labate
      • Nick Finck
      • Read Write Web
      • Russ Unger
      • Stephen Anderson
      • Todd Zaki Warfel
      • UX Booth
      • Whitney Hess
      • Will Evans
    • Archives
      • June 2010
      • May 2010
      • April 2010
      • February 2010
      • January 2010
      • December 2009
      • November 2009
      • October 2009
      • September 2009
      • August 2009
      • July 2009
      • June 2009
      • May 2009
      • April 2009
    • Search






    • Home
    • About
    • Contact

    © Copyright Brad’s Ramblings. All rights reserved.
    Designed by FTL Wordpress Themes brought to you by Smashing Magazine

    Back to Top