Team Effectiveness Assessment: 28 Questions, Scored in Your Browser

A team effectiveness assessment is a structured set of statements that every member of a team rates, usually anonymously, to measure how well the team works together. Good ones cover psychological safety, dependability, structure and clarity, meaning, impact and how the team handles conflict. Scores are read by dimension, and the output should be one or two specific changes the team makes before running the assessment again.

Ask every team member to rate the same set of statements on a 1 to 5 scale, anonymously, then average the scores by dimension and look at the spread within each one. Pair that with one outcome measure the team already tracks, such as delivery against commitments, so you can see whether changes in how the team works show up in what it produces. Re-run the same statements every quarter; a single reading tells you far less than the change between two.

Google's Project Aristotle studied 180 teams and found five dynamics that set effective teams apart: psychological safety, dependability, structure and clarity, meaning, and impact. Psychological safety mattered most. The study also found that team size, seniority, tenure, colocation and the individual performance of team members did not predict effectiveness. People on teams with a stronger team culture were rated effective by executives twice as often, and were less likely to leave.

Richard Hackman, who studied teams at Harvard for decades, argued that effectiveness depends mostly on conditions leaders set up in advance. He set out five conditions in his 2002 book Leading Teams. Later work with Ruth Wageman expanded them to six: a real team with stable membership, a compelling direction, the right people, a sound structure, a supportive organizational context, and competent team coaching. The first three are treated as essentials and the last three as enablers.

Quarterly works for most teams: often enough to see whether a change made a difference, and rarely enough that people still answer thoughtfully. Run it again sooner after a big change, such as a new manager or a reorganization, but wait roughly six weeks so the reading reflects the new team once the shock has passed. Annual-only assessment is too slow to act on.

Yes. People answer honestly only when they are confident nobody can trace a score back to them, so collect answers anonymously and never report a group smaller than three respondents. Tell the team in advance exactly who will see what. On very small teams, report the team as a single group and do not split results by role or seniority.

Team performance is the output: what the team delivered, measured against its goals. Team effectiveness is the capability behind it: how well the team works together, and whether it can keep delivering without burning people out. A team can post strong performance for a quarter on the effort of two people while its effectiveness is falling, which is why it is worth measuring both.

Share the scores with the whole team within two weeks, name the lowest dimension, and ask the team what they think is behind it before offering your own explanation. Agree on one change, give it one owner, and re-run the same assessment in about 90 days to see whether the score moved. If the lowest dimension is about individual motivation, follow up one-on-one, because a team conversation will not surface what a specific person needs.

No. No published norm exists for these 28 statements, so any benchmark we showed you would be invented. The useful comparison is your own team against itself a quarter later, and the manager's scores against the team's. If you need external benchmarks, paid instruments such as Leadership Circle's BRITE and the AIIR Team Effectiveness Survey compare results against their own databases, usually with a certified facilitator and a per-team fee.

Yes. The 28 statements, the scoring and the guide on this page are free and ungated, with no email required. Scoring runs in your browser and your individual answers are never sent or stored. If you have allowed analytics, the page logs only which dimension scored lowest and how many statements were answered. You can copy the statements as plain text and run them with your team in any anonymous survey tool.