To further develop and assess our design desires, we conducted a series of out-of-class sessions with teachers to understand how the co-orchestration design principles for social transitions aligned with their values and classroom practices two months after the initial study. By realizing the design desires from the design sessions in a physical artifact, namely a mid-fidelity prototype of an orchestration system for specific social transition scenarios, teachers can further reflect on how our findings align with their values in the classroom. The prototype also leaves less ambiguity by providing a sense of interacting with the system. This process allows any further discrepancies in understanding between teachers and researchers to be addressed with respect to how responsibilities should be divided in a co-orchestration system (Martinez-Maldonado et al. 2015b).
Even with our design principles guiding the design of the system, it may not align with teachers’ values if the system does not provide sufficient support to avoid teachers feeling overwhelmed. On the other hand, the system may not provide the teachers with sufficient freedom, leading them to feel frustrated about a loss of control over their classrooms. Of course, the design does not need to be ‘either or’. As the goal is co-orchestration, there may be some areas where the system does not provide sufficient support and others where it does not provide sufficient freedom. To determine where this balance is well aligned and where it is not, in the following section, we present the findings from the scenario review sessions with the teachers, as they reflect on the support around social transitions through a series of classroom social transition scenarios.
Methods
Participants
In the second part of our design process, we continued to work with the majority of the teachers who participated in Study 1. A total of seven teachers (six females, one male) participated in this process. Six of the teachers had previously participated in Study 1, while one teacher had not.
Materials
Based on the findings from Study 1, we developed an orchestration system prototype that focused on demonstrating the co-orchestration of a range of fluid social transition scenarios when students are working on personal computing devices. The prototype supported a range of scenarios with limited interactivity and no backend. This design allowed us to have the teacher still interact with the system but for a predefined set of interactions. Through discussions with teachers during Study 1 around how they would interact with the system and their current practices, we assumed that all teachers would also have access to a personal device, such as a tablet or laptop that they would have with them in the classroom. As the students are all working on individual computers, it is assumed that the orchestration system has access to all data about student-system interactions and system state, aligning with standard log data (Koedinger et al. 2010), although not to interactions among students (e.g., analytics extracted from dialogue), or actions of students outside the system.
The scenarios in this system were developed to demonstrate the co-orchestration principles that were derived from Study 1 across a range of social transition types. Although each scenario was narrow in scope, each represented a broad type of transition that may occur in the classroom. The main elements of the prototype focused on the activity planning and the real-time orchestration of a technology-enhanced classroom that spans multiple social planes. The prototype tasks included one for activity planning and four scenarios regarding real-time planned and unplanned social transitions that teachers may encounter in their class, including fixed transitions with absent students (S1) or late/early dismissed students (S2), fluid social transitions between activities (S3), and fluid social transitions within activities (S4). These scenarios were designed to cover the range of transitions as outlined in Table 1. As with Study 1, we did not cover rotating groups as they were out of scope for our research question. Additionally, we did not include rotating activities or asynchronous between activity transitions as neither provided a new type of transition that was not supported in another scenario. Finally, we did not include a scenario with a student returning from an absence as the teachers expressed during Study 1 that they would want to work one-on-one with those students to bring them up to speed rather than having them jump into the on-going lesson. Below we describe each of the prototype activities and how they were developed to align with our six desires.
In the prototype, we first support the planning of the lesson. From Study 1, the first design desire was to support the teacher in designing the lesson (desire 1) while the system provides support with student pairing (desire 2). In designing a session for his/her students, a teacher creates a macro-script that comprises the activities on which students work, along with the social level of the activity, when and how groups are made, and the transitions between activities (transitions to next activity). Figure 1 shows an example of these choices. The different elements can be combined to create unique designs that allow for a range of social transitions. In the planning task, the system provides a template. Teachers can fill the above elements into this template in order to plan their lesson, including synchronous, time-based transitions as well as fluid (i.e., asynchronous) transitions between and within activities. For these within-activity transitions to occur, the system would monitor the students’ actions (desire 4) and recommend to the students when it may be beneficial for them to transition social levels while still working on the same activity. Additionally, through automatic grouping from the system (with teacher checks; desire 3), students can be quickly paired, which allows students to work with a variety of partners but still gives the teacher a chance to review and approve the group assignments.
In addition to supporting the planning of lessons with social transitions, the system provides real-time support for when these plans are put into action in the classroom. Scenarios S1 and S2 involve timed transitions, in which all students switch activities at the same time (see Fig. 2). Although timed transitions are not fluid, they are used most commonly in the classroom, and teachers could benefit from support in making these transitions well-timed and in making adjustments when they are not well-timed (Campbell and Skinner 2004). In the scenarios, the prototype system shows the teacher the amount of time that has passed, the students’ progress, and the activity in which students are currently engaged. Thus, it addresses the need for system monitoring (desire 4), which provides the teacher with awareness of the state of the classroom (desire 5). The system also provides orchestration tools that allow the teacher to flexibly adjust the activity (e.g., adding/decreasing time, pausing an activity, moving students between activities and groups; desire 3). Without teacher intervention, when the time remaining for an activity reaches zero, the system automatically moves students to the next activity (desire 2), directly informs the students about this change (desire 6), and makes the teacher aware of the change through the interface (desire 4/5). This information can all be seen in the top bars of the scenarios shown in Fig. 2.
The student absenteeism scenario (S1) illustrates the occurrence of pragmatic transitions in class (see Fig. 2, left). In this scenario, as students sign into the system, they can indicate if their partner is absent that day. If both members of the partnership are present, the system automatically prompts them to begin working (desires 2 and 6). If a student’s partner is absent, the system automatically finds a new partner for the student (desire 2) and notifies the teacher (desire 5). The teacher is able to still change the groups if needed (desire 3). This orchestration support allows the teacher to focus on supporting students at the beginning of class rather than having to figure out who is present. Additionally, this way of making changes to social groups also applies to students who are late or who are dismissed early, which is the focus of S2. In S2, the students are working on the activity, and three students are missing from class (see Fig. 2, right). Students with missing partners begin to work on the activity with another partner, and as the missing students arrive in class, they are paired with their original partner and automatically begin to work (desire 2). When a student leaves class early, the partner is automatically moved to a new partner for the rest of the activity (desire 2), with the system showing the pairing to the teacher in both instances and the teacher being able to change pairs if needed (desires 3 and 5).
In the between-activity fluid social transition scenario (S3), students work on an individual activity followed by a collaborative activity with a partner who was assigned during planning (see Fig. 3, left). In this scenario, as students finish their individual activity, they are automatically moved to the next activity and given instructions (desires 2 and 6) when their partner is ready as well. If a student’s partner is not yet ready, the student is asked to wait, as the system can monitor the progress of both students (desire 4). The system makes the teacher aware of the progress of the students (desire 4/5), and if a student is taking too long to finish, the teacher can manually advance the waiting partner or ask the student who is still working to move on (desire 3). If, during planning, the teacher selected to have pairing happen just-in-time for students, students will be teamed up and advanced to the collaborative activity as soon as another student is ready (desire 2).
Within the fluid within-activity transition scenario (S4), the system can use information about the student state (desire 4) to automatically have students switch social levels within a activity if this transition would be beneficial (desire 2; see Fig. 3, right). Recognizing when transitions might be beneficial is an open area for research. In S4, students who are struggling with an individual activity are paired with one another to complete the activity (desire 2), the students are directly informed of this change (desire 6); the teacher is notified and can intervene, as needed (desires 3 and 5). While working with a partner on a new activity, students who are not being productive in their pairs are separated to work individually by the system. Although the question of how social levels should be adapted remains open, this scenario was intended to demonstrate the division of roles with a co-orchestration system and how it could support this process.
Design and Procedures
Each scenario review session was done individually with each teacher. A session lasted for one hour and was semi-structured to give teachers time to interact with the five tasks described in the previous section. The first half of the scenario review sessions focused on the lesson planning, in order to test the orchestration support and to understand how well the support aligned with how teachers currently think about lesson planning. We first instructed the teachers to plan an activity on paper, as they would for their regular class in which the students are working individually for part of the activity and collaboratively for part of the activity. We then asked the teachers to take their planned activity and design the same activity in the orchestration system. This allowed us to see how an activity that was not designed within the constraints of the system could be implemented with the planning support and how the range of social transition options impacted the design. During the planning process, the teachers were asked to think aloud, and we subsequently conducted a short interview with the teachers to prompt a discussion regarding the shared control.
For the second half of the sessions, the researcher walked the teachers through the four real-time scenarios, with the ability to pause after each action, such as a student completing an activity or students getting paired, to allow for an ad hoc discussion to occur regarding the co-orchestration support. The teachers were informed that each of the scenarios assumed that the students would be working on their own device, allowing the student-system interactions to be tracked, by the software, during the activity. The researcher introduced each of the scenarios and, as actions happened in real time, pointed out and explained the changes. At the end of all four scenarios, the researcher conducted a short interview with the teachers about the real-time co-orchestration support for social transitions. During the interview, the researcher prompted the teachers to express what they found surprising or confusing and to explore their understanding and feelings of control.
Data Analysis
Screen captures with audio data were collected from each of the sessions. As with Study 1, we used thematic analysis to analyze the results (Aronson 1995; Fereday and Muir-Cochrane 2006). We again followed an iterative process using affinity diagramming (Miles et al. 2013), which involves the grouping and re-grouping of individual pieces of data to find common themes (Aronson 1995). The data that were used for grouping in the thematic analysis were extracted by a researcher who reviewed the screen capture videos and transcribed on-topic dialogue into separate notes. Each note represented a complete thought expressed by a participant during the scenario review sessions. Across the seven sessions, we gathered a total of 627 notes. These notes were compiled into overarching themes, which were then reviewed by a team of three researchers and restructured as needed.
Findings
In Study 2, the co-orchestration scenarios of social transitions provided the teachers with an opportunity to reflect on how they may share the orchestration responsibility with a system regarding concrete actions and situations involving social transitions. Although each of the scenarios focused on the social transitions, there was a continued theme from Study 1, with the teachers focusing on how these scenarios would support student learning and how the orchestration support would allow them to spend more time supporting students. Through the use of the orchestration system, the teachers felt that they would “be able to teach more and to teach more in depth” (T2) when some of the orchestration load was shared. Additionally, they “had a better idea of how to use [their] time” and “would be able to target the kids that [they] need to see” (T4). Below we discuss the balance of the system roles in terms of the primary orchestration elements within the literature (Prieto et al. 2011b) and if this balance aligned with teacher expectations.
Lesson Planning
From Study 1, we developed the desires that in co-orchestration systems, the teacher should be responsible for the lesson planning in order to retain initial control over the student learning (desire 1). In the lesson design task, as mentioned, the teachers were provided with a template for their lesson design, along with different features for the options. All of the teachers expressed that they “did not think that [any option] was missing” (T3). The teachers “like[d] having the flexibility” to plan an activity based on what would work for their class (T4). Additionally, when first engaging with the real-time scenarios, all of the teachers questioned where the lesson settings had come from and indicated that these were decisions they would want to have already set during the lesson planning, emphasizing the importance that teachers place on planning.
Besides the teachers’ view that the orchestration system did not encroach on their planning control, six of the seven teachers indicated that the template from the system actually made them reflect more on their planning. The teachers liked the system “because it broke it down into chunks and steers [them] towards thinking about group/individual” (T7) and “gives you different ideas of what to group the students by and then how to transition” (T6). This support provided the teachers with more ideas about what might work for their class. In particular, the teachers found the idea of the transitions novel, commenting that they “don’t typically ever transition with something like that” (T2) and “had not thought of transitioning in that way” (T3) but thought that it was something “interesting” and “new” to think about. This broadening of ideas came about when the teachers transferred their paper planning into the system; after seeing the options in the system, they changed their planning of transitions (see Fig. 1).
An aspect of planning that did not surface until the reflection on the fluid social transition scenario, S3, was students’ waiting time between activities when they are working at their own pace. Four of the seven teachers asked “when [the students] are waiting for their partner, is there anything that they are doing?” (T7) and stated that they were “not necessarily a fan of them just waiting” (T5). All four of these teachers suggested that this is something they could plan for by having a task in place that “if it is right there for [the students], they could just click over and it is not disruptive to the kids around them” (T4). Additionally, there were some automatic decisions made by the system that the teachers wanted to guide during planning, which we address in the following section. These requests for the ability to make additional decisions during the planning so that the system can carry them out in the classroom, support the idea that if teachers have a larger orchestration role during the planning, they are able to share more of the role of real-time orchestration.
Teacher Control and Automatic Decisions
Based on Study 1, we recommended that the co-orchestration responsibilities be split, with the system taking real-time orchestration action within the bounds of the lesson design (desire 2), enabling teachers to focus on student learning. In other words, the system informs the teacher of a decision but does not wait for them to approve it before taking action. At the same time, the teacher is able to take any orchestration action if necessary, to adapt the lesson design or revert a system decision (desire 3). In the scenario review sessions, all of the teachers expressed pleasure that the system kept the class moving forward, with one teacher stating that the fluid social transitions “is ideal in an ideal situation” and it “would be fantastic if [they] were able to do [it]” (T2). The system was able to “make [the] transitions a little more seamless, a little more quick” (T4). In terms of groups, the teachers liked the fact that they were no longer the bottleneck. One teacher commented that when a student is absent, “you do not have to deal with the ‘Wait, your partner is not here. Well, let’s wait and see.’ It is just like ‘bang’, there is a partner” (T1). The same sentiment was expressed for when a student leaves early, in which case “[the students] are not like, ‘[teacher], what do I do?’ They are just able to go and join a group” (T2). The teachers felt that “if anything, [they thought] that it would run better than if [they were] doing it on [their] own” (T6), because the system would allow students to work at their own pace and get the support they need, which teachers cannot provide when they are also having to manage the transitions.
In the scenario review sessions, the teachers also focused on how the system support for real-time decisions allowed them to focus on other aspects of teaching. The student pairing support from the system helped to “take away [teacher] bias” and allowed teachers to not “waste any brain power on reassigning [students]” (T3). In addition to reducing the cognitive aspects for the teachers, they saw the support as “huge time savers in pairing students and transitions and grouping methods” (T2) and stated that it would “take some time off of [their] plates” (T5). When the system took over “those little bits and pieces of [the teacher] managing it” (T3), the teachers could instead “focus on the misconceptions” (T1) to support student learning.
However, there were moments during the real-time scenarios when the teachers were concerned about a decision that was made. In these instances, the teachers were curious about what actions they could take in terms of orchestration to address such a decision. For example, when the students had more choice, such as marking other students as absent or setting their own pace, the teachers were concerned that the students may just be clicking without any intent and expressed that they “would want to be able to override that” (T2) in order to undo an action or move students back to complete an activity. The system provided the teachers with the ability to take orchestration actions, and they felt they “could pretty much do whatever [they] wanted” (T4) once the action was shown to them. Partially due to the ease of this control, where the teachers “did not have to type in and justify why,” a level of trust was built with the system, insofar as the teachers felt “it trusts [them] and [they] are in charge” (T3) even though the running of the lesson was being implemented by the system.
Nevertheless, there were still instances of automatic fluid transitions in which the teachers felt they did not have enough say. When adapting the use of social level to student needs, there are many metrics that could be adapted to (e.g., motivation, strategies, prior knowledge, metacognition), and when forming new groups, there are many ways to get the new group started when the students may be in different places in the activity. Five of the seven teachers explicitly mentioned they would want to “choose how the students are going to be adapted to” and paired (T5). This choice is something that they would wish to have during the planning while the system still automates in real time. Such a division would provide the teachers with some control over the automation while not having to carry any of the orchestration load during the lesson.
Awareness and Monitoring
Within the orchestration system, for the system to support automatic transitions, it needs to monitor and understand the state of the students (desire 4). In addition to all seven of the teachers finding this general monitoring “so cool” (T5), over half of the teachers also commented on how it supplemented the monitoring that they could undertake in the classroom on their own. In the classroom, when teachers are working with students, they “sometimes struggle with knowing when a group is ready to go on” (T7). The teachers felt that they “could walk around but it is faster to just have it on the screen” (T6), allowing teachers to spend more time with the students. Additionally, through the system monitoring, “there is…an expectation and there is a paper trail or data left behind so there is some accountability” (T4). This accountability can prevent the students from “hiding” (T4), which the teachers cannot prevent on their own.
Through the system monitoring and displaying information to the teacher, the teachers also expressed having a greater awareness of what was happening in the classroom than they would otherwise have (desire 5). The orchestration system made time-related aspects of the learning more visible, as a teacher “could look up and realize that [a student] has been waiting three minutes” (T2). The information provided the teachers with “a quick way to look” (T3) without interrupting what they were doing. Additionally, when the system was able to make the teacher aware of why it had performed an orchestration action, “that really made [the teachers] trust it” (T3).
However, the information regarding the system’s orchestration actions was often still not sufficient, and the teachers wanted the system to be more explainable. Five of the seven teachers wanted to know “how the system would know” some information (T6). The teachers all wished for a way to understand how the system had made its decisions, enabling them to judge whether the decisions were correct or whether more support was needed. Specifically, the teachers wanted to have a better understanding and “get notified about all of the misconceptions that [the students] are having all the time” (T1). Although not related to the orchestration of social transitions, as the system relieved teachers of much of the burden of managing transitions in real time, the teachers felt they would be able to give more thought to student learning support. The teachers wanted the option to see “where [student] misconceptions were” (T2) and “what their approach was” (T7) so that they could “see who is having trouble” (T7).
Student Communication
Finally, five of the seven teachers commented on the reduced reliance on the teacher that the system provided through directly communicating with the students who their partner is, what their next activity is, and when to transition (desire 6). When the system gives directions directly to the students, “it really keeps it off of the teacher” (T3), enabling them to use their time for other things. Additionally, the teachers appreciated these direct instructions from system to student, as “that way [students] do not interrupt [the teacher]” (T2). The teachers also liked that the directions come from a different source “because a lot of [students] don’t want to just listen to [the teacher]” (T4). Thus, the system can provide another source of information for the students.
However, the teachers did not want all of the orchestration communication to come from the system. Although they appreciated the system’s support of communication regarding the social transitions, over half of the teachers expressed a desire to communicate with the students through the system and give the students small encouragements and reminders about behavior. The teachers wanted to use the system to prevent students from “get[ting] embarrassed in front of their friends and then get[ting] confrontational” (T1). In this way, the teacher could continue “working with other students” (T2) and could send “something that is quick and easy” (T5).
Study 2 Discussion
Through the scenario review sessions, we aimed to encourage teachers to reflect on the co-orchestration design desires from Study 1, in order to explore whether the divisions still aligned with their values. To help with this reflection, we presented the desires as realized in an early orchestration system prototype. The teachers reacted positively to the orchestration system. At the beginning of the sessions, the teachers were “a little hesitant, but after seeing some of the sessions in action, [they] feel like it is something that [they] could do” (T4). Once they had been through the different social transition scenarios, the teachers wished to have a co-orchestration system in their classrooms, with one teacher saying, “I hope I am alive when this happens and still teaching” (T2). By taking some of the orchestration load off of the teachers’ plates, they felt they would be able to focus more on supporting student learning.
Overall, the teachers liked the balance achieved by the teacher doing more of the upfront planning work and the system orchestrating the real-time flow with teacher oversight. This sharing of the orchestration responsibility allows for fluid transitions that would not have been possible before, without a dedicated co-orchestration system. The teachers felt that with this system, they could focus more time on helping the students, which was a primary value for them. Even where the scenarios fell short, such as in setting the adaptation metrics and having non-productive wait time for students, the teachers merely wanted to have more control during planning to specify these terms. They then felt secure in the system automatically orchestrating the lesson in real time within these parameters.
Additionally, the teachers liked the support that the system monitoring could provide in terms of being able to orchestrate the fluid social transitions and the awareness support with which it provided them. However, they did not want the system to be a black box. As they were still responsible for their classroom, they wished for greater awareness of what information the system used to make its decisions, such as when to pair students for an activity that is set to be done independently. This would enable them to comprehend the system’s decisions and ensure that they were correct for their class. To account for this need, we would extend our fifth design desire to include teacher awareness of system decision-making processes and our fourth design desire to include system explainability (Putnam and Conati 2019).
Although the early prototype may have presented some usability issues that could have influenced the teachers’ experiences and viewpoints regarding the support the system provided them, we fixed any issues that were discovered before the later sessions. Across all sessions, we supported the teachers in the use of the system and could answer any questions that they had in the moment. We could not tie any of our results to usability issues.