Skip to Content

I enjoy the way Mark Finnern ushers out 2006 with his blog Collecting the Best Of SDN and BPX in 2006 and his thread: Best Of 2006 … That approach represents a very positive method to look over a past year and an uplifting closing note for the end of a calendar year.

In my own culture and tradition, the end of a year is also a time for reflection and soul-searching.  How to improve communication and listening?  Has any behavior offended? Where was patience lacking?  Where were the faults and errors? How best to extend a hand to community, colleagues, associates, with a pledge for amends, renewed commitment, enhanced delivery of services?  There are, in some cultures, even promises that are called “new year resolutions”.


These are usually made between self and self, but since we are in a very public domain, it might be interesting and even beneficial to externalize some of these from a community perspective. Often declaring our resolutions help generate them into being

Our BPX launch, for example, aroused interest and curiosity in quite a large segment of our existing SDN population and attracted an incredible 73,000 + registrations many of whom are net new visitors to our environment.

If we look at the candid comments of some concerning the launch and what being a Business Process Expert community member means, it is clear that we are very much in an evolving state with plenty of opportunity for growth, development, and improving intelligibility.  While the role(s) of a Business Process Expert apparently resonates with and intrigues many, we have much work to do in creating more coherence, an enhanced taxonomy, a content and collaboration pipeline and an atmosphere that draws the community to the website, helps peers to interact and provides value to all who choose to participate.

So what could be some resolutions?  Personal ones could be to intensify the listening and offer more support to newbies.  Creating more beginner corner and help guides to ease people into the collaboration venues: blogs, forums and wiki help and support.  Creating a series of opportunities for industry specific practitioners to “meetup” in live chats or new forums.  And quite possibly, working at injecting some spirit of fun and entertainment into the environment making learning and sharing of learning enjoyable.  Another angle  is to see how to truly create a “one team – one enterprise” as Paul Taylor eloquently expressed it in a forum post.  He also said:

“Often the focus within SDN is more orientated to the technology side without a clear understanding of the business impact or implications of doing so. Therefore perhaps we also need a “Meet the Business” corner for both the indispensable IT folks to meet the dependable business folks so that we all can share common ideas, thoughts and the issues – risks of new paradigms such as ESA – SOA. Maybe then we can agree on the role of BPX as well!”

Those sentiments resonate with an appropriate sense of “peace to all, goodwill toward all” commitment.  That’s also a nice hope with which to end the year

To report this post you need to login first.


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

  1. Former Member
    Now that the concept is out, hopefully we’ll see it materialized in the customer and partner community in more tangible forms. Shai is talking about 10,000 customers on Netweaver Business Process Platform by end of 2007. Assuming customers are doing something (prototype, mini or full-blown projects) with it and with a minimum of one resource, that’s at least a potential 10,000 real BPXs end of 2007.

    That’s an action-packed year ahead of us. I don’t know how yet but it feels like it. Looking forward to it.

    1. Marilyn Pratt Post author
      Thanks Andre, and also for being one of the first to embrace the idea of this community.  Your hopes reminded me of one of our challenges.  Rather than “wait” and see how we evolve certification or how we illustrate the process innovation we all want to embrace, we will need to see real examples with real projects with real people sharing real experience: the good, the bad, the ugly.  And this is a slightly new paradigm.  It isn’t just a matter of us creating some “best practices” or leading practices or other rather academic BPX guides.  It means a shift in responsibility and thought leadership from the traditional expectations of “us” delivering content and expertise to the more community “we” create the context and the value.  “We” should expect in 2007 that much of the best materials are “our” responsibility…we, meaning the entire community.  Let’s work to ensure that “we” don’t disappoint ourselves.

Leave a Reply