A few months ago, an SAP employee who was a well-known Twitter presence left SAP. It was widely reported that this person was part of SAP’s 3,000 person layoff that occurred during that period. What I found interesting (though hardly surprising) was the aftermath to this event on the blogosphere. The subsequent “commentary frenzy,” much of it rampant speculation, reminded me that amidst a blog-and-Twitter-hypefest, the essence of a story can be obscured. At this year’s Sapphire, I had a chance to sit down with a couple of the leaders of SAP's social media presence. My goal? To get a clearer sense of the realities beneath the hype.
Before I share a few thoughts on what I learned in Orlando, it’s important to separate what SAP is doing on the product side versus the community interaction side. On the product side, SAP continues to “socialize” its applications by embedding unstructured data access, customer “sentiment analysis,” and other Web 2.0 approaches across the product line. Other social networking product experiments are underway within SAP, without a formal connection to product rollouts. The product side of social media is *not* the focus of this blog entry. For that side of the issue, Susan Scrupski of ITS Insider has already written a detailed post on her views of SAP’s ongoing “socialization of the enterprise.”
One of the criticisms that came out of the pre-conference blogs was that “SAP doesn’t have a social media strategy.” That much is dead-on accurate. SAP’s aggressive, sometimes frenetic approach to putting flags in the ground of communities like Twitter, LinkedIn, and Facebook is not, in most cases, centrally coordinated as part of a documented strategy. This lack-of-strategy leads to the phenomenon of certain individuals/areas within SAP popping up on Twitter, seemingly at random.
For example, “SAP CRM” is on Twitter, and doing a pretty solid job, in my opinion, of being conversational and not just Tweeting marketing verbiage. But you won’t find SAP SRM, SCM, or PLM on Twitter. I also like what sapbrasil is up to, but there aren’t many geographic equivalents on Twitter currently.
The problem with not having a coherent strategy is that there aren’t many rules of the road or formalized best practices, which leads to the occasional frantic burst as new SAP personalities hop onto Twitter and get a brisk lesson in the differences between pushing product and engaging in conversation. But Twitter has an effective way of self-policing stuff that stinks. Unless you’re a celebrity, if you don’t have either good information or good conversation (hopefully both), no one who matters will follow you.
Yes, the “SAP doesn’t have a social media strategy” argument is fundamentally correct; two of SAP’s leaders in social media voluntarily conceded this in Orlando. But here’s where the blogosphere mostly got it wrong: just because there isn’t an overall strategy doesn’t mean that some of the “legs” of that future table aren’t already well developed, and well run within their context. Consider a key component, perhaps overlooked because of its obviousness: The SAP Community Network, or SCN for short. Despite the inevitable growing pains, SAP is ahead of most enterprise peers when it comes to online community building. A published strategy may be lacking, but six years of trial and error on SCN, from managing wiki disputes to addressing overly commercial blog postings - while 1.6 million members buzz through the site - is far more valuable than a white board exercise.
Beyond SCN, there is the SAP Mentor initiative (disclosure: I am an SAP Mentor). Although the SAP Mentors are not required to be on Twitter, many of them happen to be. To find them, follow @SAPMentors on Twitter, and then browse through the SAP Mentors that Twitter Id is following. SAP Mentors are also active on Facebook and LinkedIn; many of them are SCN stalwarts also. SAP Mentors are an unruly bunch; they can be as tough on SAP as any other blogger or analyst. To empower “evangelists” who do not consider themselves as such, and would probably reject such a term, but who are well informed on SAP trends by virtue of the initiative – that’s a pretty brilliant effort on SAP’s part. I don’t know of an equivalent program at a large enterprise vendor.
Similarly, SAP’s Blogger Relations program, increasingly tied into the Mentor initiative where appropriate, is another means of putting influential voices front and center with SAP executives. These bloggers are a pretty ornery group, not likely be swayed by their arguments with SAP executives, but their work is certainly more informed based on this kind of access. Being part of this program, I can attest to the well-thought philosophy behind it. For what it’s worth, analysts who participate in other enterprise blogger programs have told me SAP is definitely ahead of the curve in this area.
Neither of these initiatives are perfect, but they are examples of how the apparent chaos on the surface can be misleading. It’s always tempting to make fun of SAP when a social media “noob” from inside the company hits Twitter - heck, I’ve done so myself - but it would be unfair to allow such satire to obscure a deeper analysis. In all the criticism I have seen of SAP’s social media efforts, not once have I seen a mention of the SAP Mentor initiative as being relevant to SAP’s social media strategy, but what could be more relevant?
When taken with the other legs of SAP’s social media approach (and I didn’t mention some successful Facebook experiments and a serious - and still growing - connection to LinkedIn), it’s clear that SAP’s lack of a formal social media strategy does not correlate with missing the boat. You could even make the argument that SAP’s willingness to encourage, or at least tolerate, an anarchic edge to these activities is actually a strength.
That doesn't mean that SAP doesn't deserve its share of criticism in this area. Here’s a better target: Why doesn’t the transparency touted in keynotes by executives and board members translate into their own involvement on SCN blogs, and possibly even Twitter? (Exception granted to CTO Vishal Sikka and his SCN blogging). Nor does that transparency necessarily carry over to crucial customer issues, the management of the Enterprise Support rollout being an oft-cited example.
Along those lines, I have personally worked with a couple of SAP product managers in the last year who intentionally avoided getting involved in public conversations about SAP product issues for fear of their own professional standing within SAP. I would hope (and expect) that an internal “employee policy” regarding participation in social media would be another aspect of SAP’s social media strategy that will appear before too long. I hear through the grapevine that one has been “in the works” for months, and may be finalized soon - let’s hope so.
Perhaps those employees’ fears of repercussions for participation weren’t valid, and perhaps those I came in contact with were the exceptions rather than the rule. But in my view, it underscored that there are cultural issues within SAP between those who want to engage in open, transparent conversations (and see their essential value) versus those who perceive such endeavors as time wasting, competitively problematic, professionally risky, or even subversive. That type of criticism against SAP is absolutely fair game, though I could say the same of many other behemoths, including Web 2.0 darlings Google and Amazon, both of which borrow more from the ruthless secrecy of Microsoft than the openness of open source. (Though Microsoft has opened up more than expected in recent months, so I may need another foil soon).
We can add Facebook to the list. The Facebook Terms of Service fiasco was instructive for SAP. SAP announced a new Terms of Service (which they call “Terms of Use” or TOU) for SCN two weeks ago; you may have noticed little controversy. That’s because SAP consulted influential community members behind the scenes, including the SAP Mentors. The result of those intense discussions bore fruit for SAP. You can bet those consultations included talks with SAP Mentor Anne Petterøe, herself instrumental in organizing the groundswell that compelled Facebook to alter its new Terms of Service after a very unflattering public outcry.
This conversation on SAP’s social media direction reminded me that beneath many overhyped blog explosions is a more serious story deserving a more serious analysis – not devoid of criticism, but bolstered by rigorous reporting.
5 comments:
Jon, as always I think you offer a well balanced perspective. It would be good to understand how we stack up versus other large companies both in our space as well as in the worldwide space
Marco ten Vaanholt
Marco, I agree.
The next step, if I were to expand this blog post, is clearly to take what SAP is up in social media/community building and contrast it with other enterprise vendors and large players are up to. If I get more info on this broader view I will definitely blog it up. Of course, a great social media strategy is only part of the equation. Not to mention there are very important questions on the ROI of such ventures that still need to be fleshed out.
Plus: if the overall corporate direction doesn't resonate with the strategy, it will simply highlight the contradictions in bolder relief. Transparency can be a beast in this way, as many companies are learning. Will be an interesting story to watch inside and outside of SAP.
- Jon
Jon,
I'd argue that what you are seeing is, in fact, a strategy. It's just an evolving strategy being developed at a very large company as we grapple with what is a new format. It's an evolving thing - more evolved in some areas, less evolved in others.
Also, it's very easy to imagine what the criticisms would be if we waited until we had a fully baked, synchronized strategy before diving in. Actually, there wouldn't be criticism, because we wouldn't be participating if we waited for a full blown strategy encompassing all geographies and application areas.
What, in your view, would SAP's social media strategy look like?
I am responsible for Web topics in SAP's Global Communications department, with a strong focus on social media technology and strategy. One of the topics we are currently working on is exactly the subject of your post, and we're getting close! :)
Engaging in existing social networks, and establishing new channels where it makes sense is something we are certainly looking at and already executing on as part of achieving our objectives, but what we don't want to do is gatecrash other people's parties, and this is one reason many are still hesitant to begin engaging.
But one thing we are very conscious of from top to bottom, is the fact that without dialogue, we will lose touch with our stakeholders. SAP may be a company that has a certain bottom line to reach like any other, but we are also a company very much on the verge of some really exciting and positive internal transformation, and that will find its way to our customers very soon I'm sure, if it is not already! Appreciate your post. I agree with marco, very well-balanced.
Best,
Sean
@Sean - thanks for your comments. It's good to hear more is in the works. On the whole I'm encouraged that those in SAP can take a post like this in stride. Part of being "out there" on these type of issues is dealing with a range of feedback, not all of it very easy to read or even fair. Internal transformation is not easy. To the degree that it happens, I have no doubt there will be positive impact on customers.
@Kate - I hear your point, definitely validity to it. I feel pretty comfortable saying that SAP doesn't have a formal strategy because the point was conceded to me by some key players inside SAP. However, another way to frame this is that having a strategy may not be all that important. I would argue that far more important than a formal strategy document would be:
1. A strong internal commitment to supporting those whose inside SAP whose role involves social media, including access to training around etiquette, and engaging in authentic conversations versus pushing product. That "support" would NOT include message shaping but would include examples of folks like Craig Ccmehil, Marilyn Pratt, and James Farrar, to cite a few inside SAP who really "get it" with these mediums. To some degree that already probably exists, but not all I come in contact with get it like these folks do.
2. As I said in the blog itself, more written guidelines, especially for product managers, so they feel more clear and comfortable on whether they are encouraged to participate or restricted, and if so, in what ways. Policy around this is probably way more important that strategy.
Beyond these two points, I feel like i've said my piece for now, and it's time to let SAP do its thing and we'll check in on this down the line.
- Jon
Post a Comment