|
Features
Say the word “intranet” and many business managers cringe. Bad memories of overtime and over-budget IT projects that never delivered on their promise to increase internal collaboration and know-ledge sharing abound. Why? Because so many homegrown, custom intranets were built with little input from the end user and required technical expertise to continuously update and maintain, business users failed to adopt them. Luckily, the concept of “anytime, anywhere” access to business-critical information lured developers back to the drawing board and fueled the growth of the web-based software—software as a service (SaaS), hosted—market. Today, large and small organizations alike are getting up and running with web-based collaboration solutions in a matter of minutes, with no upfront investment in hardware or software.
Wikis are increasingly gaining popularity in the enterprise and are being deployed for many different types of projects, in particular for team collaboration. While doing research at the beginning of 2008, I found that wikis had recently become ubiquitous in many organizations. Join me for a quick review of some of the common myths about wikis coupled with best practices for wikis inside the enterprise.
Columns
Collaboration is a vexing topic for many intranet managers. The requests from business areas for wikis or SharePoint spaces are never-ending, but the question remains: Where do these fit in relation to the intranet?
With the continuing buzz around Web 2.0—and Web 3.0 discussions starting up—let’s consider the impact that this has on the operational aspect of intranet management. While the sophistication, complexity, and size of webites has increased, many companies continue to manage their web teams in the same archaic way they did in 1995—potentially increasing the risk and liability for their organizations.
Read_Me_File
Reviewed this issue: The Enterprise Social Software Report, Web 2.0: A Strategy Guide, Enterprise Web 2.0 blog
|