Column 2

How recognizing, capturing and reusing patterns in knowledge work can be useful: repackaging parts of cases into a new case to speed the work. This is a bit like having some structured subprocesses available to call for a case as required: that blend of structured and unstructured that allows the knowledge worker to select a preexisting pattern if one exists, or do their own thing otherwise.

Adam Deane's funny take on the "war" between BPM and ECM that is being caused by case management: both vendor camps want to claim it for their own. Underneath the humor, some good points (and a fun read).

What needs to be added to a basic ECM platform in order to do true case management (which, of course, starts with the assumption that CM is built on ECM).

Under the title "Advanced Case Management and BPM: Are they the same?", a discussion from IBM on their case management strategy. Unclear how they are overlaying their product suite on this definition yet; their definition extends into areas of both ECM and BPM, for which they have multiple products.

How the ECM vendors are repositioning their products (accurately or not) as case management.

A case is not just documents: it's a container for documents, rules, other data and the relationships between all of them.