--- title: "One Department Has Low Engagement Scores: What to Do | Spradley" description: "Is it the manager, the work, or a company problem that only shows there? A decision rule, the evidence for each, and what to do when the group is tiny." url: https://spradley.io/articles/what-to-do-when-one-department-has-low-engagement-scores --- # One Department Has Low Engagement Scores: What to Do Is it the manager, the work, or a company problem that only shows there? A decision rule, the evidence for each, and what to do when the group is tiny. Spradley Research Research team Nov 10, 2026 ![A 1980s airport baggage hall. A manager in a blazer, seen from behind, kneels with a torch to peer under a stopped luggage carousel, while a baggage handler in ear defenders, seen in profile, stands holding a suitcase in each hand, waiting to load them](https://spradley.io/media/articles/what-to-do-when-one-department-has-low-engagement-scores/hero.webp) When one department has low engagement scores, decide what kind of problem it is before you plan anything. There are three candidates: the local manager, the work that department does, or a company-wide problem that happens to surface there first. Each leaves different evidence and each needs a different person to fix it. If the department has too few people for a report, widen the group you ask, and never try to work out who said what. ## Key takeaways - A low department score shows you where to look. It does not show you whose problem it is. - Manager cause: the same work scores better under someone else, and people’s reasons are about how the team is run. - Work cause: the same role scores low wherever it sits, under whoever leads it. - Company-wide cause: the reason people give is a decision nobody in the department made, and traces of it appear elsewhere. - Too small to report on: report it one level up, ask a wider group, and never subtract one result from another. ## Why not just go and talk to the manager? Because the manager is the obvious suspect, and obvious suspects are sometimes innocent. Gallup estimates that [managers account for at least 70% of the variance in employee engagement scores across business units](https://news.gallup.com/businessjournal/182792/managers-account-variance-employee-engagement.aspx). That figure is from 2015 and describes how scores spread across a very large number of teams. It cannot tell you why this particular team is low. Blame the manager too early and two things go wrong. If you are right, the department has still learned that low scores get someone in trouble, and next year’s answers will be more careful. If you are wrong, the real cause stays where it is and the next manager inherits it. ## Where does the evidence come from? The test below runs on two kinds of evidence. Comparisons by role, site and manager start date come from your HR records. Reasons have to come from the people in the department, and a rating carries none. **Worked example.** Spradley collects reasons by interview. Each person has a one-to-one conversation with an AI interviewer, typed or spoken, and every answer gets a follow-up asking what lies behind it. The analysis records the causes people describe in their own words and links them across findings. So when one department names a shift pattern, and two others name the same pattern more quietly, you can see the cause is shared. A department’s lean is reported only when its evidence clearly tilts one way compared with everyone else. When the report leaves a comparison open, a leader can put it as a question, such as “do other departments mention the new rota?”. The engine rereads the raw answers and returns checked claims that have been through the privacy judge, within minutes. The leader never sees the raw text. Personal Agent, a leader’s own AI agent over their reports, can also build a comparison or a root-cause write-up, and every sentence in it is scored against the evidence. If your departments live in HiBob, they [sync into Spradley every night](https://spradley.io/integrations/hibob), so the groupings match the org chart you already use. ## How do you tell the three causes apart? Cause Evidence that points here Evidence that points away Who acts first The local manager Reasons are about how decisions are made, shared or credited inside the team. The drop began when the manager changed. Teams doing the same job under other managers look normal. Scores were low under two or more managers. Complaints name rotas, kit or targets set somewhere else. The manager’s own manager, with support and a skip-level conversation. A warning comes later, if at all. The work itself The same role scores low at other sites. Reasons name workload, equipment, physical conditions or shift length. It has been low for years. A sister team doing identical work is fine. Whoever designs the work: staffing, tools, the rota. Often not the department manager. A company problem that shows here Reasons name a company decision: a pay structure, a new system, a reorganisation, a policy. The same theme appears in other departments, more faintly. This department feels it first or hardest. Nobody outside the department mentions it. The owner of the decision. The department hears that it has gone there. Causes can overlap. A manager who handles a bad rota badly is part of both problems. When two rows both fit, write the single question whose answer would separate them, and get that answered before acting. ## What does that look like in a real department? Take a regional airport, invented for this example. The head of people has results for nine departments, and baggage handling sits well below the rest. Two things changed there in the spring: a new airport-wide shift pattern, and a new supervisor. - **Manager?** Handlers do mention the supervisor, but what they describe is him enforcing the new pattern. Nobody describes unfairness or being ignored. Weak evidence. - **The work?** Check-in moved to the same pattern and held steady. Baggage did not. Handlers explain why: the pattern puts the heaviest bank of arrivals at the tail of a split shift, when the team is thinnest. Check-in has no such peak. - **Company-wide?** Security staff raise the same split shift, less sharply. The decision was made centrally. Verdict: a company decision that only bites hard where the work has a late peak. The fix belongs to the operations director who owns the shift design. A coaching plan for the supervisor would have missed it. ## In what order should you test? 1. **Check the gap is real.** Compare it with how far departments usually differ from each other and with this department’s own history. Small groups swing a long way by chance. 2. **Look outward.** Does the reason people give appear in any other department? If yes, start from the company row. 3. **Look sideways.** Does the same role score low in another place, under another manager? If yes, it is the work. 4. **Look at the manager last.** Check timing against the manager’s start date, and what people say about how the team is run. 5. **If two rows survive,** ask the one question that splits them. The manager comes last on purpose. It is the conclusion people jump to first, and the costliest to get wrong. For more on reading a fall over time, see [why engagement scores drop](https://spradley.io/articles/why-engagement-scores-dropped). ## What if the department is too small to report on? Then the reporting rule is doing its job, and you should not try to get round it. In Spradley, ratings, numbers and live views never appear for fewer than five people. A score is also withheld if it could expose someone, for example when one group could be subtracted from another to reveal a smaller one. Written findings go through a separate privacy judge that rewrites, holds or withholds anything pointing at a person. Before a study goes out, Spradley flags any group that would fall short of a report, so you can widen it in time. What you can do instead: - **Report one level up.** Merge the team with its neighbours and accept a blurrier picture. - **Never do the subtraction yourself.** Taking the division’s result away from the department’s is how a team of three gets exposed. - **Ask a wider group.** If the cause is the work or a company decision, people outside the small team will see it too. Personal Agent can draft a follow-up interview for the open question, and it has to reach at least five people, so it cannot be aimed at a tiny team. - **Use ordinary management for a suspected manager cause.** Skip-level meetings, the manager’s own manager, and exit conversations. A survey of three people cannot carry that weight. Our guide to the [anonymity threshold](https://spradley.io/articles/employee-survey-anonymity-threshold) covers where the line usually falls and why. ## What should you avoid while you find out? - Do not ask the manager to explain the score to their team before you know the cause. It reads as a hunt. - Do not publish a league table of departments that singles out a small one. - Do tell the department you have seen the result, what you are checking, and when you will come back to them. Once you know the cause, the next step is sorting what to act on. Our piece on taking action on survey results picks up from there. ## What can this rule not tell you? - It cannot untangle causes that really are tangled. Sometimes the answer is two rows, and you fix both. - It needs comparisons. A company with one department per role has no sideways check. - It cannot make a group of three readable. - It has no study behind it. It is a way of being honest about what you know, and a shortcut to the right owner. To try it on your own results, [see how one department’s reasons get compared with the rest of the company](https://spradley.io/contact). ## Frequently asked questions ### Is low engagement in one department always the manager’s fault? No. Managers explain a lot of the difference between teams, but a low department can also reflect hard work conditions or a company decision that lands there first. Check whether the same role scores low elsewhere, and whether other departments raise the same reason, before you look at the manager. ### Should you tell the manager their department scored low? Yes, privately and before anyone else does. Frame it as something you are working out together, not a verdict. Ask what they think is going on, then test that against what their team actually said. ### How big a gap between departments is worth acting on? There is no research-backed cut-off. Compare the gap with how much departments usually differ in your company and with this department’s own past results. In a small group a few people changing their answers can move the score a long way. ### What can you do if a department is too small to see its results? Look at the result one level up, merged with neighbouring teams, and ask your open question to a wider group. Never subtract one group’s result from another to reach the small team. If you suspect a manager problem, use skip-level meetings and the manager’s own manager. ### Should you run a separate survey just for the low department? Only if you have one specific question that would change what you do, and the group is big enough to protect the people answering. Often the answers you already have can settle it if you ask them a sharper question. A repeat survey with no explanation tends to read as stalling. ## Key terms Lean A department’s tilt on a finding, reported only when its evidence clearly differs from the rest of the company. Skip-level conversation A meeting between staff and their manager’s manager, without the direct manager present. ## More articles [Explore all resources](https://spradley.io/articles) [ ![A manager in a cardigan, seen in profile, standing on an upturned crate in a garden centre greenhouse and reading from a single blank sheet of paper to three staff in green aprons paused over a potting bench, one of them holding up a blank wall calendar and pointing at it](https://spradley.io/media/articles/how-to-communicate-employee-survey-results/hero.webp) Taking action ### How to Communicate Employee Survey Results to Staff A fill-in first message to staff in four parts: what we heard, what we still do not understand, what we will do, and when you will hear again. ](https://spradley.io/articles/how-to-communicate-employee-survey-results)[ ![A man in a short-sleeved shirt and tie, seen from behind on a kick stool in a housing association repairs office, blowing a cloud of dust off a thick ring binder he has pulled from a high shelf, while a repairs operative in overalls waits in profile beside him holding out an identical new, empty binder](https://spradley.io/media/articles/why-nothing-changes-after-employee-survey/hero.webp) Taking action ### Why Nothing Changes After Your Employee Survey Survey follow-through breaks at four points. Check your last cycle for the sign each one leaves, and find where yours stopped. ](https://spradley.io/articles/why-nothing-changes-after-employee-survey)[ ![A manager in an insurance office, seen from behind, taps a blank wall barometer while a claims handler at a desk of folders raises a hand to speak](https://spradley.io/media/articles/spradley-vs-lattice/hero.webp) Comparisons ### Spradley vs Lattice for Employee Feedback Spradley vs Lattice: run one fallen score through both, see what each does when the reason is unknown, and when to keep Lattice and add interviews. ](https://spradley.io/articles/spradley-vs-lattice)[ ![A practice manager in a 1980s veterinary clinic, seen from behind, presses a stethoscope to the closed staff-room door while a vet nurse in profile waits beside her holding a cat carrier](https://spradley.io/media/articles/spradley-vs-leapsome/hero.webp) Comparisons ### Spradley vs Leapsome: Surveys or Reasons? Spradley vs Leapsome on one workplace problem: what each tells you, what each does when the cause is still unknown, and whether to keep, add or replace. ](https://spradley.io/articles/spradley-vs-leapsome)[ ![A librarian in a cardigan in a 1980s library back office, seen from behind, peering through a large magnifying glass at one blank index card pinned to a corkboard crowded with hundreds of them, while a colleague in profile tips another mail sack of blank cards onto the table beside her](https://spradley.io/media/articles/how-to-analyze-open-ended-employee-survey-comments/hero.webp) Analysis ### How to Analyse Open-Ended Employee Survey Comments Split each comment into what people see, what they blame and what they suggest. Then mark the gaps comments cannot fill and ask again. ](https://spradley.io/articles/how-to-analyze-open-ended-employee-survey-comments)[ ![A man carrying a box of desk belongings stops by the lift to talk with a colleague](https://spradley.io/media/blog/exit-interview-questions/hero.webp) Interview guide ### Exit interview questions and a guide to run them Exit interview questions in a ready-to-run 25-minute guide: probes, who should ask, when to hold it, and how to sort answers into preventable turnover. ](https://spradley.io/articles/exit-interview-questions)