Topic
Drexler-Sibbet team performance model
Weak Weak
Allan Drexler and David Sibbet's model describes seven stages of team development, each framed as a question the team must answer. Stages 1–4 are about creating the team; stages 5–7 are about sustaining performance.
Its practical advantage over tuckman: each stage names both the resolved and unresolved state, so it functions as a diagnostic rather than merely a description.
Evidence: Weak. No independent empirical validation; a practitioner framework developed for facilitation work. Its practical advantage over tuckman is structural rather than evidential: naming both the resolved and unresolved state for each stage makes it usable as a diagnostic. The seven questions are more useful than the seven labels.
Use when: launching a team, or diagnosing a team that is underperforming for reasons nobody can name.
Do not use when: the team is fine and you want to run an activity. Do not intervene in a working team.
The seven stages
Creating
| # | Stage | Question | Resolved | Unresolved |
|---|---|---|---|---|
| 1 | Orientation | Why am I here? | Purpose, membership, sense of belonging | Disorientation, uncertainty, fear |
| 2 | Trust building | Who are you? | Mutual regard, spontaneous interaction, reliability | Caution, facade, mistrust |
| 3 | Goal clarification | What are we doing? | Explicit assumptions, clear integrated goals | Apathy, skepticism, irrelevant competition |
| 4 | Commitment | How will we do it? | Assigned roles, allocated resources, shared decisions | Dependence, resistance |
Sustaining
| # | Stage | Question | Resolved | Unresolved |
|---|---|---|---|---|
| 5 | Implementation | Who does what, when, where? | Clear process, alignment, disciplined execution | Conflict, missed deadlines, confusion |
| 6 | High performance | Wow! | Spontaneous interaction, synergy, surpassing expectations | Overload, disharmony |
| 7 | Renewal | Why continue? | Recognition, change mastery, staying power | Boredom, burnout |
How to use it as a diagnostic
Ask the team to rate each of the seven questions as resolved / partly / unresolved, individually and anonymously, then compare. Two patterns are informative:
- The team disagrees about which stage is unresolved. That disagreement is itself the finding, and usually points at stage 1 or 3.
- A late-stage symptom with an early-stage cause. Missed deadlines (stage 5) are very often unclear goals (stage 3) or absent commitment (stage 4). Fixing the symptom with more project management fails.
The model is explicitly non-linear: teams revisit earlier stages whenever membership, purpose, or context changes. A new manager resets stages 1 and 2 for everyone, whether or not anyone acknowledges it.
Examples by audience
Health care: a multidisciplinary team where each profession has a different answer to "what are we doing?" is stuck at stage 3, and will present as stage 5 chaos in the clinic. Ninety minutes on goal clarification is worth more than a new rota.
Software: a squad with clear tickets (stage 5) and no answer to "why am I here?" (stage 1) delivers steadily and loses people. Attrition is a stage 1 and stage 7 signal, not a compensation signal.
Executive: a newly appointed executive team spends its first months at stage 5 because the calendar demands output. Stages 1–4 then surface as slow-motion conflict about scope and authority for the following year. Invest the two days early.
Limitations
- Little independent empirical validation.
- Seven stages is more than most groups will retain; use the questions rather than the labels.
- Requires a facilitator to be useful; self-administration tends to be shallow.