Team Development

Understanding the concept

Team development involves learning how to work together under real demands. The forming–storming–norming–performing sequence provides a vocabulary for recurring challenges, not a timetable every team must follow. Membership changes and difficult tasks may reopen earlier disagreements.

Teams evolve through predictable stages of development, and getting stuck at an early stage (especially storming) prevents the coordination and trust needed for high performance. Shared mental models let members anticipate each other's actions without constant explicit communication, which becomes critical under time pressure.

Trust allows members to rely on one another; coordination aligns timing and responsibility; shared mental models support a common understanding of tasks and dependencies. Conflict can reveal unresolved expectations rather than indicate that the team is irretrievably broken. Development requires working through those expectations with clear agreements and opportunities to test them. Calling a team 'storming' is not an intervention unless the label leads to an explanation of what must change.

Core components and theoretical lenses

Use the following distinctions to unpack the chapter's central idea. Each identifies a different aspect of the problem; their relationships matter as much as the labels themselves.

1. 01

   Forming (orientation and politeness)

2. 02

   Storming (conflict over roles, power, direction)

3. 03

   Norming (agreement on working rules)

4. 04

   Performing (interdependent, trust-based execution)

5. 05

   Trust building mechanisms

6. 06

   Shared mental models and coordination

Conceptual constructs

A construct names an idea used to interpret behaviour. It is not directly interchangeable with a survey score or a single incident. In this chapter, the constructs below organize the diagnosis; examine how they could explain the observations before deciding what to change.

• Team development stages (Tuckman)
• Trust
• Shared mental models
• Coordination
• Psychological safety (related)

Observable and measurable indicators

Indicators connect an abstract explanation to something that can be observed. Check the operational definition, reporting period and comparison group. A survey average can conceal differences between teams, and an administrative record can reflect willingness to report as well as underlying behaviour.

• Frequency and tone of conflict episodes logged in retrospectives
• Cycle time for decisions requiring cross-member agreement
• Trust survey scores (cognitive and affective trust)
• Rework caused by misaligned assumptions between sub-teams
• Time to consensus on technical disputes

Reading the case evidence

Separate what the case reports from what you infer. A figure can establish the scale of a problem without establishing its cause. Note what information is absent and how that gap affects your confidence in a recommendation.

Decision alternatives and trade-offs

Alternatives represent different priorities and assumptions. The advantages and limitations below are the existing module's analytical prompts. Compare them against the same evidence rather than choosing first and finding a theory afterward.

Evidence-based discussion

For the ERP project, distinguish disagreements about expertise, authority and work priorities. Compare alternatives by how they rebuild dependable coordination. Establish who decides, how blocked tasks are escalated and how commitments are reviewed. Evaluate progress through completed dependencies and the quality of joint problem-solving rather than assuming that a calmer meeting means the team has reached a later developmental stage.

Theory-linked interpretation from the module

Use Tuckman's stage model to diagnose that the team is stuck in storming, and trust theory to explain why documentation-for-self-protection behavior signals low affective trust. Shared mental model theory explains why compliance and the vendor are misaligned with IT/operations. A good justification weighs schedule risk against the durability of the fix chosen.

Your managerial judgement

Should the VP sponsor prioritize speed (restructuring authority) or team process (facilitated norming/shared mental models) to unblock the ERP team, and what is the risk of each path given the penalty deadline?

Write a recommendation that identifies a preferred alternative, uses the reported evidence, acknowledges uncertainty and specifies a review point. Another choice can be defensible when its assumptions and trade-offs are made explicit.

Possible consequences

The module offers the following projections for discussion. They depend on implementation and context; they are not guaranteed effects or verified forecasts.

• Short-term: any intervention will consume scarce time against a tight penalty deadline
• Short-term: restructuring authority may cause a leadership exit or morale dip
• Long-term: reaching a performing stage improves velocity for the remaining 48 branches
• Long-term: unresolved distrust between IT and ops could recur in future joint projects
• Long-term: vendor relationship credibility is affected by how internal conflict is perceived externally

Reflection questions

1. What specific behaviors indicate this team is stuck in storming rather than progressing to norming?
2. Why does low trust lead people to document issues defensively rather than resolve them collaboratively?
3. How does excluding compliance early undermine the team's shared mental model?
4. What would a performing-stage version of this team look like in observable terms?

Practice: Know → Analyse → Decide

These are the original module questions. Reading or printing this textbook does not change quiz scores, completion or certificate eligibility.