Mar 19 2008
I am intrigued by this bit of advice from Michael Idinopulos writing about Creating a Participatory Knowledgebase: 3 Best Practices
Lead with what you want, not what you have. Many groups, especially research groups, tend to use the wiki as a dumping ground for research they’ve already done. This research typically takes the form of reports which were written for a specific audience to answer a specific question at a specific moment in time. So the value of the reports themselves isn’t so great. What is valuable, however, is the insights embedded in those reports. That’s what contributors should be encouraged to post to the wiki. Put differently, a page called “Trends in Retail Channel Marketing” is a better wiki page than “2006 Analysis of our Company’s Channel Marketing Spend”. (Of course, the report might be useful as backup–so include it as a link from the main page on trends).
Since I’ve recently been up to my eyeballs with a wiki on knowledge sharing, this caught my eye. How do we use language to engage others? What makes something “yet another info dump” and another thing an attractor towards ongoing knowledge sharing?
The KS wiki is mostly about sharing information about knowledge sharing tools and methods. This information is available all over the web, but scattered. What it also lacks is insights of what to use when and a place for stories of use. Right now, we are really working hard to try and find ways to express the invitation for sharing use stories, but I had totally forgotten about ways to ask for what you want? Now I’m thinking maybe a page that is a springboard to expressing need.