OUGN Vårseminar 2014

Process analysts and developers often make the mistake of equating user interaction with process flow. This is even more abundant now that we can execute the BPMN 2.0 models that we create. Analysts tend to model the user interaction in the process and then ask the developers to generate/build a screen for every human task that is modeled. This results in user interfaces that are hard to use, error prone and inflexible The resulting processes are very hard to change and too fine grained. Saving money in the project by generating a screen for every human task flow will cost the organization a lot of money. The reasons will be explained in this session. A better approach is to design the process flow and to design the user interface(s) separate from each other. This way you will be more flexible both to make process changes and to make interface changes. It will result in an user interface that people love to use and a business process that satisfies the needs of the business. This is illustrated with two cases.