About a month ago, I was talking to a friend involved with wikis & collaboration at a major corporate. The thorny issue of "governance" came up. What do you need to manage with a wiki. Now part of this relates to the previous post around where wikis fit in with the plethora of other collaboration tools that most organisations have. The other issue is one of "reliance". So if a group (a team or a community) is using a wiki for their own purposes, that's OK. If other people come to rely on their content in a major way, does this then need to be managed more tightly. What do you do about "reliance"? Do you end up moving from the left to the right of the "after" diagram here. And if so, how do you make that decision?
Now if your organisation has decided that your wiki is your intranet, not really an issue. The thought that came to my mind was: viewer metrics are key here. If you have a team of 10 people working on something and only 10 people visit those pages, no worries. If 10,000 people visit those pages then that may indicate that this stuff is becoming important. And hey, it might even be worth investing in developing this content more.
What do you think?
Tuesday, August 28, 2007
Subscribe to:
Post Comments (Atom)
Posts
1 comments:
情趣用品, 情趣, 按摩棒, 跳蛋, 充氣娃娃, 情境坊歡愉用品, 情趣用品, 情人節禮物, 情惑用品性易購, A片, 視訊聊天室, 視訊, 視訊交友網, 免費視訊聊天, 情趣用品, 情趣用品, 情趣, 情趣用品, 台北情趣用品, 情人節禮物, 情趣用品, 情趣用品, 情趣, 情境坊歡愉用品, 情人視訊網, 成人用品, 免費A片, 情色文學, 免費A片, A片, 免費視訊聊天, 威而柔, 情惑用品性易購, 色情遊戲, 情惑用品性易購, 辣妹視訊, A片, 徵信社, 情趣用品, 情趣, 徵信, 徵信社, 外遇, 徵信, 徵信社, 外遇, 情趣用品, 情趣用品, 免費a片, a片, 免費av, 色情影片, 免費a片, a片, 免費av, 色情影片, 情色, 情色網, 色情網站, 色情, 成人網, 成人圖片, 成人影片, 18成人, 情趣風情, 中部人情趣網, 台北情趣用品, 情人節禮物, 成人情趣用品, 一夜情趣用品情趣, 情境坊歡愉用品, 情人視訊網, 美姬成人用品, 情人花束, 按摩棒, 情人歡愉用品, 情趣用品, 性感睡衣, 免費視訊聊天, 視訊交友網, 美姬圖影, 紅煙論壇, 交友聊天室, 海角七號, 寄情築園小遊戲, aio交友愛情館, 美女視訊, 色情A片, 視訊交友網, 情境坊歡愉用品, 情趣, 情趣, 貸款, 免費視訊聊天室, 美女視訊, 成人, 免費A片, 免費A片, a片, 情色貼圖, 成人網站, 情色電影, 情趣用品, AV女優, 情色交友, A片下載, 美女視訊, A片下載, 視訊交友網, 自慰套, 情色文學, 一葉情貼圖片區, 視訊交友網, 視訊, 情趣用品,
Post a Comment