Internal workshop was conducted with the objectives of updating scenario definitions and user journey map in the second phase of iterative requirement elicitation. In our first phase of the user need analysis, our primary purpose was to collect insights about the pilot partners. Throughout scenario definitions referring to the pilots, we wanted to highlight the overall processes, the interaction between the users and the technology, and the potential opportunities for technology implementation. We gathered several user needs by interviewing several employees from different departments in the pilot partners, who were identified as users for the tool to be developed. These needs formed the basis for the scenario definitions, describing the status quo processes and interactions between software, machines, and user (As-Is scenario). Additionally, we created a vision (To-Be scenario) to draw the first implementation possibilities. The scenarios were created as storyboards with text and illustrations to make them more tangible for other partners.
Within the second phase of the user need analysis, we referred to the To-Be scenarios to create user-journey maps to structure existing information and align the user needs and technological requirements. The primary purpose of this user-journey map is to structure the To-Be scenarios so that user needs, actions, in-, and outcomes are associated with a process step. Additionally, we aligned the components with the scenario steps to give the first draft of possible technology implementation. Overall, the user-journey map acts as a collaborative tool that should start a dialogue between pilot and technical partners, where they can discuss and clarify open issues and align the process if necessary. Further it is a tool to keep the user needs in mind when it comes to technological implementation.