The notion of agile software development appeared around the time when academics took interest in what the software engineers have been doing to make their job easier. In this iterative, 'small-steps' methodology aimed at getting projects done in time, extensive analysis are performed and problem identification is clearly separated from the actual development. The very same ailment plagues workflow design.

'Workflow model design' — this surely sounds like an undertaking that can only be completed using a state-of-the-art software. Such a technical wording suggests a conundrum that requires sophisticated tools and in-depth knowledge of the field, often leaving the user paralyzed by the unknown.

More often than not, I have heard customers say: „We have a problem with internal communication that we are trying to solve with a tool; we need a workflow management system.“ I used to get excited about such inquiries, knowing well that a properly implemented workflow system can be a game-changer in solving internal communication problems.