Corporate Blogging looks like a hot topic these days, and whenever the discussion starts about blog in a company, it nearly always starts with the debate about whether it should be internal (intranet) or external (public).
Lilia advocates public weblogs, even for internal KM purposes, because this is what obviously makes most sense to foster knowledge creation and innovation. But the private audience weblog is needed because some conversations should remain within a private setting.
Take competitive intelligence. Take R&D project logs. It would make a lot of sense for my employer if I could blog about something I learned today about a pending reorg at one of our competitors. But I would need to make sure that my post can only be read by members of a closed community of employees of my company + some other outside experts recognized as allies by the management of my company.
Some day there will be metadata defining access permissions on everyevery blog post. This post I am just writing would obviously be public. The next one, explaining something I just learned about Siemens or GE, would be restricted to my company's Competitive Intelligence community unless it is false information I want to spread, in which case I would make it available only to foes. And the last one, announcing that my appartment in Paris will be available for rent last week of July, would be restricted to people within one degree of separation from me on LinkedIn...
Blogging is inviting people to a conversation with you. In some cases, you want to be selective. And this is where the notion of community becomes key.