Making the Wiki Work


“If you build it, they will come.” We’ve all heard those words way too many times, and yet I’ll bet if you look around at your online haunts you can find more than a few ghost towns: places that some web worker built where nobody bothered to come. Part of the problem is that we tend to be the virtual vanguard: we assume that everyone else on the team will “get” the latest bit of social software as fast as we do, and jump wholeheartedly on board.

In real life, things are different, as anyone who has ever tried to set up a corporate wiki has probably discovered. Faced with the possibility of building up a vibrant company-wide user-edited online resource, most people end up scratching their heads and retreating back to more familiar modes of communication. Now Atlassian (makers of commercial wiki software Confluence) have done something about this particular problem with their new site Wikipatterns.

As you can probably guess from the name, Wikipatterns is itself a wiki. In this case, it’s about the patterns and practices that a wiki champion can use within an organization to get people started using this resource (as well as some of the antipatterns that are known to discourage wiki use – like the presence of WikiTrolls or the problem of being Overrun by Camels). On the plus side, you can read about strategies for engaging people from simple (leaving a few typos for them to fix, so they discover how easy it is to edit a wiki page) to more complex (building pages for poker tournament results to demonstrate the low cost of adding a page).

There’s a lot of knowledge distilled in this site. If you’re trying to figure out how to get people on board with a wiki – or some other distributed networking software – it’s worth your while to poke around and learn from people who’ve been down this road before you.



As you be able to belike surmisal from the name, Wikipatterns is itself a wiki. In this case, it’s most the patterns and practices that a wiki endorse be able to ingest within an methodicalness to achieve folks started using this inventiveness (as well as several of the antipatterns that are famous to advise wiki best exchange rates ingest – alike the proximity of WikiTrolls or the difficulty of existence Overrun by Camels). On the nonnegative side, you be able to feature most strategies for attractive folks from ultimate (leaving a some typos for them to fix, so they conceive how cushy it is to modify a wiki page) to more Byzantine (building pages for cards competition results to shew the baritone outlay of adding a page).



I can’t be bothered with anything these days, but shrug. I just don’t have anything to say recently.




I want to all of you know, World is mine, and yoursite good


Osama A.

Ouch. This is a REALLY bad marketing move from Confluence. Think about this:

1- What is the point of evangelizing the open-ness of wikis, if you then force people to adopt very complex technical terms and patterns about how people work? Why force me to think of my team as either trolls or fairies, and how does that help me make a decision towards whether wiki will benefit my workgroup or business? Why not let me come up with my own terms (which is in line with the philosophy behind wikis in the first place)?

2- If you look at as a product, Confluence is making a classic mistake of focusing entirely on FEATUREs rather than actual benefits. It would have been better to use the guide to inspire everyone who is curious about wikis, rather than give them a headache and learning curve.

More on my blog…

Stewart Mader

Thanks very much for linking to! I appreciate that you’re helping to spread the word!
Stewart Mader
Wiki Evangelist, Atlassian

Amie Gillingham

Nice resource! We have been debating whether or not to add wiki structure to our business since many of our customers range from computer illiterate technophobes to technically adept but only within their comfort zone. We don’t want to bypass the technology simply because some current users might fear it, but we also want to find a way to ease them into the 21st century. I’ll definitely pass this along to our tech team!

Comments are closed.