Difference between revisions of "Wiki"
| Line 4: | Line 4: | ||
==Purpose & Benefits== | ==Purpose & Benefits== | ||
| + | A Wiki allows everyone who should have access to the information to have access. It reduces confusion caused by e-mailing documents and facilitates sharing information. A Wiki also allows for the timely creation and updating of information and can be connected to a workflow so that any necessary approvals and checks are obtained. | ||
==Description== | ==Description== | ||
| + | Provides online creation of knowledge assets and eliminates the need for other authoring tools, such as Microsoft Word, if desired. Many organizations use a wiki for some or all of their documented knowledge base as it is more easily updated and shared and can eliminate confusion caused by emailing documents. | ||
| + | |||
| + | A Wiki not only provides open, online creation of knowledge assets but also provides the ability to upload attachments, control page access, WYSIWYG (what you see is what you get) editing and versioning. | ||
| + | |||
| + | A Wiki can also be used to facilitate group work through the use of virtual workspaces that allow employees and external partners to share/create information, best practices, e-mails, calendars and other knowledge assets. | ||
==Variations== | ==Variations== | ||
==Implementation Guide== | ==Implementation Guide== | ||
| + | Similar to other technology implementations. | ||
| + | |||
| + | 1. Gather business requirements and align projects with specific business goals. | ||
| + | |||
| + | 2. Implementing a Wiki or any technology is a business decision not an IT decision. | ||
| + | |||
| + | 3. Use Agile and Iterative Approach to Implementation. | ||
| + | |||
| + | 4. | ||
| + | |||
| + | |||
==Success Factors== | ==Success Factors== | ||
==Common Pitfalls== | ==Common Pitfalls== | ||
| − | + | ||
[[Category:Content management]] | [[Category:Content management]] | ||
Revision as of 12:04, 7 March 2016
Contents
Definition
An application for collaborative content developmentwhich allows anyone to add, delete, or revise contentby using a web browser
Purpose & Benefits
A Wiki allows everyone who should have access to the information to have access. It reduces confusion caused by e-mailing documents and facilitates sharing information. A Wiki also allows for the timely creation and updating of information and can be connected to a workflow so that any necessary approvals and checks are obtained.
Description
Provides online creation of knowledge assets and eliminates the need for other authoring tools, such as Microsoft Word, if desired. Many organizations use a wiki for some or all of their documented knowledge base as it is more easily updated and shared and can eliminate confusion caused by emailing documents.
A Wiki not only provides open, online creation of knowledge assets but also provides the ability to upload attachments, control page access, WYSIWYG (what you see is what you get) editing and versioning.
A Wiki can also be used to facilitate group work through the use of virtual workspaces that allow employees and external partners to share/create information, best practices, e-mails, calendars and other knowledge assets.
Variations
Implementation Guide
Similar to other technology implementations.
1. Gather business requirements and align projects with specific business goals.
2. Implementing a Wiki or any technology is a business decision not an IT decision.
3. Use Agile and Iterative Approach to Implementation.
4.
