Re: Knowledge Bases -- What are they, really?

[Craig Cardimon <craig -dot- cardimon -at- gmail -dot- com>]

I went through this several years ago. I was tasked with converting our
existing documentation into a knowledge base format. This took roughly six
months with my putting in 50 hours a week. It was brutal but I got it done.

Craig


>
> It has been my experience that those wanting a knowledge base are
> doing so because "oooh! look! shiny!" It turns out that they don't
> know what it is that they are asking for, but are pretty darn sure
> they have to have one. That is, until presented with what it might
> cost to convert existing documentation into something that someone
> might call a knowledge base. There is no free lunch.
>
> Bob
>
>

-- 
Cordially,
Craig Cardimon - Let me help you with your resume or LinkedIn Profile.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives