I think the most succesful software development teams are those who are fostering a culture of constantly trying new things out.

We have all burned our fingers on new immature technology, applying tools that were not the right tools for the job, or doing something we found out later was just plain stupid. While it may be just to blame whatever idea or product we tried out, putting the blame on the concept of "trying out" is taking a step down a dangerous path as it will lead to blaming those who are "trying".

I once had a talk with a guy that said something like: "We tried using frameworks and it didn't work, so we don't do that anymore" -- That may be trying, but perhaps a pretty early judgment on something as generic as the concept of a framework (It really sounded like the word "framework" was becoming taboo in that company). If you stop trying new things out I guess that means you don't care about improvements. 

Recently I had a talk about experiences with Stored Procedures. Perhaps you tried using Stored Procedures to solve a particular problem and it didn't work out very well. Now, that doesn't necessarily make Stored Procedures something evil that should never be touched again. Or how about build scripts -- How do you know if MSBuild or NAnt is best for you if you haven't tried both?

When we reach software nirvana I think everyone is accepting that trial and error really is the only way to improve, and thus encourage it as an everyday activity.