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.
Category Archives: Trends
Wiki Adoption: A Pilot Project As An Obligatory Routine
When introducing a new and in its type different software, this aphorism, that once Oscar Wilde and also Mark Twain adjudicated, fits very well, because: a wiki adoption can not be repeated very often. This is why we recommend to prepare a wiki project in the timeframe of a pilot phase, for later application.
111 Reasons why you need an Enterprise Wiki
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.
11 Questions to Answer when Evaluating Enterprise Wiki Software
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.
Wikis need a customized Design
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.
Management Dashboards in an Intranet
By using management dashboards, your company’s managers will have access to a better overview and more transparency. By dashboards, we mean graphical evaluations that represent certain quantifiable key numbers in charts and make time segments visible through trending. This compiles information into a critical mass in an easily understandable and accessible way.
Scaling Git with Stash Data Center
Stash has always been the fastest and most secure Git repository management tool available, and now, it’s also the most scalable. With clustering built-in, the Data Center deployment option for Stash is designed for massive scale to meet enterprise needs.
New pricing model for Jira Service Desk 2.0
Atlassian has responded to the feedback on its previous JIRA Service Desk pricing model. The pricing has changed to agent-based pricing plus the required JIRA user tier. Get started with three agents for $10/month. Teams with more than three agents pay $25 per agent per month. Each agent can serve unlimited customers. Whether you serve 100 or 100,000, customers are free.
Atlassian announces Confluence Data Center
The Data Center deployment option that was already available for JIRA was designed to meet the needs of large enterprise customers providing performance at scale, high availability and instant scalability.
Architecture of a Wiki-Project: Elements, Process, Approach, Rules
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.