I don’t think it was too hard to get buy-in from a majority of the staff. I have to make it clear that this is a young team, with most of the team in their 20s still. It was probably easier to get the buy-in because of this. Beyond RSS, I installed two email subscription plugins — one for posts, one for comments — for those that think a feed is something you do in the kitchen.

As we rolled it out, not everyone was into it at first. Those of us that were would talk in the office about the posts, which piqued the interest of others who hadn’t gotten into it yet. They didn’t want to be left out of the conversation so they started checking it regularly. At least one person said they forgot to go look, and ended up setting that as her homepage so she’d always see it.

If I were on a team of developers, sysadmins, and/or support staff the blog would have to be toned differently. I could see that being an office Slashdot-like site, where people posted interesting tech articles, new product updates, triumph over a buggy section of code, and “we’re getting a lot of these types of support calls” type things. Stuff that’s all work related, but not necessarily in the nitty-gritty details of the job.

How are you thinking of using a work team blog?