I have something against Knowledge Base modules. My complaint is this – they’re all crap!
Knowledge Base modules are supposed to be this repository for a given service, and this repository is supposed to provide all kinds of helpful Q&A-type articles to make using the service easier and more efficient. They’re typically intended to be a first-line support item, to be used by the end-user _before_ calling customer support and bugging an operator or a technician with your problem or question. It’s a pretty nice idea – in theory.
The trouble comes in when you actually try to use one of these so-called Knowledge Base modules. I have, as yet, to find a single one that actually provides me with any useful knowledge. The way I figure it, at least half of my queries into a Knowledge Base turn up zero results. The rest of the queries usually only produce a list of ‘related’ articles that have nothing to do whatsoever with what I actually want to know. They reason _these_ articles show up at all is because the search term(s) I entered happened to be mentioned once or twice in the course of explaining how to do something else. Usually after a couple of tries, I just throw my hands up in exasperation and dial the customer support number – only to have them refer me _back_ to the Knowledge Base. ((Just for the record, I’ll have none of that. I make them give me my answer and explain that the Knowledge Base didn’t have the answer I needed.))
This all goes along with the problem that documentation for most things also leaves something to be desired. I know, I hate writing documentation, too. It’s a pain in the neck and can often double the time it takes to release the product to the public. But for the end-user, that documentation is a critical part of using the service or software and can be the deal-breaker if it’s poorly done.