1. Position: BPMN is incompatible
with ACM
Keith D Swenson
VP at Fujitsu America, Inc.
Chairman of Workflow Management Coalition
© Copyright 2011 Fujitsu

2. Proposition
Any work support system
that depends upon processes
designed with BPMN
(or BPMN-like languages)
cannot be considered
an ACM system.
© Copyright 2011 Fujitsu

3. What is BPMN-like
 This is not a critique of BPMN in particular.
 Here, I use BPMN to refer to any flowchart like, two-
dimensional process diagram with boxes and lines.
© Copyright 2011 Fujitsu

4. Change: Lifecycle
BPM ACM
& PCM
© Copyright 2011 Fujitsu

5. -- 1 --
Drawing a diagram requires a kind of
abstract thinking about the process that a
business user is not comfortable with.
© Copyright 2011 Fujitsu

6. -- 2 --
Drawing an executable diagram actually
involves some programmer-like skills
© Copyright 2011 Fujitsu

7. -- 3 --
Modifying someone else’s diagram is
particularly difficult:
the assumptions that went into drawing the
diagram are not visible in the diagram
The BPMN-like diagram is the output of
planning, and supporting concepts are lost
© Copyright 2011 Fujitsu

8. © Copyright 2011 Fujitsu

9. The Nescafè Process
(example from: M zur Muehlen)
© Copyright 2011 Fujitsu

10. Web Service Web Service Web Service
A B C
© Copyright 2011 Fujitsu

11. Can a Step be Inserted?
Web Service
X
Web Service Web Service Web Service
A B C
© Copyright 2011 Fujitsu

12. Can Steps be Rearranged?
Web Service Web Service Web Service
A B C
© Copyright 2011 Fujitsu

13. © Copyright 2011 Fujitsu

14. Criterion 1:
Ability to design a basic process quickly with
very little investment by the user is far more
important than the ability to define a precise
process which uses more time an attention
from the business user.
© Copyright 2011 Fujitsu

15. Criterion 2:
Process design must not require a skill beyond
what business users possess
© Copyright 2011 Fujitsu

16. Criterion 3:
For a process definition to be modified by
business users there must be no hidden
assumptions.
© Copyright 2011 Fujitsu

17. For Routine Work For Knowledge Work
Created ahead of time Created when needed,
by specialist crafted to by the person doing the work.
automatically respond Manually adjusted for
to many situations. changing situations.
© Copyright 2011 Fujitsu

18. The simple checklist
 Boil the water
 Put coffee in the cup
 Put boiling water in the cup
© Copyright 2011 Fujitsu

19. The simple checklist
 Boil the water
 Put coffee in the cup
 Put sugar in the cup
 Put boiling water in the cup
© Copyright 2011 Fujitsu

20. Why Not BOTH?
If a system has BPMN, then 5% will use it
95% will be unable to modify those diagram
The system will no longer be adaptive
© Copyright 2011 Fujitsu

21. Conclusion
 For all participants to be able to adapt processes to their
need, all processes need to be in low-tech form
 You must force all users into a least-common-denominator
situation, using the low-tech form
 The mere presence of a flow-chart format will disrupt the ability
to be adaptive.
© Copyright 2011 Fujitsu

22.  What are the open questions that need to be answered?
© Copyright 2011 Fujitsu