Cultivating Customer Communities

One of the disadvantages of writing an article like 8 Bold Resolutions for Marketers is that you simply can’t go into detail on each of the topics covered.  The 5th resolution, “I will carefully cultivate my customer community,” was based on my extensive interview (below) with Mark Yolton, SVP of Marketing at SAP.  Mark is in charge of the extraordinarily successful SAP Community Network and not surprisingly, can and does make a great case why other marketers should cultivate their own customer communities.

DN: What do you think have been the keys to SAP’s success with the SCN to-date?
First, we began with a targeted audience and a focused mission: to help developers achieve success with SAP’s platforms and solutions. Only after we had critical mass in that audience did we expand to include a broader base, with the expansion of the target audience driven by the community itself, and features and functionality prioritized based on what our target community members wanted or needed.  Essentially, we were pulled along by serving them, rather than pushing them into new directions we thought interesting, with the success of our community members always as our guide.  Over time, we expended from the base of developers, to sysadmins and IT professionals more broadly, then to business process experts and project managers who straddle IT and lines of business, to business analysts and dashboard designers, and then to include university students and professors – all drawn by community member and market needs.  We moved from basic discussion forums which were appropriate for basic Q&A, to longer-form blogs, to a wiki which is more flexible for projects and work groups… and included aspects of gamification, a career center with job board when the economy took a downturn, to an outside-in innovation crowdsourcing space. Constant evolution through monthly updates and larger advances, based on active listening and responsiveness to community feedback.

DN: What are the real advantages of having a user community?

The advantages depend on your vantage point…

Our individual members report that they are more productive, finding answers and solutions faster, and of higher quality, by being able to consult with other customer and partner members of the 2 million-plus SAP community.  Individually, they elevate their expertise, and put it on display where the quality of ideas – rather than other factors – helps people rise to the top and get positive attention.  Their careers accelerate, their professional horizons expand beyond their city, or country, or industry.  On a more visceral level, there’s also an energy that comes with connectedness; members are energized by each other, the back-and-forth of interaction, the excitement and enthusiasm, and the feeling of being part of something bigger and more important than each of us individually … it’s a contagious excitement and an immeasurable but palpable sense of belonging and shared value.

Our SAP customer companies who have employees participating in the SAP community gain open access to subject matter experts for fast implementation and issue resolution so their projects are completed faster, and with higher quality, which helps them reduce their  operations costs and total cost of operations.  From the connectedness across industries and across global commerce, they are able to increase their business and technical knowledge and insight, make business connections within the vast SAP ecosystem to expand their market influence, and have an easier time discovering, evaluating, and accessing SAP and our partner solutions for more advanced implementations. They even have a greater ability to keep up with emerging trends, and to influence SAP and its ecosystem through participation and connections.  And prospective customers in the solution evaluation cycle have the ability to interact with active SAP customers to get their unfettered feedback and advice – and to get a sense of the extraordinary value and unique benefit the SAP community provides.

SAP partners have the opportunity to establish themselves as subject matter experts, and to gain access to the entire global universe of more than 170,000 customer accounts in our installed base for more fine-tuned market insight as a way to focus their solution offerings, and to keep an eye out for sales opportunities.  They can forge relationships with other SAP partners for solution co-development and joint go-to-market, and even post-sale they can call upon a wider set of experts to help speed problem resolution.   We can also demonstrate SAP’s unusually strong commitment to the SAP partner ecosystem through all of these efforts, as well as our work and investments to generate and pass along leads to partners – it strengthens those partner ties with SAP and the value of partnering with SAP, so we gain more of the best partners to augment and extend SAP’s core.

For SAP as the host of the community, we gain faster adoption and ramp-up whenever we introduce new or upgraded products and services to the market, since our reach and influence are huge and immediate.  As a company, we gain speed, agility, better decision making, and reduce our risk because we gain rich insights into what our customers really want and value, gleaned through our direct connections and fluid feedback loops and listening posts.  We can improve  product and solution quality through our customers’ direct outside-in feedback on our products, services, processes, and  customer experiences.  We reduce the cost, complexity, and time to provide core support while maintaining high quality – and can plow those savings back into better community mechanisms and product innovation.  Those and other forms of interaction lead to higher customer satisfaction and loyalty, better customer retention, up-sell and cross-sell opportunities on the top line, and efficiencies through cost savings on the bottom line.

DN: Would it be as useful (to you or your members) if it wasn’t so large?
There’s a certain critical mass that needs to be built in order for a community to be vibrant, diverse, distributed, and valuable.  If we had a very simple product or a homogenous market, we could deliver benefits with a small member base.  But SAP is a global company, with a vast array of products and solutions, operating in nearly every country and territory on the planet, every industry, serving every aspect of global commerce.  In order to serve our diverse market, we need a very large member base to gain access to experts in everything from Finance to HR lines of business, banking to mining to consumer-goods industries, in Europe and South America and Asia, and across every solution and sub-module of SAP’s portfolio.  We hit the tipping point at about a million individual members several years ago, and we continue to grow at about 40,000 new members each month.  Those kinds of member numbers give us depth and diversity of expertise in just about any relevant topic of interest to our SAP community.

DN: If you were advising a fellow CMO who was thinking of setting up a community today, what would tell him/her? Any shortcuts?
Without hesitation, I would advise any other CMO to lean forward and start building their community without delay, because the value far outweighs the cost, and it is the future.  However, it’s not easy, simple, or inexpensive, and it’s not something that you can build, launch, and then let go.  Community is part science – the platforms, plumbing, apps, and underlying infrastructure – and part art – the policies, practices, programs, and people-oriented components.  It’s uncharted territory, so you’ll need to navigate areas of company rules, emerging legal precedents, daily new learnings, and plenty of antibodies.  It’s not something that you can short-cut; authenticity and transparency and long-term relationships and commitments are key. Get an expert on board who has experience, form a core team to execute, and be personally involved.

DN:  Lots of communities are started (like LinkedIn groups) but very few gain traction.  Why do you think that is?
Communities take work over the long-term, and it’s clear that not everyone who starts one is expecting, anticipating, or willing to put in the time and effort to make them work.  There are hunters and farmers, and communities require aspects of both … hunters to undertake and execute big but limited-time and scope projects, launch them, and move on … short bursts of energy, big pay-offs, motivated by the adrenaline rush of achievement and covering alot of new ground fast; farmers who will toil day-after-day, pruning, nudging, nurturing over the long-term… almost imperceptibly small moves but with staying power, persistence, and timeframes of months and years.  I believe that some communities fail because they don’t take the longer-term view, expect results too fast, and don’t deliver enough value to their target audiences to warrant their members’ continued attention and deep engagement.

DN:  How do you see communities evolving in the next few years?
The platforms and tools have evolved, now, to the point where almost anyone can participate; you don’t need to be a tech guru to participate.  This means that for companies like SAP, we can move from technologist-based communities, to business-oriented communities, right on to communities of c-level members.  We will see both public and private areas where open discussions can occur, whether shared with the world or with a select group of trusted members.  We will see more companies hosting communities of their customers and partners, where those groups really set the agendas, guide the company to build products or to set standards that better suit the needs of the customers.  We will come to expect, as consumers and customers, that the brands we do business with provide the benefits to us of online communities.  And companies will see that the benefits of hosting customer communities will differentiate them, and then will be an expected way of doing business, with tremendous value to everyone who participates.

The Anatomy of a Social Business Community

Most brands dream of having a vital user community that creates on-going dialog between the brand and its customers.  But few have succeeded on the level of the SAP Community Network which is led by Chip Rodgers.  I interviewed Chip for an upcoming case study on FastCompany.com and in advance of his presentation at the B2B Corporate Social Media Summit September 28/29 in Philadelphia.  The following is my Q&A with Chip. Admittedly, it is long one but well worth studying if you are thinking about creating your own community.

DN: Can you give some background on the SAP Community Network?
The SAP Community Network actually started about eight years ago, and so we’ve had a little bit of time to ramp up. We currently have about 2.5 million members, and it’s a very active community. We get between a million and a million and a half unique visitors a month and about 3,000 to 4,000 posts a day in discussions and blogs and wiki pages.

DN: Tell me about the membership of the SAP Community Network.
It’s about 50% customers and then another probably 30% partners and then we have a large group of employee members as well. There are also independent contractors, developers— just people who are interested in the SAP ecosystem. It’s open to anyone that wants to join. There are a few core pieces of information that we ask for and obviously unique email address.

DN: From a content standpoint, with all these members, are you constantly feeding this beast yourself or is it somewhat self-sustaining?
I have two teams. The content team works with about 400 SAP experts to feed the community with a lot of our formal content: white papers, articles, solution briefs, eLearning, videos, etc. I have a team of about 12 working with a group of stakeholders that are SAP solution managers or folks from support or people in solution marketing that have all the actual information, the expertise and are actually the ones that are building the content.  I’ve also got a group of six that are managing the community-generated content, so that’s our blogs and forums and wikis, and similarly they’re working with a group of about 700 moderators that are in the community.

DN: You know the scale of this community is kind of mind-boggling. Can you draw a direct line between your activities and your ROI?
More and more we’re able to show that there is a connection. We’ve gotten to the point where we’re running a lot of webinars on different topic areas, different product areas. We’ve really cut back with list-buying and some of those traditional marketing costs to get people to come in and listen to a webinar, learn about a new product area, and then take the next step as a pipeline opportunity.

