
A team effectiveness assessment survey is a structured way to see how an intact team is set up, how members work together, and whether the work produces sustainable results. This guide covers the frameworks behind it, question design, administration, scoring, interpretation, and how to turn findings into a few focused improvements.
Key Takeaways
- The survey examines team design, collaboration, and results, not individual engagement.
- Seven drivers shape effectiveness: purpose, roles, resources, safety, dependability, coordination, and results.
- Protect confidentiality, and read averages next to distributions and comments.
- Value comes from a few owned actions and a follow-up check.
Team Effectiveness Assessment Survey: Purpose and Framework
What the survey measures
Hackman's 2002 work gives three criteria for effectiveness:
- Team output meets relevant standards
- The team can work together effectively in the future
- Members have a meaningful, satisfying experience
Hackman notes that their relative importance varies by circumstance. Trust, learning, inclusion, and psychological safety all feed the second and third criteria.
Choose the right unit of analysis
Survey an interdependent team: people who share work, decisions, goals, or outcomes, with clear boundaries and collective accountability. A department or reporting line alone is not evidence of a team.
Before launching, check:
- Task interdependence
- Membership boundaries
- Whether people answer for shared results
How it differs from other tools
| Tool | What it measures |
|---|---|
| Team effectiveness survey | Team conditions, processes, and outcomes |
| Engagement survey (such as Gallup Q12) | Individual engagement and workplace conditions |
| 360-degree feedback | Others' views of one person's performance |
| Personality assessment | Individual traits |
| Performance review | Individual accountability for results |
These tools answer different questions. Using an engagement score to judge team effectiveness is like using a thermometer to check blood pressure.
The Hackman framework
Hackman's five conditions are a real team, a compelling direction, an enabling structure, a supportive organizational context, and expert coaching. Each translates into survey themes:
- Real team: Are boundaries and membership clear?
- Direction: Do members share goals and priorities?
- Structure: Are roles, norms, and decision rights clear?
- Context: Do information, resources, and support reach the team?
- Coaching: Does the team get timely help with its work?
The model is one useful lens. It guarantees nothing, and it is not the only valid framework.
The seven-driver survey model
"Seven drivers" is not one standardized model. Tannenbaum and Salas published a specific seven-driver framework in 2020, and Google's Project Aristotle names other factors.
This article uses a practical seven-driver set that complements Hackman's conditions:
- Shared goals and direction: Members understand purpose, priorities, success measures, and the link to organizational outcomes.
- Roles, structure, and decision rights: Responsibilities, authority, handoffs, and decision ownership are clear.
- Resources and enabling processes: The team has information, tools, time, staffing, meeting practices, and organizational support.
- Psychological safety and inclusion: People can ask questions, admit mistakes, challenge assumptions, and contribute without fear of embarrassment or punishment.
- Dependability and accountability: Members follow through, meet standards, raise risks early, and handle missed commitments constructively.
- Communication, coordination, and collaboration: Information flows, disagreements get resolved, and people coordinate across functions or locations.
- Results, meaning, impact, and growth: The team delivers useful outcomes, sees why the work matters, learns, and builds collective capability.

