Practical process anti-pattern: RID

The anti-pattern Ruined in Details (RID) was detected while looking at business processes documented by the users.  Often, the sequence of activities (or tasks) is the following:
Role B: receive documents from role A
Role B: do your work
Role B: send documents to role C
Role C: receive documents from role B
Role C: do your work
Role C: send documents to role D

Sure that receiving and sending documents are important, but those activities don't add the value. Indicating only value-added-value activities (e.g. "do your work") will make diagrams more compact and easier to understand.

Maybe this anti-pattern is a sign that there are problems with integration?


No comments: