What is a wiki? Well, if you don’t know, let’s look at what the most famous wiki, Wikipedia, has to say.
A wiki is a collection of web pages designed to enable anyone who accesses it to contribute or modify content, using a simplified markup language.[1][2] Wikis are often used to create collaborative websites and to power community websites. The collaborative encyclopedia, Wikipedia, is one of the best-known wikis.[2] Wikis are used in business to provide intranets and Knowledge Management systems. Ward Cunningham, developer of the first wiki software, WikiWikiWeb, originally described it as “the simplest online database that could possibly work”.[3]
“Wiki” (/wiːkiː/) is originally a Hawaiian word for “fast”. It has been suggested that “wiki” means “What I Know Is”.[citation needed] However, this is a backronym. “Wiki Wiki” is a reduplication of the same word.
Seem simple enough? If not, here is one more great visual explanation:
It’s part of the Plain English Series:
If they are not already, wikis are the wave of the future in many settings because of their collaborative ability. While most organiziations (i.e. businesses, churches, etc.) are still only using email, many others have embraced the power of the wiki and are really harnessing it’s power in creative ways.
As I’m still fairly new to wikis (I have 2 that I have created, 1 that I’m a part of, and I joined Wikipedia as a user–though still too nervous to create content yet, or correct).
But let me give you just one example of where I didn’t use it, and how I wish I did and why.
On Sunday June 8, my former church Bel Air Presbyterian Church, had its annual Student Sunday service which I coordinated between Student Ministry staff, Middle School, High School and College students. Between all of us there were approximately 20-25 people involved in the service from worship music, speaking, sound, lighting, skits and more.
And I did what I always did to coordinate an event…..I used email. Big mistake. Email is terrible at coordinating stuff. By the time June 8 rolled around my inbox was filled with emails that I could hardly keep track of…”Who was doing what?” “Why?” If I had used a wiki and given every person access to that wiki, or at least specific supervisors in each department, the coordination would have been smooth, and there wouldln’t have been the need for me to continually follow up on tasks and micromanage at some degree.
I think it will take a long time before many people stop using emails for these things and use a wiki. Certainly I’m not saying to never use email, but when it comes to coordinating activities, ministries, tasks, etc. there is not better tool than a wiki.
I wish that when I was the college director of The Quest I had known more about wikis, and I would have gotten rid of those mass email lists that hardly anyone reads or responds to.
Some Reasons for Using Wikis:
Some of these have crossover value and are repetitive, but here is what I came up with.
- Promotes, encourages team work/participation.
- Decentralizes the hierarchy..now everyone is participating.
- Harnesses more creativity.
- Eliminates/reduces micromanaging by supervisors on tasks.
- Allows everyone to see what is happening/being accomplished.
- Levels the playing field (everyone’s work is valued).
- Eliminates/reduces the need for email.
- Encourages a team as everyone can view the achieving of a goal/job being done.
- Allows for multiple voices, therefore the best ideas rise to the top.
- Is a speedier tool than email chains going back and forth. Quick correction, agreement, completion, etc.
This is what I could come up with. How about you? What can you add to the list?
I’ve been playing around with Wet Paint, Wikispaces, and I’m also registered with Wikipedia to edit, etc., but I don’t have a handle on that site yet.
Do you use a wiki? Which one? Do you like it?
How have you used a wiki in your ministry, or line of work, and was it effective? How?
A must read book on this topic is Wikinomics: How Mass Collaboration Changes Everything by Don Tapscott and Anthony D. Williams. Awesome, awesome book.
Formulating an Online Strategy for College Ministry
- Part 1–Simplicity, Flexibility, Cost and Speed.
- Part 2–The Purpose of Your Website
- Part 3–Why You Should Be Blogging
- Part 4–Using Facebook Effectively
- Part 5–How Twitter Can Catalyze Your Ministry
- Part 6–Using Social Network Platforms as Your Central Hub
- Part 7–Flickr, YouTube and Other Forms of Sharing and Streaming
- Part 8–Ministry Collaboration Using Wikis
- Part 9–Opening Up Your Ministry’s API
{ 3 comments… read them below or add one }
I love wikis. Love the idea, love how they create a new way of communication and transferring information. Here is the problem. I’ll be specific with my situation. As a band director I need to get information to my band. Right now we use email because that is by far the most consistent way to reach the players. Most of them use and understand email. So the problem with a wiki is that only early adopters are going to use and most of my band is not early adopters.
So my question is: how do you get people who aren’t internet compliant to use wikis?
I love wikis. Love the idea, love how they create a new way of communication and transferring information. Here is the problem. I’ll be specific with my situation. As a band director I need to get information to my band. Right now we use email because that is by far the most consistent way to reach the players. Most of them use and understand email. So the problem with a wiki is that only early adopters are going to use and most of my band is not early adopters.
So my question is: how do you get people who aren’t internet compliant to use wikis?
Tyler,
Great question.
My problem is not with email, but what email is used for. I think that’s a great use for email (i.e. sending it to the band on a consistent basis). The problem becomes when it’s used to coordinate lots of activities and decisions.
It would be interesting for you to experiment with a wiki for the band and see how it goes.
There will always be early adopters and they are easy to convince…but many are pretty slow for change, so that’s a hard job…educating people, getting them excited about change..showing them how it will improve their communication.
I think you have to do a test case; let people see it for themselves, and get them to slowly buy into it.
rhett
{ 3 trackbacks }