Tuesday, August 4, 2009

The Russian Method

In my first days in the computer business in India, I worked amongst a small group of research engineers clustered around (then) a spanking new PDP-11/40 mini-computer system with its sparkling lights, putty colored body, elegant contemporary console panel and the quiet hum of the RP-05 disk drives. All set in an air-conditioned temple where people moved around with hushed voices. We ran RSX-11M – a multi-user operating system that supported, I believe, eight simultaneous users. But ignore the technical jargon – this is simply background material for what follows.

Our friend V, who was in charge of the “system” was a man of tremendous wit and few words. He was also a man of tremendous patience who would try all means possible to keep the computer running and the users productive. But more than once, the computer had a habit of seizing up, lost in some internal thoughts it kept looping in, the console lights flashing in the same endless sequence. When all else failed, V would use what he called the “Russian Method” to fix the problem. He would turn off power, turn it on again and reboot the system and presto – all was well again.

The word “Russian Method” has gone down in my vocabulary as undue use of excessive force to solve an otherwise difficult problem. We use the Russian Method to open recalcitrant jam jars; we use the Russian method to bang in nails that are bent; We use the Russian method to force open nuts with pliers when the wrench does not seem to work; We use the Russian Method to slam doors that would not shut otherwise.

Unfortunately in enterprise architecture also, people tend to use the Russian Method for difficult problems. And if the difficult problem had a chance for a solution, the Russian Method often guarantees that the difficult becomes the impossible.

The best of the Russian Methods is with-holding budget approval. Promise to cut off the budget and even the toughest individual comes groveling at your feet. Another is the totem-pole method used for determining order of layoff. Follow up with needs for various certifications and accreditations before a system can be cutover and the hardiest program manager is ready to hand over his first born.

The Russian Method is simply use of escalating force. Often, a slight effort in analyzing root causes and symptoms and tailoring a solution approach accordingly can provide more benefits. But boy, does the use of the Russian Method make you feel good!

No comments: