Selim Erol of the Vienna University of Economics and Business Administration presented the first paper of the afternoon, co-authored with Gustaf Neumann, on using wikis in an organizational context, in terms of which aspects may have influence on the success of the implementation. They have also developed a prototype of wiki-based editor for workflow definitions, including enacting a web-based workflow based on the workflow definitions.
He gave a summary of wikis — again, likely unnecessary to an audience of academics who are all presenting papers on BPM and social software — and used Wikipedia as an example of how placing content authoring in an open space (public) ensures critical mass of community, which in turn ensures critical mass of content and artifacts; and how mutual control enables content negotiation and self-healing.
He summarized the characteristics of BPM, then looked at applying wiki characteristics to BPM, particularly in process (and rules) design. He sees a number of aspects that determine the degree to which collective intelligence can be used in a wiki environment:
- Size of crowd/community participating
- Level of crowd/community organization
- Degree of objects’ structuredness/specificity
- Degree of objects’ completeness
The risks of wiki application are much different in public and enterprise applications, however: in a public domain such as Wikipedia, there are issues such as edit wars and vandalism, whereas in an enterprise environment, the issues are more of lack of subjectivity, domination based on corporate rank, and desertion by the community due to smaller size and more politicized environment.
He gave a brief demonstration of the XoWiki-based workflow system that they have created, providing a wiki environment for specifying process flow collaboratively. It’s still a bit of a code-like interface, although also provides a graphical representation, but it’s great to be seeing process modeling done in a more generalized wiki context. I think that there needs to be more crossover between academia and the vendor world, however: he stated one key differentiator as being that it’s web-based, but a number of BPMS vendors have web-based process modelers now.