As with several previous posts from Mr. Ukelson, I really like this one, about Process Simplicity.? Simplifying and Simplicity have been themes of late- because what software needs, and specifically what BPM needs - is deeper thinking into how it is surfaced to those of us who use it.
I also like how Mr. Ukelson focuses on what his product can do for the business, and not about whether it is BPM or ACM or something else.? He offers a definition of BPM as the "discipline of making work processes simpler", which leads to interesting conclusions and points of comparison.
I agree with the philosophy of making work processes simpler, though you could say "making work simpler" because not every participant of a process will perceive it to be a process - to that person it may look like a single action or reaction, or a case.
Finally Law 10 ? This is an interesting law from a BPM perspective ? isn?t BPM about exposing and codifying the routine (which is version of the obvious)? So maybe BPM?s job is to lay the groundwork so we can get to Law 10 in business processes, and something else will need to come along enabling the next step towards Law 10.
(law 10 was "Simplicity is about subtracting the obvious, and adding the meaningful.")
I think Mr. Ukelson may be on to something.? And I think his characterization of the BPM/ACM debate is one of the better "framings" of the discussion that I've seen.? Not that that won't stop anyone from disagreeing with me... please comment!