Here is a number that should bother every People leader: global employee engagement dropped to 21% in 2024, an 11-year low, costing an estimated $438 billion in lost productivity (Gallup, 2025). And the tool most organizations use to detect the problem? The same annual engagement survey they have been running since 2012.
Engagement surveys are fine for what they do. They measure sentiment. They tell you whether people feel supported, whether they trust leadership, whether they would recommend your company to a friend. What they do not tell you is anything about how your teams actually function when they are under pressure, navigating conflict, or trying to make a decision with incomplete information.
Team dynamics are behavioral. They show up in patterns: who speaks up, who defers, who bridges disconnected groups, who shuts down when stakes rise. Measuring those patterns requires different instruments than a Likert scale.
Here are six approaches, ordered roughly from most common to least common. Each one measures something real. Each one has a blind spot.
1. Pulse Surveys (Culture Amp, Officevibe, Lattice)
What it measures: Frequent, lightweight check-ins on morale, manager effectiveness, workload, and belonging. Most run weekly or biweekly with 3-10 questions.
Why teams use them: Speed and simplicity. Pulse surveys close the feedback loop faster than annual surveys. Culture Amp reports that organizations using pulse surveys alongside annual surveys see 15-20% higher participation rates because employees believe the data gets used (Culture Amp, 2024).
The blind spot: Pulse surveys still measure what people say, not what they do. A team can report high satisfaction while quietly avoiding every difficult conversation. And survey fatigue is real: 92% of employees believe it matters that their company listens, but only 7% say their company acts on feedback well (Qualtrics, 2024). When action does not follow data, response rates crater. One case study documented a drop from 65% to below 25% within six months of inaction.
When to use it: As a consistent temperature check. Pulse surveys work best when someone is accountable for acting on the results within a defined window (two weeks, not two quarters).
2. 360-Degree Feedback
What it measures: Peer, manager, and direct-report perceptions of an individual's competencies, leadership behaviors, and collaboration style. Typically run annually or semi-annually.
Why teams use them: 90% of Fortune 500 companies use some form of 360-degree feedback (APA, 2012). When done well, 360s surface blind spots that self-assessment alone cannot catch. Research shows employees who receive 360 feedback demonstrate 15.9% better retention rates compared to those who do not (Pro Evaluation System, 2024).
The blind spot: 360s measure perceptions of individuals, not the dynamics between them. They tell you that a manager is seen as a poor listener. They do not tell you that the entire team has developed a workaround where they route decisions through a single senior IC to avoid that manager. A meta-analysis also found that in roughly one-third of cases, 360 feedback actually lowered subsequent performance, likely due to defensiveness and poor delivery (APA, Evidence-Based Answers to 15 Questions About Leveraging 360-Degree Feedback).
When to use it: For individual development, especially for new managers. Pair it with coaching. Do not use it as a performance evaluation tool unless you want people to game the ratings.
3. Personality Assessments (CliftonStrengths, DISC, MBTI)
What it measures: Individual working styles, strengths, communication preferences, and cognitive tendencies. CliftonStrengths alone has been taken by over 35 million people, and 90% of Fortune 500 companies have used it (Gallup, 2024).
Why teams use them: They create a shared vocabulary for differences. Once a team knows that one member leads with "Deliberative" and another with "Activator," they have language for a tension that previously just felt like friction. Gallup's research shows strengths-based development increases engagement by up to 23%.
The blind spot: Personality assessments are static. They capture who someone is on a Tuesday afternoon when they take the test. They do not capture how that person adapts (or fails to adapt) under pressure, in a new group, or after a reorg. The map is not the territory. A team can have a beautifully diverse CliftonStrengths profile and still collapse under its first real conflict because no one has practiced navigating that diversity under load.
When to use it: During team formation or onboarding. Useful as a conversation starter. Less useful as an ongoing measurement system because the data does not update.
4. Sprint Retrospectives (Qualitative Signals)
What it measures: Team-generated reflection on what worked, what did not, and what to change. The richest qualitative data source most teams already have and routinely ignore.
Why teams use them: Retros are baked into Agile practice, meaning many teams already run them. Organizations with effective Agile practices, including quality retrospectives, see 30% gains in efficiency, customer satisfaction, and employee engagement (Atlassian, 2024). And a meta-study on team reflexivity found that teams with structured reflection practices show 25% better performance outcomes.
The blind spot: Most retros are terrible. The action item completion rate for the average retro sits around 40% without deliberate follow-through systems (Easy Agile, 2024). Power dynamics distort the conversation: junior members defer, loud voices dominate, and the same safe topics recycle every two weeks. Retros measure what the team is willing to say out loud. The dynamics that matter most are often the ones nobody mentions.
When to use it: Every sprint, if you actually close the loop. The data lives in the patterns across retros, not in any single session. Track themes over time.
5. Network Analysis / ONA (Organizational Network Analysis)
What it measures: The actual structure of communication and collaboration within and across teams, derived from metadata (email volume, meeting co-attendance, Slack channel overlap, document co-editing). Tools like Microsoft Viva Insights, Confirm, and Polinode map these invisible networks.
Why teams use them: ONA reveals what org charts hide. Benchmark analyses across 200+ ONA projects show an average 10-15% increase in productivity and 20-30% higher engagement scores when leaders act on network insights (i4cp / Rob Cross research). ONA is especially powerful for identifying bottlenecks, silos, and overloaded connectors who are one resignation away from breaking a team's information flow.
The blind spot: ONA measures volume and structure of interaction, not quality. Two people meeting six times a week might be collaborating beautifully or locked in a passive-aggressive approval loop. The tool cannot tell the difference. ONA also raises significant privacy concerns. Employees who learn their communication patterns are being analyzed tend to change their behavior, which corrupts the data. And the insights are descriptive, not prescriptive: knowing that Team A is siloed from Team B does not tell you why or how to fix it.
When to use it: Post-reorg, post-acquisition, or when you suspect collaboration bottlenecks. Requires careful communication about privacy and intent.
6. Behavioral Simulation Data (QuestWorks / QuestDash)
What it measures: Real-time behavioral patterns generated when teams navigate simulated challenges together. QuestWorks, the flight simulator for team dynamics, runs teams through scenario-based quests on its own cinematic, voice-controlled platform. QuestDash then surfaces behavioral data: who steps up under pressure, which team members bridge communication gaps, where delegation breaks down, how conflict patterns shift over time.
Why it works differently: Every other approach on this list measures either what people say (surveys, retros, 360s) or what people are (personality assessments) or how often people connect (ONA). Simulation data measures what people do when the situation demands it. That is a fundamentally different signal. It is the difference between asking a pilot how they would handle engine failure and watching them handle it in a flight simulator.
HeroGPT, the private AI coaching layer, processes individual simulation patterns without ever sharing them upstream. HeroTypes, the public personality profiles that emerge from gameplay, give teammates a shared language (similar to CliftonStrengths, but updated continuously based on behavior rather than a one-time assessment). Leaders see aggregate team trends and strengths-based XP highlights through the weekly team health report. Everything else stays private.
The blind spot: Simulation is not reality. How someone behaves in a quest is a strong predictor of how they behave at work, but it is still a proxy. Teams also need to opt in voluntarily. QuestWorks is not tied to performance reviews, and participation cannot be mandatory without undermining the psychological safety that makes the data valid in the first place. At $20/user/month with a 14-day free trial, the cost is accessible, but buy-in still requires cultural readiness.
When to use it: When you want ongoing behavioral data, not a one-time snapshot. Especially valuable for remote teams navigating trust gaps and for leaders who need to see team patterns without surveillance. If you are evaluating whether simulation belongs in your measurement stack, the article on team dynamics simulators vs. traditional team building events breaks down the tradeoffs.
Building a Measurement Stack
No single tool captures the full picture. The strongest teams use a combination:
Minimum viable stack: Pulse surveys (sentiment) + retros (qualitative reflection) + one behavioral layer. This gives you what people feel, what they are willing to say, and what they actually do.
Full stack: Add personality assessments during onboarding, 360s annually for managers, and ONA after structural changes. Layer simulation data on top for the continuous behavioral signal that everything else misses.
Most organizations have plenty of measurement. What they lack is behavioral measurement. Surveys and assessments tell you the weather report. Simulation data shows you the atmospheric pressure system that is causing it. The emerging category of team dynamics simulation exists specifically to fill this gap.
Try it free
