Over the past 12 months, I’ve taken a number of client inquiries on globalization and multilingual strategies. But in all cases, it turned out that the challenge wasn’t really providing multilingual support. Instead, organizations are struggling to meet demand among customers, suppliers, partners, regulators and others for direct access to core enterprise systems from multiple regions, often through mobile devices or pervasive web applications. So the real question is: How are user engagement strategies affecting our ability to achieve a single, global business and technology platform that supports the increasingly pervasive use of mobile technologies?
This is now a top-of-mind consideration for many companies, especially as emerging markets are an increasingly important part of their global business strategies. The challenge is how best to tailor and adapt their products and services to capitalize on these emerging market opportunities without losing the benefits of economies of scale and the requirements for global transparency and compliance. And it’s not just about global IT service delivery; it’s about how technology can now serve the unique needs of both internal and external users, particularly where major differences may exist across language, culture, law, infrastructure, geography, value systems, and the economy.
On March 30, 2010, Yale University placed a migration to Google Apps for its email services on hold over privacy and security concerns, especially regarding a lack of transparency about in what country its data would be stored in.
Michael Fisher, a computer science professor involved in the decision, said that “People were mainly interested in technical questions like the mechanics of moving, wondering ‘Could we do it?’ ,but nobody asked the question of ‘Should we do it?’” and went on to say that the migration would “also makes the data subject to the vagaries of foreign laws and governments, and “that Google was not willing to provide ITS with a list of countries to which the University’s data could be sent, but only a list of about 15 countries to which the data would not be sent.”
This closely aligns with our January report, “As IaaS Cloud Adoption Goes Global, Tech Vendors Must Address Local Concerns” which examined security and privacy issues involved in moving data to the cloud, especially when it’s no longer clear what country your data will reside in. In this report, we offered that IaaS providers should give “guidance on where data is located and location guarantees if necessary. Rather than merely claiming that data is in the cloud, tech vendors must be prepared to identify the location of data and provide location guarantees (at a premium) if required.”