Comments on: UIEtips: Failure Is Not an Option — It’s a Requirement http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/ UIE\'s latest insights on the world of design Sat, 11 Feb 2012 08:11:47 +0000 hourly 1 http://wordpress.org/?v=3.2 By: Komik Videolar http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-147371 Komik Videolar Sun, 12 Jul 2009 18:10:54 +0000 http://www.uie.com/brainsparks/?p=742#comment-147371 Thanks all. Thanks all.

]]> By: Roger Belveal http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-146119 Roger Belveal Thu, 16 Apr 2009 00:03:31 +0000 http://www.uie.com/brainsparks/?p=742#comment-146119 There are things that are learned through failure that cannot be learned through success. Case in point, in the airplane industry, along with the huge number of tests done on the ground and in the air to verify airworthiness and safety, there is a deliberate destructive test done on every airframe. This is expensive and really unreasonable as it subjects the airplane structure to forces many times over what it will ever face in normal service. The goal of course, is to discover how much force it can actually withstand and what is the source and nature of the failure when it finally does occur. And the test doesn’t stop until failure occurs. Then changes are made and it is repeated. So what can be learned by this for software? There has long been controversy in every project it seems over what constitutes a “fair” usability test. Indeed there are many kinds of tests, each having its own objectives and methods. I suppose the premise of making a test “fair” is faulty itself or not, depending upon what you want to accomplish by it; whether to learn something or prove something. There are things that are learned through failure that cannot be learned through success. Case in point, in the airplane industry, along with the huge number of tests done on the ground and in the air to verify airworthiness and safety, there is a deliberate destructive test done on every airframe. This is expensive and really unreasonable as it subjects the airplane structure to forces many times over what it will ever face in normal service. The goal of course, is to discover how much force it can actually withstand and what is the source and nature of the failure when it finally does occur. And the test doesn’t stop until failure occurs. Then changes are made and it is repeated.

So what can be learned by this for software? There has long been controversy in every project it seems over what constitutes a “fair” usability test. Indeed there are many kinds of tests, each having its own objectives and methods. I suppose the premise of making a test “fair” is faulty itself or not, depending upon what you want to accomplish by it; whether to learn something or prove something.

]]> By: name http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-146040 name Thu, 02 Apr 2009 15:22:47 +0000 http://www.uie.com/brainsparks/?p=742#comment-146040 My first failure will be to not "embrace failure" :-) Sorry, but I just don't think it's that complicated... "no risk, no reward" "learn from your mistakes" Those are fine ideas, but "celebrating failure" is a bit hard to swallow and seems a little overly exaggerated. Counter-intuitive statements like the following will make you do a double-take, think twice, and ponder the idea in depth. "One thing is clear from our research: Failing is hard work. All teams need to get better at it through regular practice." But software/web development already suffers greatly from excessive smoke and mirrors. Common sense and a pragmatic approach are in short supply. I will continue to simply avoid mistakes and failure as a general rule. My first failure will be to not “embrace failure” :-) Sorry, but I just don’t think it’s that complicated…

“no risk, no reward”
“learn from your mistakes”

Those are fine ideas, but “celebrating failure” is a bit hard to swallow and seems a little overly exaggerated.

Counter-intuitive statements like the following will make you do a double-take, think twice, and ponder the idea in depth.

“One thing is clear from our research: Failing is hard work. All teams need to get better at it through regular practice.”

But software/web development already suffers greatly from excessive smoke and mirrors. Common sense and a pragmatic approach are in short supply.

I will continue to simply avoid mistakes and failure as a general rule.

]]> By: Email subject lines: Are yours a big yawn? » Interactive Marketing - MIMA Blog http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-145577 Email subject lines: Are yours a big yawn? » Interactive Marketing - MIMA Blog Tue, 10 Feb 2009 13:25:19 +0000 http://www.uie.com/brainsparks/?p=742#comment-145577 [...] the ubiquitous Jared M. Spool: UIE Tips: Failure is Not an Option — It’s a Requirement UIE Tips: Four Essential Skills for Information Architects UIE Tips: How to Innovate Right [...] [...] the ubiquitous Jared M. Spool: UIE Tips: Failure is Not an Option — It’s a Requirement UIE Tips: Four Essential Skills for Information Architects UIE Tips: How to Innovate Right [...]

]]> By: Inder P Singh http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144348 Inder P Singh Thu, 27 Nov 2008 11:04:09 +0000 http://www.uie.com/brainsparks/?p=742#comment-144348 I imagine several organizations make the following arrangements to mitigate risks and allow learning from failures: 1. Execute small a.k.a. pilot projects (small for resources committed/ dollar value at risk/ etc.) in areas where several factors are unknown. 2. Perform reviews and testing. 3. Gather feedback from real users (as early as feasible and as frequent as feasible) Inder I imagine several organizations make the following arrangements to mitigate risks and allow learning from failures:
1. Execute small a.k.a. pilot projects (small for resources committed/ dollar value at risk/ etc.) in areas where several factors are unknown.
2. Perform reviews and testing.
3. Gather feedback from real users (as early as feasible and as frequent as feasible)

