But, for the sake of argument, let’s assume that what brought you here is a genuine interest in sabotage.  If you want some methods to make the knowledge base project go belly-up, rest-assured I’ve got a few tricks up my sleeve for you:

Start from a blank slate.

Enough said.  You fill in the blanks here:

…
…
…
…

Not that easy, is it?  Now build something and expect people to know what the hell they’re supposed to do without setting expectations or providing a few examples.

Restrict authorship.

Draw a Venn diagram: One circle will contain all the names of your subject matter experts. One circle will contain all the people with technical expertise. Now look at the overlapping names and pick only people from your department. Meet with this elite team (affectionately called The Mighty Triumvirate) and set a schedule of alternating Wednesdays and Fridays during each semester when content will be published.

Assume that Triumvirate’s blessed canon is the ultimate authority on campus because you have locked down the content, while in the mean time all the people you rejected have–in true higher ed fashion–circumvented you and published a million other versions of the content via Facebook pages, blog posts, slideshare presentations, departmental and personal Websites, etc. Eventually there is mass chaos, and no best source for information (least of all the Triumvirate’s knowledge base because no one has updated it since 1996).

Be the knowledge base.

Keep answering every question that someone asks you.  It’s easier for you to answer it than to show them how to use the knowledge base.  If the answer does require the use of the knowledge base, look it up for them.  Don’t prepare them for a time when you might be out of the office or at a meeting.

Related posts:

1. Teaching Them to Fish: Strategy for Implementing a Knowledge Base
2. University Intranets: Let’s Secure Our Internal Knowledge Base from Ourselves #Fail
3. Kings of All Cosmos: How to Get Internal Knowledge Out There

Here’s a strategy I’ve used when implementing a new knowledge base in a scenario where users rely on IT support people and helpdesk systems:

1. When a new helpdesk request is submitted, the IT support person uses the knowledge base to determine if an answer has already been documented.
2. If the answer has been documented, the IT support person sends the link to the knowledge base answer along with an explanation of how to find it by searching the knowledge base. (Ex: “Hi Fred, I found these instructions by searching with “iPhone” and “IMAP” in our knowledge base: http://www.knowledgebaseurlhere.edu…”)
3. If the answer there is no documented answer in the knowledge base, the IT support person could either take the time to document it first and then follow the steps for #2, or he or she could reply to the ticket but save a copy of the answer for the knowledge base later.

There are several reasons for using this strategy:

• It develops and maintains and the knowledge base documentation. Each time helpdesk issues arise, documentation is either being created or reviewed.  Your efforts are placed proportionally to the need of your customer base.
• It ensures a consistent party-line answer. Your knowledge base becomes the canon.  All helpdesk people refer to it for answers, so there is less of a chance that users become confused or frustrated by answers that change based on which person they ask.
• It saves support staff the redundant effort of providing an explanation if one is already out there. If one user has an issue, chances are another user may have it later.  Having that information saved for future–even if one or two steps need to be updated–will save you effort later.
• It’s a subtle way to show users how to search for answers within the knowledge base. You are not only encouraging support people to use and maintain a knowledge base, but you are having support people teach the users how to use the knowledge base.  Instead of just feeding them the answers, you are teaching them how to fish for them!

For more information, check out Writing Documentation & Training Materials.

Photo Credit: Fishing Harbour in Setubal by fotografar

Related posts:

1. Kings of All Cosmos: How to Get Internal Knowledge Out There
2. 3 Ways to Build Knowledge Base #FAIL
3. University Intranets: Let’s Secure Our Internal Knowledge Base from Ourselves #Fail