Only 22% of companies report good results from their engagement surveys. The most consistent complaint isn't the survey itself - it's what happens after. Dashboards produce recommendations. Recommendations get viewed. And then nothing changes. Manager behavior stays the same. The dashboard becomes a quarterly ritual, not a catalyst for action.
We think the dashboard is the problem, not the solution. Here's why we don't build them.
A heatmap converts measurement into surveillance. It invites leadership to ask "which team is red?" instead of "what do we do next?"
Heatmaps Create Surveillance, Not Insight
The moment you give leadership a color-coded grid of teams and scores, you've changed the question. The useful question - "what should we do differently?" - gets replaced by a more seductive one: "who's underperforming?" That's surveillance. It feels productive because it identifies a target, but it produces defensiveness, not improvement. Managers who know they're being ranked on a heatmap don't become better managers. They become better at managing the score.
And surveillance has a second-order effect that's even more damaging: it destroys the honest answering that measurement depends on. If employees suspect their responses will be traced back to their team and used to evaluate their manager, they stop telling the truth. The instrument that's supposed to measure trust becomes the thing that erodes it. That's not a hypothetical risk - it's the documented reality of most enterprise engagement programs.
Department Segmentation Feeds the Same Problem
We don't offer department-level segmentation either, and for the same reasons. Slicing data by department feeds the heatmap instinct. It creates internal league tables - which team scored highest, which scored lowest - and those league tables produce gaming and defensiveness, not improvement. Leaders start managing their department's score rather than addressing the underlying dynamics.
There's a privacy dimension too. In a sub-500 company, the more you slice, the smaller each group becomes. Once you're looking at a team of eight, individual responses become identifiable even without names attached. The anonymity that honest answering depends on gets eroded by the very feature that's supposed to provide insight. We won't build a feature that weakens the foundation it relies on.
What Actually Matters After a Pulse
In a sub-500 company, leadership doesn't need a grid of colored squares to know where the friction is. They work closely enough with their teams to have intuitions. What they need is confirmation of those intuitions, a clear next step, and a way to know whether that step worked.
After a pulse closes, what matters is three things: the Trust Score trend, one suggested action, and a re-measure to see whether that action moved trust.
That's what TrustXP delivers. Not a dashboard that distributes blame, but a cycle that drives change. The Trust Score shows you the trajectory. The suggested action gives you something specific to do. And the next pulse tells you whether it worked. That loop - measure, act, re-measure - is the entire point. Everything else is decoration.
Measurement Should Build Trust, Not Undermine It
We built TrustXP on the principle that the act of measuring trust should itself be trustworthy. That means no surveillance, no league tables, no identifying individuals, and no features that incentivize managing the score instead of managing the team. If a feature would make leadership feel informed but make employees feel watched, we don't build it.
Read our Trust & Security approach → · Start measuring trust for free →