In Enterprise 2.0, and indeed as early as June last year, I talk about the benefits of internal micro-blogging using enterprise versions of tools like Twitter.

If this is an area of interest to you (and it probably should be), then I strongly recommend you read two posts from Jeremiah Owyang and Neville Hobson.

In List of enterprise microblogging tools: Twitter for the intranet, Jeremiah has started a list of vendor offerings in the area (currently standing at eight). Well worth watching I think.

Neville takes one of the offerings, Yammer, for a test drive in Twitter for the enterprise from Yammer.

• Tonari no Totoro video

Like blogs, wikis and other social software that has gone before, I advise caution. Make sure you know what you want from such tools (and also what you need in terms of security and control) before diving straight in.

There’s a new review of Enterprise 2.0 in town – this time from Pleon’s Daniel Penton, writing for Simply Communicate who also interviewed me last month.

Daniel’s review is practical and down to earth, a point made clear from the title “Web 2.0 made simple”. He highlights both the Oracle and Janssen-Cilag case studies that feature in the book as examples that “make a very compelling argument for Enterprise 2.0.”

He also singles out the 4Cs Approach that runs through the book, labeling it as “a practical action-led guide to employing social software within organisations.”

I was particularly interested to see Daniel picking up on the increasing friction between business and IT departments that will result as companies try to introduce these tools:

As a result, an initiative often falls over when it gets to the IT department, who are more concerned with maintaining current infrastructure than experimenting with new unproven technologies. This is one of the major challenges of widespread adoption of Web 2.0 technologies in the enterprise.

He concludes that the book is “a great way to educate people new to the subject while enabling those who are already experienced in the area” and “shows how easy it can (and should) be to start experimenting with Web 2.0 technologies in the workplace.”

Who am I to argue with that?