If you’re aspiring to become a Microsoft MVP, you’ve probably wondered what the path is “supposed” to look like. This is what mine actually looked like—messy, imperfect, and full of self-doubt—along with the few things I wish I’d understood earlier.
By Guest Blogger Barret Blake
Before I Tried for MVP
I get asked a lot how I became a Microsoft MVP—and the honest answer is: I wasn’t chasing it. I was happy simply being part of the developer community: attending the occasional user group or conference, and writing a blog post now and then when something caught my interest.
Over time, this career has been great to me, and I felt more and more that I should give something back. But I didn’t feel like I had much to offer. You know the voice: “Who cares what I have to say?” So I stayed in the same pattern—showing up, learning a lot, but not really stepping into consistent contribution.
The Nudge (and the Accountability) That Changed Everything
Then I unexpectedly found myself needing to find a new job. I landed at a consulting firm helping lead a team of Microsoft Dynamics developers. Our boss was a Microsoft MVP—the first MVP I’d met outside of a conference hallway—and he was serious about community involvement. We ran and hosted the local Dynamics user group, and several of us (including me) were encouraged to submit sessions to conferences.
Saying Yes to Speaking
I was hesitant, but I submitted to multiple conferences anyway. The first accepted session was as a co-presenter at Community Summit NA in Orlando. The session went well—despite my constant feeling of terror—and that was the moment I decided to keep saying “yes” to speaking opportunities.
Barret speaking at an event.
Deciding to Go for It
After a few months (and a couple more speaking opportunities), my boss suggested I set a goal to become an MVP myself. By then I’d taken a real interest in Power Automate and had written several posts about what I was learning. Still, I didn’t think my perspective would matter to anyone else, so I mostly shrugged the idea off.
A few months later, another local MVP I’d met suggested the same thing—and offered to submit me. That was the first time I thought, “Maybe I should at least take this seriously.” So I kept writing, kept submitting sessions, and started speaking at multiple user groups.
Submitting the Nomination
About six months later, I decided that whether I felt ready or not, it was time to submit. My friend put my name forward and I started the process. I was prepared: the MVPs guiding me had explained how it worked, so I had my contributions documented—blog posts, sessions, and community activities—ready to share.
To be honest, I went through it half-heartedly. I genuinely didn’t think I would be accepted.
By that point I was connected with two MVPs and familiar with several others through their blogs and community sessions. I compared myself to them and came up short. What could I offer that wasn’t already covered across the community? But with their encouragement, I submitted—and then I waited.
The Waiting Game
That waiting period is the hardest part. It can take a couple of months for a new candidate to be reviewed, and that was true for me too. Around 4–5 months later—right around the 1st of the year—I got the email: I’d been accepted into the program as an MVP for Power Automate in the Business Applications area.*
After Acceptance (and New Doubts)
I’m now in my 3rd year as an MVP for Power Automate. With the 2025 renewal, I wondered if I’d contributed enough around .NET to try adding that category as well. The same comparison trap showed up again—I looked at other MVPs and felt behind. I decided to try anyway. To my amazement, it was approved, and now I’m an MVP in both categories.
Comparison is hard to outgrow. Even now, I still have to fight that feeling of insufficiency—and, yes, the imposter voice shows up. But I’ve learned that “feeling ready” isn’t the requirement. Consistent effort is. I keep pushing forward, offering what I can, and hoping that even one person gets value from it. If that happens, it’s worth it.
Barret speaking at an event.
What I’d Tell Aspiring MVPs
Sadly, neither of the MVPs who gave me that initial push are still in the program, but I’ll always be grateful for their guidance and encouragement. If you take nothing else from this, remember one thing: you do have something to offer. Make the effort. Submit the session. Write the post. Help the next person. You may succeed. You may fail. But if you inspire even one person, it will have been worth it.
Resources
- Connect with Barret on LinkedIn
- Learn more about the MVP Program and follow us on X and LinkedIn.
- Check the Reactor for quarterly opportunities to hear from MVPs about their MVP journey.
- *Editor’s note it takes about three months to have a nomination reviewed.
Microsoft