Now lately I've been working with a couple of new public technical communities, and some customers who are forming their own Internal Technical Communities, and I've spent most of that time working on some lessons learnt style strategies on how to start, grow and sustain a new or existing technical community. When I caught wind of the podcast Nick, Athena and Adam were doing I thought, "Unreal, I wander what insights and innovative ideas they have towards this very tough topic!".
To say I was disappointed was to put it lightly! But before I fire up the Bunsen, let me put some context around this.
I'm a big fan of blogs... except the ones that offer zero value. And my measure of value is either and or either passionate opinion, surgical insight, or clever humor. I hate reading the ego blogs, or the "I'm so anti-establishment I want to eat my own Evisu jeans!" blogs, or the fine whine blogs, you know, otherwise known as the bogs! And the same holds true with podcasts.
So when I took 45 or so minutes out of my day today, to listen to the podcast, I was expecting three well versed, well experienced user group leaders to:
- Offer insight into how to start, maintain, grow a technical community
- Describe how others could start a user group and what resources where available
- Provide some best practice advice on how to develop content and culture speakers
Instead what I copped was 45+ minutes of retrospective chin rubbing, eyes-north brow furrowing, and in some cases, complete speculation on how Microsoft runs their technical community engagement strategy (which for those who listened and know the shot, realized how wrong some of the info in the podcast was) with no real substantive supporting info.
Now the first thing most people will be thinking is, "What the deuce! Has Lempho gone Randle!? Isn't he paid to shake the pom poms at all community activity!?". Well, not really. I'm paid to be a Developer Evangelist, and I'm also responsible for working with technical communities to kick buttuci! But part of that is looking to the elders of the game to step forward and come up with new ways to improve things. New ways to change the game! Every time I see someone with some experience looking backwards and rubbing their chin, I think, who's looking forward? Who's looking for ways to maneuver and improve the status quo!?
And why am I getting all hot and Nacho about this? Well, the topic of user groups a.k.a technical communities a.k.a Miguel Sanchez a.k.a Dr. Nyugen Van Falk, is very dear to my heart. And after realizing over the past 18 months how really hard it is to start, run and make successful a user/technical group can be, hearing all the boo hoo just makes me want to do the locomotion! I mean no one ever sets out to screw the pooch, but no plan is fool proof! Or I'd be capable of flight and time travel!
Fact of the matter is, we could all spend a lot of time wandering why things didn't quite work out the way we had hoped in retrospect, or we can lead a revolution completely to our liking! One approach is easy, the other is damn hard! And no, this is not a metaphor for why Coatesy, Chuck and I didn't get the chance to share a bed at CodeCamp last year!