Projects fail.

 

Technology projects fail.

 

Neither of those come as a surprise but far too often the response to that failure falls sadly short: we spend hours on end doing debriefs, post-mortems, sunset reviews and whatever else we call our poke-and-prod sessions. We come up with reasons, without necessarily understanding or embracing purpose in our failure.

Kerwin Rae says that the key to success is failure.

 

I’m with him there and it’s not a “fake it till you make it” thing, or a “keep trying and eventually you’ll succeed” thing. Instead we ought to recognize that if we had what we need (resources, process, know-how, technology or anything else really) that would make us the company we want to be tomorrow, today … well, we’d already be that company today.

 

We tackle these projects exactly and solely because we don’t have what it takes, and it’s only in doing so we get closer. Technology must therefore become an evolutionary component of our business contexts, where we recognize from the onset that there’s no magic silver bullet.

 

In doing so we start to extract purpose from our failures, instead of either trying to recover from them or being too afraid to try again.

 

Side note: We might just be the right partner to help you figure it out.