Freigeben über

To MVP, Or Not To MVP…

  • Artikel

I was recently moved to comment on a blog post from a gentleman who turned down being re-awarded the MVP designation from Microsoft. After giving it more thought, I decided to write this blog to promote more discussion regarding the value and challenges with the MVP program. So please comment on the following:

  • If you are an MVP, what do you regard as the benefits? Challenges?
  • If you are not an MVP, would you want to be? Why? Why not?

Comments

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    February 08, 2011
    I am not an MVP but I don't see any disadvantages about becoming one. Those being rewarded for great community work with something like the title of "MVP" really sets an example of great programming spirit and that anyone that works hard can achieve great things. But not to forget those that are not awarded with the MVP award; those individuals that help out in other ways, ways that might not be contributing to forums, writing blog posts. Such as strong souls within corporates that fights for spreading knowledge and help those in need to get to the next level. Short answer would probably by: Yes being an MVP would be an honor.

  • Anonymous
    February 08, 2011
    @Filip Ekberg Thanks for your feedback from the non-MVP perspective.  The "award" for MVP certainly designates the awardee as a contributor to the community.

  • Anonymous
    February 08, 2011
    @Joseph Guadagno I agree.  I made many contacts and new friendships via the MVP program.  That alone seems priceless to me.

  • Anonymous
    February 08, 2011
    I agree with Joseph. Becoming a MVP isn't going to change your life. You should already be building strong connections in the community, you should already be gaining benefit from those connections, etc. The MVP program provides you more opportunity to reach outside your immediate community (either geographical or online). The benefit shrinkage that is often complained about (lowering MSDN subscription level, Microsoft bucks at company store, etc) are not what the MVP program truly provides. Those are just fringe benefits.

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    February 08, 2011
    No matter what organization you have, there will be people that don't like something about it and decide to leave. I have read the post Emily referenced and the poster seems to have been part of a product group that doesn't share much information. This varies from group to group. I've been an MVP for two different products and the information to and from each of those groups has been fantastic. I greatly appreciate what I get that I can then use to enhance the community. But more importantly, I'll agree with other commenters here. It's the friendships I value most.

  • Anonymous
    February 08, 2011
    I'm an MVP and I read the article a few days ago you are talking about.  I think like anything else it takes time to become a good MVP.  I tell new MVPs all the time "did you know this or that" and get blank stares.  It seemed like he didn't really try to take full advantage of being an MVP.  I will tell anyone that will listen that it has its advantages BUT you have to know and understand what to do. I know I have personally shaped many a product over the last 4 or 5 years (I've lost count).   I'll admit that I didn't have that connection with the product teams the first year or two I was an MVP.  Honestly I just didn't know how to take advantage of it.  And then I started to learn how to be a better MVP.  I would take feedback from my team members and actually walk into a building where the product was written and talk to someone about it.  Usually trying to find the guy that worked on it.   I remember a few years ago at the MVP Summit several of us were tired of going to sessions on campus so we went over to one of the buildings to hang out with a friend that worked there.  It was by far the most productive evening we had while on campus all week and it was a blast engaging with the MSFT employees about their product.  Believe me when I say they (MSFT employees)  listen, you just have to remember that just like us they don't like being yelled out, made fun of, etc.  They really do want to build a better product, you just have to ask them nicely and with respect and you'll get that back in return.  

  • Anonymous
    February 08, 2011
    @Steve Evans I appreciate your perspective on motive. The "happy" MVPs were already champions in the community and not determined to become MVPs. If the community activities happen naturally, the MVP program is a great compliment. Doing community activities for the sake of becoming an MVP appears to be one of the complaints from the ex-MVP who inspired this blog.

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    February 08, 2011
    @Craig Berntson Thanks for your feedback. Even if the communication from the product teams were lacking, I would not personally devalue the ongoing networking opportunities.

  • Anonymous
    February 08, 2011
    @Keith Elder Excellent feedback for MVPs!  Thanks for your comment, it is worthy of being a blog post on it's own :-)

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    February 08, 2011
    I'm fortunate to work with two great product teams (Silverlight and ASP.NET) and have the benefit of associating with people in and out of the MVP program who enjoy working with those technologies and who are willing to help others learn more about them and get better at what they do. I've made friendships through the MVP program that wouldn't have happened otherwise and the program has benefited me simply through learning about better processes I could be following or better ways to write code. It's also a blast to hang out with friends and make new friends at the MVP Summit each year and interact with product team members. Although the MVP program isn't perfect by any means, it definitely adds value in my opinion through more direct access to technology, associating with some great people at Microsoft and in the MVP program and getting a chance to help out in various communities. As far as people complaining about the MVP program, that's certainly their right and there are a few complaints that I agree with that should be fixed. However, the most effective way to deal with problems or suggest improvements is to talk directly with the appropriate MVP lead, MVP leadership, fellow MVPs, etc. If that doesn't work and someone decides to relinquish their MVP award then that's their choice. However, do it in private.  Voicing those types of complaints in public reminds me of a child who screams and throws a fit just to get attention.

  • Anonymous
    February 08, 2011
    I attended an MVP Summit a few years ago as what they called an "Influencer".  Although I wasn't an MVP, I really enjoyed that experience!  It gave me a chance to talk with the people working on the software I use daily, and to get insight into what was coming in future versions of Visual Studio.  I would LOVE to be awarded an MVP, and I hope that one day I shall be.

  • Anonymous
    February 08, 2011
    I read that article a few days ago, and as a non-mvp, I was a bit perplexed by it.  I'm glad that reading through the comments that not every product group is as non-interactive as the one wrote about.  I see the MVP program as an award given to people from the community who take their own personal time to help out.  Unfortunately, some of these people feel they have an entitlement after they get the award.  If you feel that it takes too much work and the rewards aren't enough for an MVP award, then you probably either don't get it or don't have what it takes to be an MVP.  Helping out in the community should be reward enough.  The award is just a recognition for what you do. If I was awarded an MVP, I would be honored because it would mean others have found my contributions to the community worthwhile and helpful.  As being a member of the local community in Denver, I had made great connections already, and could only imagine the networking opportunities an MVP award would bring.

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    February 08, 2011
    ...In the end, the love you take...is equal to the love you make.

  • Anonymous
    February 08, 2011
    @Ryan Cromwell "To send back a thank you is childish and ungrateful, in my opinion.  It smells of wanting to be a cool kid. " I agree with your statement.  The MVP Award is just that - an award with a "thank you" for what you have done for the community.  If someone turns it down (publicly at that) it appears to have some other "cool kid" or "I am above that" attitude - when in reality it is ungrateful. Having said all that, I would ADMIRE anyone who would "step down" from being an MVP if he/she were no longer engaging in any of the activities that landed him/her the MVP Award in the first place.  To do so shows strength of character.   But to turn down a "thank you" because you aren't happy with the benefits of the "thank you" is childish.

  • Anonymous
    February 08, 2011
    @Steele Price "I believe it is a marketing faux pas by Microsoft to promote MVPs as "Experts" in anything but building communities around a topic." While I agree that MVPs do build communities around a certain topic, I disagree that they are not "experts".  "Expert" is a relative term.  Some might regard me an "expert" in ASP.NET, while I personally consider others more expert than me in ASP.NET. If an MVP's contributions serve the community, it is reasonable the community will look to such one as a go-to person, or expert.

  • Anonymous
    February 08, 2011
    @Scott Cate "The MVP program is an award, with a few benefits. AWARD is the key. It's a thank you for what you did LAST YEAR. It doesn't commit you to doing more THIS YEAR. I don't understand rejecting the award. Maybe you reject the benefits, but there is no reason to reject the award. It's like saying, don't thank me for what I did." Nicely stated!

  • Anonymous
    February 08, 2011
    @Dan Wahlin "However, the most effective way to deal with problems or suggest improvements is to talk directly with the appropriate MVP lead, MVP leadership, fellow MVPs, etc. If that doesn't work and someone decides to relinquish their MVP award then that's their choice. However, do it in private.  Voicing those types of complaints in public reminds me of a child who screams and throws a fit just to get attention." I totally agree.

  • Anonymous
    February 08, 2011
    The comment has been removed

  • Anonymous
    February 08, 2011
    @James Kipling "What I want to see removed from the MVP program is the corruption." Thanks for your candid feedback.  While I am not denying your concern, I am personally unaware of the corruption you speak of.  For example, I personally have no knowledge of anyone remaining in the MVP program because of where he/she is employed. If you feel you have valid concernswith specific examples, please contact me offline.  Thanks!

  • Anonymous
    February 09, 2011
    @Kelly Sommers Kelly, really enjoyed your feedback.  Thanks for your comment :) With regard to the question: "What's the expectations of MVP's once awarded. What do they expect as the next steps in their partnership with Microsoft?" - Scott Cate answered that one well.  The award is for what you have accomplished, not for what you are going to do.  Therefore, although there may be opportunities for MVPs to respond to, they are under no obligation to do anything other than enjoy the award.  As it turns out, most MVPs are passionate about what they do, and the award does not typically end their activities.

  • Anonymous
    February 09, 2011
    The biggest problem at the moment, in my opinion, is that very knowledgeable people are turning down MVP awards because their no longer being taking serious by either the community or the design teams and that's a shame. @Kelly I totally agree with you and I believe the warped perception comes from the fact that the audience in general considers the MVP to stand for Most Valued Professional. Being a professional hints at being an expert on a certain subject. The ideal option from a general audience point of view would be to phase out the 'Community Experts' into a different award program. The MVP's would become 'Experts' again. MVP's (if Microsoft would like community input that is) could discuss on behalf of the community with the Microsoft teams about future roadmaps and the community could discuss with the MVP and will once again have their 'professionals' to turn to. The 'Community Experts' will still receive their thanks and appreciation for their volunteer work and devotion to a product and everyone will be in sync again about who's what. J.

  • Anonymous
    February 09, 2011
    One thing I do find interesting is that there are certain people who specifically set the target of becoming an MVP. It's like setting a weight loss goal - you can target that goal, but when you reach it, then what? Most people who set the target reach it, and then it's done. On the other hand, focusing on living a healthy lifestyle means the weight loss goal is a side effect and hitting the target doesn't mean changing the habits. I view my MVP award the same way. I did not start doing talks, publishing a prolific blog or getting involved in various events with the goal of becoming an MVP. I did it because I'm passionate about Silverlight and focused on sharing it's benefits with others and showing them best practices and ways to use it to solve business problems. I am thankful and feel blessed that the result of that focus was an MVP award. Before being awarded, I honestly did not know what the award would really entail beyond recognition. Now I do know. It is different for every group, but I can say in my opinion the Silverlight MVP is phenomenal. It provides me with unprecedented access to the product teams. I do feel my input is heard and that I can help influence the product future, because the Microsoft employees have made themselves very accessible and listen attentively to the needs. As MVPs I believe most of us don't feel we are "experts with an MVP badge" but rather that our status of MVP makes us official representatives of the community, and therefore I see most MVPs in my platform focused on listening to the people in the community and their customers and the issues they raise are not "my problem is..." but "the community perception is..." This to me is very valuable and helps Microsoft leverage a worldwide team to connect with the community. The program is by no means perfect and as I mentioned I understand there are different experiences in different platforms and disciplines. But nothing is perfect and my experience has been the team at Microsoft listens when we have feedback and responds. I do agree probably the most important thing the MVP program can do is a better of educating the community about what an MVP represnts - a 30 second elevator pitch that doesn't just focus on the side of recognition, but the value and benefits that come from the position. Thanks everyone for sharing your thoughts!

  • Anonymous
    February 09, 2011
    In the broader development community MVP status is the grounds for a good laugh. As a developer inside the Microsoft community, the MVP status generally comes at the expense of researching new emerging non-Microsoft technologies. I wouldn't consider being an MVP, my time is better invested in becoming more employable by keeping up to date with non-Microsoft technologies.

  • Anonymous
    February 09, 2011
    The comment has been removed

  • Anonymous
    February 09, 2011
    @Jeremy Likness, part of the reason people set these goals is because that's how its told to some of us. I was asked multiple times "do you want to pursue being an MVP?". I think all of the language around how the program is displayed, how MVP's are promoted make it look exactly like a recognition of expertise. That's why I think 2 programs are needed for Community Leaders and Experts. Both are useful, but messaging around both are entirely different. How you get recognized is different as well.

  • Anonymous
    February 09, 2011
    @Oisin Greham 'Every time I read about some MVP complaining about the efforts he/she has to do to ensure their continuing membership in this magical clan, then I just want to reach out through the internet and twist their whinging earlobes and yell: "If it's feeling like work then stop. Noone's forcing you."' Great statement.  Becoming an MVP should be natural.  Remaining an MVP should be natural too.

  • Anonymous
    February 09, 2011
    The comment has been removed

  • Anonymous
    February 10, 2011
    I received the MVP award this year for the first time, and I'm very proud to say that I was awarded it. Microsoft makes it very clear (as have many of the commentators here) that nothing is expected of you as an MVP - it is a recognition of the work that you have already done. However, for me personally, receiving the reward had the effect of encouraging me to do more of those activities which I was already doing - running usergroups, speaking at conferences, answering forum questions. In fact, I've started blogging only since having become an MVP, having seen the great blogs that some of my peers write. I certainly did not start doing community activities with the specific objective of becoming an MVP, but I would be lying if I said that I wasn't motivated to receive the award. I think everybody likes being recognised and, in the world of I.T., an official recognition from Microsoft is hard to beat. I've never boasted about my MVP status, I don't get any particular benefits from it, but the little glass award sits on my desk and I'm not ashamed of that. I am very humbled to be an MVP and feel that I need to now justify those three little letters. The program may have some flaws, but in my (very limited) experience it is not as "broken" as the MVP-refuser suggests - in fact, every time I gather together with other MVPs I get motivated and inspired by their knowledge, helpfulness, and enthusiasm and I hope that, maybe just occasionally, I might have that effect on others too.