Sandy attended a sneak peak of Blueworks Live recently, and has reported on it in her blog:
They are trying to reinvent the public BPM community, while avoiding the problems that they perceive with other vendors? community sites:
- They are mainly product support sites
- They have high membership numbers, but low participation
- A majority of the information is from the sponsor company
- The customer perception is that these sites are proprietary and biased, and that there?s already too many sources of information on BPM
I think they have some of the right ideas here - they've identified legitimate problems with the current approaches of these communities - but there's still some work to do on defining what a healthy BPM community consists of.? I think they have a couple elements right, such as:
1.? A common thread tying it all together: BPM / Process
2.? A "safe" place to share (company spaces, or even more granular spaces)
3.? Don't try to reinvent twitter, just leverage it
But the mechanics will take some work.? As Sandy points out, pro-level users of Twitter aren't going to rely on BlueWorks Live to show them interesting tweets.? Having said that, however, how many people are going to add a column for "#bwlive" to their TweetDeck?? So it may be somewhat additive to the experience, but time will tell. Sandy says "It?s probably good for the Twitter newbies, since they haven?t figured out groups, hashtags or Tweetdeck yet; maybe that?s more representative of the expected user base."? I think that's probably right - more representative of the expected user base.? Most of the personnel I work with don't use Twitter at all yet.
Like Sandy, I think their blog section needs to pull in content from other sources.? I think they could curate this somewhat by reaching out to prominent bloggers (like Sandy) and ask for permission to republish interesting posts (or set up a submission process for authors to bring relevant posts to their attention).
I think the real question for BlueWorks Live:? is this the Minimum Viable Product offering, to be improved upon in future releases, or do Phil and IBM believe that it is fully baked?? I believe it is the former, and that the intention is to keep releasing frequent updates and improvements, as they were doing with Blueprint before.
You can see our previous coverage of this topic here (our sneak preview was a little earlier, but we're looking forward to just laying hands on the product and taking it for a test drive on Saturday).? BlueWorks Live announcement here.