ValiCert expected to save millions annually while cranking out new software for banks, insurers and government agencies. Senior Vice President David Jevans recalls optimistic predictions that the company would "cut the budget by half here and hire twice as many people there." Colleagues would swap work across the globe every 12 hours, helping ValiCert "put more people on it and get it done sooner," he says.
The reality was different. The Indian engineers, who knew little about ValiCert's software or how it was used, omitted features Americans considered intuitive. U.S. programmers, accustomed to quick chats over cubicle walls, spent months writing detailed instructions for overseas assignments, delaying new products. Fear and distrust thrived as ValiCert's finances deteriorated, and co-workers, 14 times zones apart, traded curt e-mails. In the fall of 2002, executives brought back to the U.S. a key project that had been assigned to India, irritating some Indian employees.
"At times, we were thinking, 'What have we done here?' " recalls John Vigouroux, who joined ValiCert in July 2002 and became chief executive three months later.
Shifting work to India eventually did help cut ValiCert's engineering costs by two-thirds, keeping the company and its major products alive -- and saving 65 positions which remained in the U.S. But not before ValiCert experienced a harrowing period of instability and doubt, and only after its executives significantly refined the company's global division of labor.