Anatoly has written a nice post expanding on the term "BPM" - it isn't a definition so much as a helpful explanation to make it easier to understand what "looks like BPM" and what doesn't.? More specifically, he's talking about what is a "BPMN" process and what is not, rather than "what is BPM" and what is not. Important distinction.? Key attributes:
- Inputs and Outputs are primarily Events
- BPMN Process is the story of an object, not of a subject
- BPMN Process is not complete until all the work is done
- BPMN Process is customer oriented
- BPMN Process is macro, not micro-management.
Read his post for full explanation.? His top ten list expands on the characteristics I usually cite for BPM (or BPMN):
If it has value, and volume, and it is business, then it is probably BPM.
The corollary being that things that aren't repeatable (volume), or don't have much value, or aren't the focus of your business, don't make sense to invest in with respect to BPM.? Which relates directly to our recent post on the opportunities that come with scale.