Difference between revisions of "Wiki"
(→Implementation Guide) |
(→Common pitfalls) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
The processes and activities that can be implemented using a wiki to support them are varied, but they all have in common the ability to create and share information in a browser-based environment. | The processes and activities that can be implemented using a wiki to support them are varied, but they all have in common the ability to create and share information in a browser-based environment. | ||
| − | ==Implementation | + | ==Implementation guide== |
| − | + | ||
| − | [[ | + | See the [[http://wiki-nkm.iaea.org/wiki/index.php/Information_technology#Implementation_guide Implementation guide]] in the [[Information technology]] article. |
| − | ==Success | + | ==Success factors== |
Similar to any IT implementation project, it is critical to involve the users. Understand how they work: their processes, how they think about and organize the documented knowledge that they use, who they work with, when they work. | Similar to any IT implementation project, it is critical to involve the users. Understand how they work: their processes, how they think about and organize the documented knowledge that they use, who they work with, when they work. | ||
Align the wiki initiative with the KM strategy, which is aligned with the over-all organizational strategy. | Align the wiki initiative with the KM strategy, which is aligned with the over-all organizational strategy. | ||
| − | ==Common | + | See the [[http://wiki-nkm.iaea.org/wiki/index.php/Information_technology#Success_factors Success factors]] in the [[Information technology]] article. |
| + | |||
| + | ==Common pitfalls== | ||
Having/obtaining adequate resources: human (people trained and experienced in wiki technology), financial (to obtain the hardware and software necessary), and time (to plan, implement, and maintain). This includes establishing the necessary processes and governance for the wiki. | Having/obtaining adequate resources: human (people trained and experienced in wiki technology), financial (to obtain the hardware and software necessary), and time (to plan, implement, and maintain). This includes establishing the necessary processes and governance for the wiki. | ||
Other pitfalls are those common to any technology implementation: ensure that it aligns with the organization's goals, objectives, and processes; involve users in the definition and creation of the data model and system; include change management activities in the roll-out and implementation. | Other pitfalls are those common to any technology implementation: ensure that it aligns with the organization's goals, objectives, and processes; involve users in the definition and creation of the data model and system; include change management activities in the roll-out and implementation. | ||
| − | ==Related | + | See the [[http://wiki-nkm.iaea.org/wiki/index.php/Information_technology#Common_pitfalls Common pitfalls]] in the [[Information technology]] article. |
| + | |||
| + | ==Related articles== | ||
| + | [[Information technology]] | ||
| + | |||
| + | [[Knowledge management strategy]] | ||
[[Category:Content management]] | [[Category:Content management]] | ||
Latest revision as of 14:36, 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
The processes and activities that can be implemented using a wiki to support them are varied, but they all have in common the ability to create and share information in a browser-based environment.
Implementation guide
See the [Implementation guide] in the Information technology article.
Success factors
Similar to any IT implementation project, it is critical to involve the users. Understand how they work: their processes, how they think about and organize the documented knowledge that they use, who they work with, when they work.
Align the wiki initiative with the KM strategy, which is aligned with the over-all organizational strategy.
See the [Success factors] in the Information technology article.
Common pitfalls
Having/obtaining adequate resources: human (people trained and experienced in wiki technology), financial (to obtain the hardware and software necessary), and time (to plan, implement, and maintain). This includes establishing the necessary processes and governance for the wiki.
Other pitfalls are those common to any technology implementation: ensure that it aligns with the organization's goals, objectives, and processes; involve users in the definition and creation of the data model and system; include change management activities in the roll-out and implementation.
See the [Common pitfalls] in the Information technology article.
