Skip to content

A three-stage design space for hybrid control in dynamic pairing: before, during, and after pairing up.

Design · All designs
Evidence · no claims cited

Description

The article organizes the dynamic pairing process into a design space of control distribution across three stages: "Stage 1—Before Pairing Up, Stage 2—During Pairing Up(pairing, collaboration, and unpairing), andStage 3—After Pairing Up." Across these stages, the authors identified seven hybrid-control design challenges formulated as How Might We questions. This theory frames how agency and control can be distributed between teachers and students at each moment of pairing, from preparation and timing to transitions and future pairing.

Design Implications

Context

Requirements

  • A classroom context where students transition between individual tutoring and collaborative peer tutoring.

Constraints

  • The design space was derived from teacher and student participants in algebra equation-solving contexts.

Target Learners

  • K-12 mathematics students
  • secondary mathematics teachers

Learning Goals

  • classroom orchestration of collaborative learning
  • student agency in pairing decisions

Claims

Examples

-

Key Sources

  • Kexin Bella Yang, Menghan Liu, Liyi Xu, Nikol Rummel, and Vincent Aleven. (2026). Balancing Teacher and Student Agency: Co-Orchestration Tool Design Supporting Real-Time Dynamic Pairing. https://doi.org/10.1145/3816902
Page metadata
Field Value
type design
id theory-three-stage-hybrid-control-design-space
title A three-stage design space for hybrid control in dynamic pairing: before, during, and after pairing up.
description The article organizes the dynamic pairing process into a design space of control distribution across three stages: "Stage 1—Before Pairing Up, Stage 2—During Pairing Up(pairing, collaboration, and unpairing), andStage...
status review
generated by process:settle-candidates on 2026-10-12
trust unverified — no one has confirmed this page's content
sources 1 — kexin-bella-yang-2026

Frontmatter is the page's machine-readable record — see the Schema & Guide.