I recently received a reviewer's comments on an S-BPM related paper that I would like to share.
The reviewer criticised that the terminology used in most S-BPM related papers is too specific for the general BPM community. He/she also suggested that when describing the S-BPM approach we should position it more closely among other approaches to BPM. Specifically the reviewer suggested Role-Activity Diagrams and UML collaboration diagrams as related approaches.
I think these comments are fair enough, and especially useful for S-BPM folks who want to reach a wider audience. What are your views about this? Have you had similar feedback? How can we be more successful in getting our message across?