I've recently discovered hat MySmartChannels can be used as a branding and support tool - an efficient way to stay in touch with customers and help them gain insights into the technology areas where they are likely to face decisions. This use-case for blog-like behavior is useful for guiding clients on subject matter relevant to their respective lines of business. I call these knowledge-weblogs (KLogs for short). My klogs [however] are private, customer focused communication channels that help them as much as they help me maintain brand awareness with their staff. KLogs also provide a mechanism for slowly morphing my brand; providing awareness to my customers about new skills and solutions I have to offer or have become proficient in - in a sense, it's a "rolling-brand-space". Private klogs represent some unique opportunities and architectural challenges. For example - most klog entries are useful to all my clients, whereas some are very specific (and relevant) to a narrow part of my clientel. I don't want to create 20 separate weblogs, and furthermore, I'm a bigot when it comes to reusability. ;-) To achieve security and intimate authoring for specific clients, I use my own technology platform - MySmartChannels - which was inspired by a desire to build a Web services platform for loosely-coupled artifacts and the emerging weblogging space. MySmartChannels provides the ability to share specific klog entries out to appropriate client-subscribed channels. Each client is a named user in MySmartChannels so it's very easy to manage dozens of klogs that provide different collections of content depending on the client needs. And it also provides a mechanism for reusing klog entries (i.e., some entries are useful to all clients, while some are targeted for specific problem areas and only relevant to a few clients). Since the platform is XML/XSLT/RSS based, consumption of my private Klog entries content occurs in corporate portals, KlipFolio, AmphetaDesk, and our own stylesheets that I sometimes customize for clients (again, branding my content in the process). It would be extremely difficult to do this with any off-the-shelf blog tool – more likely a content management tool would be up to the task but that would be like turning off a light switch with a sledge-hammer. This is a pretty good idea IMHO - but I think it's only the beginning for KLogs - there are numerous use-cases, but I have come to appreciate the need for a klog platform that seriously considers the deeper architectural issues of security, associations, and a design that outlives its intended objectives. | 
