I think the author is confused with three different concepts: fault tolerant system, idea generation and agile development.
A system being fault tolerant, like googke, just means that it can rollforward/rollback when an error occurs. It is nothing more than a technical concept.
People in design industry often use brainstorming to generate and screen ideas. IDEO is just one of them. Brainstorming is not an explaination of either how they succeed or why they succeed.
And the framework Ruby on Rails characterizing convention over configuration and don't repeat yourself even has nothing to do with "failure-tolerance", thought it emphasizes fast iteration in development.
The over generalization in the article make its conclusion very unconvincing.
A system being fault tolerant, like googke, just means that it can rollforward/rollback when an error occurs. It is nothing more than a technical concept.
People in design industry often use brainstorming to generate and screen ideas. IDEO is just one of them. Brainstorming is not an explaination of either how they succeed or why they succeed.
And the framework Ruby on Rails characterizing convention over configuration and don't repeat yourself even has nothing to do with "failure-tolerance", thought it emphasizes fast iteration in development.
The over generalization in the article make its conclusion very unconvincing.