The case for a wiki

[Brian Gryth]

My agency is exploring the possibility of deploying a wiki to provide
a mechanism for constituents to contribute in the development of
content like FAQs, instructions, and a glossary for one of our filing
applications.

We feel that deploying a wiki will or hopefully will result in the
following:

1. Improve the content we provide to the public by ensuring that the
most useful and easily-understood information is provided;
2. Provide useful business intelligence that will improve public
relations and improve future development;
3. Build a sense of ownership of the information and the system the
information supports; and
4. Goodwill and trust for agency.

We are working through concerns about giving up control over our
content and about IT security. I’m reaching for any assistance from
the community, especially if you or your organization has deployed a
wiki internally or externally. We would like to know what questions
the decision makers asked? What concerns did people have? How did
you address IT security concerns? What would you do differently?
What worked? How has it improved the organization? Anything else
that you think would be of help to me and my colleagues.

[Christoph Berendes]

Contact @markelliott

--
Sent from my mobile device

[John Wonderlich]

Tons of useful things can grow out of a publicly deployed wiki.

I don't know what context you're operating within, but I find the biggest liability of most wiki projects is disuse and apathy, and perhaps spam.

Since it's so simple to set up a pbwiki, or a mediawiki installation (or some other option), the downside strikes me as rather limited. (although that depends on what kind of work or coordination you're hoping will take place on the wiki.)

Does anyone have a link to a resource that compares the features of different kinds of wiki platforms?

[Matt Cooperrider]

> Does anyone have a link to a resource that compares the features of
> different kinds of wiki platforms?

http://www.wikimatrix.org/