"Delivering uncommon results in software culture"

Type r for Retry

We’ve all done it – compiled a program, run it, get the wrong results and out of complete astonishment re-run it just to see if we get different output a second time. We haven’t changed the code, we haven’t recompiled it and we even know it’s foolish as we’re attempting it – but we simply can’t believe our eyes. We somehow expect the laws of physics to produce quantum chance results.  

We change nothing, but we expect different results.

The same can be said in business. We try something – it doesn’t produce the results expected, so we do it again (and again) expecting different results from the same approach. It’s just as misguided.

We blame it on the usual suspects and rely heavily on the notion that “it’ll be different next time” – that sometime soon it’ll work. We justify to ourselves that the economy, the prospect or the season are the only factors conveniently absolving the couple of 500lb gorillas in the room.

We continue to look to “traditional solutions”. We mistakenly believe that because we saw a lot of something in the past that it must have worked; we confuse that visibility with success. We somehow believe that if we use well known approaches that we can be exempt from failure and criticism – because well, everyone did it too – right?…

Programmers don’t do that for very long, and neither should business. Assumptions need to be constantly re-examined. They should always be addressed when your expectations didn’t meet your results.

If an approach doesn’t work don’t blame it on an individual, the economy or the weather. Research why it didn’t and make a course correction or stop the approach. Being more dogmatic about an approach (screaming your message) just makes it louder – not better. So too is the tact of “they’ll come round.” Take your ego out of the messaging and depersonalize yourself from the picture.

Adapting requires more thought than traditional approaches. Adapt to your environment – don’t attempt to force your environment to adapt to your beliefs.

“What passes for tradition is usually an excuse for sloppiness.” – Gustav Mahler.

 

About the Author
I’ve had the good fortune to travel and work internationally. I’ve also had the good fortune to have grown up in New Zealand and have lived the American “immigrant experience” for more than half of my life. I’ve also had an unorthodox musical journey that led me to and kept me in Kansas City. Music, IT and travel became partners along the way helping me appreciate multiple worldviews and the concepts of cross-disciplinary approaches to life and work. My non-conventional experiences reflect my meanderings about this interesting occupational field. The beauty of having been in IT for 30 years is that our solutions become predictably cyclic while our problems remain the same. Culture is a topic I’m rather obsessive about. I firmly believe that it will help to usher in a renaissance in American business – oddly enough in the hands of IT.
  1. Larry Nickles Reply

    I 100% agree. I’ve found that when reality disappears (i.e. It should be working!), stop what you are doing, drop all assumptions, and start over from the beginning. “Is it plugged in?”

Leave a Reply

*