Drew: You started this in 2003, which predates Twitter and Facebook, and I’m curious how you brought [them] into your community. Are they adjuncts or are they truly integrated into this?
Having this background of engaging with the community, when Facebook and Twitter came along, they were natural extensions and ways of engaging with the community. We now have a group that is really focused just purely on social media. We work together to leverage the community and our social media activity. A little bit more specifically, we do a number of things like, if you post a blog in the community, we have an RSS feed to a Twitter account so it automatically tweets the title of the new blog that was published. We think of Twitter, Facebook, LinkedIn, even YouTube, as kind of extensions— concentric circles around the community— to reach community members and try to get the word out.

DN: Was it tough in the beginning to get management behind the community?
We laid a lot of groundwork for social media within SAP. We were fortunate that we had a board member that thought it was the thing to do and defended it every time. When we first opened the communities with blogs and forums and wiki, some executives were nervous – saying, “why should we create a place just for people to complain?”  But our feeling was that there are plenty of public places for people to criticize the company, why not create the place where we can be a part of the conversation?  And fortunately, our board defended it.

DN: Has the community ever defended the brand?
What we’ve found is if you work with the community and build trust, and you’re open about how you engage and you answer questions and address issues that come up, the community will support you. It’s not always SAP that has to defend [itself] when someone goes haywire.  We see this all the time where somebody says something negative or even a little wacky in the community, and your knee-jerk reaction might be, we have to answer that. And what ends up happening is a lot of other community members come in and say, “Well you might have a point here, but this is way over the line.”  The whole group kind of comes together.

DN: What are the other ways that you report on the success, or what are the metrics that you guys look at to rationalize your existence?
We actually have a few metrics. One is just purely in terms of activity and contributions in the community, page views, member satisfaction, things like that. We do those transactional kinds of things with the community to makes sure that we’ve got good content that people find interesting, so that’s one level of measurement. One of our KPI’s is driving activity to those webinars that turns into real pipeline opportunity dollars. It’s traceable back to activity in the community.

The third is a part of the community called SAP EcoHub (http://ecohub.sap.com). It started as an online store for our partners to set up storefronts and sell their products.  We’ve expanded it to include SAP products as well. It is connected to the community so that if there are conversations going on about certain product areas, we have links in those conversations going back to EcoHub. If you happen to be on a conversation you can see the product.  That is an increasing channel for us, for our partners and for SAP to drive revenue directly.

DN: You have a few people that are in the conversation, how do you make sure that they are all on brand?
We do have a social media corporate policy, guidelines, best practices case stories, and training courses.  We have an active internal social community, so there’s a lot of discussion and activity and assets [and] resources available to people when they start to put a toe in the water in social media.  A lot of those principles are similar to when anybody goes for media training, for example.  There are a few guiding principles like, “Don’t talk about things that you don’t know about.” And stay away from forward-looking statements like, “We’re going to do this,” or “We’re going to do that.”  But otherwise I think a lot of it is just common sense.

DN: You have this substantive, meaty community where people are actually participating, and you’ve already proven its worth and along comes Twitter and Facebook. Has there been conflict because [social media] is a separate group, and it’s not part of your group?
There is a social media group driving policies, best practices, training, reporting, and other aspects of social media for SAP, but we’re all part of marketing. It’s interesting because community and social media are somewhere in the middle of several traditional corporate groups.  It’s a little bit of marketing; it’s a little bit of communications; it’s a little bit of support, there’s an aspect of listening for product roll-in, and there’s an aspect of sales channel. So there are always discussions about where does it really belong. But community and social media are about people connecting – so if you’re doing it right, the entire organization is responsible for connecting with customers and partners in their respective areas.  So yes, we are separate groups, but we have a communities and social media council of leaders from each of those groups as well as social media ambassadors embedded throughout organizations and geographies at SAP.

DN: With 2.5 million community members, your activities are dwarfing anything SAP might have on Facebook [or] Twitter. How as the marketing/social team dealt with this?
We actually work very well together and leverage each other’s strengths on a nearly daily basis.  But it’s interesting that when we were first having discussions about Communities joining marketing, our CMO was saying “There’s an opportunity to learn from what Community Network has done.   We need to have more conversations and engage with our audience. We can’t just create another email blast with a bunch of creative and offers.”  It’s been a cultural change within the company.

DN: Have your content development efforts had a measurable impact on SEO?
We are very much SEO champions, and it’s been through experience. We had to figure out what to do on all those pages to do better with search engine: where things are laid out; how are we tagging pages; what are the titles in the pages, how are URLs formed. So many things factor into it. We had this three-month project just to go through everything and then get the word out to all the stakeholders and get everybody to update all their pages. I mean it was dramatic; We were bumping along at around 400,000 unique monthly visitors, and all of a sudden we shot up to like 900,000. It was unbelievable— just blew me away.