You’ve got several different companies in related industries, multiple branches and offices in several countries; you’re an MNC (Multi-National Corporation.) You have legacy IT systems, with rivalries, varying budgets and databases at various stages of development. But you want teams to collaborate, other business units to share ideas to leverage cross-company opportunities for revenues and productivity improvements. The challenge boils down to how to get everyone on the same system, securely, while avoiding a massive IT expenditure. The answer is the Web; it’s just how you go about it.
Many MNC’s have an inherent distrust of the Web as a viable platform for collaboration. We’ve seen this in North American and European companies. What we’ve found this boils down to is two main issues; 1) IT departments raise the spectre of security of data, and essentially, further erosion of budget for hardware and software, thus people and the perceived value to the organizational whole and 2) lack of C-Level knowledge and buy-in to Web based applications. Many MNC’s still see the Web as pretty much just a marketing tool, and measure their Web activity by sales only.
Some MNC’s however, such as Citi Bank and Chevron, have actively engaged with Web-based tools such as Wiki’s to provide a single platform solution across multiple divisions and business units. Very successfully. In some cases, the Wiki is hosted within the corporate infrastructure, while in other cases, it sits hosted by the provider. It comes down to a needs analysis, data protection requirements and ease of access by staff.
Wiki’s are one choice for a Web-based collaboration tool, and arguably the best solution. They can reduce email traffic (cutting down on bandwidth, infrastructure and productivity costs) and improve process efficiencies and project outcomes.
Using a hosted Wiki is a concern, but becoming far less so. The heart of hosting concerns usually lies with where the data is stored and privacy laws. U.S. privacy and data laws can be hard to handle for most organizations, but data can be moved around. Placing a Wiki internally can allow for integration to existing LDAP and Active Directory processes, enabling SSO (Single Sign-On) capability while protecting the intellectual property generated in a Wiki. This also keeps IT happy that budgets are protected, but reduces the challenges of implementing legacy solutions custom-coded.
Implementing a Wiki takes a long-term strategic approach, but less time and attention than an ERP solution. It is also less costly. An On-Demand solution can be enabled in just a few days. Training is relatively painless and knowledge workers will have little trouble becoming comfortable with the system.
The long and short of it is, a Wiki, or a Web-based solution for collaboration, can save millions in productivity, improve project outcomes and become a valuable knowledge asset to any corporation. Chances are, you’re competition is looking at some solution. That doesn’t mean you should, but it should be a part of your consideration in developing competitive practices. Enough MNC’s have adopted Wiki’s and similar collaboration tools leveraging the Web that such usage will only continue.
The key to success with Web-based tools is careful planning and understanding how another Web-based solution fits into your overall Web strategy. Policies on usage, security and management controls need to be put in place as well; before implementing. Find a consultant who has helped guide these projects, and also understands broader Web policies within the organization.