{"id":328,"date":"2008-08-18T09:21:39","date_gmt":"2008-08-18T16:21:39","guid":{"rendered":"http:\/\/www.spreadingscience.com\/?p=328"},"modified":"2008-08-18T09:40:43","modified_gmt":"2008-08-18T16:40:43","slug":"wikis-tacit-becomes-explicit","status":"publish","type":"post","link":"https:\/\/www.spreadingscience.com\/2008\/08\/18\/wikis-tacit-becomes-explicit\/","title":{"rendered":"Wikis – Tacit becomes explicit"},"content":{"rendered":"

\" by <\/em><\/span>Z0rk<\/a><\/em><\/strong><\/span>
\n<\/em>
The tacitness of wikis<\/a>:
\n[Via
Library clips<\/a>]<\/p>\n

Stewart Mader from Grow Your Wiki<\/a> is guest posting<\/a> on Wikinomics<\/a> and his lastest post is on the effectiveness of wikis enabling tacit sharing.<\/p>\n

Documents that are open and dynamic allow people to evolve the documents by direct editing or leaving comments…ie. people are sharing their experience and what they know can add to the richness of the document.<\/p>\n

Right away I thought of the How-To Guides I’m writing for our Communities of Practice (CoP) at work.\t<\/p><\/blockquote>\n

Wikis are great for communal documents, such as How-to guides or protocols. As people gain expertise, they can provide comments, hints or questions that can make the document richer. <\/em><\/p>\n

This way they can help me evolve the document, even though it’s finished. Well, that’s the idea, it’s never finished…I may miss a feature, and I can’t experience every context, so there’s stuff that happens when people use Communities that I may not know up front. eg. a new way to use blogs, a workaround (exception to procedure) page for Document Control as each client has different needs.<\/p>\n

They may leave a comment about a feature of our CoPs where they have a workaround, or a use case.
\neg. someone might say everyone in our team has a status blog, so when we go to a meeting we already know what everyone has been up to, our meetings are more about action.
\nAnother person visiting the guide may see this and use this idea.
\nA simple comment box on a wiki has enabled the sharing and receiving of know-how by two people that don’t even know each other, plus this is perpetual as another person may come along and get value or an idea from reading the same comment. In fact another person may leave a comment back and say that they found it more manageable having one group blog for status. The original person my see this and comment back saying, that is a great idea, I didn’t know that was possible. Oops, that’s because I may have not put that fact in the guide, lucky that comments allow for others to help where the guide fails.
\nAnd as Stewart mentions I can go and refine the guide and leave a comment saying thanks.<\/p><\/blockquote>\n

Also, all of this interplay, this dialog, is also explicit, it is all time-stamped and it can be used to analyze how useful that particular document is. By making it explicit, a lot of metrics can be applied that will finally be able to measure what formally was invisible. This will not only be useful for the organization but also for the individual, say during performance reviews. Before, no one knew how important a protocol might be, especially if it was just stuffed into a binder in the lab. Now, anyone could look and see just how often that protocol was examined, and by whom.<\/em>.<\/p>\n

In the end we have this explicit type deliverable that has to be formal and succinct as it has to cater to many audiences, and can’t be too explanatory (long), and try to cover every context possible, as people won’t bother reading it. But on top of this we have a layer of collective know-how and feedback via the comments which inturn we feed back into the document (via edit) some tacit know-how.<\/p>\n

The point is having perpetually live documents (editing and comments) harnesses the collective wisdom, where people can share their know-how, and benefit the user experience as a whole. It’s a win win situation.<\/p><\/blockquote>\n

And, if a different document needs to be created for a different audience, the community will be there to help.
\n<\/em>
\n<\/p>\n

Technorati Tags: Open Access<\/a>, Social media<\/a>, Web 2.0<\/a><\/p>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

by Z0rk The tacitness of wikis: [Via Library clips] Stewart Mader from Grow Your Wiki is guest posting on Wikinomics and his lastest post is on the effectiveness of wikis enabling tacit sharing. Documents that are open and dynamic allow people to evolve the documents by direct editing or leaving comments…ie. people are sharing their … Continue reading Wikis – Tacit becomes explicit<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[4],"tags":[],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pe2yp-5i","jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":73,"url":"https:\/\/www.spreadingscience.com\/2008\/03\/24\/why-km-10-failed-in-a-nutshell\/","url_meta":{"origin":328,"position":0},"title":"Why km 1.0 failed in a nutshell","date":"March 24, 2008","format":false,"excerpt":"by degreezero2000 Why km 1.0 failed in a nutshell: [Via Library clips] CIO magazine has an interview article on enterprise wikis with Ross Mayfield from Socialtext, but don\u2019t think you will just come away with wiki knowledge, this article has some of the best quotes on why KM 1.0 has\u2026","rel":"","context":"In "Web 2.0"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":151,"url":"https:\/\/www.spreadingscience.com\/2008\/04\/30\/information-on-wikis\/","url_meta":{"origin":328,"position":1},"title":"information on Wikis","date":"April 30, 2008","format":false,"excerpt":"by cogdogblog Business Whitepapers: [Via pbwiki.] How Wikis Enable Enterprise Collaboration The Five Keys to Enterprise-Grade Security and Infrastructure for On-Demand Wikis Seven Wiki Essentials: The Must-Have Elements of Every Successful Wiki Initiative [More] Some very nice whitepapers discussing not only pbwiki and hosted systems but also why wikis are\u2026","rel":"","context":"In "Web 2.0"","img":{"alt_text":"","src":"https:\/\/i2.wp.com\/www.spreadingscience.com\/wp-content\/uploads\/2008\/04\/wiki-wiki.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":420,"url":"https:\/\/www.spreadingscience.com\/2008\/10\/27\/discussing-web-20\/","url_meta":{"origin":328,"position":2},"title":"Discussing Web 2.0","date":"October 27, 2008","format":false,"excerpt":"by notsogoodphotography Are scientists missing the boat?;.: [Via Bench Marks] ....or has that boat already sailed? I've read many a blog posting or magazine article declaring that scientists are behind the curve, and we biologists have been slow to pick up the new online tools that are available. I've repeatedly\u2026","rel":"","context":"In "Science"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":621,"url":"https:\/\/www.spreadingscience.com\/2010\/01\/21\/why-knowledge-management-failed\/","url_meta":{"origin":328,"position":3},"title":"Why knowledge management failed","date":"January 21, 2010","format":false,"excerpt":"by Parksy1964 A Better Way to Manage Knowledge: [Via HarvardBusiness.org] We give a lot of talks and presentations about the ways and places companies and their employees learn the fastest. We call these learning environments creation spaces \u2014 places where individuals and teams interact and collaborate within a broader learning\u2026","rel":"","context":"In "Knowledge Creation"","img":{"alt_text":"","src":"https:\/\/i2.wp.com\/www.spreadingscience.com\/wp-content\/uploads\/2010\/01\/knowledge1.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":299,"url":"https:\/\/www.spreadingscience.com\/2008\/07\/26\/liking-knol-somewhat\/","url_meta":{"origin":328,"position":4},"title":"Liking knol somewhat","date":"July 26, 2008","format":false,"excerpt":"by eye of einstein So, after writing about my knol dislikes, let me discuss some of my positive thoughts about knol. Knol is the newest feature from Google. As I wrote earlier, I do not like some of the non-Web 2.0 features seen in some of the early essays (i.e.\u2026","rel":"","context":"In "Science"","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.spreadingscience.com\/wp-content\/uploads\/2008\/07\/drops.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":259,"url":"https:\/\/www.spreadingscience.com\/2008\/06\/30\/ross-is-right\/","url_meta":{"origin":328,"position":5},"title":"Ross is right","date":"June 30, 2008","format":false,"excerpt":"by jeffpearce Socialtext is Growing Up: [Via Enterprise 2.0 Blog] I had a great chat with Socialtext\u2019s co-founder Ross Mayfield this week, and he highlighted a few interesting facts about wiki implementations. Notably, he says that wikis fail in the enterprise if they are imposed by IT, rather than by\u2026","rel":"","context":"In "Web 2.0"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/posts\/328"}],"collection":[{"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/comments?post=328"}],"version-history":[{"count":0,"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/posts\/328\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/media?parent=328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/categories?post=328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.spreadingscience.com\/wp-json\/wp\/v2\/tags?post=328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}