We'd been waiting for Blueworks Live to go live ever since we first heard about it in November.? Now that it is actually live... well, now what?
Why, review the reviews, of course!
First up: Sandy Kemsley:
Lombardi has always been at the forefront of the integration of social and BPM, although previously focused purely on the process discovery/design phase, and the IBM acquisition has allowed Lombardi?s social process discovery to be combined with IBM?s online BPM community to create something greater than the sum of the parts. For all my criticism of IBM, they have some incredible pockets of innovation that sometimes burst out into actual product.
Overall, although there?s nothing really new about this sort of easy sequential workflow design and execution, the user interface is clean and uncluttered, and pop-up tips on the fields assist the user on what to enter. Assuming that you can wrench your users away from using email for these processes, there won?t be much of a learning curve for them to create new processes on their own, and even less to use processes created by others. If you want to see this in action, there?s a Blueworks Live YouTube channel with a couple of videos on creating and participating in a process.
But she's not convinced that Blueworks truly addresses the community goals that Phil Gilbert set out to address, nor that the different functions are well-integrated enough. Interesting comment thread where IBM explains why the tooling is different between process execution and "modeling".? I actually agree with the justification, and I don't see a reason to view the separation of complexity from simplicity as a negative.? I like doing to one place for process, rather than more than one...
Next up:? Mike Gammage:
Sandy Kemsley has a characteristically sound review on her Column 2 blog, and her verdict on Blueworks Live is downbeat.? She's underwhelmed by the Twitter integration, the public and private streams, and the level of integration with the Blueprint BPMS engine.
I think Sandy's blog comes across as downbeat because she starts with the positive (check my quote above) and finishes with the criticisms, rather than the other way around.? Mike's central criticisms:
It's Overly Democratic. Every enterprise wants its people engaged with process excellence and continuous improvement. But it's a step too far to simply say that everyone should therefore be able to create and automate process.? [...]
Well, first of all - these Luddites (tongue-in-cheek) already define, and execute processes today!? Using email, spreadsheets, and word documents.? Since they already do it today, Blueworks Live isn't making it worse - it is rather attempting to give those users more appropriate tools for the job.? He continues with point #2:
It's a Governance Headache. I don't see how governance, compliance, risks and controls can be efficiently managed in a world where an organization's processes are automated in such a decentralized way by people who may be experts in their field but are novices in process design and management.
Again, given that these folks are doing this today, we're not worse off.? In fact, we're better off because the processes defined and executed in Blueworks Live are actually tracked, keep audit trail, and feed into reports in a centralized, governable space.? And if someone is abusing it, you (as site administrator) can revoke their access or reduce their permissions.
There is a real danger that IBM's and Phil's messaging could in a sense "devalue" the process improvement expert-? or even IT experts.? But having talked to Phil about this at length- the point isn't to devalue the expertise or discipline of process improvement or IT - if the community functions well, those experts will actually become:
- more accessible
- more leveraged
- more valuable
Because it is easier for those with process knowledge to share it.? The processes that can be executed in Blueworks Live today are so simple that they simply don't require process design expertise.? And that's intentional.
I love Mike's closing argument:
In that context, it's difficult to see how Blueworks Live helps at all.? Would you dine at a restaurant where each chef did their own thing? A good menu has coherence.? A good restaurant creates the perfect customer experience by harnessing the genius and creativity of each chef de partie and their team together with the skills of the maitre d' and his or her team. I don't want beetroot for a pudding, or filet be boeuf Wellington served Thai style and with popcorn.
Actually, I've been dining at that restaurant my whole adult life.? Email, Lotus Notes databases, Excel spreadsheets, ad-hoc website forms.? Sharepoint "processes".? Each "chef" doing their own thing - with the exceptions being a few excellent process-oriented software applications.? Blueworks may not be filet mignon, but perhaps it is fast-food?
My own summary:? For "version 1" of the new vision for Blueworks Live, it is pretty good.? No one is completely satisfied, but the potential for something greater is there, and I have no doubt they'll keep beating the drum by releasing updates every 6-9 weeks.? We've already "toyed" with it, using it for a vacation request process, for example.? I was a little disappointed the reporting was buried on the admin page, for example.? But otherwise it is clean and easy to use, with a LOT of room for improvement.? The key thing will be which improvements to say no to, not which ones to say yes to.? IBM is going to have to edit itself if this product offering is going to succeed.
(Side Note: interesting response from Phil in the comments section of Mike's blog: execute to get documentation)
UPDATE:? In writing this, I omitted two other blog entries of note that I intended to include.
First, Phil Gilbert's own blog:
The arc of history is clear: technology advances always insert specialists to use new technology, taking control from the original worker. Then, as the technology matures and becomes more accessible, people with more general skills gain access to the technology and regain control over their work. From farming to manufacturing to computing this has been the case. We've spent the past half century digitizing the assets of the business and that required, in essence, that control over those assets were assumed by IT. But now it's shifting back, and BPM is the mechanism by which that move is most fully realized today. IBM Blueworks Live is a major step in that evolution. It doesn't solve every BPM problem - by design! But it does solve a set of problems that have eluded IT for decades: how do we give our businesses the tooling to continue the flexible ad hoc processes they need in a changing world, while normalizing the information so that those processes are more efficient, more transparent and easy to build and deploy.
Meet IBM Blueworks Live: the new face of BPM.
And from David Moser:
All very worthy, but much less interesting than the next piece of news, which was the launch of Blueworks Live. This combines three elements ? the Blueworks BPM collaboration community (blogs, wikis); the highly successful (Lombardi) Blueprint process discovery and definition environment; and a new workflow execution engine. All running in the Cloud and, apparently, available through your browser for a test drive from November 20th. (Yes, that?s this Saturday ? perhaps one of the software world?s most specific launch dates ever?!).
In the comments Ian Gotts frets that some users won't be happy only having access to "automated" processes and not to the modeled processes in Blueworks, but this strikes me as an unlikely problem for the real users.? Second, it is better to start with too little, than too much, in your product.? Wikipedia contains excellent links and content explaining Minimum Viable Product.