Dennis McDonald has a lengthy blog post called "How Can You Communicate the Corporate Benefits of Enterprise 2.0 Network Effects?". There's too much there to summarize, but especially pay attention to the parts after the section "Relationship Enabled Network Effects". The post was prompted by Rod Boothby, who has also extensively written about using blogging software to supercharge the enterprise (comments on McDonald's post here).

My observations and thoughts:

• every person, project, resource, process in an organization should be primarily identified by a web page, not an email address (i.e. a http: URI, not a mailto: URI)
• this URI should be easily discovered (i.e. it probably should a variant of name.corporation.com)
• all documentation, internal business cards, etc. should refer to this web page when refering to the person
  
• these webpages should be of similar structure but have ad-hoc content
• the blogging model of content creation is ideal for this purpose
  

Tagging deserves a special mention:

• tagging should be used to create spontaneous links that both organize a person's content and cut across the organization
• formally specifying tags is bad, encouraging reuse is good
• tags will be recycled because they are inherently temporal; this is why specing tags will always be too little too late.

Of course, some blogging software is better than others. The BlogMatrix Platform (you're looking at it) was created for exactly the type of application discussed above.