Jochen provides one of the best accounts that I have read about how to use an internal blog for communicating within teams. He describes how each IT team member makes a “daily” post to communicate four key items:
- Good news
Our “Daily Blog” has become an important communication tool. Managers and coworkers get up-to-date information about what a team is working on, what’s going well and what problems arose lately—without having time-consuming meetings. And via the comment section, people can respond with questions or additions, therefore starting dialogues.
And there’s another, hidden advantage: by writing about it, people deliberate about their work. So, there’s not only a communication aspect, but also a reflection aspect in our blogging. Both effects combined really make the time spent writing daily blog entries worthwhile.
I am constantly reading (and sometimes writing) about differences between people who do blog and those who do not blog. In teams, however, there is just one group – team member’s who do communicate. The only question becomes how that communication occurs; one-to-one, one-to-many, face-to-face, conference call, e-mail, blogs, and wikis (did I miss something?)
The simplicity of blogs makes them a viable alternative that many teams have adopted. Blogs are both compartmentalized (one post at a time) and comprehensive (all posts are contained in the blog). Blogs are more easily searched than e-mail and not reliant on who kept or deleted which message.
Finally, Jochen points out that the “continuous flow of information about [the team’s] current work fosters transparency and the exchange of ideas and helpful hints.” Read the entire post here.