Debunking the myth that a wiki-foundation is central to what Linchpin is. Personalization and grabbing the attention of active users is what makes Linchpin stand out.
A company wiki needs an custom design. And not as a nice optional extra, but as an absolutely essential component of a successful wiki project. There are sound reasons and convincing arguments for this.
If you’re one of these newbies, this is my advice: don’t worry about this stuff right at the beginning! Don’t spend hours trying to find, fix and understand everything or build a clever structure. Instead, just get your first pages up so you can share your knowledge with your colleagues. This is what is most important in the beginning.
A fundamental factor for the success of an enterprise wiki’s introduction is design optimization. This includes fine-tuning of the wiki’s online appearance, usability and navigation controls. In addition to this, guidelines (or templates) must be created for the actual wiki content to support productive and efficient work. This post covers the content design aspects most important to a company’s new wiki.
An enterprise wiki, intranet or knowledge base is most successful when many employees actively use it, driving a good return on your investment. Employees will rarely immediately or actively use their new wiki if their company only runs an automated introduction. A targeted wiki launch campaign can help to advertise the wiki, and create the best conditions for successfully establishing it throughout the company.
Steffen Opel, Managing Director of the software company Utoolity GmbH, uses draw.io extensively in his company and was kind enough to provide us with a testimonial: What advantages does draw.io offer compared to other solutions?
There is only one best intranet software. It’s ours.” It’s the condensed marketing message of most ads not only for intranets. We all know it can’t be true if two people say it. But the main problem is that companies still try to find out who is right and who is lying.
Most people suffer from the daily load of emails. I have met people who claim that it is not a big issue, but they also tell me that it’s just because the amount of emails they receive is fairly low. We can all feel the pain that emails create. And most know that the using email is often unappropriate. But how do we know when to email and when to go for a better alternative? That’s unsolved for most people. Most of the time we don’t even know what the appropriate action is. And often we fail to act professionally, although we know better.
The basis for this article were recently constructed under the leadership of Martin Seibert at an open-space session at the WikiSym in Portugal. The original document is available in English under the title “How good is MS Sharepoint as a wiki?”
Without professional knowledge management, companies are losing potential, wasting resources, and acquiring unwanted competitive disadvantages. Along with many other companies, the industry giant Microsoft has rolled out its own application, SharePoint, which allows data to be centrally deposited and edited.
Companies that want to convert from their current company wiki system to Confluence must overcome a few challenges: existing users are used to working with the platform, changing systems always involves trade-offs, and transferring existing content is complex and painful. In the previous article, we described these common challenges in detail. In this article, we will explain why the switch to Confluence is still a good idea and why the exhausting migration process is still worth the effort.