Flames from the front: in search of mediocrity. (mediocrity in the information systems industry)

Just for drill, let's take a little quiz. Suppose you're assigned to a project for your very best customer. This customer accounts for the single biggest piece of your revenue and there appears to be a lot more work down the line. You do your usual razzmatazz and run across something that, if changed, would save Mr. Customer a bunch of money.

You know, however, that if this something is left alone, no one else will know, it won't effect your bill, and the project will be a lot easier to complete. This little something is also one of Mr. Customer's favorite things - one of his sacred cows.

You: A) Convince yourself that good enough is good enough and never bring it up; B) Go into convulsions, start vomiting pea soup, and declare that you have been possessed by the evil genius who invented cost/benefit analysis; C) Realize the politics involved, say nary a word to anyone, and whistle "Somewhere Over the Rainbow" under your breath as you present a lesser solution; D) Suck up your guts and tell the customer what he needs to know.

Twenty years ago, most of you would have selected the obvious D. Today, I'm afraid that most would choose anything but D.

Perhaps it's downsizing, or maybe it's people working long hours. Who knows? But just a little bit of observation will bring you to the same conclusion. There is hardly anything that you can find which is the best it could be.