The Next JBoss posted by Chantal Yang at Monday, March 30, 2009

One of the most common goals we hear from prospects is, "We want to be the next JBoss." The inevitable follow up question is, "How did you do it?"

I like to say "with a lot of blood, toils, tears and sweat," but that would border on sentimentality. The truth is, JBoss in 2003 had a lot going for it already: good, free technology (or, in more famous words, "It's free and it doesn't suck"); a growing community; and a firebrand of a chief executive in Marc Fleury.

What PR provided was discipline, consistency, and a soapbox. The rest was history.

You could argue that open source developers were the original online social networkers. With that in mind, there were three things that JBoss did right that went against conventional PR wisdom at the time, but are more applicable than ever today, especially given the rise of social media usage.

First, JBoss always put the community first. Under the open source mantra of "release early, release often," JBoss developers didn't wait for sign off from PR to release code, announce it on community mailing lists, and blog about it. This was initially a major headache for PR, as I often took calls from reporters asking me why I hadn't told them about such and such a release. And, as JBoss expanded the number of projects over which it had direct stewardship, this disconnect only exacerbated.

The PR team initially tried to control this, but communities don't work this way. Traditional PR often focuses on controlling the flow of information when it should focus on the content itself, regardless of whether it is delivered through press releases, interviews, blog posts, podcasts, or presentations. Once we accepted that, we used the the blogs (remember, this was 2003!) as another way to get information out that supported messages of innovation, community, and participation.

Second, JBoss did not fear controversy. We never attempted to "censor" Fleury; his strong opinions, enthusiasm, and colorful choice of words gave him an authentic voice that no amount of PR prepping/media training could ever create. But those strong opinions--not just from him but from other JBossians--sometimes rubbed others the wrong way, inviting controversy after controversy. While each episode was challenging to go through, JBoss always came out of it smarter than before.

It's always a good idea to take the high road, but there are times when it really pays to be scrappy. If you're the David in a hot market with lots of Goliath players, you can't always turn the other cheek. Those willing to put up a good fight have a fighting chance.

Lastly, JBoss was incredibly metrics-driven. The company bootstrapped itself for almost four years before taking on venture financing. PR, as Fleury liked to tell it, was JBoss' biggest investment. To track this investment, we established detailed reporting that looked at every article, every positive and negative word, and every key message we wanted to get across. This was done on a quarterly basis, and when things didn't track, we adjusted the program.

Fast forward that five years to 2009 and you will see that metrics is more important than ever. We're in the midst of a recession, so measuring spending vs. results is essential. Though PR is still more art than science, there are sophisticated tools now to make reporting that much easier and that much more valuable to the company.

If you're doing PR today, you know it's a changing business. JBoss' success was a product of its time, though it offers some lessons that stand true today. You have many more tools with which to build community around your offerings and measure adoption and visibility. You may not be the next JBoss; but you could very well create your own category and become the benchmark for startups to come.