Wiki - Best Practices

Objective

Share content optimization techniques for managing wiki content

Context

Organizations with intranet usability issues dampen productivity by under-investing
  • in nomenclature alignment (definition of acronyms, internal jargon terms, contentious terms and aliases)
  • content curation and re-use

Anti-pattern consequences

  • Long ramps:  New or transfer employees have trouble learning by using intranet search tools.
  • People don't scale:  Every new or recently transferred worker will have FAQs – but subject matter experts are often too busy to respond.
  • Impaired responsiveness:  Decision processes are stalled when domain knowledge is hard to find.

Guiding principles to address the anti-pattern

  • Optimize intranet search results
  • Body of knowledge is
    • large enough to be useful
    • small enough to be maintained
  • Everyone pitches in

Recommendations for wiki optimization


NormDescriptionTrade off, caveat, or assumption
1No barriers to contributionMost 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
2Low bar to experiment, high bar to retainThe department's wiki is an ideal tool to test new content and processes.
This implies that authors delete/update content almost as frequently as they create new pages. The goal is to minimize the net increase in wiki content.
Outdated clutter needs to be deleted
3Publish closely held, mission critical methods  Insight, wisdom, and knowledge that took years to acquire is given to your peers via a wiki without a second thought.
The more valuable the content, the longer it will be relevant.
This norm requires management to create a safe environment and incentives for sharing.
4Limit publication of meeting minutes because they make the worst contentClutter is the enemy.
  • Meeting minutes are commonly published, but they have a short-value-window as wiki content.
  • Centralized decision logs are better than myriad meeting minutes pages.
If you insist on publishing meeting minutes, please:
  • extract the essential information to a more concise vehicle
  • delete them after they are no longer needed
5Be mindful of diminishing returns from polishingThe goal is to have a concise encyclopedia, not a polished marketing site. Curation investment levels:
  • Insufficient: Allowing short-value-window wiki content to increase the size of the wiki
  • Sufficient: Try any promising content experiment, but be sure to adjust/delete the failed failed ones.
  • Overkill: Marketing-level quality, polishing department pages, major sub-site launches within the wiki
Every organization's wiki potentially generates a return on investment which decreases the more you gold-plate it.

Reflect and act

  1. Consider how valuable reference information about custom apps, data, and processes and results would be for a new employee.
  2. Search for that valuable content using your intranet's search features.  Assess if this experience is an acceptable way to ramp new employees.
  3. Some secrecy is necessary.  However, it's easy to get carried away.  
    1. Remind your colleagues about the high costs of unnecessary secrecy.
    2. Reduce security settings on reference information if possible.  
  4. It is likely that every initiative needs a central body of knowledge for reference information -- including jargon, definitions, and major decisions.
  5. If anyone feels insecure about the political risks of content sharing, offer them a path to improve stakeholder management skills.  The goal is to as transparent as possible about capabilities, practices, and learnings.

Comments