Failing fast

It seems like everyone is singing the benefits of fast failure these days. Avoid blame cultures! Throw mud at the wall! Just give it a try! If it doesn’t work no big deal.

I get it. We’re so very agile don’t you know.

But I also sense a big disconnect between the theory and the practice – in my own life and in those of many others I see.

I suspect part of the problem is that the idea of fast failure often comes bundled up with a notion of toughness. As in, “get over it”. We humans don’t really like the idea of being vulnerable. even though in many ways we are. Failure hurts, even if it shouldn’t. Noble failure probably hurts even more.

Is there room for that in an agile world? Just asking.

3 thoughts on “Failing fast

  1. bStormhands

    The thing of it is, is that failure is draining, and without some wins, you end up emotionally depleted and burnt out. Not fun.

  2. James Cherkoff

    Fail fast is a helpful approach if everyone in an organisation is involved. However, if you are the only agile one, you’ll be in danger of becoming the guy who constantly fails (fast).


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.