First, despite the corporate governance problems at Satyam, none of their global customers had raised any concerns related to the quality of operational delivery and performance in their projects. In fact, there has been an increase in the size and scope of projects delivered to global customers by the major Indian software firms over the last few years. Hence if it had been a problem related to inability to execute large projects, we would have heard this from the market loud and clear.
Ironically, Krishnan last summer helped arrange for my colleague Rob Preston and me to interview Raju, dropping a letter of recommendation to the Satyam founder as we were trying to lock down our schedules. At that time, and for very good reasons, Krishnan held "Chairman Raju" and the entire company in the highest regard, so Krishnan's perspectives on Satyam's bombshell, plus the collateral impact it's had on other Indian software and services companies, come from someone who is very familiar with all of those companies and their leaders and their customers and their business models.
In that context, Krishnan's column urges CIOs to take the time to separate the actions of Satyam's founder from the performance delivered by the rest of the company; and to separate the legitimate risks CIOs now see in doing further business with Satyam against the proven value it and other Indian IT firms have consistently delivered. It is advice well worth heeding.
Please join us for InformationWeek's Editorial Webcast: "Offshore In India: What's Next?" on Thursday, Jan. 22, at 11 a.m. EST. Editor In Chief Rob Preston and a panel of top executives from the Indian IT industry will discuss these and other issues. Go here to register.