UPI Study › Courses › Leadership and Organizational Behavior › Free lessons › Lesson 11.6 Free with a free account
Evaluating Team Effectiveness and Addressing Common Team Performance Problems
Leadership and Organizational Behavior · Chapter 11: Work Teams, Group Dynamics, and Team PerformanceSection 11.6 · lesson 67 of 12210 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Leadership and Organizational Behavior.
Lesson complete
Earn the 3 college credits for Leadership and Organizational Behavior
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Building Sustainable High-Performance Team Cultures in Organizations →← Integrating Team Goals with Organizational Objectives and Managing Team ConflictNext lesson: Building Sustainable High-Performance Team Cultures in Organizations →
In this lesson
Rigorous assessment is the prerequisite to sustained improvement.
- Apply Hackman's three criteria
- Balance output metrics with process health
- Diagnose the root dysfunction, not the symptom
- Run reviews that improve how a team works
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,293 words). Read along, or search it.
Work Teams, Group Dynamics, and Team Performance
Evaluating Team Effectiveness and Diagnosing Dysfunction
Building a team is straightforward. Building an effective team is hard. Building one that sustains high performance over time is harder still. Evaluating team effectiveness, rigorously and honestly, is the prerequisite to sustained improvement. Without clear assessment, something specific goes wrong. Teams that appear productive may be failing on dimensions nobody is measuring. Those failures only become visible in the medium term. Member burnout is one. Skill stagnation is another. Hidden interpersonal tensions are a third. And misalignment with shifting organizational priorities is a fourth. This section covers Hackman's effectiveness criteria and balanced measurement. Then diagnosing dysfunction, and running reviews that actually change how a team works.
The Case
What Assessment Catches Before It Is Too Late
Consider why a productive-looking team can still be failing. Output is the easiest thing to measure, so it is what gets measured. A team hitting its numbers passes every check that exists. Meanwhile four things can be deteriorating quietly underneath. Members may be burning out, which shows up only when they leave. Skills may be stagnating, because the team keeps doing what it already knows. Interpersonal tensions may be accumulating without ever surfacing. And the team may be drifting out of alignment with organizational priorities. None of those four appears in a delivery report. All four eventually appear in results, and by then the causes are months old. Assessment exists to catch them while the correction is still cheap.
Hackman
Three Criteria for Genuine Effectiveness
Richard Hackman's research identified three criteria for genuine team effectiveness. Most organizations measure only the first of them. First, output effectiveness. The team's output must meet or exceed the standards of those who receive, review, or use it. Second, process sustainability. The team's processes must maintain or enhance members' capacity to work together in future. Read the consequence of that criterion carefully. Teams that deliver results by burning out their members are not effective by this definition. Third, member growth. The team experience must contribute positively to members' personal learning and growth. The second criterion is the radical one, because output alone cannot distinguish sustainability from consumption.
Enabling Conditions
Failures Are Usually Structural
Hackman also identified a set of enabling conditions. A real team, meaning clear membership and genuine interdependence. A compelling direction. An enabling structure. A supportive organizational context. And available coaching. The diagnostic consequence of that list is significant. In this framework, team failures are rarely purely behavioral. They usually reflect deficiencies in one or more enabling conditions. Which moves the first question from who is failing, to what is missing. And note the first condition especially. Many groups called teams are not real teams at all.
Metrics
Neither Half Works Alone
Effective team measurement balances two things that are usually treated as alternatives. Quantitative output metrics on one side. Qualitative assessments of process health on the other. Pure output metrics include revenue generated, or defect rate. They capture results, but they miss the conditions producing those results. So they tell you what happened without telling you whether it will happen again. Pure process metrics include meeting attendance, or documentation completeness. They capture activity, but not value. A team can be flawless on every process metric and produce nothing anyone wanted. So a balanced measurement system integrates both. Neither half is sufficient, and each half is misleading in a different direction.
Five Categories
A Balanced Measurement System
A balanced system uses five metric categories. Quantitative output covers revenue, units produced, defects per million, and on-time rate. It is measured through dashboards and automated tracking. Quality of work covers client satisfaction scores, error rates, and rework frequency. It is measured through surveys, audits, and inspection data. Process health covers decision cycle time, meeting effectiveness ratings, and norm adherence. It is measured through observation and retrospective surveys. Member engagement covers employee net promoter score, absenteeism, and voluntary contribution rate. It is measured through pulse surveys and human resources data. And learning and innovation covers new approaches tried, skills developed, and experiments run. That last category is the only one that measures whether the team is getting better.
Lencioni
Five Dysfunctions, Stacked
When teams underperform, the causes cluster into predictable patterns. Patrick Lencioni's widely read model identifies five dysfunctions. They are arranged hierarchically rather than as a list. At the base is absence of trust, which is the foundation failure. Above it sits fear of conflict, where open debate stops happening. Above that, lack of commitment, where decisions are made but not owned. Then avoidance of accountability, where nobody challenges a peer. And at the top, inattention to collective results. The stack matters more than the list. Each level rests on the one beneath it. Which means the visible dysfunction is rarely the one that needs fixing.
The Chain
Why the Order Matters
The model's real claim is about the chain, not the categories. Each dysfunction enables the next. A team that cannot trust cannot debate openly. Debate requires exposing a half-formed idea to people who might reject it. A team that cannot debate openly cannot commit to decisions. Unspoken disagreement does not disappear. It just goes unrepresented in the decision. A team that has not really committed will not hold each other accountable. And a team without accountability drifts away from collective results. This is why diagnosing the root dysfunction matters so much. A team that appears to avoid accountability may actually lack trust. Members do not call each other out because they do not feel safe doing it.
Common Problems
Four Challenges, Four Different Fixes
Four common performance challenges recur, and each needs a different intervention. Unclear objectives allow members to define success in incompatible ways. Everyone is succeeding by their own definition, and the team is not. Insufficient resources force tradeoffs without a clear decision framework. So the same tradeoff gets made repeatedly, and inconsistently, by different people. Talent mismatches leave critical capabilities uncovered. That gap is usually invisible until the moment the capability is needed. Leadership vacuums occur where nobody assumes responsibility for facilitation and integration. The work between people then belongs to no one at all. All four present identically, as the team is underperforming. Only diagnosis distinguishes them, and a confident wrong fix hides the real problem further.
Reviews
Space to Reflect on How, Not Just What
Regular structured reviews are distinct from project status meetings. That distinction is the entire point of them. A status meeting asks what the team is producing. A review creates dedicated space to reflect on how the team is functioning. Several established formats serve this purpose. Sprint retrospectives, which come from agile practice. After-action reviews, which come from military practice. And structured team health assessments. All three have one key design requirement in common. Psychological safety. Members must believe honest input will be met with curiosity. Run without it, a retrospective produces a polite fiction, which is worse than none at all.
Three Questions
The Structure That Builds the Habit
Effective retrospectives follow a consistent three-question structure. What went well? Naming a success precisely is what allows it to be repeated deliberately. Without that, success stays accidental and cannot be scaled. What did not go as planned? Notice that the framing is about the plan, not about a person. That is what keeps the question answerable in a room full of colleagues. And what should we change? Without that third question, the first two are merely an interesting discussion. The discipline is in regularly addressing all three. Not just celebrating successes, and not just diagnosing failures.
Synthesis
What Rigorous Evaluation Actually Requires
Pull the whole section together into five practices. Judge a team against all three of Hackman's criteria, not output alone. Check the enabling conditions before attributing any failure to behavior. Measure across five categories, integrating output with process health. Diagnose the root dysfunction rather than the visible symptom. And run structured reviews that ask how, protected by psychological safety. Now notice what all five have in common. Each one resists the same temptation. The temptation is to read a team's health from whatever is easiest to see. Output is visible. Behavior is visible. Symptoms are visible. Sustainability, enabling structure, and root causes are not, which is exactly why they get missed.
About Leadership and Organizational Behavior at UPI Study
Leadership and Organizational Behavior (Business 206) is a self-paced online course of 122 video lessons in 20 chapters, from personality, perception and motivation to leadership and power, teams, decision-making, conflict, organizational structure, culture, ethics and change. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Compare: Management and leadership courses · Foundations of Leadership vs Leadership and OB
Why take it here
Why students take Leadership and Organizational Behavior with UPI Study
Where the credit goes
Universities that work with NCCRS
Leadership and Organizational Behavior carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Evaluating Team Effectiveness and Addressing Common Team Performance Problems
What are Hackman's criteria for team effectiveness?
What are the five dysfunctions of a team?
What should a balanced team performance scorecard measure?
How do you run an effective team retrospective?
About the Leadership and Organizational Behavior course
How many college credits is Leadership and Organizational Behavior?
How much does Leadership and Organizational Behavior cost and what is included?
Which universities accept UPI Study credits?
How long does Leadership and Organizational Behavior take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Leadership and Organizational Behavior.
122 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →