Your engagement survey came back. The numbers are in a deck.
HR has prepared talking points. And somewhere in the back of your mind, you’re wondering: Do these results actually tell me anything I can act on?
You’re not wrong to wonder. Engagement surveys have become standard practice—an annual ritual that produces scores, benchmarks, and trend lines. They generate data. What they rarely generate is understanding.
I’ve walked into dozens of organizations holding their survey results like a map, only to discover the map doesn’t match the territory. The scores say communication is a problem, but they don’t say which communication, between whom, or why. The data shows engagement dropped in Q3, but it doesn’t reveal what environmental factors caused the drop. The benchmarks indicate you’re below industry average on “manager effectiveness,” but they don’t explain what managers are actually doing—or what’s preventing them from doing something else.
Surveys measure sentiment.
They don’t diagnose systems. And that gap is where most improvement efforts go to die.
The Fundamental Limitation
Engagement surveys can only surface what you thought to ask about. You design questions around topics leadership already identified as important—communication, recognition, workload, manager relationships, career development. Employees rate their satisfaction. You get numbers.
What you don’t get is the thing you didn’t know to ask about.
The real driver of your turnover might be how shift schedules interact with childcare availability. The actual cause of your coordination failures might be an approval process that prevents anyone from making decisions without three levels of sign-off. The root of your “communication problem” might be a physical layout that makes it impossible for two teams to interact informally. None of these will appear in your survey because you didn’t know to ask about them.
Surveys are confirmatory tools. They can validate or quantify hypotheses you already have. They can’t generate hypotheses you don’t have. They can’t reveal the patterns you’re not looking for.
When the Survey Creates More Questions Than Answers
I worked with an agricultural firm—a network of greenhouse operations—that had conducted their first engagement survey in years. The results came back troubling. Trust, communication, and fairness scores were significantly lower among hourly greenhouse workers than among office staff. The gap was stark, nearly 30% across all topic areas.
Leadership looked at these numbers and had… questions. Lots of them. Why was trust so low? What specifically was wrong with communication? What did “fairness” even mean to these employees? The survey had quantified a problem without explaining it. They recognized that a deeper dive was needed before they could act.
When I conducted interviews with greenhouse workers, the picture clarified quickly. The issue wasn’t abstract “trust” or generic “communication.” It was specific: nearly all information reached hourly workers secondhand, translated by a third party or read aloud by bilingual shift leads. They experienced every piece of company communication as delayed and indirect. Questions took days to get answered. They felt—accurately—like afterthoughts in the information flow.
The survey had captured the symptom (low trust scores) without revealing the cause (communication architecture that treated a major employee population as an afterthought). No amount of staring at the survey data would have surfaced that insight. It required actually talking to people and following their experience to its roots.
When Surveys Miss Because Employees Don’t Trust Them
There’s another limitation surveys rarely acknowledge: employees know what surveys are for.
I assessed a healthcare practice network where turnover among providers was running well above industry averages. Leadership had tried surveys. The results were oddly muted—nothing dramatically wrong, scores hovering around acceptable ranges. Based on the data, you’d think the organization was basically fine.
It wasn’t. When I interviewed clinical staff confidentially, a flood of frustration emerged. Employees described raising concerns through official channels and being met with defensiveness or dismissal. They’d learned that honest feedback created risk without producing change. Several described a “culture of defeat.” The most experienced clinicians—the ones with options—were actively planning exits.
The survey had missed this entirely. Not because the questions were wrong, but because employees had learned not to answer honestly. When your experience tells you that raising concerns gets you labeled as a problem, you don’t put your real concerns in a survey attached to your department and demographics. You give acceptable answers and keep your head down.
The survey measured what employees were willing to say. It didn’t measure what they actually experienced.
What Diagnosis Requires Instead
If surveys are confirmatory tools that measure sentiment, what do you use when you need to discover causes and understand systems?
You need a methodology that starts from employee experience rather than leadership assumptions. One that lets people direct the conversation toward what actually matters in their reality, rather than rating their satisfaction with topics you predetermined. One that traces from surface symptoms to underlying causes. One that distinguishes between individual complaints and organizational patterns.
This is why I developed the Strategic Workforce Insight Mapping (SWIM) process. It uses psychodynamic interviewing techniques—methods from clinical psychology adapted for organizational settings—to surface what surveys can’t reach.
The approach is different in kind, not just degree. Instead of asking employees to rate “communication” on a five-point scale, you ask them to walk you through how information actually flows in their daily work. Where do they get what they need? Where don’t they? What happens when they have a question? What happens when they raise a concern? You follow their experience, probing from general observations to specific examples, from symptoms to root causes.
What emerges isn’t sentiment data. It’s a map of how the organization actually functions—which pathways work, which are broken, which behaviors the environment rewards, which it punishes. You discover the things you didn’t know to ask about because you let employees tell you what matters rather than limiting them to your predetermined categories.
The Difference in Practice
Surveys tell you engagement is down. Diagnosis tells you why—specifically enough to act on.
Surveys tell you communication scores are low. Diagnosis reveals that second-shift employees learn about policy changes three days after first shift because the communication process wasn’t designed with shift differentials in mind.
Surveys tell you manager effectiveness is a problem. Diagnosis uncovers that managers are making decisions inconsistently because leadership never aligned on priorities, so every manager is optimizing for a different goal.
Surveys tell you turnover is a concern. Diagnosis shows that your most experienced employees are leaving because the workload distribution system creates impossible demands for anyone carrying complex accounts.
The gap between these two levels of insight is the gap between treating symptoms and addressing causes. Surveys give you the symptom. Diagnosis gives you the cause—and the cause tells you where to intervene.
When to Use What
Surveys aren’t useless. They’re useful for what they’re designed to do: tracking sentiment over time, benchmarking against industry data, quantifying known issues, and signaling when something has shifted enough to warrant attention.
What surveys can’t do is tell you what you don’t already know or explain why the patterns you’re seeing exist. For that, you need diagnosis—a systematic examination of how environmental factors produce the outcomes you’re experiencing.
If your survey results make sense and point to clear actions, a survey may be enough. If your survey raises more questions than it answers, if the numbers don’t match what you’re seeing operationally, if you’ve acted on survey results before without producing real change—then you need something the survey can’t provide. You need to actually understand what’s happening. And that requires a different tool.
Dustin Snyder is the founder of Wayforward Associates, specializing in organizational diagnostics and change management for companies at critical inflection points. His Strategic Workforce Insight Mapping (SWIM) process provides leadership teams with actionable insights and implementation roadmaps that consistently generate workforce buy-in on necessary change. To explore whether your organization could benefit from this approach, visit wayforward.work/ohi to complete the Organizational Health Index.
