Skip to content

Group Processing

Element · All elements
Evidence · 6 claims (6 for) · 6 studies (3 causal, 2 review, 1 quant-synthesis), q2–q3 · 3 of 6 report an effect size · 5 claims rest on one study

Description

Group processing is the fifth element of cooperative learning: after (or during) a collaborative task, the group explicitly reflects on its functioning — which member actions helped or hindered the work, and what to do differently next time. It converts collaboration from an assumed condition into an object of learning, giving teams feedback on both task performance and interpersonal effectiveness.

Design Implications

Processing improves both achievement and the durability of cooperative groups by making team behaviors explicit and adjustable Cooperative learning with group rewards and individual accountability improves achievement. [+S]. Processing works best when it is specific (naming concrete behaviors, not "we did fine"), scheduled (not left to leftover time), and followed by a goal for the next session. Combining group-level processing with individual accountability keeps reflection from masking unequal contribution Cooperative learning with group rewards and individual accountability improves achievement. [+S].

Context

Requirements

  • Clear criteria for what "working well together" looks like, so reflection targets observable behaviors
  • Time explicitly allocated for processing — it must not be squeezed out by task completion
  • A structure: checklists, sentence stems ("One thing our group did well was…"), or rating scales
  • A follow-through loop: the group sets one improvement goal for the next session (Check-In at the start of the next meeting closes the loop)

Constraints

  • Without individual accountability, processing can become social loafing theater — groups praise themselves while work stays unequal Cooperative learning with group rewards and individual accountability improves achievement. [~S]
  • Unstructured "how did it go?" discussions tend to produce politeness and vague agreement rather than behavioral change
  • In short-lived or one-off groups, processing has little payoff because there is no next session to apply improvements to
  • Groups with unresolved interpersonal conflict may need teacher-mediated processing before self-processing works

Target Learners

  • Learners new to collaborative work, who lack scripts for giving and receiving peer feedback
  • Long-term teams (project groups, lab teams) where processing compounds across sessions
  • Less useful for individuals working alone; the reflection target is the group as a system

Target Learning Goals

  • Collaborative skill acquisition: turn-taking, elaborating, challenging ideas constructively
  • Metacognition: monitoring group processes, not just individual understanding
  • Social-emotional learning: perspective-taking, conflict resolution, shared norms

Affordances

  • Collaborative Learning — processing is the feedback mechanism that makes cooperative structures improve over time rather than repeat their dysfunctions
  • Assessment for Learning — group processing is formative assessment applied to team process: criteria, evidence of current performance, and a next-step goal
  • Self-Regulated Learning — the reflect-and-set-goal cycle enacts the self-regulation loop (forethought → performance → self-reflection) at the group level
  • Scaffolding — teacher-structured processing prompts (checklists, stems) can be faded as groups internalize the reflection routine

Claims

  • Positive Interdependence — processing evaluates whether the group is actually relying on one another
  • Individual Accountability — the counterweight that keeps processing honest about contribution
  • Check-In — the opening counterpart that carries the previous session's processing goal forward
  • Coaching — teacher mediation of early processing conversations before groups self-manage

Patterns That Use This Element

Examples

Learning Together model — Johnson & Johnson's cooperative learning approach specifies processing as a routine end-of-session step: groups list two member behaviors that helped and one to change.

Project-Based Learning (PBLWorks) — PBL team contracts and milestone retrospectives operationalize group processing across multi-week projects.

Team retrospectives in agile software education — Capstone and software engineering courses adopt sprint retrospectives ("keep / stop / start") as an authentic professional form of group processing.

Key Sources

  • Johnson, D. W., & Johnson, R. T. (2009). An educational psychology success story: Social interdependence theory and cooperative learning. Educational Researcher, 38(5), 365–379. doi:10.3102/0013189X09339057
  • Johnson, D. W., Johnson, R. T., & Holubec, E. J. (2008). Cooperation in the classroom (8th ed.). Interaction Book Company.
  • Slavin, R. E. (1996). Research on cooperative learning and achievement: What we know, what we need to know. Contemporary Educational Psychology, 21(1), 43–69. doi:10.1006/ceps.1996.0004
  • Yager, S., Johnson, D. W., Johnson, R. T., & Snider, B. (1986). The impact of group processing on achievement in cooperative learning. Journal of Social Psychology, 126(3), 389–397. doi:10.1080/00224545.1986.9713601
Page metadata
Field Value
type element
id group-processing
title Group Processing
description A structured reflection in which cooperative groups evaluate how well they worked together and identify behaviors to keep or change.
status review
canonical True
generated by claude/unspecified on 2026-08-29
trust unverified — no one has confirmed this page's content

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