In a few days, my time as a Microsoft Most Valuable Professional (MVP) will come to a close. Sad, yes I know… OK, not really so much sad as the natural evolution of things. I first received the MVP award a mere four days before my daughter was born. Even back then, I knew that I would have to eventually bow out of the program. Of course, there are people in the program who successfully juggle their job, home life, and somehow still manage to be excellent MVPs, but I don’t feel I’m one of them, so I’ve asked not to be renewed this year.
The MVP program is excellent and I’ve enjoyed being a part of it. Most of all, I’ll miss going to the MVP Summit and hanging out with the other MVPs. There are other benefits of course—access to early information, free software—but those don’t match the amount of effort it takes to get the award. As I describe in the post mentioned below, you really have to doing community work because you love doing community work—otherwise the time investment just doesn’t make sense.
I already sent the obligatory “so long and thanks for all the fish” message to my fellow MVPs. I wish you all well and keep up the excellent work!
First of all, if there is only one thing to remember about the MVP award, it’s this: the Microsoft Most Valuable Professional (MVP) award isn’t a certification. There are no set criteria or steps that someone can take to become an MVP. As the name implies, it’s an award.
“This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in SharePoint Services technical communities during the past year.”
In practical terms, this means helping with community-focused resources such as contributing to newsgroups, speaking at conferences, writing/blogging about your subject (e.g., SharePoint) and contributing code to CodePlex (an open source site).