You Can’t Keep A Good BPM Market Down
Its been a week since SAP’s big BPM announcement. Not exactly an earth-shattering announcement. My summary - at some point in the future (2 years?), SAP-only shops will be able to more easily configure internal SAP application workflows. This is a SAP application workflow band-aid, not a viable BPM offering. I am not alone in this assessment - the reviews have ranged from unimpressed to downright negative.
Honestly, this is no surprise. The big software vendors - I call them Stackers - have been and continue to pursue the promise of BPM half-heartedly. Actually, they have done everything in their power to bury BPM deep in what they view as their real markets. You can’t blame them - BPM ain’t in their DNA. And it is really hard to change your DNA.
SAP wants you to buy applications from them. BPM to them is just some integration and workflow between their applications. Always has and always will be - no matter what the Netweaver BPM roadmap says. Not to get too cheeky, but SAP does not have the best reputation in this sense - see their public spat with Waste Management about non-delivery of promised functionality.


Process People: Describe in as much detail as possible the problem or need on a project level that first made you consider BPM and/or Lombardi as a viable solution.
Unfortunately, this approach just doesn’t work when documenting business processes. It’s not the processes themselves that present a problem — it’s the people. When you try to document each step chronologically, the inevitable result is a trip down rat-hole lane. Rat-holing is when you get caught up with the minor details and exceptions that occur in any process. I’ve seen documentation sessions go on for hours with little to show for the effort because each stakeholder in the room was preoccupied with the subtle exceptions to the steps that they themselves were most passionate about. 



