- Principle of context-awareness
BPM should fit to the organizational context.
It should not follow a cook-book approach. - Principle of continuity
BPM should be a permanent practice.
It should not be a one-off project. - Principle of enablement
BPM should develop capabilities.
It should not be limited to fire-fighting. - Principle of holism
BPM should be inclusive in scope.
It should not have an isolated focus. - Principle of institutionalization
BPM should be embedded in the organizational structure.
It should not be an ad-hoc responsibility. - Principle of involvement
BPM should integrate all stakeholder groups.
It should not neglect employee participation. - Principle of joint understanding
BPM should create shared meaning.
It should not be the language of experts. - Principle of purpose
BPM should contribute to strategic value creation.
It should not be done for the sake of doing it. - Principle of simplicity
BPM should be economical.
It should not be over-engineered. - Principle of technology appropriation
BPM should make opportune use of technology.
It should not consider technology management as an after-thought.
We strongly call for the discussion and refinement of the identified principles as outlined above since we believe that such principles could make an important contribution to the BPM community. We therefore like to encourage colleagues from research and practice worldwide to provide us with their perspectives on the above principles.
The current version of the 10 Principles of Good BPM is also available as a file – click on the image on the right side to download the .pdf for discussion purposes. Any type of feedback on the further development of the principles is welcome.