An internal microblog can become a useful channel of communication within an enterprise. Similar to having lunch or coffee together, or chatting in the hallway, employees exchange information, news, ideas or project details in a microblog. Sometimes the posts are time sensitive and important, sometimes they are just about exchanging ideas with colleagues and getting their input. Enterprises can benefit from that. What are specific use cases, and how can the internal tweeting gain strength? We have collected 36 use cases. Here are the first dozen.
Within a company there can be many approaches for the development of texts as well as the sharing of texts for further revision. We could, for example, write a text in Word and then load the final version into the enterprise wiki. We could also send around texts by e-mail, asking colleagues to read them and, if necessary, to make changes. But we could also develop a text directly within a wiki. What should we think of this particular work process?
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.
Working with Confluence, you notice how fast the content of your wiki is constantly expanding. Eventually some content needs to be updated due to new information or developments. The question that might arise: Shall I create a new page with new content or rather update the existing page? In this video, Martin Seibert from //SEIBERT/MEDIA explains the advantages of updating a page rather than creating a new one. This approach might involve a bit of work and time but reduces redundancies and helps communicating updates to the existing followers of the old content.
At //SEIBERT/MEDIA, we’ve been working on a wiki for years. Through our day-to-day work as well as through dozens of enterprise wiki projects, we have experienced – thanks to innumerable different cases – how useful and valuable a wiki can be on a number of levels. Therefore, we believe it is high time to compress the arguments for a wiki into the limited space offered by tweets to make our points as efficiently as possible.
Free download for your test environment
What started as a hackathon project at //SEIBERT/MEDIA, has become an alpha version that is available on the Atlassian Marketplace. The plugin Microblogging for Confluence is the first mircoblog extension for Atlassian’s social collaboration platform and therefore a solution that allows a seamless and direct information exchange with the team within the wiki – without leaving Confluence.
Wikis for enterprise use, both those available commercially as well as those available in open-source contexts, have become quite sophisticated. This article introduces and evaluates possible requirements as well as decision-making criteria.
//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.