Like many other companies these days, Capgemini has an internal blogging community. I used to write frequent posts on my own internal blog, but I have been passive for over 6 months. The reason is that I do most of my blogging out in the open these days, which is already taking up much of my time.
I must also admit that I had another reason, besides being too busy blogging elsewhere, for pushing aside the internal blog-o-sphere: the fact that it is only visible from within Capgemini. But I have changed my mind after reading this post on the “Go Big Always” (GBA) blog by Sam Lawrence. I am very much inspired by this post. Thanks for waking me up, Sam!
The internal blogging community of Capgemini is fairly large. People from all over the globe are active in this community. There are blogs that focus on development methodologies, on specific technologies and products, on right shoring experiences, et cetera. However, I am not sure how actively other employees read these blogs and benefit from their contents.
Most people at Capgemini (at least as far as I can see) use good old e-mail for finding and sharing information. They simply direct a question or item of interest at an e-mail group. This usually results in quick answers too. On the other hand, people also complain about receiving too much generally directed e-mail that pollutes their e-mail boxes. Maybe we should use e-mail for specifically directed information only, and use the blogs for generally directed information. That would take a rather large collaborative effort in our case.
But would that really solve anything? Moving information from e-mail boxes to RSS feeds doesn’t make much difference to me. I still have to read them, and I still won’t have time enough to do that (the number of feed subscriptions I have in my RSS Software exceeds 80…). For me personally, podcasts form part of the solution. I listen to them while I am commuting or mowing the lawn (if I had one). The podcasts that aggregate news and information are usually the best ones.
So, I can only conclude boldly with this: All Capgemini personnel should get iPods. Depending on your role, your skills, your position and your ambitions, your iPod will be automatically synchronized with what you need to hear. We’ll probably need to be a little bit further in the development of the third version of the Web to really make this work…