Inder

]]> By: şiir http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144338 şiir Mon, 24 Nov 2008 17:47:17 +0000 http://www.uie.com/brainsparks/?p=742#comment-144338 I have not said anything about this before, because no one was taking credit for it. It was originally supposed to be an “adult” children’s book. I have the original sketches and I am pretty sure that I have the original notes. I have often wondered how (and if) this leaked to the internet. The guy that I am pretty sure wrote it, would have definitely taken credit if he had posted it. I have not said anything about this before, because no one was taking credit for it. It was originally supposed to be an “adult” children’s book. I have the original sketches and I am pretty sure that I have the original notes. I have often wondered how (and if) this leaked to the internet. The guy that I am pretty sure wrote it, would have definitely taken credit if he had posted it.

]]> By: porno izle http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144300 porno izle Mon, 17 Nov 2008 15:21:32 +0000 http://www.uie.com/brainsparks/?p=742#comment-144300 thank you. thank you.

]]> By: Daniel Szuc http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144208 Daniel Szuc Sat, 01 Nov 2008 04:19:12 +0000 http://www.uie.com/brainsparks/?p=742#comment-144208 Enjoyable reading and unfortunately seen too many projects afraid of failure. Its interesting to note, that so much gets invested into the build and implement stages and little into failing early or doing enough research early on to assess value of the thing you are about to build. Why are teams so afraid to invest up front to see if something will work or needs to change? (seems such a waste of time and monies) What is UIE seeing? Are companies started to invest more in user/design research to help better understand value proposition to drive products forward? Seems just as there are gaps between design and implementation, there are huge gaps between user research (if any is done at all) and design. Enjoyable reading and unfortunately seen too many projects afraid of failure.

Its interesting to note, that so much gets invested into the build and implement stages and little into failing early or doing enough research early on to assess value of the thing you are about to build. Why are teams so afraid to invest up front to see if something will work or needs to change? (seems such a waste of time and monies)

What is UIE seeing? Are companies started to invest more in user/design research to help better understand value proposition to drive products forward?

Seems just as there are gaps between design and implementation, there are huge gaps between user research (if any is done at all) and design.

]]> By: stephen http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144204 stephen Fri, 31 Oct 2008 16:07:15 +0000 http://www.uie.com/brainsparks/?p=742#comment-144204 what was the site that failed? uie? what was the site that failed? uie?

]]> By: Steven Clark http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144191 Steven Clark Wed, 29 Oct 2008 22:21:48 +0000 http://www.uie.com/brainsparks/?p=742#comment-144191 Jared, it reminded me of the story of 3M and how they learned to accept innovation. Apologies but you may find the post I wrote quite interesting... http://stevenclark.com.au/2008/10/30/our-corporate-culture-should-support-failure/ I've long had this very subject in mind if I do a dissertation next year or do research masters or even PhD in the future - the failure of organisations to capitalise on failure. More to the point of my interest is how the human factor in performance reviews can systemically work against the innovator. On the surface we all understand that new ideas are worth capturing, yet most businesses fail at it miserably. Interesting subject. Apologies for linking to my own article written as a response but it's a pet subject of mine so I couldn't help it. If I'm wrong it it about any of the 3M story then people should probably email Seth Godin, that's where I got the meaty detail of the tale about the invention of masking tape. 3M are indeed a legendary innovative company worth exploring. Jared, it reminded me of the story of 3M and how they learned to accept innovation. Apologies but you may find the post I wrote quite interesting…

http://stevenclark.com.au/2008/10/30/our-corporate-culture-should-support-failure/

