A wiki is definitely the way to go. Processes change, sometimes frequently, and in a fast-paced environment like a help desk a tool that allows quick, easy access and management of that type of content is extremely important to allow people to do their jobs effectively.
One of the greatest benefits I've found is the heiarchical sturcture of many wikis, allowing employees to find the correct content from a number of different customer angles.
拥有一定的结构是必要的，在任何 Wiki 中开发一些对一般编辑大众有意义的东西，并且从阅读到编辑的门槛很低。 您还可能需要一个迁移策略，将数百个小笔记转换为更可读和可搜索的内容。
I would recommend a wiki wiht a "Wiki Gardener" role- someone who cleans up the duplicate entries and sorts.
Wiki technology with a Rich Text Editor option would useful if your Support Desk are not totally technical.
Having some structure is imperative, developing something in any Wiki that makes sense to the general editing populace, and has a low threshold to get from reading to editing. You will also possibly need a migration strategy for taking hundereds of little notes into something more readable and searchable.
发布评论
评论（3）
你可以说得更详细点吗？
这可能属于“政策和程序”管理软件。 这里有一些：
http://www.softscout.com/software/Human- Resources/Policy-and-Procedures.html
我想找到一个更像 wiki 或更容易集成到网站中的网站，作为更通用的公司知识库。
Can you be more specific?
This may fall under "policies and procedures" management software. Here are some:
http://www.softscout.com/software/Human-Resources/Policy-and-Procedures.html
I'd like to find one that's more wiki-like or easier to integrate into a a website serving as a more general company knowlege base.
维基百科绝对是最佳选择。 流程有时会频繁变化，在像服务台这样的快节奏环境中，允许快速、轻松访问和管理此类内容的工具对于让人们有效地完成工作极其重要。
我发现的最大好处之一是许多 wiki 的分层结构，允许员工从许多不同的客户角度找到正确的内容。
A wiki is definitely the way to go. Processes change, sometimes frequently, and in a fast-paced environment like a help desk a tool that allows quick, easy access and management of that type of content is extremely important to allow people to do their jobs effectively.
One of the greatest benefits I've found is the heiarchical sturcture of many wikis, allowing employees to find the correct content from a number of different customer angles.
我会推荐一个具有“维基园丁”角色的维基 - 清理重复条目和排序的人。
如果您的支持台不完全是技术性的，带有富文本编辑器选项的 Wiki 技术会很有用。
拥有一定的结构是必要的，在任何 Wiki 中开发一些对一般编辑大众有意义的东西，并且从阅读到编辑的门槛很低。 您还可能需要一个迁移策略，将数百个小笔记转换为更可读和可搜索的内容。
I would recommend a wiki wiht a "Wiki Gardener" role- someone who cleans up the duplicate entries and sorts.
Wiki technology with a Rich Text Editor option would useful if your Support Desk are not totally technical.
Having some structure is imperative, developing something in any Wiki that makes sense to the general editing populace, and has a low threshold to get from reading to editing. You will also possibly need a migration strategy for taking hundereds of little notes into something more readable and searchable.