Dealing with failure successfully

failure by jurvetson

What Google Could Learn From Pixar
[Via Daring Fireball]

Peter Sims:

Despite an unbroken string of 11 blockbuster films, Catmull regularly says, “Success hides problems.” It’s an insight Google should acknowledge and act on.

[More]

One thing the article mentions is that Pixar is always working to find solutions to problems. I wrote about this before, where I sketched out some of the technical problems each Pixar movie was designed to solve.

As Pixar says, “Success hides problems.” The complementary idea, that “Failure reveals problems”, is one very few organizations want to examine. At many companies, failure leads to loss of employment. The organizations seem to believe that as long as someone never fails, then they must be better than others. Fear of failure prevents innovation. This leads to a maladaptive company, one that is not resilient enough to deal with failure when it inevitably happens, because the hidden problems do eventually pierce the bubble of complacency.

In a complex world, failure often tell you more than success. I use the game I learned in Junior High School called Bulls and Creots as an example. Here, outright failure to get anything right actually gives you more knowledge than any other single guess.

Similarly, with some very complex systems, the only way to get to clarity is to make something fail, to make it work wrong. In biological systems, some of the most insightful work has come from disabling a part of the system and seeing what happens. So, for example, in a metabolic pathway with a large number of enzymes, looking at a single enzyme tells us little about the process, since in many cases we do not know what the enzyme really does.

But disable the enzyme and what will happen? If it is a critical part of the pathway, then none of the final product will be produced. Instead, a large amount of an intermediary product will build up – the intermediary product that the disabled enzyme was supposed to work with but can’t. So, like throwing a wrench in an assembly line backs up everything behind the wrench, a disabled enzyme results in a backup of intermediary product. Study that product and you will know what the enzyme does. Do this for each enzyme in the pathway and you can then delineated what happens at each step as you add material at the beginning of the pathway.

This and other approaches yielded understanding like this, which shows the complex intermediary metabolic pathways in cells. Pretty complicated but it was only revealed through things like designed failure.

intermediary metabolism

Failure and the continuing drive to solve problems is how you keep innovation fresh and creative. Pixar gets that. Companies that do not will discover that Failure does eventually reveal problems in even successful companies and if they do not deal with that failure in a productive way, the organization could go down in flames.

And this is quite likely simply because the company has no experience with failure and will lack the resilience to deal with that Failure in a successful fashion.

All part of the great cycle of knowledge

mandala by Peter Kaminski

Open access saves $1B
[Via Naturally Selected]

A new analysis suggests that making papers open access would pump $1 billion into the U.S. economy over the next few decades.

That’s about five times the amount it costs to archive the papers, according to ScienceInsider.

The economic analysis, about the effects of a pending National Institutes of Health policy that would make all papers from federally funded research free after a delay, comes from John Houghton at Victoria University in Melbourne, Australia, and his colleagues. He has also suggested open access could save nearly half a billion euros per year in the UK, as well. You can read more about the newest model here.

Publishers, of course, have decried the proposal. Do you think such a potentially dramatic cost savings is enough to convince skeptics?

[More]

I’m sure that the analysis will meet with some scrutiny but that is how we usually get closer to the truth. Someone takes some data to create information and produces some knowledge. Someone else takes that, adds some more data and, hopefully, creates more knowledge and a better understanding.

Cranking the cycle several times is how wisdom is achieved. So, perhaps soon we can find out if Open Access is actually a wise approach for many situations.

Apple’s iTunes Remote app and one guy

[Crossposted at A Man with a PhD]

Apple’s iTunes Remote app was developed by one person – report
[Via AppleInsider]

Apple’s iTunes Remote application for the iPhone has not been updated in over 8 months because the software was written by just one person, and he is currently busy with other projects, according to a new report which describes Apple as “a huge startup.”

[More]

Here is how he describes the way Apple runs things:

Apple doesn’t build large teams to work on every product they make. Instead, they hire very few, but very intelligent people who can work on different projects and move around as needed.

One day you might be working on the Remote app, and the next day you might get pulled on to another project that needs your help.

The engineers on the Mac OS and iOS teams move back and forth between the two projects based on release cycles and what needs to ship next.

That is how we worked at Immunex – whatever was on fire got the bucket brigade approach. we all worked on multiple projects at the same time, allowing us to drop something that was going slow and pick up on something that needed more attention.Once we had gotten our role done, we handed it off to the next member of the bucket brigade and picked up another project.

In order to make this work well, there needs to be constant vetting of the progression by everyone involved. Any bumps in the road can be smoothed over if more eyes are on the prize.

Thus everyone feels a part of a successful project, even if they had a little part. Immunex’s great drug was Enbrel. I had a very small part working on that molecule quire early. While only peripheral to the amazing work done by others, I felt every bit as proud of its success.

Plus this approach keeps smart people interested and helps prevent empire building, which can be a real detriment to the rapid actions a small team needs to make.

Any company basing its success on the creativity of its employees needs to have a management style closer to Apple’s or Immunex’s.