Making the Most of the Sitecore Community Mentor Program

If you spend any time in Sitecore community circles — Slack, Stack Exchange, LinkedIn, or the hallway track at Sitecore Symposium — you’ll eventually run into the same piece of advice: find a mentor. It’s good advice. But it’s also advice that a lot of people nod along to and then never act on, usually because they’re not sure what the Sitecore Community Mentor Program actually is, how to get into it, or what “good mentorship” even looks like in a technical community like this one.

What the Community Mentor Program Is — and Isn’t

At its core, the program is simple: Sitecore MVPs volunteer to guide community members who want to become more active contributors — through blogging, speaking, open-source work, forum participation, and other forms of community engagement. Mentors commit to a couple of hours a month, join a broader Mentor Network with monthly calls, and in return get credit toward their own MVP application, plus the leadership and communication reps that come from teaching someone else. Mentees get structured support from someone who’s already done the thing they’re trying to do, along with the networking that comes with it.

Here’s the part people get wrong, though: the program is not an MVP shortcut.

It’s tempting to treat mentorship as a checkbox on the road to an MVP award — find a mentor, do the minimum, get the title. But that framing has it backwards. Sitecore doesn’t award MVP status for having participated in a mentorship; it awards it for sustained, visible contribution to the community. The mentor program is a support structure for building that contribution habit — not a substitute for it. If MVP recognition follows, it should follow as a natural byproduct of consistent sharing and a genuinely strengthened personal brand, not as the goal you were mentored toward.

That distinction matters because it changes how you should show up. A mentee chasing a title treats the relationship transactionally — show up, get tips, disappear once the applications close. A mentee who’s actually there to build a habit treats the relationship as scaffolding for a practice they intend to keep long after any award decision. Mentors can tell the difference immediately, and it shapes how much effort they’re willing to invest.

The same logic applies from the mentor’s side. Mentoring isn’t a favor you do to pad your own application, either — it should be a genuine extension of the same community-mindedness that got you recognized as an MVP in the first place. If you’re only mentoring because it counts toward something, your mentee will feel that, too.

How to Join — Finding a Mentor or a Mentee

The official path runs through the MVP Directory. Once you’re logged in, you can filter the MVP list to show only those who’ve flagged themselves as open to mentorship. From there, browse profiles, find someone whose focus area lines up with yours (XM Cloud, Content Hub, personalization, DevOps, whatever your lane is), and use the “Request Mentorship” button on their profile to send a request.

If you’re an MVP interested in mentoring, the process runs the other direction: log into your MVP profile and update the mentor information section so you show up as available in the directory filter. That’s the official, structured entry point, and it’s the one Sitecore actually tracks.

But the directory is the floor, not the ceiling. In practice, most mentor/mentee matches I’ve seen — including my own — started somewhere more informal:

• Sitecore Slack. Mentors who are active and helpful in the community channels get noticed. If you’re looking for a mentor, pay attention to who consistently gives thoughtful, patient answers — that’s usually a strong signal of who’ll be a good teacher, not just a good MVP.
• LinkedIn. A lot of MVPs post openly about being available to mentor, or share their mentees’ wins publicly. Following and engaging with that content is a low-pressure way to get on someone’s radar before you ever send a formal request.
• Events and webinars. Symposium, Sitecore-hosted webinars, local user groups — these are where relationships actually start. The directory request just formalizes something that often begins with a conversation.

If you’re a prospective mentee and you don’t see an obvious match in the directory, don’t be afraid to reach out directly to an MVP whose work you follow and ask if they’re taking on mentees. Most are flattered to be asked, even if they have to say not right now.

How to Be a Great Mentee

The mentees who get the most out of this relationship tend to share a few habits:

Come with a starting point, not a blank page. “I want to get more involved in the community” is a feeling, not a plan. “I want to start a blog and publish consistently” or “I want to get comfortable submitting a conference talk” gives your mentor something concrete to help you build toward.

Do the homework between sessions. Mentors are volunteering a few hours a month, not running a course. The mentees who progress fastest are the ones who show up to each call having actually attempted what was discussed last time — a draft post, a GitHub repo, a talk outline — even if it’s rough.

