There's a common misconception at executive level that is really holding back progress in BPM and process excellence: the idea that all process modelling tools are equal.
The latest culprit is Paul Harmon in his article on BPTrends this week What Can Enterprise Process Work Accomplish?
Paul writes some thoughtful stuff, and his style always reminds me of the brilliant Garrison Keillor, and I agree with 95% of what he writes in this latest piece - but it has a fatal flaw.
He outlines the essentials of a Business Process Architecture - that it should be comprehensive, integrated from top to bottom, linked with real-time metrics, and that it needs the whole-hearted involvement of the business - "lightweight Business Process Architecture contained within an IT-developed Enterprise Architecture could not possibly serve the purpose". Completely agree.
He believes that every organization needs an effective Business Process Architecture because "the survival of large organizations depends, increasingly, on their ability to understand themselves and to execute effective changes in response to a rapidly changing environment". Completely agree.
He says that "to develop a Business Process Architecture for a mid-to-large sized organization is no mean feat" and that "this is not something you want to attempt with Visio... you need a good process modelling tool with a good process repository to manage this effort". Completely agree.
But he goes on: "So, you need process modelling software, and any one of the many process modellling tools will serve".
To be fair, Paul Harmon is not alone in making comments of this sort. My experience is that it's a common perception at exec level, even among some CIOs.
But the idea that all process modelling tools are equal is not just wrong - it's a huge barrier to BPM success.
It's plainly wrong because there is a very wide spectrum of process modelling tools, with a range of methodologies and process languages. It's about as true as saying all cars are equal. Or that hammers and screwdrivers and spirit levels are all equal tools.
More importantly, it's also the key to why BPM success has been so elusive, why process maturity, CMMI Level 5 and cultures of continuous excellence are still so far out of reach for most organizations.
Let me stake a claim and invite the brickbats.
No organization can efficiently and sustainably build a Business Process Architecture that underpins continuous excellence, without a process modelling tool that has four properties:
- It uses the language of the business
- It is owned by the business, within a governance framework that enables collaboration on change by all process stakeholders
- It is deployed to process consumers across the organization as a personalised intelligent operations manual - 'the way we work' - with features that encourage engagement in continuous improvement
- The Business Operational view of process is synchronised with the complementary but different Enterprise Architecture view of the organization's processes.
These have surely got to be essentials for a tool that can efficiently and sustainably underpin the ideal Business Process Architecture that Paul is describing? This is where the market is heading, and where any savvy organization will be looking for its solution. And, I know I would say this, but, right now, Nimbus Control has got to be the leader in this space.

Good points made but might the same could be said about Casewise, IDS Scheer's Aris and IBM System Architect...........
Posted by: Paul Fowle | 14 July 2010 at 03:03 PM
Paul - I don't think so?
The tools you've mentioned - Casewise, ARIS, System Architect - are technical, designed for, and overwhelmingly used by, IT people.
They were never intended for deployment to process consumers, to be collaborative frameworks, to provide robust governance.
That's not to say that they aren't being re-architected to meet these new requirements - but they currently live in IT. And, as Paul Harmon's article says, any organization needs a Business Process Architecture that is owned by the business, and drives the EA view.
Posted by: Mike Gammage | 14 July 2010 at 04:04 PM
Paul - Mike is correct. The tools you mentioned are almost entirely IT centric and overwhelmingly complicated to use. For that reason, they are rarely used or understood by the business partners (or the IT architects) that IT will have to interact with.
The tool has to be user friendly and functional for the business analyst, comprehensive enough for IT. I have found that iGrafx provides an excellent tool in this arena. It allows you to easily map your process and link related resources. It also allow for the ability to quickly (without programming) do an What-If analysis through simulation. I would recommend iGrafx to anyone looking to do BPA.
Posted by: Robert Thacker | 14 July 2010 at 06:00 PM
Very interesting post and points raised. I don't agree with the sentiment though that 'you don't want to attempt this with Visio'. Triaster's Process Navigator system is built upon Visio and is successfully used in many large organisations, see www.triaster.co.uk
It's very easy to use and is foccused primarily on capturing those 80% of manual business processes. From what I've seen it's very similar to Nimbus Control in both its architecture and execution.
Perhaps then, all process modelling (mapping?) tools are the same, or at least similar, if they share certain features.
Posted by: Dale Moore | 27 July 2010 at 11:13 AM
Hi Dale, thanks for your comments.
I should point out that the remark about the limitations of Visio as an enterprise process repository was Paul Harmon's not mine.
But I do agree with him. I'm not familiar with Triaster so I don't know to what extent it overcomes the limitations of Visio.
re your final point about the similarity between tools [what they claim at least!]. It's a common enough perception, and unfortunate inmho because they aren't really.
That's why I set out what I see as the four properties of a process modelling tool that can underpin an enterprise continuous excellence programme ['properties' makes it sound a bit grand, but that's essentially what they are]...
Posted by: Mike Gammage | 27 July 2010 at 12:55 PM