By now you'll be aware that mark.yolton/blog/2011/12/09/the-new-scn--launch-now-planned-for-early-2012, and you may have seen mark.yolton/blog/2011/12/10/the-new-scn-an-update-on-our-delayed-release. I do make reference to both of these further on, please read them before continuing. I also want to make clear that I have no special inside knowledge of either the SCN Development team or the Jive 5 release that the new SCN is based on. Everything I write here is drawn on publicly available documents and conversations.
Now that's out of the way, my first reaction at hearing about the delay was disapointment, but I do have to say that when I read Mark's second post on the delay, I was delighted at seeing someone (Mark, in this case) take ownership of an onerous decison so completely.
Some will ask: Who’s responsible for this delay? Who needs to be held accountable? Who can we point a finger at for this delay? Easy answer: the buck stops here, with me.
From an SCN user and stakeholder's perspective, there's two ways to look at the delay. One is the social media and communication aspect. To be blunt, Mark's first post on the matter looked like it was written by someone with a PHD in PR. Lots of words, but little content beyond the absolute necessary. However, the second post (just over a day later) was worth the wait as it gave a clear precise and concise message about the issues, that was directed both at me (a user and stakeholder) and to the support team behind SCN. Regardless of how SAP management or Development is perceived outside the organisation, these words will be seen by the developers and support teams behind SCN as an act of faith in them, as an acknowledgement that they did their best. Both posts acknowledge the effort put in by the various teams, and his choice to 'stand them down' is a welcome recognition of reality that many others would do well to follow. It is obvious from Mark's tone that while he acted in consultation with others, the final decison to delay was his and his alone (for better or worse), and that he is willing to stand by that decision without playing the blame game.
As far as I'm concerned, there will be some loss of face involved for the SCN Project managers; after all, this upgrade has been promised and planned for a long time now. According to Dennis Howlett, the issues with the new system have been known for 4 weeks or more. On the other hand, Thomas Jung (who had early access due to being a moderator) gave no indication of such problems when discussing the new system on the most recent Enterprise geeks podcast. Of course, the conspiracy minded will remind us that Thomas IS an SAP employee, but one thing he points out is that SAP are a major Jive user and customer. While Mark is at pains to seperate the functional issues with the new SCN from the underlying Jive functionality, I'm suprised at Jive's absence from the story; As the developers (and presumably experts) in the underlying product, they had a unique opportunity to highlight risks around the conversion and search indexing. Bear in mind that I have no way of knowing if advice was offered, the quality of the offered advice or what part if any of that advice was followed.
Another perspective, that the majority of the SAP community seem to be taking, is that we are talking about technical issues, with some management problems on the side; Understandably so, as many of us have war stories about, say, SAP software (just off the top of my mind !!), that is meant to work out of the box but doesn't (Reading MichaelKrigsman is always a good reminder of how bad projects can go).
Curiously enough, this takes us right back to an entirely different Social Media view of the issue from where I started. The pragmatic decision (which I do agree with BTW) is that at a minimum, the user experience of the new SCN has to exceed that of the current SCN. At the moment, the new SCN would be a retrograde step, so releasing it would damage the community. However, there's more to migrating to a new community system than just upgrading the look and feel. According to Mark's second post, there are a lot of issues around data access and integrity, such as data migration, search indexing, security and so on. As far as I'm concerned, these are core components of SCN. In other words,
The 'User Experience' is not the value in the Community.
I don't come here for bells and whistles, I can live with unreliable interfaces (hey, I still remember the old grey screen SAP GUI). This community is invaluable to me because it provides authoritative information on how to resolve speciifc problems, not the theory, not the http://help.sap.com pages (written before the first customer installation is started), but real answers from people who have been there, done that, scars, t-shirt and all, and in return I offer my thoughts, views and experiences. In other words, while the tools demonstrated in the new release of SCN will make my life easier, the value they add is insignificant when compared to the information value of SCN.
By refusing to compromise the data, the real value in SCN, Mark made the right decison.