Scaffold the transition into team work with explicit team-level AI norms and coding-inclusive team entry points¶

Strategy · All strategies
Evidence · no claims cited

Description¶

The article recommends treating the onset of collaboration as a design moment: instructors should "consider designing team entry points that include meaningful coding components" and run "A targeted intervention at the start of the collaborative phase, explicitly discussing how AI tools should be used within teams, who is responsible for verification, and how AI contributions should be attributed". This targets the behavioral disruption observed at TP1 and the verification degradation that persists beyond it.

Design Implications¶

Context¶

Requirements¶

• Instructors must be able to time an intervention at the start of the collaborative phase and discuss AI use, verification responsibility, and attribution norms within teams.

Constraints¶

• Non-coding tasks like TP1 may suppress LLM use in ways unrelated to social context, so entry-task content shapes what AI behavior can be observed.

Target Learners¶

• Undergraduate computing students working on team-based projects

Target Learning Goals¶

• Deliberate LLM engagement, including prompting and output verification, during collaborative work

Related Strategies¶

• Team Contracts

Examples¶

-

Key Sources¶

• Sehrish Basir Nizamani, Zannah Ziew, Saad Nizamani, and Khyati Goyal. (2026). Less Deliberate in Teams: Student LLM Use Across Individual and Collaborative Work. https://arxiv.org/abs/2606.30860