The digital form of the talk in the hallway, where employees exchange information, news, ideas and project details and receive feedback and input, are a benefit for enterprises. But what are specific use cases for an enterprise microblog? We have collected 36 use cases. After the first twelve, read more about use cases 13 to 24.
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.
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.
Microblogging for Confluence, developed by //SEIBERT/MEDIA, is the plugin that enriches Atlassian’s social collaboration platform with seamlessly integrated Enterprise-Microblogging features. This add-on is already available on the Atlassian Marketplace: Download the alpha version for free and evaluate it in your test environment just as you like.
From dozens of enterprise Wiki projects, we know that the successful introduction of a Wiki into a company typically depends on three factors: technology; organization; and culture. In the first of these three articles we focused on the requirements of technology. The second of these articles focused on organizational factors. This report will now focus on the implications of company culture and how these relate to the introduction of a Wiki.
From dozens of enterprise Wiki projects, we know that the successful introduction of a Wiki into a company typically depends on three factors: technology; organization; and culture. In the first of these three articles we focused on the requirements of technology. This report will now focus on the organizational factors for a promising Wiki project.
In the article Architecture of a Wiki-Project: Elements, Process, Approach, Rules, the procedure for a typical adoption of a Wiki is portrayed in detail; we suggest you read that article first. This article completes our explanation with the types of questions, which many customers have, questions that require coherent, unambiguous answers.
Many companies are unsure of how a successful Wiki project should be started and executed. This article will give you an overview 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 collected many experiences regarding the process for Wiki-projects, which we will happily explain here – regardless of whether or not you are currently running a project with us, are planning a project with us, or simply wish to be more successful with your Wiki – without our help.
Microblogging for Confluence is a plugin developed by //SEIBERT/MEDIA, which expands Confluence by a seamlessly integrated microblogging function. Developed within the scope of an intern “Hackathon” and since then constantly enhanced by our team, this add-on has gained a great stability and a wealth of features. We have now released a new version. In this article we show the big and small innovations that are part of the latest release.