Figure A1
A mapping diagram shows connections among expert stories, meta requirements, and design principles across four themes.The mapping diagram shows three vertical sections labeled from left to right as follows: “Expert Stories, Kernel Theories and Justificatory Knowledge,” “Meta Requirements (M R),” and “Design Principles (D P).” Under the “Expert Stories, Kernel Theories and Justificatory Knowledge” section, four thematic groups are arranged from top to bottom as follows: The first group is “Process,” and the text from top to bottom is as follows: “Expert Stories (E S)” “I want to make collaborators perform a second task parallel to their main activity.” “I want to stop all activity in the system and force breaks.” “I want to visualize the remaining time for any process step.” “I want to vary the rhythm and length of work phases and exchange.” “I want to make collaborators repeat a process step in order to refine a solution.” “I want to celebrate achievements after a stressful work phase to motivate collaborators.” “I want to intervene in the collaboration to keep activities focused and efficient.” “I want to make collaborators proceed and not question their current result or solution.” “I want to hide planned process steps from collaborators to keep them focused.” “Kernel Theories (K T) and Justificatory Knowledge (J T)” “Media Richness Theory” “Cognitive Load” “Creativity under Constraints” “Radical Creativity” “Activation Theory” “Subsequent Creativity” The second group is “Collaboration” and the text from top to bottom is as follows: “Expert Stories” “I want to limit channels and availabilities of interpersonal exchange.” “I want to block monologues and limit speaking time for collaborators.” “I want to disable any distracting applications or functionalities on collaborators’ computers.” “I want to disable audio and video connection depending on familiarity of collaborators.” “I want to divide collaborators into sub-groups (3 to 5) to intensify the collaboration.” “I want to be able to make collaborators’ activities visible for each other.” “I want to be able to hide collaborators’ activities from each other.” “Kernel Theories and Justificatory Knowledge” “Media Richness Theory” “Cognitive Load” “Activity Theory” “Social Loafing” “Production Blocking” “Social Facilitation Theory” “Psychological Safety” “Shared Understanding” The third group is “Feedback” and the text from top to bottom is as follows: “Expert Stories” “I want to create an environment that does not follow collaborators’ daily routines.” “I want to make collaborators forget about external expectations.” “I want to keep collaborators from discussing daily business and existing solutions.” “I want to disable any form of negative feedback.” “I want to block discussions to avoid premature criticism.” “I want to force mitigation and integration of objections to support transparency.” “I want to mix up collaborators differently for decision making.” “Kernel Theories and Justificatory Knowledge” “Activity Theory” “Social Facilitation Theory” “Psychological Safety” “Creativity under Constraints” “Theory of Creativity” “Radical Creativity” The fourth group is “Features” and the text from top to bottom is as follows: “Expert Stories” “I want to limit options for expression during initial brainstorming.” “I want to limit shapes and colors for sticky notes to an absolute minimum.” “I want to limit features for note taking and information sharing.” “I want to limit features depending on roles of collaborators.” “I want to limit functionalities available depending on collaborators’ skill levels.” “I want the system to be usable with basic knowledge of text editing and mouse navigation.” “I want to provide limited work areas for every step.” “I want to offer prefilled work areas to inspire activity.” “I want to offer the most diverse and rich media and features possible during prototyping.” “Kernel Theories and Justificatory Knowledge” “Media Richness Theory” “Persuasive Technology” “Feature Fatigue” “Activity Theory” “Creativity under Constraints” “Theory of Creativity” In the center under the “Meta Requirements (M R)” section, eleven text boxes are arranged in a vertical section, labeled from top to bottom as follows: Text Box 1: “M R 1” “In order to make collaborators think outside their daily work reality and spark their creativity, the system should make collaborators perform parallel subtasks or stop all activity, depending on energy levels and process phase.” Text Box 2: “M R 2” “In order to manage efficiency and quality of the process and keep collaborators engaged and focused, the system should vary and visualize the time available and make collaborators repeat and celebrate activities or proceed to the next activity, depending on results and collaborative dynamics.” Text Box 3: “M R 3” “In order to avoid cognitive overload and focus collaborators’ activity, the system should limit the overview of process steps and work areas.” Text Box 4: “M R 4” “In order to prevent monologues and promote psychological safety and shared understanding, the system should limit speaking time and available channels for interpersonal exchange, depending on familiarity and phase in the process.” Text Box 5: “M R 5” “In order to prevent distractions, reduce cognitive load and promote activity, the system should be able to block distracting applications and functionalities on collaborators’ computer systems.” Text Box 6: “M R 6” “In order to promote engagement and prevent social loafing, the system should allow to create sub-groups and visualize or hide collaborators’ activity in the system, depending on the work phase and collaborative dynamics.” Text Box 7: “M R 7” “In order to promote radical creativity and prevent routine responses and premature criticism, the system should disable any form of positive and negative feedback or discussions around external expectations during divergent phases in the collaboration.” Text Box 8: “M R 8” “In order to avoid topic drift and promote transparency and applicability of generated solutions, the system should enable collaborators to mix up differently for decision making and make them integrate objections in a systematic way at later stage convergent phases in the collaboration.” Text Box 9: “M R 9” “In order to prevent feature fatigue, confusion and lack of activity in the initial stages of divergent thinking, the system should offer minimal features and functionalities, depending on collaborators’ skill level.” Text Box 10: “M R 10” “In order to enable collaborators to use the system without special knowledge and support adaptation and activity, the system should offer simple navigation and limited work areas which are prefilled with examples for use or content.” Text Box 11: “M R 11” “In order to support prototyping, simulation and exploration of ideas in later phases of divergent creativity, the system should offer a large feature diversity and media richness, depending on collaborators’ skill level.” Multiple right-pointing arrows from “Expert Stories (E S)” and “Kernel Theories (K T) and Justificatory Knowledge (J T)” of the “Expert Stories, Kernel Theories and Justificatory Knowledge” section connect to the M R text boxes of the “Meta Requirements (M R)” section. On the far right, under the “Design Principles (D P)” section, five text boxes are arranged in a vertical series labeled from top to bottom as follows: Text Box 1: “D P 1” “For designers and developers to design C S S that enable users to forget their daily work and spark more radical forms of creativity in the context of virtual collaboration, employ a set of sub-tasks that collaborators need to perform parallel to their main activities during divergent phases of the collaboration, involving repetition and celebration, and enable the system to block activities at points of decreasing focus, in order to stimulate positive spillover effects between explicit and implicit conscious processes and to prevent routine responses to external expectations.” Text Box 2: “D P 2” “For designers and developers to design C S S that promote focused activity and efficiency in the context of virtual collaboration, block distracting applications and functionalities on collaborators’ computer systems, make collaborators proceed through stages with limited overview of work areas and visibility of user activities, involving the visualization of remaining time, in order to prevent distractions and premature discussions and promote engagement.” Text Box 3: “D P 3” “For designers and developers to design C S S that promote shared understanding and applicability of generated solutions in the context of virtual collaboration, enable collaborators to mix groups and guide them through a process of systematic integration of objections during later stage convergent phases of the collaboration, involving limited channels and individual speaking time for interpersonal exchange, in order to prevent topic drift and promote psychological safety.” Text Box 4: “D P 4” “For designers and developers to design C S S that enable inexperienced users to engage from the start in the context of virtual collaboration, create subgroups and limit features to a viable minimum in initial stages of divergent thinking, involving only basic functionalities for input, highlighting, navigation and simple examples in work areas, in order to prevent hesitancy to contribute and promote social facilitation.” Text Box 5: “D P 5” “For designers and developers to design C S S that enable inexperienced users to express, simulate and differentiate ideas in the context of virtual collaboration, increase feature variety only in later phases of divergent creativity, involving various forms of media input, creating, highlighting and connecting of elements, in order to prevent cognitive overload and promote focused exploration.” A right-pointing arrow from text box 1 of the “Meta Requirements (M R)” section points to text box 1 of the “Design Principles (D P)” section. Two right-pointing arrows from text box 2 of the “Meta Requirements (M R)” section point to text box 1 and text box 2 of the “Design Principles (D P)” section. A right-pointing arrow from text box 3 of the “Meta Requirements (M R)” section points to text box 2 of the “Design Principles (D P)” section. A right-pointing arrow from text box 4 of the “Meta Requirements (M R)” section points to text box 3 of the “Design Principles (D P)” section. A right-pointing arrow from text box 5 of the “Meta Requirements (M R)” section points to text box 2 of the “Design Principles (D P)” section. A right-pointing arrow from text box 6 of the “Meta Requirements (M R)” section points to text box 2 of the “Design Principles (D P)” section. A right-pointing arrow from text box 7 of the “Meta Requirements (M R)” section points to text box 1 of the “Design Principles (D P)” section. A right-pointing arrow from text box 8 of the “Meta Requirements (M R)” section points to text box 3 of the “Design Principles (D P)” section. A right-pointing arrow from text box 9 of the “Meta Requirements (M R)” section points to text box 4 of the “Design Principles (D P)” section. Two right-pointing arrows from text box 10 of the “Meta Requirements (M R)” section point to text box 4 and text box 5 of the “Design Principles (D P)” section. A right-pointing arrow from text box 11 of the “Meta Requirements (M R)” section points to text box 5 of the “Design Principles (D P)” section.

Mapping diagram. Source: Authors’ own work, Möller et al. (2020) 

or Create an Account

Close Modal
Close Modal