Team Effectiveness Survey Questions
Question design principles
Write team-level statements that use "this team" or "we" and describe observable conditions. Address one idea per item.
Avoid:
- Leading wording ("Our excellent communication...")
- Double-barreled items ("Roles are clear and workloads fair")
- Personality-based or blame-oriented statements
Pew Research Center advises against double-barreled questions and stresses that response options should be exhaustive and non-overlapping. Build each item with:
- One consistently labeled agreement or frequency scale
- A timeframe where relevant (such as "over the past three months")
- A "not enough information" option
Sample statements by driver
Balance the set across all seven drivers rather than leaning on morale or satisfaction. These sample statements are a starting point:
- Goals: "This team's top priorities are clear." "We know how we measure success."
- Roles: "I know who makes the final call on decisions in our area." "Handoffs between members rarely cause rework."
- Resources: "We have the tools to do our work well." "Our meetings end with clear decisions."
- Safety: "On this team, people can admit mistakes without being embarrassed." "We can disagree openly."
- Dependability: "Team members deliver what they commit to." "We raise risks early."
- Coordination: "Information reaches us in time to act." "Work across functions is well coordinated."
- Results: "Our work is useful to the people who depend on it." "We get better at what we do over time."
Open-ended questions
Add two to four open items to reveal the context behind ratings:
- What should this team continue, stop, start, or change?
- Describe a recent situation where our teamwork helped or hurt results. (Ask for no names.)
Tailor the survey to your context
Wording can shift for public agencies, nonprofits, growing companies, or enterprise teams, while core dimensions stay comparable. A public agency might ask about "service to residents," a startup about "scaling decisions."
Include inclusion and belonging items where relevant. Skip demographic and role questions that could identify people on a small team.
Pilot the survey with a few representative respondents to check clarity, completion time, and whether any item reads as a judgment of an individual. Census Bureau guidance supports cognitive interviews and pilots for this purpose.
How to Run a Team Effectiveness Assessment Survey
Preparation determines whether people answer honestly.
- Define purpose and boundary. Name the team, sponsor, and intended use: team development, operating improvement, leadership development, or organizational diagnosis. Tell participants which.
- Set confidentiality rules first. Decide a minimum reporting threshold (OPM's playbook cites 10 respondents as an example for unit reporting). No threshold is a universal safe harbor: on small teams, other attributes can still identify people. State who sees raw responses, aggregated scores, and written comments.
- Pick a calm window. Avoid fielding during a crisis, major deadline, reorganization, or recent conflict. Keep the survey short, since long surveys invite fatigue and careless answers.
- Commit to reporting back. Schedule the debrief before launch and promise prompt results.
- Decide who responds. Include all relevant members, clarify whether the leader answers, and keep extended contributors or stakeholders in a separate group so responsibilities don't blur.

How to Score, Interpret, and Act on Results
Scoring the survey
- Code the scale numerically (for a 1-5 scale, Strongly Disagree = 1).
- Reverse-score negatively worded items so all point the same way. On a 1-5 scale, the formula is 6 minus the response.
- Calculate results by driver, not as one overall team score.
- Show averages alongside response distributions, counts, and written themes.
Single Likert items are ordinal, and Sullivan and Artino note that frequency distributions can be more informative than means. A 3.5 average may hide a team split between 5s and 2s.
Interpreting patterns
Look for strengths, low-scoring drivers, uneven responses, and gaps between related drivers. The fix depends on the driver. A low resources score may need organizational support. A low safety score calls for leadership and team-norm work.
A score is not a diagnosis. Test hypotheses against open comments, interviews, meeting observation, performance indicators, decision logs, or stakeholder feedback.
Compare the team with its own future results before using external benchmarks. No common cut score exists. If you compare teams, confirm similar mandates, composition, response conditions, and privacy protections.
Debriefing the findings
A good debrief follows a simple structure:
- Restate the purpose and confidentiality rules.
- Review patterns without guessing who said what.
- Invite examples.
- Separate symptoms from causes.
- Discuss what the team can influence.
Examine both the lowest-scoring driver and the most divided one. Research supports the practice: a meta-analysis of debriefs estimated that well-run debriefs can improve team performance by roughly 20-25%. That is a review-level estimate, not a promise for any given team, and a survey alone guarantees nothing.

Turning results into action
Limit the plan to a few high-leverage changes. Give each an owner, deadline, needed support, and observable indicator. Separate team-owned fixes from issues to escalate to senior leadership or another department.
Match the intervention to the diagnosis:
- Direction problems: clarify the team charter and priorities
- Ownership problems: define decision rights with tools such as RACI or RAPID
- Process problems: redesign meetings and handoffs
- Trust or safety concerns: coach leaders and set behavioral norms
- Resource or incentive barriers: escalate for organizational-level action
Plan a follow-up assessment once changes have had time to operate. Reuse the same core questions, review progress against the plan, and revise the survey only if the team's mandate or context changes materially.
Some organizations want help beyond the survey itself. The Hive Consultants, a Portland, Oregon-based firm serving organizations across the United States, offers facilitated interpretation, team coaching, leadership development, and broader organizational development.
Its work centers on clarity, alignment, inclusion, psychological safety, and sustainable team effectiveness, particularly for complex, public-facing, and mission-driven organizations.
Frequently Asked Questions
What are Hackman's five conditions for team effectiveness?
A real team, a compelling direction, an enabling structure, a supportive context, and expert coaching. Adapt them to the team's work and context.
What are the 7 drivers of team effectiveness?
Shared goals, roles and decision rights, resources and processes, psychological safety and inclusion, dependability, communication and coordination, and results, meaning, impact, and growth. Other published seven-driver models exist.
What is a team effectiveness assessment survey?
A team-level diagnostic that gathers members' views on how the team is set up, collaborates, makes decisions, and delivers outcomes.
What questions should a team effectiveness assessment survey include?
Cover purpose, roles, resources, psychological safety, accountability, communication, coordination, results, and learning. Close with an open question on the team's top improvement opportunity.
How do you score a team effectiveness assessment survey?
Group responses by driver and summarize with distributions as well as averages. Read them alongside open comments and other evidence, never as one pass-or-fail score.
What should leaders do after a team effectiveness survey?
Share findings openly, facilitate a constructive discussion, and prioritize a few root causes. Assign owners and timelines, then repeat the assessment to check progress.