Dave and I are still trying to figure out exactly what this means, but I just ran across a couple of others that got me thinking about this again: The Philadelphia eLearning SIG Blog and The Seattle Captivate User Group Blog.
Both blogs serve the needs of their community. In discussing the blog with Ben Cragio from Phlesig, he says that this looks to be a great tool for the community:
1 - Cover more topics than we could possibly cover in 6 - 12 annual meetings a year.This makes so much sense, especially given how easy (and free) it is to get blogs together.
2 - Item #1 allows us to respond to the specific interests of our group. As a member of our e-SIG (and this is true in most technology user groups), it's quite likely that a topic you might be interested in, that talks directly to the work you are doing or where you are going, simply won't be addressed over the course of the year. Or it may be addressed too late.
3 - Get more members involved with the e-SIG.
4 - Increase the stickiness of the e-SIG by allowing people to maintain and add
connections in between meetings.
5 - Continue the dialogue in between meetings.
6 - Help steer better presentations to our physical meetings. Comments, voting and stats provide excellent guidance into what topics are in demand.
7 - We're an e-SIG so we should be using e-Learning! This blog is an informal e-Learning tool.
8 - Expose our members to blogging as a method of e-Learning and allow them to
judge for themselves where it fits into their toolkit.
9 - Hopefully gain perspectives from professionals outside of our group that we
wouldn't normally here.
Have I just been missing it? Should I have created the Los Angeles eLearning SIG Blog months ago?
It would seem that the critical ingredient is participation. Ben obviously is really helping the Phlesig take off. But it does seem like we may all be missing an opportunity. Thoughts?