Be honest about what’s actually blocking you. Often it isn’t a skills gap — it’s fear of publishing something imperfect, or not knowing what topic is “worth” writing about. Say that out loud. A good mentor can address a confidence problem far more easily than a mentee can solve it silently on their own.

Treat feedback as material, not judgment. You’re going to get notes on drafts, talk pitches, or code samples that sting a little. That’s the point of the relationship — a mentor’s job is to catch the rough edges before your audience does.

Respect the time. Show up prepared, keep your ask reasonable (a couple of hours a month, remember, is the mentor’s stated commitment), and be the kind of mentee who makes your mentor glad they signed up.

How to Be a Great Mentor

Mentoring well is a different skill than being technically strong, and it’s worth being deliberate about.

Meet people where they are. A mentee who’s never published anything needs a very different first conversation than one who’s blogged for a year and wants help finding their voice for conference talks. Resist the urge to hand everyone the same generic advice.

Give them a small, finishable first task. Momentum beats ambition early on. A mentee who publishes one short, imperfect blog post is in a fundamentally better position than one who’s been “planning a big series” for three months and hasn’t shipped anything.

Model consistency, not perfection. The most valuable thing you can demonstrate isn’t polish — it’s the habit of showing up regularly. Share your own messy first drafts or early talks if you have them. It normalizes the fact that everyone starts rough.

Help them find their format, not just your format. Just because you built your brand on blogging doesn’t mean that’s the right channel for your mentee. Some people find their footing through video, some through speaking, some through open-source tooling or GitHub snippets. Part of your job is helping them discover which mode of contribution actually feels natural and sustainable for them — because sustainable is what turns into a real habit.

Show up for the Mentor Network, too. The monthly mentor calls exist so you’re not figuring this out in isolation. Other mentors are a good source of ideas when you’re stuck on how to help a particular mentee.

Remember the “why.” You’re not building someone’s MVP application. You’re helping someone build a habit of contribution that will outlast any single award cycle. If that habit sticks, the recognition tends to take care of itself.

An Example Mentor/Mentee Structure

Every mentor runs this differently, and that’s fine — but having some structure beats winging it every time. Here’s the cadence I use with my own mentees, offered as a starting template rather than a rulebook.

Cadence: Every two weeks, roughly 30–45 minutes.

Weeks 1–2 (Foundation): We don’t start with content ideas — we start with infrastructure. Get a blog set up (even a simple one), figure out a publishing workflow, and remove every logistical excuse for not writing.

Weeks 3–6 (Small starts): We pick two or three low-stakes topics — usually something the mentee just solved for themselves, since “I just figured this out and wish someone had written it down” is nearly always a good post. The goal here is publishing, not perfection. First posts are almost never anyone’s best work, and that’s fine.

Weeks 7 onward (Finding their lane): Once the habit of shipping something every couple of weeks is in place, the conversation shifts from what should I write to what’s natural for me. For some mentees that stays blogging. For others it turns into speaking at a local user group, recording short walkthrough videos, publishing GitHub snippets, or building and open-sourcing a small Sitecore tool. I’m not trying to turn every mentee into a blogger — I’m trying to help them find whichever form of contribution they’ll actually keep doing without me nudging them.

Throughout, the through-line is consistency over intensity. A mentee who contributes something small every two or three weeks for a year will be in a stronger position — as a contributor, as a professional, and yes, eventually as a potential MVP candidate — than one who tries to produce one perfect flagship piece and burns out.

The Real Payoff

The Sitecore Community Mentor Program works because it lowers the activation energy for getting started — pairing people who want to contribute with people who’ve already built the muscle for it. But the program is only as good as what you bring to it. Mentees who show up with curiosity and follow-through, and mentors who show up with patience and genuine investment, get far more out of this than the six-line description on the program page suggests.

If you’ve been sitting on the idea of getting a mentor — or becoming one — the MVP Directory is a good place to start. But don’t wait for the perfect moment to send that request. The best time to start building the habit is now.