I’ve long had this very subject in mind if I do a dissertation next year or do research masters or even PhD in the future – the failure of organisations to capitalise on failure. More to the point of my interest is how the human factor in performance reviews can systemically work against the innovator. On the surface we all understand that new ideas are worth capturing, yet most businesses fail at it miserably.

Interesting subject. Apologies for linking to my own article written as a response but it’s a pet subject of mine so I couldn’t help it. If I’m wrong it it about any of the 3M story then people should probably email Seth Godin, that’s where I got the meaty detail of the tale about the invention of masking tape. 3M are indeed a legendary innovative company worth exploring.

]]> By: Roy Zornow http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144190 Roy Zornow Wed, 29 Oct 2008 21:36:09 +0000 http://www.uie.com/brainsparks/?p=742#comment-144190 This is kinda cliche but absolutely true. There's a due diligence in trying out a new direction and not giving up on it. When confused try to be led by heuristics, but yes sometimes you get smacked down. I much prefer an employee who is innovating though. This is kinda cliche but absolutely true. There’s a due diligence in trying out a new direction and not giving up on it. When confused try to be led by heuristics, but yes sometimes you get smacked down. I much prefer an employee who is innovating though.

]]> By: Grammar Pedant http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144189 Grammar Pedant Wed, 29 Oct 2008 21:09:44 +0000 http://www.uie.com/brainsparks/?p=742#comment-144189 "Why Designer's Fail", eh? Maybe because they can't use apostrophes correctly? “Why Designer’s Fail”, eh?

Maybe because they can’t use apostrophes correctly?

]]> By: Steve Gentile http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144188 Steve Gentile Wed, 29 Oct 2008 20:18:40 +0000 http://www.uie.com/brainsparks/?p=742#comment-144188 We have been conditioned to assign positive value and attributes to success, negative value and attributes to failure. Herein lies the issue. Until we turn that thinking around (or inside out or from another point of view), the outcome of every effort will remain the same, plus or minus. I look at "failure" as currently unrealized and unrecognized potential and "success" as currently realized and recognized potential. That being said, all "successes" become mainstream immediately, "failures" take a bit more time and effort. It doesn't stop the innovation process or throw countless babies out with the bathwater -- lucky for us. Remember, success is not without fault or blemish, it's just greatly diminished in the bigger POV. Steve - www.thinktanknyc.com thinking done differently! We have been conditioned to assign positive value and attributes to success, negative value and attributes to failure. Herein lies the issue. Until we turn that thinking around (or inside out or from another point of view), the outcome of every effort will remain the same, plus or minus.

I look at “failure” as currently unrealized and unrecognized potential and “success” as currently realized and recognized potential. That being said, all “successes” become mainstream immediately, “failures” take a bit more time and effort. It doesn’t stop the innovation process or throw countless babies out with the bathwater — lucky for us.

Remember, success is not without fault or blemish, it’s just greatly diminished in the bigger POV.

Steve –
http://www.thinktanknyc.com
thinking done differently!

]]> By: Samantha LeVan http://www.uie.com/brainsparks/2008/10/29/uietips-failure-not-an-option/comment-page-1/#comment-144186 Samantha LeVan Wed, 29 Oct 2008 19:45:44 +0000 http://www.uie.com/brainsparks/?p=742#comment-144186 Larger organizations tend to be afraid of admitting failure. They're afraid of backlash from the public and from their own employees. Individual contributors have come afraid to fail and afraid to admit to failure for fear of losing their job. At the highest organizational level, failure needs to be accepted and supported. Reward teams and indivuduals for documenting failures (the "whats" and "whys"). Encourage honesty and require all failures to be a learning event. In my user research work, I always divide my findings for the client into "successes we should continue in future iterations" and "failures we can learn from". Often I have to rephrase it so it doesn't sound like failure, but my hope is that over time, people will learn to embrace failure because with failure comes learning and with learning comes success. Larger organizations tend to be afraid of admitting failure. They’re afraid of backlash from the public and from their own employees. Individual contributors have come afraid to fail and afraid to admit to failure for fear of losing their job.

At the highest organizational level, failure needs to be accepted and supported. Reward teams and indivuduals for documenting failures (the “whats” and “whys”). Encourage honesty and require all failures to be a learning event.

In my user research work, I always divide my findings for the client into “successes we should continue in future iterations” and “failures we can learn from”. Often I have to rephrase it so it doesn’t sound like failure, but my hope is that over time, people will learn to embrace failure because with failure comes learning and with learning comes success.

]]>