Page Comparison

1. Wikis allow organizations and groups to benefit from rapid, secure collabortion of information that is easily created, edited and integrated with other resources
2. You have a variety of wiki choices, a number of which are a great fit to different use cases for organizations, groups and teams
3. Confluence is a popular, affordable, flexible, easy to use wiki that has both server versions and cloud versions
4. The wiki features are so easy to use, many users never

1. bother learning what other features Confluence offers
2. Confluence offers a good range of extension and integration options as needed
3. Sky Web Team provides support for a number of leading wiki solutions including Confluence

SWTR ranks Confluence as a "GOLD" rated wiki

The SWTR ( Sky Web Technology Rank ) of   8.5    is based on 4 summary factors scaled from 1 ( worse ) to 10 ( better )

• Value - 9 for value ( combination of function, features, integration )
• Cost - 7 for net costs ( combination of pricing, administration work )
• Risk - 9 for low operations risks for users and administrators
• Support - 9 for good product support, user input to Atlassian and an active user community with good tips, plugins

Wikis help solve information sharing problems for organizations and groups

What problems do wikis solve?

Maybe. There are many ways to share different types of information across organizations and groups including applications, databases, documents, shared drives, files, media, chat services and more.

Wikis provide organizations and groups a way to rapidly, securely collaborate different types of information that is easily created, edited and integrated with other resources. Many other solutions require more extensive training and expertise to implement ( Web and mobile applications, complex data analytics tool suites, databases etc ). Wikis provide a simple, easy way to

1. integrate those existing resources as a flexible, simple "front-door" for users to find and access a wide variety of information
2. add a variety of information and content types quickly by users without extensive training requirements
3. add new types of information with "low-code" frameworks for developers

Confluence makes it easy to see if it adds value for your needs

Wikis differ in features, technologies and costs. Some are open-source and free to download and use. Some are commercial with a variety of licensing models. Confluence offers a low-end free to see how it adds value to your teams. Unlike some "try and buy" products that are free for 90 days or a year, the Confluence free tier is permanently free so you can learn to use it on your schedule.

Most wikis offer a good variety of integration features for different information and content types right of out of the box.

In addition, good wikis offer both an active 3rd party marketplace with plugin applications to extend the wiki and a simplified development model to add your own application plugins. Confluence scores well here too.

The SWT Wiki Audit - Should your organization use wikis?

1. Does your organization need to securely integrate a variety of content across teams and groups internally or externally?
2. Is it easy to create and update new content quickly as needed at a low cost now?
3. Is it easy to maintain and manage an accurate history of the content changes over time?
4. Beyond chat and Web meeting video recordings, is there a good way to create and manage curated, searchable content easily for teams?
5. For major projects is there a solid way to integrate solution options, design documentation, decision history with feedback across all parties?
6. For on-boarding new members or updating member skills and knowledge, is there a productive way to do that effectively now?

Symptoms you may need a wiki

1. You have training sessions where developers show everyone how to regex your email or chat sessions to find answers to problems
2. Like Garth in "Wayne's World", our organization fears change
3. Your existing documentation for users and IT is often out of date
4. You failed compliance and change management audits
5. What your project teams define, developers build and users get trained on are out of synch
6. Projects and solution upgrades take longer than expected and it's not clear why

Some "wins" for wikis

Team Knowledge base

Problem - small staff with rapidly expanding technology needs

One IT infrastructure team I managed during a recession had a slow RIF ( Reduction In Force ) while we rapidly grew our servers and added new OS stacks to our backlog in addition to all the normal software maintenance, support, compliance audits and new projects. A challenge?

Solution - Knowledge base wiki

Yes. I created an "extended" wiki that used added plugins. All of our team work tickets and support tickets were reviewed against the team knowledge base. Initially there were few solutions there but we added and tagged our solutions going forward. It also offered quick dashboards with integrated SQL queries on our operating environments.

Impacts - With fewer staff expanded infrastructure technology capability 300% in 18 months

18 months later the team was smaller but our ability to cover a wide range of technologies productively had grown 300% - not a bad payoff ! Other teams also started using our knowledge base as well - a real win for the company.

Sharing content with local and remote users

Companies may not be setup to easily share content securely across teams. Internally, we were able to share content to authorized users quickly using the wiki.

Problem - on-demand content sharing

High volume data and document sharing applications are normally well engineered by organizations. Lower volume or on-demand sharing of content is a challenge

Solution - wikis setup easy on-demand content sharing with authorized users

Easy to setup a wiki space, add users and permissions for content upload and access

Impacts - where automated content sharing didn't exist, wikis provide another secure option

In minutes, users can setup secure content sharing

Voluntary Data quality, sharing supports the Information Maturity Life Cycle

Problem - too many spread sheets create too many versions of the truth

One company I worked at had solid "systems of record" and "trusted data stores" with many Web services and APIs, multiple databases to validate, ingest, integrate and distribute information centrally. Despite that, users created thousands of separate spread sheets. Every user had a different story to tell with different data at different ages. The problems getting useful answers were large. Rolling out an enterprise-wide data quality infrastructure initiatives isn't a quick project. It usually requires a culture change starting at the top as well.

Solution - voluntary data sharing with round-trip data stores

I offered a simple, self service data integration app in the wiki that authorized teams could access as a short-term alternative. Users could search the catalog of integrated data stores. If one didn't exist, they could submit a spread sheet that was validated and posted to a data store. When needed, users could edit the data directly or download the data again to a spread sheet and re-publish their data.

Impacts - natural data quality and efficiency improved informally

As users starting using this "round trip" process to search for data, download data if available and upload data if not available, the user teams gradually started reusing data, checking data quality and reducing data conflicts across teams. This "voluntary" data quality system paid off quickly. We improved data sharing, data services, data ownership and data qualtiy. Eventually, some of these data stores will "migrate" into formal "systems of record" with normal corporate data governance which is good. In the interim, voluntary data integration sources did improve data quality.

Does a wiki make sense for you?

You have many choices for wikis that fit different use cases. If you need help defining the value for your use cases and looking at candidate wiki solutions or getting started, let us know.