Team effectiveness
·
9 min read
Key findings
In a study Hackman cites, 40 per cent of first explanations for poor performance concerned personality, so requests arrive as team building.
Hackman's five conditions are a real team, a compelling direction, an enabling structure, a supportive context and expert coaching, with coaching last.
Hackman estimates that 60 per cent of the variation in team effectiveness depends on the enabling conditions and 10 per cent on real-time coaching.
A week of agendas, membership lists, six conversations and one observed meeting is enough to assess the conditions without a survey.
A 2026 pilot of five teams found purpose scores rose by an average of 13 per cent after a workshop, with no comparison group.
Ask each member of a struggling leadership team to write down who is on it, separately, and compare the lists.
A team effectiveness model is a set of conditions an adviser checks to find out why a team underperforms. Richard Hackman names five: a real team, a compelling direction, an enabling structure, a supportive organisational context and available expert coaching. The adviser checks them in that order before agreeing to team building, because only the fifth points at coaching.
A director reports that the leadership team is not working well together and asks for a team building session.
The session happens, people enjoy it, and six weeks later the same meetings produce the same outcomes.
The request named an intervention before anyone had diagnosed the problem.
Team Effectiveness Models Compared
Six models recur in the guides that rank for this term, and each answers a different question.
Tuckman describes stages of team development from forming to performing, and suits a team that is new or has changed membership
GRPI, from Richard Beckhard in the early 1970s, checks goals, roles, processes and interpersonal relationships, with relationships at the base
Lencioni lists five dysfunctions, starting with absence of trust, and suits a team that avoids conflict
T7, from Michael Lombardo and Robert Eichinger, separates five internal factors from two external ones, team leader fit and organisational support
Katzenbach and Smith distinguish a working group from a real team by whether the work needs collective work products
Hackman names conditions that leaders can create and maintain, and tests effectiveness against three outcomes
Asana, in an article dated 17 April 2026, summarises four of these models, and Atlassian summarised four in 2021.
Workhuman updated a seven-model version on 28 August 2026.
Asana and Atlassian advise choosing one model, and Workhuman matches models to team types.
None says what to do when the leader's request already contains a diagnosis.
For an internal adviser, the useful test is whether each part of a model names something the organisation can change.
Hackman's conditions name things the organisation controls, such as structure, context and coaching.
This article therefore works from them, and psychological safety at team level covers the trust-based models in more depth.
The Attribution Problem
Hackman cites a study in which Richard Corn asked members of teams to name the root cause of their team's performance.
The teams ranged from community health groups to a mutual fund company to military units.
For teams performing well, over 60 per cent of the explanations concerned someone's personality or behaviour, and that someone was frequently the leader.
For teams performing poorly, 40 per cent of the first attributions were about personality or behaviour.
Few explanations addressed the team and organisational features that may have driven the result.
Hackman calls the pattern the leader attribution error.
It explains why the request arrives as team building, because the person asking has already located the cause in people.
Three Outcomes To Measure
Hackman tests effectiveness against three criteria.
The output is acceptable to the people who receive or use it
The team ends its work at least as capable as it began
Members are at least as satisfied as they are frustrated
None of the three requires extraordinary accomplishment, and all three can be checked before any intervention is proposed.
The first needs a conversation with the client of the team's work.
The second needs the team's own account of what it has learned about working together.
The third needs a short private conversation with each member.
Five Conditions
Hackman's 2002 account sets out five conditions that raise the chances of effectiveness.
A real team, rather than a team in name only
A compelling direction for the work
An enabling structure that helps rather than impedes teamwork
A supportive organisational context
Ample expert coaching in teamwork
The first three are the core conditions, and the last two help a team harvest the benefits of a good basic design.
His 2011 account lists six enabling conditions.
They are a real team, a compelling direction, the right people, clear norms of conduct, a supportive organisational context and competent coaching.
Both versions place coaching last.
In the 2011 account Hackman gives his own rough estimate of where effectiveness comes from.
Sixty per cent of the variation depends on the enabling conditions, 30 per cent on the quality of the launch and 10 per cent on the leader's real-time coaching.
He also reports a study of intelligence analysis teams, with Michael O'Connor.
In it the conditions accounted for 74 per cent of the variation in a multi-attribute measure of overall effectiveness.
Both figures come from one researcher's work with a specific kind of team, and the first is a stated estimate.
What Makes A Real Team
Hackman lists four features of a real work team.
A genuine team task
Clear boundaries, so members know who is on it
Clearly specified authority to manage their own work
Stable membership over a reasonable period
The boundary question defeats more groups than it should.
Hackman describes ambiguity about membership so great that people cannot reliably tell those who share accountability for the outcome from those who help out.
A clear boundary does not require everyone to work in one place at one time, and it does not freeze membership.
It means members know who is on the team.
Ask each member of a struggling leadership team to write down who is on it, separately, and compare the lists.
Coaching Comes Last
Hackman states that the leader's job is to get the enabling conditions in place and launch the team well.
He adds that the job is certainly not to run the team through team building exercises intended to build trust and harmony.
His evidence is Ruth Wageman's research on service teams at Xerox.
Team design accounted for more variation in self-management and performance than the leader's coaching did.
Good coaching helped well-designed teams manage themselves and made almost no difference to poorly designed ones.
Bad coaching hurt poorly designed teams and did little to well-designed ones.
Coaching a team whose first three conditions are broken therefore wastes the coach's time.
When coaching is the wrong answer covers the same question for an individual.
Team design accounted for more variation in self-management and performance than the leader's coaching did.
A Diagnostic That Takes A Week
A practitioner can assess the conditions without a survey instrument.
The sequence below assumes an HR business partner, a managing director and her leadership team of eight.
Day one, contracting. The business partner asks the managing director what has been tried, what outcome would count, and whether she accepts that the findings may concern her own part
Days one and two, documents. The last three meeting agendas and minutes are read for whether the work is genuinely shared
Day two, membership lists. Each of the eight writes down who is on the team, separately, and the lists are compared
Days three and four, conversations. Six short conversations use one question per condition
Day five, observation. One meeting is watched for who defers to whom, where decisions land, and how much time goes to information rather than decisions
Day six, write-up. A statement of which conditions hold and which do not, with the evidence for each
Day seven, playback. The managing director sees it first and alone, and the team sees it a few days later
The output is a different document from a team report.
It names conditions and the evidence for each, and it says nothing about anyone's personality.
Evidence For Each Condition
A condition holds when the adviser can find the following.
Real team. The membership lists agree, and at least one task needs a joint work product
Direction. Six separate one-sentence statements of purpose say the same thing
Structure. Members can name the decisions the team takes without the leader, a topic covered in decision rights inside a team
Context. Members can name one reward, one source of information and one resource that help, and one that hinders
Coaching. The team has reviewed how it works within the last six months and can name what changed
These are practitioner tests rather than validated instruments.
A published instrument, the Team Diagnostic Survey, exists for the conditions.
The diagnostic here is the lighter version that an internal adviser can run without one.
Six Questions
What work can only be done by this group together
Who is on the team, and who decided that
What is this team's purpose, in one sentence
What can this team decide without asking
What does the organisation give you that helps
When did the team last review how it works
The third question is the most revealing when asked of six people separately.
Six different sentences means that nobody has set a direction the team shares.
Reporting To The Sponsor
A diagnosis of conditions reads differently from a report on relationships, and it is easier to act on.
Hackman treats creating and maintaining the conditions as the main responsibility of leadership.
A finding about conditions is therefore a finding about leadership practice, which the sponsor can accept without being accused of anything.
Three sentences carry the report.
This group is not currently a team, because four members named a different membership and the work does not require them jointly.
The direction is set in three different ways by three stakeholders, which the team cannot resolve on its own.
Here is what I recommend, and one of the three actions belongs to you rather than to them.
The last clause assigns one action to the sponsor.
If the sponsor resists a finding that implicates them, advising a leader you disagree with covers the conversation.
When Team Building Is Right
Team development work earns its place in a narrow set of conditions.
The team is real, the direction is agreed, the structure works, and the members still cannot operate together.
That situation exists, and it is rarer than the volume of requests suggests.
Two other cases justify a session.
A newly formed team needs a launch that establishes the task, the boundary and the norms.
A team whose composition has changed substantially needs the same work again.
Hackman notes that a relaunch can give a persistently ineffective team a fresh start.
Designing a two-day offsite covers how to build one around decisions.
The Difficult Team Member
Hackman warns that the impulse to scapegoat a member when the going gets rough can be strong.
The scapegoated member often starts to behave in line with teammates' expectations, which sets a self-fuelling spiral in motion.
Teams should therefore move slowly on an impulse to blame and dismiss someone they find disruptive.
A practitioner asked to coach the difficult person should first check whether the task, the norms or the composition are producing the difficulty.
Groups That Are Not Teams
Some groups meet weekly, share a name, and have no work that requires them together.
Katzenbach and Smith distinguish a working group from a team.
A working group relies on the sum of individual contributions, and a team needs collective work products and mutual accountability.
They add that a structured working group can make more sense, particularly at the top of multibusiness companies.
Hackman says teams should be used only when there are good reasons for them that can be named.
Naming this is a service to the sponsor, and it is rarely welcome.
Two honest options follow.
Convert the group into an information forum, halve its frequency, and stop calling it a team.
Or give it a real shared task with a decision attached, which is a decision for the sponsor rather than the group.
Recent Peer-Reviewed Evidence
A pilot study in Frontiers in Psychology, published on 8 April 2026, used Hackman and Wageman's conditions with five teams at a University of Michigan research institute.
The teams took part in an 11.5-hour workshop spread over five to six weeks, aimed at purpose and structure.
Compelling purpose scores rose by an average of 13 per cent immediately afterwards.
Sound structure scores rose by an average of 8 per cent in three of four teams.
They fell in the fourth, which the researchers suggest may reflect a shorter scale.
The study had no comparison group, and its researchers could not confirm what drove the later changes.
It shows that purpose and structure can be scored with a standard survey.
It also shows that a workshop aimed at those two conditions moved the scores in the short term.
Where The Tools Sit
In Trusted Talent Advisor, component 01, The Core Practitioner Guide, holds the Capability Architecture lens, which separates structural causes from role design, skill and behavioural ones.
Component 02, The Stakeholder Conversation Toolkit, covers turning a request such as team building into a brief the requester can defend.
Sources
1. Hackman, J. R. Leading Teams: Setting the Stage for Great Performances. Harvard Business School Press, 2002.
2. Hackman, J. R. Collaborative Intelligence: Using Teams to Solve Hard Problems. Berrett-Koehler, 2011.
3. Katzenbach, J. R. and Smith, D. K. The Wisdom of Teams: Creating the High-Performance Organization. Harvard Business Review Press.
4. Laursen, B., LaPensee, E., Brudzinski, M. and Richards, B. Strategy Jams: Using Design Thinking to Charter Teams with Compelling Purpose and Sound Structure. Frontiers in Psychology, 8 April 2026.
5. Tronier, R. Team Effectiveness: 4 Models to Build Better Teams. Asana, 17 April 2026.
6. deBara, D. 4 Team Effectiveness Models to Understand Your Team Better. Atlassian, 23 September 2021.
7. Workhuman Editorial Team. 7 Best Team Effectiveness Models in 2025. Workhuman, updated 28 August 2026.
From the system
Trusted Talent Advisor sets out the full method: seven components, 51 tools, The Talent Template Pack and The Prompt Library.
See the system
Questions this answers
What is the Hackman model of team effectiveness?
Hackman's 2002 account names five conditions: a real team, a compelling direction, an enabling structure, a supportive organisational context and available expert coaching. The first three are core and coaching comes last. His 2011 account lists six, adding the right people and clear norms of conduct.
What are the models of team effectiveness?
The recurring ones are Tuckman's stages, GRPI, Lencioni's five dysfunctions, T7, Katzenbach and Smith's working group versus team, and Hackman's conditions. They answer different questions: the stage, role clarity, trust, internal versus external factors, or what the organisation controls.
How do you diagnose a dysfunctional team?
Read the last three agendas and minutes, ask each member separately who is on the team, hold six short conversations with one question per condition, and observe one meeting. Then report which conditions hold, with the evidence for each, before proposing any intervention.
How do you measure team effectiveness?
Hackman's three criteria are output acceptable to those who use it, a team at least as capable at the end as at the start, and members at least as satisfied as frustrated. The Team Diagnostic Survey scores the conditions that produce those outcomes.
Does team building actually improve team performance?
Hackman says a leader's job is certainly not to run team building exercises to build trust and harmony, and he estimates that 60 per cent of effectiveness depends on the enabling conditions. A session helps when the team is real, the direction is agreed and the structure works.
What are the signs of a dysfunctional team?
Early signs are members naming different teammates, giving different one-sentence purposes, and sending decisions to the leader. Lencioni's model lists absence of trust, fear of conflict, lack of commitment, avoidance of accountability and inattention to results as the behavioural dysfunctions.
Keep reading
Measuring HR impact
Internal Mobility Metrics Without A Platform
Seven measures an HR adviser can build from existing records, each with a stated definition, a base and a way to read it.
7 min read
Workforce and future skills
Job Rotation As A Talent Gap Strategy
A job rotation programme closes a talent gap when the role, the person, the cover and the evidence are agreed with both managers before it starts.
8 min read
Talent reviews and succession
Seeing Talent Below The Top Team
Visibility of leadership potential drops below the top team. A cross-unit forum, run on one page per unit and a written evidence standard, is the method for seeing it.
8 min read