An enterprise Wiki is not only a new technology for many employees (at least within the company environment); it also requires a change in the normal communication- and collaboration patterns throughout the entire company. Through our experiences with dozens of company Wiki projects, we know that the successful introduction of a Wiki usually depends upon three factors: technology; organization; and culture. This article – the first of three articles on this topic – is dedicated to the challenges of technology.
Tag Archives: English
Why Google Wave Sucks, And Why You Will Use It Anyway
This post outlines how you’ll probably use Google Wave in the future and also gives you advice on how to implement it in your company or your team of coworkers. It also reveals some big usability problems in the current version. Those issues aside, I would like to show you the advantages of the “wave” once again and describe some cool use cases that might make you love it at some point in the future.
Why Mailto Links Should Be Avoided On Websites
A so-called mailto link automatically starts an e-mail program – even if you don’t even use this program. Mailto links on websites are problematic for three main reasons: They lead to usability problems, make tracking more difficult, and could also represent a security risk.
Architecture of a Wiki-Project: Customers’ Frequently Asked Questions
In the article “Architecture of a Wiki-Project: Elements, Process, Approach, Rules”, the procedure for a typical adoption of a Wiki is portrayed in exquisite detail; the best thing to do would be for you to read that article first. This article completes our explanation with the kinds of questions that according to our experience many customers have, questions that require coherent, unambiguous answers.
Architecture of a Wiki-Project: Elements, Process, Approach, Rules
Many companies are unsure of how a successful Wiki-project should be started and executed. This article will give you an overview of this topic and inform you of the basics. //SEIBERT/MEDIA/ offers transparent services. Ultimately, as the saying goes, we’re also just cooking with water, but we’ve also collected many experiences regarding the process for Wiki-projects, which we will happily explain here – regardless of whether or not you are currently executing a project with us, are planning a project with us, or simply wish to be more successful with your Wiki – without our help.
What’s different when everyone is “always on”?
What is going to happen when you are – always and everywhere – online? As a matter of fact, I haven’t advanced any deeper analyses regarding what would happen; I am merely offering a couple of thoughts. I would be happy to see comments and discussion about the following topics.
Wikis need a customized Design
High opportunity costs can be incurred if the wiki layout isn’t customized. In this article, we will offer you a couple of arguments and explanations to answer why it is worth having your wiki professionally designed.
MS SharePoint as a Wiki: Few Functions, less Compatibility
Without professional knowledge management, companies are losing potential, wasting resources, and acquiring unwanted competitive disadvantages. Industry giant Microsoft has rolled out its own application, SharePoint, which allows data to be centrally deposited and edited. But is MS SharePoint really a good alternative to a fully developed company wiki application? Our answer is a definitive “no”.
Management Dashboards in an Intranet
By using management dashboards, your company’s managers will have access to a better overview and more transparency. By dashboards, we mean graphical evaluations that represent certain quantifiable key numbers in charts and make time segments visible through trending. This compiles information into a critical mass in an easily understandable and accessible way.
Wikis in an Intranet Part 2: TWiki in Actual Company Practice
The second article on the topic of TWiki considers the practical implementation of the application within a company intranet, introduces some of the numerous well-developed extensions, and offers summary arguments speaking for TWiki as a potentially powerful corporate wiki.
