Do we have to use the F-word?

OK, it’s a provocative title. I like to talk about two F-words: Feelings and Failure. This post is about failure and how to use it.

I was working inside a firm recently and someone said: “We can’t talk about failure around here. That would hurt our careers.” Ummm.

First, let me (apparently) change subjects completely. This post was inspired by Lean’s interest in failure and quality, which I owe largely to my relationship with the Poppendiecks. So, I want to talk about some of the things they talk about.

They posit seven principles of Lean Software Development:

• Eliminate waste
• Build quality in
• Create knowledge
  • Use the scientific method
  • Standards exist to be challenged and improved
  • Predictable performance is driven by feedback
• Defer commitment
• Deliver fast
• Respect people
• Optimize the whole

As with all good ideas, most of these are obviously good at first glance. What is apparently (from what I see in real life) not so obvious is the full meaning and application of these principles, which the Poppendiecks explain.

You will notice that I gave detail for only one: Create knowledge. (The others have more detail, not shown; perhaps subjects for another day.)

So, let’s talk about the scientific method. “But wait, weren’t you going to talk about failure?” Ah, I am talking about failure. Imagine the many failures of the Wright Brothers (two of my favorites) or Alexander Graham Bell. Only after a couple of years of failure did we hear: “Mr Watson — come here — I want to see you,” and the telephone was born.

The Poppendiecks explain the scientific method this way: “Teach teams to establish hypotheses, conduct many rapid experiments, create concise documentation and implement the best alternative.”

When we are creating something new (with software we always are), we need to fail, fail, fail, succeed. This is embedded in the Red, Green, Refactor of test driven development. This is what all inventors do. (Now you can call yourself an inventor. Really.)

Now, using failure to learn and make progress and discover is not an excuse to use failure to hide shoddy work or laziness or stupidity. (Very few workers really want to do shoddy work or be lazy, but a few of us have that kind of motivation from time to time. Examining why is perhaps a subject for another post.)

So, if your firm or the people around you don’t want to hear the F-word, tell them your team is using the scientific method. You are testing hypotheses to identify the best one. Only by failing can we succeed. (Another paradox resolved.)

Good luck with your project.

« « The Elements of Agile Style – 2 || Little’s Law – Lean Software Development – 3 » »