The Story of an Accidental MVP

kimsanchez

Microsoft

Mar 03, 2026

How do you become a Microsoft Most Valuable Professional (MVP) without even knowing the program exists? In this guest post, Visio expert Scott Helmers recounts how a deep dive into the Visio object model—sparked by building a data-driven process-mapping add-in—turned into years of community teaching, conference speaking, and direct connection with the product team. Along the way, he shares what has changed in the MVP program and what aspiring nominees should focus on today.

By Guest Blogger Scott Helmers

How I Became a Microsoft MVP by Accident

In the early 2000s I was part of a team of three people who were designing a new, data-focused style of business process map. We decided to build our software as an add-in to Microsoft Visio because the diagramming software was commonly used in so many business environments.

I was the lead geek of the three, so I needed to learn a lot about Visio to design the add-in. Prior to this project, I’d been a casual Visio user but had never had a reason to investigate Visio internals. Suddenly I needed to know about the Visio object model and how to write Visual Basic for Applications (VBA) code to program Visio. Fast forward to the result: the product we created 20 years ago, TaskMap®, is still the fastest, easiest way to create data-rich process maps.

Finding Help Online—and Starting to Teach

In the early 2000s when we began our research, printed books were a primary knowledge source, along with a collection of relatively new tech-focused websites. I’d previously used a pioneering online tech community called Experts Exchange to get IT-related assistance, so that’s one of the places where I started posting questions. Sometimes I needed help with VBA, but mostly I needed to know how to program the Visio object model.

Between reading the available books, experimenting on my own, and Experts Exchange, it wasn’t long before I was answering more questions than I was asking. In typical fashion for me (an educator at heart!), my answers tended to be longer and more tutorial in nature and not just a quick sentence or two, so I guess they stood out a bit.

An MVP panel at Ignite

The Surprise Email: You’re an MVP

Apparently, someone noticed: In June of 2008, I received an email announcing that I’d been awarded as an MVP for Visio! There was only one problem: I’d never heard of the MVP program. I had no idea what the award meant. Fortunately, the welcome package helped me understand what I’d been invited to join.

My First MVP Summit

I vividly remember attending my first MVP Summit and walking into a large room with signs on tables announcing each award category. In the sea of tables, there was exactly one table for Visio and I felt more than a little bit shy about walking over to introduce myself to 10 people from all parts of the world, most of whom had been living in the Visio-verse much longer than I had. It was humbling. And energizing.

MVPs from left to right: Jimi Hong (MVP alumna), Michel Laplane, Senaj Lelic, Chris Roth, Scott Helmers, John Goldsmith, David Parker

What the MVP Community Opened Up for Me

Following that initial award, I have requalified seventeen times for which I am very grateful. From its peak of 14 or 15, the Visio MVP technology group, now part of M365 Apps and Services category, has shrunk to six and I’ve been privileged to share the designation with Senaj Lelic, Chris Roth, David Parker, John Goldsmith, and Michel Laplane.

The people I’ve met, the direct connection to the Visio product team at Microsoft, the opportunities I’ve had to speak at conferences around the world, write books, and create courses for LinkedIn Learning, are all a direct result of being an MVP. I might have accomplished some of those things without being an MVP, but the credential has played a significant role in opening doors and launching meaningful conversations.

I’ve gone from wondering what the MVP program was to appreciating it as one of the most significant parts of my professional life.

Many people seek out the MVP award, and I applaud their recognition of its significance and their drive to contribute to the community. For me, becoming an MVP was an accident of learning and then sharing critical knowledge.

I still have no idea who nominated me all those years ago, but I am eternally grateful!

You Can’t Become an MVP ‘By Accident’ Anymore

I should also add that it’s no longer possible to become an MVP “by accident.” Program rules require a nomination from a current MVP or a full-time Microsoft employee (FTE) and each nominee must share their community contributions as part of the nomination process. If you are interested in being nominated, ensure that you’re active – writing, speaking, podcasting, contributing code, running a user group – and work with a current MVP or Microsoft FTE.