Jim Rudden, Vice President of Global Marketing | May 8th, 2009
Last week, IBM launched a “cloud-based set of strategy and business process tools” called BlueWorks. It was clearly a soft launch – BlueWorks was announced in the 13th paragraph of a release about Enterprise Cloud Services. So you may have missed it.
We didn’t.
In particular, we could not help but notice the name similarity with Blueprint — our cloud based process mapping and modeling application that has been on the market for two years. Now, before you call me paranoid, know that we average several thousand hits to our website per quarter from IBM labs in China, Italy, Germany, Canada and the US. And we get dozens of requests for Blueprint accounts from IBM Labs across the world every quarter. So, at the very least, the IBM team was aware of Blueprint — if not imitating it. They are not the first to follow Blueprint’s lead — and won’t be the last.
Despite this, IBM has missed the mark — at least from what we can tell from the slide pitch.
Bruce Silver has had his head in the IBM Clouds lately and wrote up an interesting post on BlueWorks. The phrase that captured my attention was that “democratizing modeling and analysis” is key to creating a culture of BPM in a company. On that point, we could not agree more.
Bruce goes on to say that “BlueWorks does that”. From what we have seen so far, I could not disagree more.
BlueWorks is still “tooling for the few”. What I mean by this is that IBM is missing the bigger point that needs to be addressed – that the future of BPM is dependent on our ability to enable everyone within an organization to collaborate on process improvements, within a “BPM” framework and language.
Making the entry point to these conversations based on IBM’s Component Business Modeling methodology or introducing eTOM Frameworks does virtually nothing to get broad set of people in your company talking about how to improve their everyday work. No matter if the tool is free, applies new metaphors from social networking and works in the cloud. It propagates the message that unless you are steeped in process knowledge, you have no part in the conversation.
Blueprint, on the other hand is about reaching and giving voice to the many. It is about upending traditional process paradigms and giving organizations the tools to be successful both inside and outside of traditional BPM roles.
We use social features and an “Enterprise 2.0″ approach as well — and as such it’s tempting to think that these two products are more similar than they, in fact, are. The underlying philosophy of Blueprint still stands in stark contrast to that of BlueWorks and its maker, IBM.
Blueprint is, as Bruce Silver also wrote, “Process Modeling for the Rest of Us.”
IBM said that version 1 of BlueWorks will be available some time on or after June 26. The fully mature version of Blueprint is available right now. In fact, if you want to hear how companies have already used Blueprint to drive process improvement, check out podcasts from Symantec, PRC and West Bend Insurance.
Get your own little slice of democracy right now by giving Blueprint a spin.