Knowledge Base Software
Published by Dan April 7th, 2007 in GeneralThis could apply to many software solutions, so
I think that usually, a knowledge base would be like a brain dump of all the bits of information that staff know about. As staff work within a business, they collect all sorts of small pieces of information about the business. Like, that your major product doesn’t work well with your main competitors product, it introduces problems X, Y, and Z. Or even uses of your product by customers in which it was not originally designed for, like, when Jack called last week and told the customer service guy that your tissue product works well as a bass reducer in his home studio.
Now, this type of information could be seen as useless, but, your customers may find it valuable, and you may also find it valuable if you can identify patterns (like many people use your product in a home studio, but you didn’t realise it). In its most basic form, your customer service/support team can quickly search for known problems/solutions and deliver them to the customer quickly, minimising headaches for the customers.
When I mention these examples, I’m sure some business owners or managers become overwhelmed by what must be involved in setting something like this up. But, what if it were simple? What if there was a product created for businesses that was easy to implement? I’m specifically thinking of a solution that is designed for easy of deployment and use. I’m sure there are many products out there, and they have all sorts of features, but would they be willing to sacrifice features in order to simplify it to make it more accessible to more potential customers?
I think that many times, IT guys make things too complicated. IT guys think on a different level and it’s difficult for them to think like a regular, non-IT person. What if there were IT guys around that specialised in making things simple? I’m not coming up with any quick answers, but it’s something to think about.
Hi, I have always had a beef with help files. My usual comment was, “Help files don’t help.” A lot of times, I would read about a feature that was way above my head and I would ask, “Yes, but what is the purpose this feature?” This was especially true of Autodesk Products. Since then, I have become a technical writer, and I always try to think like a non-technical person. I often fail miserably. However, I do have an ‘ace-in-the-hole’. My wife is a non-technical person and I enlist her to evaluate my writing to see if I am reaching the non-technical audience. I became interested in knowledge base software about a year ago and since have really enjoyed the improvements in General Knowledge Base This is an excellent freeform relational database with search, sort, and organizing features as well as Client/Server technology for sharing among employees and clients. The help file not only tells you how to do something, but also why you would want to.