Team Diagnostic Survey: Six Conditions Explained
Nour
Founder, Coachful
The Team Diagnostic Survey and Six Conditions associated with Hackman and Wageman help distinguish a team-design problem from a request for better interpersonal behavior. Before prescribing more team building, ask whether the group has a shared task, suitable membership, usable work arrangements and organizational support.
Coachful is our #1 recommendation for organizing the resulting coaching work. Use original preparation resources, an appropriate group session and selected actions to carry design decisions into practice. Coachful is not the Team Diagnostic Survey, does not supply its authorized scoring and should not be presented as a substitute assessment.
This guide explains all six conditions, the difference between a framework and an instrument, and a complete fictional capacity-allocation case. Its output includes an approved team charter, a blocked first decision, corrected data and a revised allocation that actually happens.
Separate the framework, the survey and your worksheet
Wageman, Hackman and Lehman's 2005 development paper describes the Team Diagnostic Survey as an instrument for studying and assessing work teams. Its original abstract reports analyses involving 2,474 members of 321 teams. That development evidence is not a guarantee about every later version, population or coaching intervention.
The framework describes conditions to investigate. The instrument has its own administration, measures and interpretation. An original worksheet can organize a practical discussion without becoming that instrument.
Keep those names honest. Do not copy protected survey items into a form, improvise a six-factor score and call it TDS, or imply practitioner authorization because you understand the model.
If the formal assessment is appropriate, confirm the current version, access, permissions, practitioner requirements and reporting process with its provider. Explain the purpose and intended use to participants before administration. A published research paper alone does not establish a person's current authorization.
The worked case below uses original design questions and observed work. It does not administer the TDS or invent a report. This distinction makes the method usable without pretending that an informal conversation has psychometric properties.
Understand conditions as influences, not performance guarantees
Hackman's 2012 paper on conditions in group research argues for shaping the setting in which groups work rather than assuming that one intervention mechanically produces a result. Favorable conditions increase possibilities; they do not control every event.
The paper also treats effectiveness broadly: the work meets relevant users' needs, the group develops its capacity to work together, and members learn or develop through the experience. A fast decision alone does not establish all those outcomes.
For an original practical review, agree evidence for each relevant question. Did the allocation fit the available resource? Could the group use a better decision process next time? What did participants experience, including concerns that remain?
Do not transform a reported research percentage into a promised improvement for a new client. Nor should a high assessment score exempt the team from checking the actual quality and consequences of its work.
Read the Six Conditions with attention to the version
The established Six Conditions distinguish real team, compelling purpose and right people from the enabling areas of work arrangements, organizational context and coaching. Read the original research and the terminology belonging to the version you are using.
Current 6 Team Conditions materials use Work Design and Organizational Support for two enabling areas. Earlier labels remain useful for reading older work, but use the terminology and interpretation belonging to the actual assessment or training version.
The explanations below give brief conceptual definitions followed by original planning examples. The prompts are not licensed survey items, scoring thresholds or requirements for a particular team size.
1. Real team: an identifiable group with joint work
A real team has a recognizable membership, work requiring members to depend on one another and enough continuity to learn together.
For an original planning conversation, distinguish a member from a contributor and an approver outside the group. Those roles can all be valuable. Confusing them can leave a guest expecting a vote or a member assuming somebody else owns the decision.
For example, five functional leaders may each report separate activity to a chief executive. If no output requires them to combine judgment, they may be a coordination forum. A shared allocation across competing initiatives could become collective work, but only if the organization actually wants that group to perform it.
Ask for a concrete output that cannot be produced adequately through independent updates alone. Then identify who must work together on it and who can provide input without joining every meeting.
Continuity need not mean freezing membership forever. If the purpose or people change, explain the new arrangement and revisit how decisions will be carried forward.
2. Compelling purpose: a consequential shared objective
Purpose should orient the team toward meaningful collective work and engage its contribution, rather than serve as a slogan.
An original purpose statement can name the output, its intended users and the decision the group must make. “Collaborate better” leaves the work undefined. “Agree an achievable allocation of the shared specialist pool for the next delivery period” gives the group something to do together.
Check scope as well as ambition. A team that can recommend but cannot approve should not promise that every proposal becomes a commitment. A challenging purpose also needs to respect the actual constraints.
Ask members to test a proposed decision against the purpose. Does it help the shared output, or merely protect one function's preference? Disagreement can reveal a useful trade-off rather than a lack of team spirit.
Do not prescribe the detailed answer under the label of purpose. The team needs room to use its expertise within the authority and boundaries it actually has.
3. Right people: capability for this task
This condition concerns the mix of expertise, perspectives and ability to work together, with a size appropriate to the work.
Use the task to explain the choice. In an original allocation example, operations understands delivery dependencies, finance checks approved scope, technology understands eligible specialist time and service represents the commitments being affected. Prestige alone does not supply those contributions.
Distinguish missing expertise from a disliked viewpoint. A person raising an inconvenient dependency may be contributing exactly what the team needs. Do not use “wrong people” as an unsupported judgment about personality or worth.
Consider whether a gap needs a core member, a specific contributor, training or external advice. Not every expert needs to attend every decision. Conversely, inviting them once may be inadequate if the group repeatedly makes decisions requiring their judgment.
Membership and staffing changes belong to the relevant authority. Coaching can surface the need and prepare options; it does not silently appoint, exclude or dismiss someone.
4. Sound structure or work design: a usable way to collaborate
This area concerns how shared work is arranged and the norms that guide members' contributions.
Translate it into the actual task. An allocation team might need a common resource unit, a way to distinguish verified data from an assumption, and a record of why an option was accepted. That is more useful than a long generic list of ideal behaviors.
Choose a few practices the group can use under pressure. For example: expose a missing dependency before deciding; let the person with relevant evidence explain it; record a decision and its unresolved limits before moving on.
Clarify what happens when there is disagreement. Is the group advising a leader, making an authorized decision or escalating a reserved matter? Consensus should not be assumed simply because everyone attends the same meeting.
Review whether the practices improve the work or add unnecessary administration. A published charter is only a starting arrangement. Its value needs to be tested in a real decision.
5. Supportive context or organizational support: conditions beyond the room
Information, resources and wider organizational systems can enable teamwork or obstruct it.
In an original example, the team may have an excellent discussion but receive an outdated staffing file. It cannot create genuine specialist availability through enthusiasm. Somebody with access and authority must correct the resource picture.
Check what the sponsor has actually provided: decision rights, usable information, time to perform the shared task and clarity about competing expectations. A verbal endorsement is different from access that works.
Look beyond one person's intention. If a functional target still requires every local project to launch immediately, members may face a conflict when asked to defer work for the collective plan. That conflict needs an organizational decision.
Keep the requested support specific: what is missing, who can supply it, by when and what decision remains blocked meanwhile. A coach can help articulate the request without pretending to control the wider organization.
6. Team coaching: assistance with the collective work
Team coaching helps the group use and develop its resources in performing its shared task.
It is different from giving every member an individual session and assuming the collective process has changed. The coach may need to observe how the group uses evidence, handles disagreement or reviews a decision together.
Match the assistance to the moment. At a launch, members may need to test the purpose and working arrangements. After a blocked allocation, they may need to examine how an unsupported assumption entered the discussion. After delivery, they can compare what was decided with what happened.
Do not fill a missing sponsor role yourself. The coach can facilitate a reconsideration, but cannot manufacture a resource, authorize a changed output or make a protected disclosure disappear.
Useful coaching should leave the team better able to perform its own review. Avoid making every future decision dependent on the coach's presence or rewarding agreement with the coach's preferred option.
Treat 60–30–10 as an attention heuristic
In her 2020 explanation, Ruth Wageman calls 60–30–10 a helpful heuristic: put substantial effort into design before the team works, attend carefully to launch or relaunch, and then support the ongoing process.
It is not a universal causal formula saying preparation produces exactly sixty percent of every outcome. Do not use it to dictate a contract's billable-hour percentages or dismiss an urgent ongoing problem because coaching appears last.
The useful planning question is what must be made workable before a session can help. The following case therefore starts with purpose and authority, then tests those arrangements in actual work.
Prepare an assessment debrief that can lead to a decision
If an authorized TDS report is used, ask the qualified practitioner to explain what its measures and comparisons mean. Do not assume a scale measures output quality directly, that a comparison group matches this team, or that a number has an invented pass/fail threshold.
Read a finding with the work in view. If responses suggest a support concern, invite a concrete example: which information or resource was unavailable, when it was needed and what happened to a decision. That discussion can clarify the issue without asking someone to defend their response as if it were misconduct.
Different views can be informative. A leader may believe access exists while another member cannot use it. Do not average the disagreement away in conversation or decide the less senior member must be mistaken. Establish what can be checked, which account remains uncertain and whose action could resolve the constraint.
Agree handling before discussion. Explain whether participants see a team report, individual material or a selected summary. In a small group, removing names may still leave a person recognizable from role or an event. Do not promise anonymity that the actual process cannot provide.
Keep the debrief focused on a legitimate next decision. Which finding matters to the team's current purpose? What additional evidence is needed? Is the response a team practice, a sponsor decision, training or another kind of support? A report can help prioritize inquiry without making the coach the authority for every resulting action.
Finally, choose the review evidence before intervening. Repeating an authorized assessment, observing a decision and checking an accepted delivery are different ways to learn. Use the appropriate procedure for each rather than combining them into a homemade overall score.
Choose evidence that matches the proposed change
| Original practical proposal | Evidence to check at review |
|---|---|
| Clarify the core allocation group. | Members know who decides and which guest supplies input; the actual decision follows that arrangement. |
| Replace separate updates with shared work. | The meeting produces an allocation requiring combined judgment, rather than five independent reports. |
| Supply missing resource information. | The named owner delivers a checked roster that the group can actually use. |
| Introduce a missing-input hold. | The team stops release when a required dependency is unverified, even when members prefer to proceed. |
| Develop self-review. | Members compare decision and delivery, identify an error and choose a process change without waiting for the coach to supply the answer. |
These are original learning checks, not TDS items or scoring guidance. An observation can support one conclusion while leaving other questions open. Having a roster, for example, does not show that members can challenge each other or that every recipient accepted the output.
Worked example: five leaders and one limited specialist pool
In this fictional case, CEO Mara asks coach Anika to improve an executive group's meetings. Most meetings contain separate updates, followed by decisions Mara makes privately. The five leaders disagree about which initiatives can use a shared specialist pool.
Anika first asks what the group should accomplish collectively. Mara identifies a real task: make an achievable allocation for 6–17 June 2028 across service project A, technology pilot B and internal rollout C. Their work depends on the same appropriately skilled resource.
The requests total sixteen specialist days: A wants seven, B five and C four. An initial planning file suggests twelve available. The group wants to leave two unallocated for variation. No one should mistake that file for a validated commitment.
Project A needs at least six specialist days completed by 9 June for an accepted customer delivery. The other outputs can change only with appropriate sponsor acceptance. These are fictional operational constraints, not rules derived from the framework.
Complete the charter before launching the task
| Design area | Completed fictional arrangement |
|---|---|
| Membership. | Noor, operations lead;Celia, finance;Gita, service;Luis, technology;Evan, people. Dana supplies resource data as a contributor, not a sixth decision member. |
| Purpose. | Agree a feasible shared allocation for 6–17 June, with clear scope changes and two specialist days unallocated. |
| Authority. | Mara authorizes Noor to confirm allocations within validated availability and accepted outputs. Changes to customer commitments or project scope require Mara's approval. |
| Information. | Dana supplies the validated roster, including leave and eligible skills, before a final allocation is released. |
| Working practices. | Label estimates; hear dependencies; hold a decision when a required input is unverified; record scope and dissent. |
| Coaching. | Anika facilitates launch and the first work review, then helps members lead their own retrospective. |
| Review. | Check delivery and actual resource use on 19 June, including member concerns and next process changes. |
All five members accept this task and their roles. Mara confirms the authority and reserved decisions. Dana accepts the data request; that acceptance is not yet evidence that the data arrived.
The group sketches a provisional allocation of A six, B three and C one: ten planned days plus two unallocated. The sketch reduces or changes requested scope and remains dependent on validated availability and sponsor acceptance. Nothing is released as a delivery promise.
The demonstration worksheet builder can organize an original charter and decision record. It must not be labeled an authorized TDS report or contain copied assessment items.
Hold the first decision when the promised support is missing
At the 30 May launch, Dana's validated roster has not arrived. The available file is an earlier twelve-day estimate. The group begins discussing which function deserves priority before Luis points out that the capacity gate is still unverified.
Anika: “What does your agreement require before release?”
Noor: “Validated available days and accepted scope changes.”
Celia: “Then ten planned days is still a sketch. Agreement around the table cannot validate the roster.”
Gita: “We can prepare the customer dependency, but we should not promise the allocation yet.”
The group records a hold. Noor asks Dana for the corrected roster by 31 May and tells Mara what remains blocked. Anika does not turn the disagreement into a listening exercise while ignoring the missing input.
On 31 May Dana supplies the checked roster. Two days in the earlier file are unavailable because planned leave was omitted. Luis confirms the remaining ten specialist days are eligible for the work under consideration. The group has ten, not twelve.
Keeping the two-day reserve now leaves eight for planned work. The earlier ten-day sketch no longer fits. Reusing it would overcommit the available pool or silently remove the reserve.
Make the revised allocation and obtain scope approval
| Work | Revised planned days | Accepted output or status |
|---|---|---|
| Project A. | 6. | Required customer delivery by 9 June. Luis checks six eligible days are available before that deadline. |
| Pilot B. | 2. | Prepare the pilot proposal by 16 June. Running the pilot is deferred; this is smaller than the earlier three-day pilot sketch. |
| Rollout C. | 0. | Deferred for this period, without a promised restart date. |
| Unallocated. | 2. | Retained for variation, with use recorded and material changes reviewed. |
| Total available. | 10. | Eight planned plus two unallocated. |
The team makes this proposal on 1 June. Celia checks that the plan contains the required customer work and does not hide the pilot's changed output. Evan checks that no additional days are being assumed from people already on other assignments.
Mara accepts the pilot preparation and rollout deferral on 2 June. Noor then releases the allocation under the agreed authority. The record names the scope changes; it does not claim all sixteen originally requested days were delivered through improved teamwork.
Gita informs the relevant customer contact of the confirmed project A delivery arrangement. Luis informs the pilot stakeholders that they will receive a proposal, not a completed pilot. Evan communicates the rollout deferral to those who would otherwise prepare it.
Review delivery, learning and continuing concern
At the 19 June review, project A used six days and its required output was accepted on 9 June. Pilot preparation used three days rather than the estimated two; its proposal was delivered on 16 June. The extra day was recorded against the reserve. No rollout C days were used.
Actual use was nine specialist days: six plus three. One of the ten remained unallocated. The group did not exceed the checked resource or call the pilot itself complete.
The team also reviews its process. The hold prevented an unverified estimate from becoming a released allocation. However, the roster delay consumed launch time, so Dana and Noor agree a future precheck with an explicit missing-data notice before the decision session.
Not every member reports a better experience. Celia says it remains difficult to challenge a senior colleague's preferred project. Anika helps the group agree that the next allocation will hear dependencies before preferences and invite unresolved objections before release.
The record therefore contains delivery evidence, a process improvement and a continuing participation concern. It does not award a fictional TDS score or conclude that one successful allocation has established enduring team effectiveness.
A contrasting case: a coordination forum may be enough
Another fictional group shares updates about independent local activities. There is no scarce shared resource, joint output or decision requiring collective accountability. Its useful purpose may be information exchange.
Instead of forcing it through a team launch, the sponsor can improve that forum's information format and referral routes. If genuinely shared work appears later, reconsider the structure then.
The framework should help choose an appropriate arrangement, not make every set of colleagues become a team or prescribe the same intervention to every group.
Use Coachful without impersonating the assessment
- Build original preparation. In Advanced use Create > Resources; in Simple use Today > My resources > Forms & worksheets. Label a charter or action record accurately.
- Choose the delivery container. Use an Event for a live group workshop. A continuing structured group curriculum may warrant a Program; one charter conversation does not require one.
- Keep assessment administration distinct. Use the authorized provider process if formal TDS is chosen. Confirm report permissions and audience before placing any permitted copy elsewhere.
- Select agreed actions. Noor's follow-up is obtaining the validated roster. Completing a Coachful task does not create sponsor authority or verify external data.
- Review the collective output. Compare the decision, actual work and remaining concerns. Keep private individual reflections distinct from the agreed team record.
The demonstration My Coaching view illustrates preparation and actions, not survey scoring or a secure anonymous assessment portal. Explore Coachful's features for the coaching workflow, the executive team-coaching guide for engagement design, and distributed leadership for decision-authority questions.
Troubleshoot the design rather than explain away the evidence
Scores become labels for individuals: return to the assessment's legitimate purpose and the collective work. Do not turn one response into a personality verdict.
A sponsor promises anonymity in a small team: clarify the actual reporting and identification limits before collecting responses. A setting called private is not an anonymity guarantee.
A condition looks strong but delivery fails: inspect the work and external changes. Favorable conditions do not eliminate uncertainty.
The team agrees but lacks authority: keep the decision pending and use the relevant approval route.
The coach is asked to fix missing resources: help formulate the sponsor request and review scope. Facilitation cannot supply unavailable specialist days.
Frequently asked questions
Are the Six Conditions and TDS identical?
No. The framework guides inquiry; TDS is a particular assessment with its own administration and interpretation.
Can I recreate the survey in Coachful?
Do not assume permission. Use an original worksheet honestly or arrange authorized assessment access.
Does 60–30–10 predict exact performance?
It is an attention heuristic, not a causal guarantee or compulsory allocation of billable hours.
Do current and older condition labels differ?
Yes. Follow the version in use; this guide explains earlier sound-structure/supportive-context labels alongside current work-design/organizational-support wording.
Must every group become a real team?
No. First establish whether its purpose needs interdependent collective work or another coordination arrangement.
