b.cognosco

I can see this being very useful for group journaling as described in "In the Same Room Does Not Mean on the Same Page", for tracking software development projects (when combined with threaded discussion, doc mgmt, RCS, etc.), and for lending a sense of coherence to a group of company weblogs across departments or even the entire enterprise.

A scenario: (I need to draw a picture of this) I can see a sort of pyramid structure -- each individual has a weblog where they narrate their work and record important insights, experiences, or problems. Each has a category for Team, Department, Division, Company, etc. where they post items relevant to a specific audience. The Team Leader runs a Multi-Weblog Author Tool, aggregating the "Team" feeds from each employee. Someone at Department, Division, and Company levels do the same.

These aggregate weblogs generate their own RSS feeds and could, again, be subscribed by any individual in the company -- leading back to each employee and providing the opportunity to comment and contribute at all levels of the organization.

This is real transparency. Combined with a culture that doesn't penalize people for saying what they think, this could be a powerful way to keep employees informed and to let employees inform the company.