Existing intranet and wiki systems in all companies are filled with content. When it comes to launching a new Confluence system or a Confluence-based intranet such as Linchpin, many customers want their existing information to be transferred to the new environment and want a fool-proof and efficient migration strategy.
Before taking on an intranet project, you really want to know what software license fees to take into account. Go ahead and call your trusted SharePoint consultant: “I want to set up a SharePoint-based intranet for 500 staff – what license fees do I need to reckon with?” You’ll get numerous ifs and buts but no specific figures.
This post is about Linch and Pin and their conversations about collaboration in an elevator. The two are working in a big corporation and analyze the difficulties of collaboration in this company during their encounters. They know, that there is a better way, but they are not in charge. Linch and Pin are the stars of our upcoming new video series. Stay tuned!
Why do so many businesses use MS SharePoint as their intranet solution? Why do they give their users a system, that the often times don’t even want because there are far better collaboration tools out there. So it often leads to frustration instead of increased productivity and collaboration in daily business. In this post I am asking the question which corporate policies lead to these decisions.
In our article, “Enterprise Wikis: Criteria and important topics in the evaluation of wiki software” we discussed the diverse and unique requirements an enterprise wiki needs to meet. Decisions about choosing the right wiki system cannot be made using generalizations, but rather only by taking into account the specific needs of the company. In this article, we will draw a concrete comparison between the approaches of the Atlasssian Confluence commercial system and the open source systems Foswiki and MediaWiki. What are the strengths of Confluence compared to Foswiki and MediaWiki?
Whoever is on the lookout for a simpler, slimmer solution that can be implemented much more quickly will find Confluence to be an extremely sophisticated package. In contrast to SharePoint, Confluence can be easily and successfully introduced without complications. And it can even be connected with SharePoint.