Archive

Posts Tagged ‘Adaptive Case Management’

Links Aug 2010

August 9, 2010 Leave a comment

Some say that ACM is just BPM except with unstructured processes. That is like saying starvation is like eating, except without any food.

While doing a review of the tweet-jam coverage, it hit me that many people want so much to categorize all work as being process oriented, that when they see work that does not fit that mold, they invoke something called an “unstructured process”.  It is fine to talk about unstructured (or unpredictable processes) but you should not think that an unstructured process acts in any way like a structured one. Read more…

ACMJAM Discussion – Part 3 of 3

August 5, 2010 Leave a comment

We held a tweetjam on the subject of Adaptive Case Management (ACM) on July 15.  I have already posted part 1 and part 2.  Here is part 3. Read more…

ACMJAM Discussion – Part 1 of 3

August 3, 2010 Leave a comment

We held a tweetjam on the subject of Adaptive Case Management  on July 15.  I have been on vacation since then, and only now getting around to writing about it. What a big task!  In two hours 660 posts were made, many of them quite thought provoking.  After eliminating the duplicate RT posts, it still came to over 6000 words.  So it is going to take me three posts to get this all in.  Here is part 1. Read more…

Design by Doing vs. Doing by Design

April 28, 2010 Leave a comment

Jim Sinur wrote a couple of interesting blog posts recently mentioning two distinct approaches for supporting work processes:

  • Doing by Design is the pre-planned definition of a predictable, routine process as traditional BPM suggests.  It involves a life-cycle that starts with process discovery, process definition, application development, simulation, testing, and ultimately deploying it.  This works if the process is predictable.
  • Design by Doing is an approach that works when the process is not predictable, and can not be written down ahead of time.  Since you can not predict it, you have to elaborate it as you go along.  You design it, as you are doing it.  There is no development life-cycle.  This works on unpredictable emergent process.

Read more…