M
Pancho
thanks for your candour - I too find there are some who are enthused - but many who feel they should only publish to a wiki if it their content is perfect without errors
I ran a wiki session at our Sharepoint Interest group last week- see attached document - please don't get hung up on my comments about wikis & controlled documents - basically I am distinguishing
wiki's purpose designed for standard procedures, manuals etc and others not in this category
cheers
@KerrieAnne & @SteelyQueen on Twitter
thanks for your candour - I too find there are some who are enthused - but many who feel they should only publish to a wiki if it their content is perfect without errors
I ran a wiki session at our Sharepoint Interest group last week- see attached document - please don't get hung up on my comments about wikis & controlled documents - basically I am distinguishing
cheers
@KerrieAnne & @SteelyQueen on Twitter
Hi, Shane,
Yes, that was a bit of a hurdle for us too. We overcame it with the following:
1)
Got a small group enthused about the wiki first. Our first wiki application wasn't the management system, but project to-do lists. This involved less users and they were a bit more of early-adopters.
2)
Training. We had a couple of sessions of hands-on training for every employee.
3)
Network effects. Once the wiki got past a critical mass, its benefits became so strong that (almost) everyone wants to use it.
Despite the above, there will always be some folks that do not contribute all they could or should. Any new tool provides an excellent excuse for that. Just yesterday I read something quite appropriate: "Wikis show not only how much internal experts know, but how eager they are to share their knowledge." [source].
Our wiki engine supports both WYSIWIG and wiki markup, and our users' preferences are divided about equally.
Yes, that was a bit of a hurdle for us too. We overcame it with the following:
1)
Got a small group enthused about the wiki first. Our first wiki application wasn't the management system, but project to-do lists. This involved less users and they were a bit more of early-adopters.
2)
Training. We had a couple of sessions of hands-on training for every employee.
3)
Network effects. Once the wiki got past a critical mass, its benefits became so strong that (almost) everyone wants to use it.
Despite the above, there will always be some folks that do not contribute all they could or should. Any new tool provides an excellent excuse for that. Just yesterday I read something quite appropriate: "Wikis show not only how much internal experts know, but how eager they are to share their knowledge." [source].
Our wiki engine supports both WYSIWIG and wiki markup, and our users' preferences are divided about equally.
Attachments
-
302.7 KB Views: 773
