THE DIMENSION
Helping a group examine experience and agree useful process adjustments.
The dimension in context
Helping a group examine experience and agree useful process adjustments.
You may contribute examples that improve shared understanding.
You may learn individually or work in a team with little review time.
An illustrative work situation
A project review focuses on each person’s completed tasks, but the main difficulty occurred between tasks: a decision was not communicated at a handoff. An individual checklist misses the interaction that created the delay. The review needs to examine the sequence of coordination as well as separate contributions.
Team review is not simply collecting individual accounts and adding them together. People may have seen different parts of the same episode. A useful process preserves those differences long enough to identify a shared dependency or misunderstood signal. The goal is a more specific learning question, not an immediate consensus story.
A small practice to examine
Reconstruct one handoff using accounts from the people involved. Mark what each person knew and expected at the time. Identify a small change to the information, timing, or ownership at that boundary. In the next comparable task, check whether the change addresses the actual interaction problem.
Review without decisions can become repetitive discussion.
A question for closer study
Would a review identify a coordination issue that no individual task record reveals on its own?
Read the example alongside the research
The following editorial passages come from the linked framework chapters. They provide context for the original teaching example above; the example is fictional and is not a reported study finding.
Team research examines shared understanding, the distribution of expertise, communication, and collective performance. These concepts describe different levels of analysis. A team can have a useful knowledge system that no single person possesses, while an individual can make a valuable contribution without fitting a fixed role label. MTC proposes six categories of reported practice: alignment, information sharing, dependable coordination, assistance, voice, and collective learning. It does not reproduce a team-role instrument or measure group intelligence.
A practical review could ask whether the team's development question can be discussed through a fictional case or a shared process map instead of individual scores. For example, the group can clarify handoff responsibilities without discovering who endorsed a particular statement. If participants choose to share a personal observation, they can select its scope rather than being required to disclose a complete report as proof of cooperation. Researchers should examine whether the activity pressures quieter members to explain themselves while more influential members remain unchallenged. The ethical quality of the exercise includes what happens when someone declines to share. A refusal should not be interpreted as a low contribution score or used to justify a new claim about the person's suitability for the team.
Continue: Team development should not become a ranking of belonging →
SOURCES AND FURTHER READING
Lewis - Measuring transactive memory systems in the field ↗Mathieu et al. - The influence of shared mental models on team process and performance ↗Woolley et al. - Evidence for a collective intelligence factor in the performance of human groups ↗AHRQ - TeamSTEPPS: Explanation and value of the curriculum ↗Edmondson - Psychological safety and learning behavior in work teams ↗Nembhard & Edmondson - Making it safe: Leader inclusiveness and professional status ↗