"Ownership" of community?
That was a question I got at TechEd Developers 2007. While I am technically on point for planning community different aspects (along with others) on MSDN and TechNet, I know that I do not "own" it. There are others, for example, focused on community from an audience specific (developers, IT professionals, etc), in addition others who are also working with community in some way, shape or form. To own it would be claiming to own all of the water in the world or something. With so many different aspects to what makes up a community, no one can really be in charge of it. The best I can do is to listen broadly, collaborate with others, and work to surpass the needs of the entire community as it pertains to MSDN and TechNet. Sounds like an interesting challenge, does it not? I'd love to hear your thoughts on this...
Some other related readings…
Bill Johnston on "Who owns community"
The International Online Community Management Association
Brian Hsi works with the MSDN, TechNet and Expression teams focused on community planning. Prior to this, Brian worked as a product manager for blogs and forums, in addition to working on a wide variety of community initiatives for MSN Games.
