Team Dynamics Assessment

Mechanically it is a questionnaire — a fixed set of rated statements, answered by one person about their own experience of the team. It becomes a survey when more than one member completes it, which is how it is designed to be used: the spread between members is usually more informative than any single average, because disagreement about whether the team is safe IS the finding. It is a diagnostic only in the loose sense that it points at which of the four dimensions to look into first; it does not tell you the cause, and a low score is the start of a conversation rather than its conclusion. Nothing here is a performance measure of individuals.

Three things do most of the work. Collect responses so that individuals cannot be identified — assessing team dynamics fails the moment people suspect their answers are attributable, because the honest answers are the ones that carry risk. Say in advance what will happen with the results, and then do exactly that; a team that has once seen a diagnostic used in a performance conversation will never answer one honestly again. And share the aggregate back, including the parts that are unflattering to whoever commissioned it. If you cannot commit to the third, running the assessment will cost you more trust than the data is worth.

The full questionnaire and your scored result across all four dimensions are free with a free account (your first test is free), and nothing is held back as a teaser. You get the per-dimension breakdown, the written reading and a growth tip per dimension immediately. Premium adds an AI-written report. To compare a team, have each member take it and share their results — there is no built-in team aggregation view.

There is no population norm for this check-in yet, so read each dimension against the middle of its own answer scale rather than against other teams. A dimension that sits clearly above the middle means your average answer leaned towards agreement; one clearly below means it leaned towards disagreement. Uneven profiles are normal — high Trust and Clarity alongside lower Conflict Quality, for example, describes a team that is competent and collegial but hasn't built the safety needed for productive disagreement.

A 360 review typically assesses individual performance from multiple perspectives. This check-in assesses the collective health of the team as a system — it is about how the team functions together, not about any individual team member's performance. The output is a team-level profile, not a person-level evaluation. Individual responses are designed to surface the team experience rather than rate colleagues.

Sharing aggregate results — the team's profile as a whole — tends to open productive conversations that a manager raising concerns alone cannot. The key is framing: 'here is what our collective check-in surfaced' invites shared ownership of the pattern, whereas 'here is what I think is wrong with the team' often triggers defensiveness. Managers sharing their own individual results alongside team aggregates often models the psychological safety the process is designed to build.

Low Clarity often looks like: recurring meetings that end without a clear decision or next step; different team members describing the team's top priority in noticeably different ways; frequent context-switching on who owns what; and a pattern of effort that feels busy but not aligned. The symptom most diagnostic of a Clarity problem is when the team is working hard and still feeling unproductive — the energy is real but the aim is fuzzy.

Not automatically. High Accountability alongside low Trust is a warning sign — it can indicate a fear-based accountability culture where people are held to commitments primarily through pressure or blame rather than shared ownership. Healthy accountability is built on the Trust and Clarity dimensions: when people trust each other and understand the shared goal, they hold each other accountable because they genuinely care about the outcome, not because someone will be blamed if it slips.

As an onboarding map rather than a verdict. A new team member's scores are inherently partial — you have less context than tenured members, you may not have witnessed all the dynamics yet, and your presence itself changes the dynamic. The most valuable use for a new member is to identify which dimensions feel most uncertain or opaque, and to use that as a guide for what questions to ask, what to observe carefully, and where to invest relational capital early.

Significantly, yes. Teams under deadline pressure, going through leadership transitions, navigating a reorg, or adding several new members simultaneously often show temporarily degraded scores on Trust and Conflict Quality specifically. This does not always indicate the team is fundamentally unhealthy — it may indicate a stress response that the team can recover from. Tracking scores over time rather than relying on a single reading is especially important for teams in volatile organizational contexts.

A common pattern teams describe is: moderate-to-high Clarity, moderate Trust, low-to-moderate Conflict Quality, and moderate Accountability. This describes a team that knows roughly what it is supposed to do, gets along reasonably well, but struggles to have the hard conversations that would actually accelerate decisions — and so important things stay stuck longer than necessary. Improving Conflict Quality typically requires deliberate investment in psychological safety before improvements in Accountability follow naturally.