MDM
|
|||
Asking this question is audacious. But important. Here's the short answer: BPM projects fail at a rate higher than tolerable (thus the question) because BPM projects, being fundamentally different than all other IT projects, are not yet sufficiently supported culturally, organizationally and economically. In particular, a BPM projects puts pressure on business executives for detailed process leadership, a time-based pressure without precedent and for which many or even most executives are not ready. The first response to ebizQ's question, from Emiel Kelly, alludes to these issues with the statement that BPM is seen as "a project, not as daily business". Subsequent comments by other contributors elaborate in worthwhile ways. But it's worth making Kelly's "not as daily business" explanation more explicit. Specifically, from the original answer above, what does it mean that BPM projects are "fundamentally different", and why is this difference important? And what is "cultural, organizational and economic" support?
|
|||
|
|||
Takeaway Summary: According to the theory of Nobel Prize winning economist Ronald Coase, corporations exist to manage the transaction costs involved in organizing work. And the size of a corporation is determined by the optimal management of those costs. However, new information technologies have changed that transaction cost landscape for business processes. It is now more than ever possible to disaggregate the work of the firm, and still maintain corporate identity and control. And for the intercompany integration technology business, the good news is that integration technologies have a leading role to play in this evolut . . . read more |
|||
