Very good article and very good point.
And, as agility is a frame of mind, it's harder to help people change and 'see' stuff in a different way.
PierG
http://pierg.wordpress.com

There is an elegance to a simple solution that just works. Once you learn to appreciate that elegance you'll start to look for simple solutions to everyday problems. You'll begin to see that the solutions should reduce complexity rather than increase it. That's where the agile state of mind begins.

Exceptions are always the antithesis of any simple solution - and in any process involving human beings, there are bound to be exceptions. In my shop we follow the 90% rule - we program for the 90% of routine cases. The corollary is that we don't program for exceptions. This requires getting into the habit of developing solutions with a built in escape hatch - a way of kicking the individual transaction out to a human being for judgment and correction. This preserves the human touch, and the flexibility in the organization's processes that are necessary to provide optimal service, but automates the 9 out of 10 routine transactions. The result of this kind of programming is inevitably a more flexible system that does not limit the users to the system's defined process, which can only contribute to the greater agility of the enterprise.

Thomas M. MacKay
Assistant Director
Information Technology Services
Christopher Newport University

A very good article. I agree with most of your thoughts. I do think that we should focus on simple elegant solutions delivered quickly. I also think you should spend a little bit of time thinking about the best return on your effort.

I somewhat disagree with your example of "automating the mopping so people will have time to fix the leak." In this case, the problem is a wet floor. I'd encourage my folks to ask why the floor is wet and hopefully jump directly to fixing the leak. Sometimes the cost of fixing the leak is so prohibitive that it makes sense to "automate the mopping".

How's that for wishy-washy?

The bottom line of Agility in my opinion is to inspect your situation and make adaptations. Deliver quickly, then inspect again. Don't do the simplest thing just because it is the simplest. But do something quickly that will add the most value for the time spent.

Michael
Excellent post as usual. If agility is the key determinant for success going forward, and I increasingly believe that it is, then IT departments must deliver systems smart enough to be useful - to handle the 90 or 95% of standard transactions. Building these systems and extending existing systems with smarter decision services is going to be the difference between success and failure.

JT
www.edmblog.com
Smart (Enough) Systems