(This column is posted at www.StevenSavage.com, Steve’s Tumblr, and Pillowfort. Find out more at my newsletter, and all my social media at my linktr.ee)
“Efficiency” has been in the air a lot in the world of business, technology, and now government. I find this amusing because after 30 years in IT I’m more in the “keep hoping” mode on achieving real efficiency in organizations. Most people don’t think about what efficiency really is, but boy are they ready to try and achieve what they don’t understand.
The illusion is usually somewhere in a Daft Punk-esque dream of “better, faster, cheaper.” We will somehow achieve efficiency that means everything is of higher quality, gets to us faster, and costs less. When you put it that way, it starts to sound suspiciously like marketing and not actually a plan which is what a lot of efficiency efforts turn out to be.
See, sometimes efficiency as people conceive of it is actually not what they want. Yes, sometimes, better, faster, and cheaper is a terrible goal. However a lot of consultants, politicians, and marketers don’t want to admit it, and in many cases are too deliberately ignorant to understand it.
To illustrate this, let me give an example from computer code. Once I was working with a coder that was pulling their ever-thinning hair out over some legacy code that was incredibly brittle – simple modifications created cascading problems. Upon closer examination, the conclusion was a case of people being “efficient” – to stay on time they’d done all sorts of tricks of half-reusing code, ignoring good long-term choices for the easiest-to-code, and left us a mess.
Totally “efficient” and a total disaster to maintain and easy to break.
Something that works may not be the cheapest, or the fastest, or even the best. However it is reliable, consistent, enduring, and keeps going. You can save money, cut corners, overload what you’re doing but it will break. Efficiency is sometimes bad for actually getting good results because when you’re goal is to save time, money, or whatever you don’t ask will it work and keep working.
If you aim for better over some single-number driven measure of efficiency – more stable code, a better process, have higher standards for your company – you will probably get gains in efficiency anyway. Your company database not crashing saves money. Not having lawsuits due to better testing of a product is good. Efficiency sometimes comes from you know, doing things well.
I feel we’ve created a cult of efficiency in America. Maybe it’s also part of our weird health craze trends or a way to cope with economic differences. Perhaps it’s some malignant leftover part of the Protestant Work Ethic. But I think we’ve really overdone it because efficiency may not be what you want – or the only thing.
In closing, let me talk about another traumatizing event in my long career. A project I was assisting with once had employed a contractor who had software that gave answers perfectly. A quick test revealed they’d basically made software that could only past the test.
It was very efficient in its own way, and absolutely totally wrong.
Steven Savage