Intercultural Collaboration
This scenario-based eLearning project teaches corporate managers about three major cultural differences and helps them make decisions that display intercultural empathy when working with multicultural teams. The experience provides managers of multicultural or global teams with a foundation for handling real-life situations and conflicts that are rooted in cultural differences.
Overview
Audience: Corporate managers of multicultural or global teams
Responsibilities: Instructional design, eLearning development, graphic design
Tools used: Articulate Storyline 360, Adobe Illustrator, Twine
Problem and Solution
This scenario-based learning experience addresses the potential problem of managers of multicultural or global teams who are unaware of cultural differences relevant to workplace collaboration and thus are unable to successfully respond to issues that are rooted in these differences. This can have negative consequences for workplace relationships, employee satisfaction, and thus organizational outcomes. According to Tsedal Neeley in the Harvard Business Review article “Global Teams that Work” (2015), global teams are most successful when members display understanding and empathy towards each other’s perspectives. Misunderstandings due to different cultural perspectives are a major source of social distance and distrust in the workplace.
As a solution to this problem, the project proposes a scenario-based learning experience that teaches managers about three cultural differences that are highly relevant to collaboration and guides them through scenarios where they practice applying this new knowledge to make empathetic decisions in the workplace.
Process
I created the learning experience by defining the learning outcome and objectives, designing and organizing the experience, creating a text storyboard in Twine, creating visual mockups with Adobe Illustrator, and developing an interactive prototype. After receiving and incorporating feedback on the interactive prototype, I developed the end product in Articulate Storyline 360.
Learning Outcome and Objectives
To determine my learning objectives, I relied on Bloom’s taxonomy. First, I defined my terminal learning objective: After learning about intercultural differences relevant to workplace collaboration, managers will apply this knowledge to make effective and interculturally empathetic decisions in the workplace.
Then, after reviewing literature on cultural differences that affect collaboration, I defined three enabling objectives to guide my organization and the creation of scenarios: After learning about intercultural differences relevant to workplace collaboration, instructors will be able to make decisions that display knowledge of and empathy towards 1) monochronic and polychronic orientations to time, 2) low and high power distance perspectives, and 3) individualist and collectivist perspectives.
Design and Organization
I reviewed literature on cultural differences relevant to workplace collaboration and then selected and compiled information that addressed my learning objectives. I relied on sources such as the articles “From Intercultural Awareness to Intercultural Empathy” by Honglin Zhu (2011) and “Monochronic vs. Polychonic Cultures: What are the Differences?” by VP Legacies.
I decided to organize the learning experience as a semi-branching scenario. Learners would be immediately dropped into a real-life context, where they have just become branch manager for a fictional soft drinks company. During the experience, they would go through three different scenarios, each corresponding to one of the target cultural differences. I chose a story-based scenario approach because it allows learners to learn by doing. Information is presented within the context of each scenario and in response to actions taken by the learner — either as advice from the previous branch manager following a mistake or in the form of real-life consequences to decisions made by the learner. This approach is more engaging than traditional “information dump” approaches, which don’t provide learners with any “mental hooks” to back the content.
In each of the three scenarios, learners would first be faced with a situation in which they were provided with two seemingly reasonable yet incorrect options (e.g., one option reflecting an individualist mindset and one reflecting a collectivist mindset). Depending on which option they choose, they would then receive feedback in the form of a real-life consequence and an option to find out “What happened?” from the previous branch manager. The purpose of this first decision point would be to experience and learn through common mistakes so that the new information is then presented within a meaningful context.
After learning about the target cultural difference from the previous manager, they would be faced with another similar situation where they are encouraged to apply their new knowledge and intercultural empathy to find a solution that addresses the needs of employees from all cultural backgrounds. This time, there would be four options, and they could not move forward until they selected the correct one. Each option would again be accompanied by feedback in the form of a real-life consequence. The purpose of the second decision point would be to practice applying their knowledge to make empathetic decisions in the workplace. This structure would be repeated for each of the three cultural topics.
Text-Based Storyboard and Feedback
Next, using the content I had selected and my design plans, I created the text storyboard in Twine. Using Twine instead of a traditional text-based storyboard allowed me to easily create branching connections.
Visual Mockups
I used Adobe Illustrator and assets from Freepik to create custom visuals for the project. I created background visuals that were full-slide and provided an office context. I also manipulated assets to create four main characters: three employees that represented different cultural backgrounds and the previous branch manager, who functioned as an on-screen coach that the learner could consult for more information after making a mistake. I created 2 to 3 versions of each character to reflect different postures and emotions. For each visual asset, I maintained a consistent flat design style as well as a custom color palette.
Interactive Prototype
I developed an interactive prototype in Articulate Storyline 360 using the text-based storyboard and visual mockups to establish the scenario’s programming. The prototype included the title screen, introduction, the first scenario with choices, and the consequences for each choice. At this point, I also developed the visuals that were not created with Adobe Illustrator, including text bubbles, buttons, and background colors. I shared the prototype with others for feedback.
In response to feedback, I added a brief drag-and-drop practice activity as a way of engaging learners with the examples in an interactive way instead of presenting them as a wall-of-text list. I also decided to present some information in the form of employee reactions instead of in the explanation provided by the previous manager in order to reduce the amount of text learners were exposed to at once and to present information in a more contextualized way.
Full Development
After making revisions to the interactive prototype, I developed the rest of the scenario-based learning experience. I published the course and tested it for errors on both desktop and mobile devices. Afterwards, I created an infographic using Adobe Illustrator to accompany the e-learning experience to reinforce the main concepts.
Takeaways and Reflection
The process of creating this scenario-based learning experience gave me my first experiences with Articulate Storyline and Adobe Illustrator. In Storyline, I gained experience with features like layers, triggers, variables (LearnerName), states, and free form drag-and-drop activities. In Adobe Illustrator, I gained experience with manipulating vector images — specifically color, shape, and position — as well as creating an infographic. I really enjoyed learning these tools, and I look forward to deepening my understanding of them with future projects.