Skip to Content

I originally posted this content on my own blog* over here: Thoughts on what’s next for the SAP community. I’ve since been encouraged, not least by folks managing this community like Jerry Janda, to post that content here too.

I don’t usually cross-post, but this is perhaps important enough to make an exception. So here is the post, in its brief entirety.

Thoughts on what’s next for the SAP Community

This evening I watched a short video, What’s Next for SAP Community?, with Björn Goerke, Chief Technology Officer and President of SAP Cloud Platform, and Thomas Grassl, Head of Developer Relations, laying out the vision for the SAP Community. Here are some brief Friday night thoughts.

I have been involved in building and helping the SAP community (small ‘c’) grow for a long time, from mailing lists in the 1990’s, through co-creating the original SAP Developer Network and seeing the changes through the SAP Community Network to become simply the SAP Community (see The SAP developer community 10 years ago, a post from 2005).

It’s been great to see Developer Relations and the SAP Community moving under the wing of the office of the CTO, and with the backing of CEO Bill McDermott, there’s certainly more than enough torque and momentum upon which to build.

The chassis has undergone some significant welding in recent years, but the current remodelling, while still needing some love and attention, is so much better for content creators. And without content, there is no community. I’m hopeful that the chassis and bodywork will go from strength to strength, especially with the recently announced 2018 redesigns, and we see the rebirth of interconnectivity.

What struck me most about listening to Björn and Thomas on the video just now was my perception of the sense of community being the strong, implicit anchor for the message and the vision. So I decided to transcribe the video, to perform a simple text analysis.

The transcription is here, and we can see from some simple textalyser analysis that the perception wasn’t too far off – the top five places for word frequencies in the entire piece are (with occurrences in brackets):

1: “our” (12)
2: “community” (10)
3: “sap” (6)
4: “how”, “new”, “customers” (5)
5: “need”, “think”, “help”, “content” (4)

Now it’s a short dialogue so perhaps this analysis needs to be taken with a pinch of salt, but it certainly occurs to me that the core message, and the core task, is getting people and knowledge connected.

We can do that, can’t we?

* yes, blog. Short for weblog. Often an entire website section (like this one), with a multitude of articles. Not an individual article or post. A blog is a collection of posts. Not a single post. Got that, community? 🙂

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Jerry Janda

    Wow, that Jerry Janda guy sure is pushy. 🙂

    I’m glad you shared your blog…er…I mean blog /post/…here. As I noted in my tweet, “Your perspective on the video is a great read.”

    –Jerry

    (6) 
  2. Michelle Crapo

    Nice blog! Great information – true information. Without “you” posting there wouldn’t be a community. I love the breakdown.

    Thank you!

    Michelle

    That Jerry guy must read an awful lot in a day.

    (3) 
  3. Jelena Perfiljeva

    People who see a corporate video and think “hm, let me run this through the text analysis and post the data and results” is what makes SAP community a great place. 🙂

    I’m curious though – what did you use to transcribe the video?

    (2) 
    1. Joachim Rees

      I’m curious though – what did you use to transcribe the video?

      I had the same thought! There is probably ‘something’ that could do that for you I’d imagine.

      I didn’t know about textalyser.net, so I think that alone was a good takeaway.

      best
      Joachim

      (1) 

Leave a Reply