Yet Another Bookmarks Service



[https://xwiki.com/en/offerings/custom-solutions/knowledge-base?utm_source=GoogleAds&utm_medium=cpc&utm_campaign=cs&utm_term=campaign&utm_content=knowledge-base&gclid=Cj0KCQjw5auGBhDEARIsAFyNm9FDna3t-M8isbUrnmdfyqIfEYZKuWdYmMMQ_o781kHSrMsPqau8cmMaAnJbEALw_] - - public:Orgasmfairy8
apps, bookmarks bar, knowledge - 3 | id:709134 -

[http://blogs.gartner.com/darin-stewart/2011/03/17/a-wiki-in-the-call-center-its-really-okay/] - - public:time
architecture, knowledge, support, wiki - 4 | id:2693 -

The same principle holds true for rapidly evolving, volatile content stores like an internal knowledgebase. Errors will creep in, but they will be detected and corrected much more quickly than if they must be processed through an under resourced editorial workflow. At the same time, the barriers to adding fresh, timely and relevant content are dramatically reduced. Incentives for contributing, commenting and rating content can further enhance quality. Such an approach clearly is not appropriate in all situations, but in a closed user environment, like a call center or an IT department, it really does work and has been successfully adopted by many organizations. The content won’t be perfect, but it will probably be better than what you have now. Never let “perfect” become the enemy of “good enough”.

Follow Tags