Cultural Norms for Internal Wikis
Background
I have built some highly successful department-level intranet sites. By focusing on knowledge management, training, employee transitions, vacation/illness coverage. . . these sites quickly proved their worth and attracted audiences.
Centralizing well chosen content in a wiki proved to be an addictive formula for those departments. The charter of the department (Marketing, Planning, IT, etc) made no impact to the success of the wiki. The critical success factor was how hard the web site manager drove cultural, communication, design, and process norms.
Cultural Norms
What attitudes and approaches foster useful intranet content?
I have built some highly successful department-level intranet sites. By focusing on knowledge management, training, employee transitions, vacation/illness coverage. . . these sites quickly proved their worth and attracted audiences.
Centralizing well chosen content in a wiki proved to be an addictive formula for those departments. The charter of the department (Marketing, Planning, IT, etc) made no impact to the success of the wiki. The critical success factor was how hard the web site manager drove cultural, communication, design, and process norms.
Cultural Norms
What attitudes and approaches foster useful intranet content?
| Norm | Description | Trade Off |
| 1. No barriers to user contribution | Most users read, but do not change or create content. Contribution is good. Therefore, any barriers to contribution (training, access, cultural) should be removed. |
Small risk that users will damage or delete important content |
| 2. Low bar to experiment, high bar to retain | The department's wiki is an ideal tool to test new content and processes. | Clutter and failed content experiments eventually need to be deleted. |
| 3. Closely held, mission critical methods make the best content | Insight, wisdom, and knowledge that took years to acquire is given to your peers via a wiki without a second thought. | This norm requires management to create a safe environment and incentives for sharing. |
| 4. Diminishing returns from polishing | Shifting from email to a wiki provides a return on investment. A wiki has inherent advantages over email. Centralization allows flexibility, control, find-ability, and reduction of email messages. |
Every corporate wiki potentially generates a return on investment which decreases the more you gold-plate it. |
Comments
Post a Comment