In general, the establishing of a wiki must be supported through a series of measures. If these activities are successful, the system – as I know from my own experience – will quickly be accepted and used by employees. At //SEIBERT/MEDIA, TWiki has been used since June 2007, now containing a total of eight Webs. The main Web alone grew to contain more than 1000 topics within just a few months.
We have already summarized 111 solid reasons for using an enterprise wiki. Now with the help of some concrete examples we are going to show you how an enterprise wiki can actually benefit your firm. Following in the footsteps of examples 1-22 and 23-44, we now close our series with 22 more concrete use examples.
We’ve already published 111 good reasons for enterprise wikis. Now we’d like to show through example use cases just what you can do with an enterprise wiki. //SEIBERT/MEDIA has distilled 66 examples for use cases: the first 22 can be found here; now, let’s move on to use cases 23 to 44.
We have summarized in our weblog 111 good reasons for using an enterprise wiki. But how can such a system blossom and show its’ added value and Return on Investment? What are some concrete examples of how companies can implement an enterprise wiki? Which possible uses make sense? Which of them are truly useful? And which of them can actually improve your efficiency? We have collected 66 ways to use wikis in organizations. Here are the first 22.
//SEIBERT/MEDIA is one of the biggest Atlassian Experts Partners worldwide. And of course we intensely use Atlassian tools for our internal organization. In the following video our colleagues Martin Seibert and Alex Boerger demonstrate first conceptual and later directly in the system what roles Confluence, JIRA and HipChat play in our digital communication, how the tools are connected to each other and how they support coordination, teamwork and productivity.
Whenever we speak with clients and go through possible services with them, they often have questions regarding why we offer services such as “Layout Design” or “Executing the Design in HTML and Implementing within the Wiki”. In this article, we will offer you a couple of arguments and explanations to answer why it is worth having your wiki professionally designed.
The Confluence plugin Microblogging for Confluence developed by //SEIBERT/MEDIA enhances Atlassians’ social collaboration platform by deeply embedded microblogging functionalities: employees can discuss ideas, get feedback on exciting topics and quickly and easily share current information with others without changing context directly in the Confluence intranet.
We can no longer conceive of the //SEIBERT/MEDIA Intranet without a Wiki. As a knowledge management system and employee portal, the Wiki is of incalculable value within the company network, fueling the Intranet motor.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationContact
Our Sites
News
Auszeichnungen
