Congrats 2016 SDL Web Community Winners!

Congrats to the SDL Web 2016 Community MVP Winners!

Five quick tips for a successful year:

1. Enjoy the uber geek status. Be sure to get to the retreat if you can. It's awesome.
2. Keep sharing. Year two is harder than winning the first year.
3. Don't under-appreciate what you have to offer.
4. Don't get complacent or over-confident either. Winners aren't "the best," though the best often share.
5. Connect with others and encourage the next generation of sharers.

To previous winners that "fell off" this year, welcome to the alumni group. Here are thoughts back from 2012 on having MVP alumnus status. Big thanks to those that shared less but maybe mentored more.

For anyone else interested in this award, 2017 will be even harder for a few reasons:

1. Community members can get an SDL Web 8 developer license for research and sharing. The list is growing. Don't wait to get started.
2. Alchemy.
3. DXA.
4. DD4T.
5. The Next Big Thing in the Community (I've seen it. You're not ready for it. It's impressive.).

You may have read how to win my vote in a post from last year. That's old advice. To join the 2017 MVP class first join today's community. Then optionally see what everyone else is doing. And then share more than everyone else.

Congratulations to the SDL Tridion MVP Class of 2015

For the first year since I started using Tridion, I could not keep up with everything. It's awesome. But I'm also sad because I wrote a guide on keeping with the Tridion community.

So rather than (yet another) community video (my last one might be the last one), let me send my congratulations to the group.

Congrats to the SDL Tridion MVP Class of 2015!

Nothing says "good job" like Clip Art. Good job to the MVPs employed by SDL, aka Community Builders.

Winners, Alumni, and Future MVPs

Even before going into the nomination process, I had a feeling this was going to be a hard year to get selected and chosen. Indeed we've had strong contributions by new members and some that didn't qualify for sharing-in-2014 (I prefer the term "alumni" because they don't necessarily leave, but often guide and support the community, even when not doing Tridion anymore). For those that got a nomination but didn't win, see my last post and definitely continue sharing to potentially win in the future.

So Many Topics for a Mature Community

I'm especially impressed by both quality and quantity shared. I especially appreciate the topics—from BluePrinting, to SmartTarget, to even more on GUI extensions we had the bookmarklet challenge, plenty of videos, ways to use "new" software, comprehensive guides, and forecasts for the product (industry). We saw plenty of Tridion Stack Exchange questions and answers (see how you ranked in 2014). Forget podcasts, Robert Curlette brought everyone to a developer summit. This is definitely not a comprehensive list (like I said, it's hard to keep up now), so I encourage you to highlight your favorites publicly or by nominating someone to be part of the next set of community MVPs.

The posts, videos, code, Q&A, and blogs definitely reflect what Product Manager Nuno Linhares calls a mature technical community.

So congratulations and remember sharing in year 2 can be harder than starting. And for those starting (again), it's not necessarily hard, but you do have to start. The rewards in sharing, connecting, and helping others go beyond any company-sponsored award. I even recommending sharing something, anything, non-Tridion and see what you can create (or break, your call). Then come back and get ready for the 2016 MVP awards.

Feel motivated? Need a call to action?

• Nominate someone else
• Start a blog. I could give you a direct link to Blogger or Wordpress, but you do Content Management for a living.

Selecting Community Winners

The first (and really only) thing the SDL Tridion Community MVP Selection Committee does at the start of the year is vote on MVPs and Community Builders (internal MVPs).

In the spirit of sharing, let me post thoughts on the selection process, a winning formula (there is none), a practical approach at selecting, and making this easier for me, which will ultimately help you.

I Don't Pick You and You Didn't Pick Me

First of all, I don't choose candidates except for the few I nominate myself. Suggesting candidates is the community's (your) job.

I ended up on the committee as a case of Midas Rule--a colleague changed job roles (it's old news but congratulate him if you haven't already), which left us with a spot open in SDL Professional Services (PS) to vote on community contributions. I've been both an MVP and a Community Builder and tend to both share about Tridion, but also promote and comment on the community itself. So having me vote on the community was a good fit at the time.

The committee has 2 from SDL and 3 externals. Committee members cannot vote for themselves, so being on the committee means I need to earn 3 out of 4 votes instead of 3 out of 5.

No Formula

There's no formula or minimum to winning aside from the "Becoming a MVP" selection criteria. If we posted detailed requirements, we'd likely encourage a slight-to-significant skew in the results as seen in this exaggerated graph:

 And a hypothetical histogram against these results might show that most only shared enough:

Congrats to the 2014 SDL Tridion Community MVPs!

Around this time of year I do two things:

• Congratulate the new SDL Tridion MVPs (2014)!
• Share some Tridion community insight, this year in a mix of practical, inspirational, and old advice to the MVP 2014 crew. 

Today MVP Chair Nuno Linhares announced the new 2014 SDL Tridion MVPs. It was an impressive year as seen in some 1300+ questions and 2500+ answers on Tridion Stack Exchange, numerous blog posts, and so many examples that customers now ask me where to start rather than where to find information. Congrats and well done!

Congrats and thanks... for making SDL Tridion MVP 2015 that much harder!

Welcome the New SDL Tridion Community MVPs!

This year I was proud to serve on the SDL Tridion Community MVP Selection Panel, which consists of 2 SDL employees and 3 externals (internal winners or "Community Builders" aren't announced publicly--the award is focused on encouraging the community to share).

I was impressed by how much the community continues to grow. I'm surprised by how much we shared in quality and quantity. And I'm hoping to clarify what the program's really about and how you can help with pictures, humor, and mentioning Tridionhotties.

First Things First

Congratulations to the 2013 SDL Tridion Community Most Valued-for-Sharing Professionals!

Update: added a link highlighting how these contributors contribute to the community. ;-)

• Albert Romkes
• Alex Klock
• Chris Summers
• Dominic Cronin
• Frank van Puffelen
• John Winter
• Nickoli Roussakov
• Quirijn Slings
• Ram Gonuguntla
• Robert Curlette
• Robert Stevenson-Leggett
• Will Price

They also contributed or were fairly visible in a few places:

• StackOverflow
• TridionDeveloper
• PowerTools
• Tridion Practice
• DD4T
• RazorMediator
• Other Google Code Projects
• GitHub
• TridionWorld Updates
• Netvibes Aggregate list

Wow. The SDL Tridion Community in 2012.

One Tridionaut shared 40 blog posts covering the ins, outs, and step-by-step coverage of GUI extensions and Yet Another sharer shared 67 posts covering snippets, approaches, and discoveries across the Tridion API stack. Almost a thousand StackOverflow #tridion questions got 1750 answers on StackOverflow. Lots checked-in open source code.

Even the occasional question or answer mattered. You didn't just participate, you were engaged, active, and helpful.

The long tail of StackOverflow #Tridion answers means even occasional sharing helps.
Are you one of last year's148 SO #tridion users?

What the Program Wants. What Some Expected. What Customers and Your Peers Need.

Ever been here? Customers and your peers often find the community through online search. Are your expertise and knowledge sharing activities "SEO-friendly?"

What the Program Wants: Sharers.

The program is a "thank you" for helping more than your immediate client or projects. It's recognition for those sharing online voluntarily and a possible incentive to help others online. In a way, it gives us permission to share. Seriously, you'd be surprised at how many senior-level experts want to, but hesitate at, sharing.

Sharers at all different levels share what they know to help each other online. In a world where there's no where to horde knowledge, it's good to know where to share (the forum, your blog, or stack overflow are great places to start) .

The community is growing. The community MVP program likes this.

And growing. This is what the MVP Community Award hopes to encourage.

The program didn't meet everyone's expectations. Nuno clarified last year, but the typical responses to an "MVP" title are why him? Why not her? Or a new one: about time he won!

1. Why Didn't So-and-So Win?

"Isn't she as good, nice, or good looking as the other candidates?"

1. Maybe it's your fault. There were some fairly qualified people that didn't get your nomination. It only takes an email (add @sdl.com to addressee).
2. The nominee didn't share enough knowledge.
   
3. Confusion between a Community award (share!) with an employee recognition award (you're awesome!). Companies have valuable employees. They should value them.

   

   Two SDL internals and 3 externals can't possibly rate who's the best. Well, maybe Tridionhotties are obvious, but surely out-of-scope for a technical community sharing award.

2. Why Did So-and-So Win?

"He's not as good, nice, or good looking as these other candidates."

He or she met three requirements that emphasize online sharing (more so than hotness or being the best/helpful/most ____):

1. Voluntarily sharing their Tridion expertise and knowledge online for the previous 12 months.
2. Getting nominated
3. Getting 3 out of 5 votes

It's pretty clear on the award page.

To receive the MVP award, nominees go through a review process by the MVP Selection panel. This panel will evaluate each nominee's voluntary contribution to the community over the past 12 months, the quality of their feedback and knowledge, and level of impact. Active MVPs will be re-evaluated every year, and the MVP title is only valid for one year each time. Active MVPs do not have to re-nominate, but are asked to continue their sharing activities.

3. Finally. What took so long to recognize So-and-So?

1. He wasn't nominated (oops, don't forget next time).
2. He didn't share enough knowledge online and/or didn't get 3 out of 5 votes.
3. The SDL Tridion Community MVP is not an Employee Recognition Program, it's not influenced by SDL management nor is it based on customer feedback. More nominations might help, but the nominee only needs one (like meiosis).

The Community in 2013.

You can start or continue to help customers online.

• Post how to guides online online
• Share your Tridion expertise online
• Ask and/or answer questions online
• Host and/or present at user events and share the results online
• Share best practices, argue against best practices... online

SDL CMT Knowledge Sharing. Knowledge Leadership? SDL staff started 16 new Tridion-related blogs since 2011. In the last year they shared over 192 posts mostly on Tridion with lots of code, examples, and best practices. With SDL Tridion 2013 coming out, I think we'll see a lot more from SDL's staff. I also see more colleagues finding ways to give themselves permission to share.

Expertise from Anywhere. One independent group has 33 blog posts, presents at events, and hasn't yet made the partner list. Customers and various consultants ask some of the most interesting, helpful questions on StackOverflow. Any individual can recognize the 7 wins in a vibrant technical community and start. Anywhere. Anytime.

You don't need my permission to share. But if you want to improve your SEO, get recognized in the community, and keep up with SDL's employees and experts-from-anywhere, you might need to give yourself or maybe your staff permission to share and participate online.

The community has helped me countless times. The community needs help. I'm not here to tell you to share. But consider asking yourself, “What can I share? How can I share? What will I share in 2013?”

Easy. By Google.

Also easy. In case you don't like Google.

Don't like writing?Got a question?Maybe an answer?

Types of Tridionauts

Portugal is known for great sausage. Unfortunately so was the SDL Tridion MVP Community retreat. Don't make me explain "sausage fest."

Despite such gender homogeneity, the 2012 group represented:

• Technical consultants from small to large partners and independent consultants
• Internals (Community Builders or MVPs that work for SDL) with roles in R&D, FC, TAM, Sales, and TC
• Various countries of origin including Netherlands, Spain, England, and the East/West US Coasts

Are techies with a Y chromosome more compelled to share? The retreat was missing:

• More non-technical consultants
• Non-consultants or customers
• A female perspective

More customer employees will share eventually. Generation 2020 may transform previously closed organizations by introducing millions of digital natives to the workforce. Some SDL Tridion customers already share, ask, and engage more than some internals.

Roles may diversify as hundreds more learn SDL Tridion and existing resources gain experience. All-in-one consultants will continue, but notice how the larger Web digital landscape has changed quickly; there are jobs in a variety of roles:

• Graphic design, client-side programming, and back-end development
• Database and system administration
• User experience, SEO, accessibility, and content strategy

So more types of Tridionauts will share, but will female Tridionauts get recognition?

I once dreamed of changing the world. My Global impact is nonexistent but I've had a wonderful and unique opportunity to contribute to, and possibly change, at least one software community. As my daughter goes from four-to-fourteen, I'm hoping to change the world again.

I'm probably a poor role model for her or young women interested in this type of knowledge work. Luckily Tridion-the-software attracts the brightest and creative problem-solvers and it's a matter of time before someone else, in a different role, possibly of a different gender, changes the community yet again.

So by all means, share or encourage others to share and then consider nominating less sausage (link opens email) for your community representatives.

Update (2016): since this post, we've had two women win the SDL Web/Tridion community award. It's better representation, maybe even high if looking at the gender ratio across the entire community, but we still need to promote and encourage Tridionauts of all types.

SDL Tridion Resource Dynamics

The SDL Tridion technical community is small (but growing). What happens when you bring Tridion resources together? Let's start with one or two Tridion techies and then poke fun of the MVPs.

One

A technical resource outside of work might surprise you. Several of my current and past peers are chefs, musicians, dancers, or martial artists. On his or her own, a so-called geek might be more creative than you would have thought. But bring two geeks together...

Two

Two things happen when you bring technical resources together. Let me explain the first thing with some Calculus humor. Where number of techies is "x" and "f of x" is the probability of Happy Hour:

The limit of f of x, as x approaches 3, is 100%. I won't translate to avoid scrutiny.

The second thing is talk eventually turns to life, philosophy, and software (mainly Tridion), in no particular order. At some point, one of us will walk away saying, "_guys_, I'm hungry. If you care to eat, see you at ..."

More

One of the "benefits" of winning an SDL Tridion MVP or CB (for SDL internals) award is access to other (all current and past MVP) Tridion resources. Here's a synopsis. These aren't actual quotes, but more of a flavor of what a typical online Tridion chat (currently Skype) looks like.

Jeremy: I released that extension I was working on. Time for a vacation!
Jaime: You get breaks?
Puf: More code. Less talk.
Dom: Talk is cheap. Let me tell you about my Tridion 5.2 project.
John: Help! I broke Tridion.
Jeff: Did you perform maintenance? What's the error?
Vin: @John did you get my PDF called, "So you broke Tridion?"
Alvin: I blogged, tweeted, and made a wiki update today!
Chris: You guys talk a lot. Anyone going to see my Gartner-Forrester symposium presentation?
Peter: I checked in a new PowerTools base class, an installer, and automated troubleshooting tool.
Albert: I just extended it.
Jules: It's not the length that matters. Hey are we doing that new thing online?
Nick: @Albert that was cool. I just blogged about it.
John: @Jules, should we get permission?
Bart: Sure, let me ask myself... "Self, can we?" Yes, we can.
Nuno: I posted on the new thing. _Yes_ to more sharing.

[100 messages later on a random Tridion-related topic, X]

Nuno: Guys, why don't you _do something_ about X?

I tease the group, but despite the sometime unending stream-of-consciousness-type sharing, the same people have done the following:

• Members of the group answer sincere newbie questions. Sometimes they don't have a choice, I keep asking questions.
• It helps to bring a stack trace if you have a technical issue (it's community building, not support, though the group can't help but "talk shop").
• The same people asking questions will turn around and help on your problem, question, or scenario (e.g. Content Bloom owner, John Winters took some time to explain some JavaScript + CSS class magic to me recently). Yes, I contradict the last bullet. It's a complex group dynamic. 
• When possible, to help each other we'll open virtual machines, confirm a solution, and get the answer back to a customer, support, or the community (via the Forum, Twitter, a blog, Google Code).

The best part IMHO is validation that no one can know everything. The group will debate and joke but still share their perspective and offer practical help. They're paradoxically modest, freely and humbly admitting they're not even the best resources (most of the time).

The MVPs are however, by definition, the most vocal.