Once an assessment is done, you still need to read the results, decide what to change first, name the people who will carry it out, turn it into real behavior, and check again. Rather than making every low score an improvement project right away, interpret the causes and context first.
After reviewing the scores, you need to interpret the causes, pick one or two things to change now, name the people responsible, change behavior, and then check again.
Look at what is happening before fixating on scores
Consider other items, written comments, and context together
Pick one to three things you will actually change now
Spell out who will change what, and by when
Re-measure weeks or months later to see what changed
The culture survey or leadership assessment is finished, and the dashboard and report are out. This is exactly where many organizations get stuck. Plenty of items scored low, HR is busy explaining the results, and leaders ask, “So what should I actually do?”
The bottleneck Telta has seen across assessment projects
Projects more often fizzled out not while collecting data, but while interpreting results and turning them into follow-up action. Neither HR nor leaders are experts in interpreting organizational assessments, yet assigning an expert to every unit is expensive.
In a systematic review of employee survey follow-up, Huebner & Zacher (2021) conclude that action planning is important but is often skipped in practice. They recommend giving managers enough support and resources to act as the drivers of change.
Perceptyx’s 2026 State of Employee Listening reports that engagement improved in only 28% of organizations without structured action planning, compared with 59% of organizations that supported managers in creating and tracking action plans, and 69% where employees actually saw behavior change.
Perceptyx’s published analysis of follow-up action after employee listening.
A low score doesn’t reveal the cause on its own. A low collaboration score, for example, might stem from conflicting goals between departments, or from a leader who doesn’t share information in time. Instead of looking only at the overall average, compare differences across units, written comments, and how items relate to one another, and start by forming a few hypotheses about why the results came out this way.
An assessment usually surfaces several items that need work. Rather than automatically starting with the lowest score, it’s more realistic to narrow the list to one to three items based on their impact on the business and on employees, whether they can actually be changed, and whether fixing them could improve other problems too.
If the issue lies in company-wide policies or systems, HR or the executive team may need to act. If it’s something a team can change itself, such as how meetings run, how feedback is given, or how roles are divided, the team’s own leader should be at the center. Rather than HR trying to carry out every action, it’s important to make the person with the authority to change it the owner.
A good action plan tells anyone who reads it exactly what to do. “Every Monday, spend 30 minutes sharing team priorities and the reasoning behind key decisions” is far easier to act on than “Strengthen communication,” because the timing, behavior, and audience are all clear.
You don’t need to rerun the full company-wide survey. If the items you set out to change are clear, use a short pulse survey that asks only those questions again, or, for leadership behaviors, revisit a subset of 360-degree feedback items. What matters is not that you took action, but whether anything actually changed.
Culture Amp reports that companies that shared survey results across the organization saw participation in the next survey rise by an average of 7 percentage points, along with better perceptions of follow-up action. Publishing results and explaining what will happen next can itself signal that “this time, we’re really going to act.”
Culture Amp reports that companies sharing results with 30% or more of employees saw next-survey participation rise by an average of 7 percentage points.
| HR | Line leaders |
|---|---|
| Assessment design, data quality, analysis support | Interpret team context, agree on priorities |
| Benchmarks, driver analysis, guidance | Action plans, team conversations, execution |
| Progress monitoring, re-measurement design | See it through as the owner |
A low score is a signal that a problem may exist, not the cause itself. If collaboration scores are low, for example, what you should do depends on whether the cause is conflicting goals, unclear roles, leader behavior, or a system bottleneck. That’s why you need to look at scores, drivers, and on-the-ground context together.
You don’t need to repeat the full assessment every time. If behavior has changed, first check the indicators closest to that behavior with a short pulse survey or a few key items, and rerun the organization-wide assessment at an appropriate interval.
The goal isn’t to replace experts entirely. It’s to lower the cost of the stage where action stalls because people get stuck interpreting the report. By supporting repetitive explanations of results, exploration of how items relate, suggestions for what to check next, and first drafts of action plans, we help HR and leaders move on to real conversations with their teams faster.
Related Reading
Note: Figures and findings are summarized from the original sources published by each organization.