Culture Survey
Leadership IQ Culture Survey
Run a Culture Survey

Leadership IQ Culture Research

Culture Survey: 10 Hidden Culture Problems Employee Engagement Surveys Miss

What a culture survey finds when it compares answers instead of ranking them.

1,354 employees 12 departments 96 managers 39 items

A good employee engagement survey will tell you whether people feel positive about their jobs, their managers, and the company. That's genuinely useful, and I'm not about to argue that engagement surveys are a waste of time, because we ask plenty of engagement-style questions inside our own culture survey. But engagement scores answer a fairly narrow question, and when a CEO asks why the strategy isn't moving or why good people keep leaving a well-run department, the engagement report usually can't say.

Every one of these ten problems produces a perfectly respectable engagement score.

Four findings no engagement report would surface

22.9%Cleared all five conditions required to execute the strategy
2.28Widest gap between accountability and candor under a single manager
13.1%Say accountability is enforced below them but not above them
1.65Point spread hiding inside one psychological safety average

Culture tends to show up in the gaps between answers rather than in any single score. Employees can be highly engaged and still afraid to report a mistake. They can understand the strategy perfectly and have no ability to act on it. They can love the ten people around them and have no faith in the executives running the place. Every one of those situations produces a respectable-looking engagement number, because the thing that's wrong lives in the relationship between two answers, and a dashboard that reports each item on its own has no way to see it.

When we analyzed the responses from those 1,354 employees, we found ten problems of exactly that kind. In every case the individual scores looked ordinary or even good, and the problem only became visible once we compared answers against each other, followed the same person through several questions, or split the company by department and manager. That comparison is the whole point of our approach to culture surveys, and it's the main thing that separates these analyses from a standard employee engagement report.

What we found

The ten problems

Each one is a comparison between answers rather than a low score on any single question.

How we found these ten problems

Every analysis on this page works the same way. We take two or more items from the culture survey that were designed to be read together, compare them at the individual level rather than the company level, and then split the result by department and by manager. Sometimes the comparison is a simple difference between two means. Sometimes it counts the people who answered one way on the first question and the opposite way on the second. And sometimes it follows the same respondent through a sequence of conditions.

All items use a seven-point Likert scale. Throughout this page, favorable means somebody answered 6 or 7, and unfavorable means they answered 1, 2, or 3. Where an analysis uses a different rule, such as counting the top three boxes rather than the top two, we say so. One item is worded in the opposite direction on purpose and is reverse-scored, so a higher figure always reads as the healthier answer.

Accountability

When accountability is really fear

5.60Average score for “My leader holds people accountable”
5.07Average across the three speaking-up items
+1.64Widest departmental gap between the two
−1.02Narrowest, at the manager level, where candor outran accountability

The strongest single item in this survey was about accountability. When employees rated “My leader holds people accountable for their performance,” the average was 5.60 on a seven-point scale and 60.6% answered favorably, which put it near the top of all 39 items. Any standard employee survey report would file that under strengths and move on.

The trouble is that accountability comes in two very different varieties and a single item can't distinguish between them. There's the kind where people know what's expected, own their results, and can tell you when something has gone wrong. And there's the kind where people know what's expected, own their results, and would never dream of admitting a mistake because of what happens to the person who admits it. Both of those produce a high accountability score. Only one of them is worth having.

So we paired the accountability item with three items about what happens when somebody speaks up: whether you can raise a concern with your leader without worrying about the reaction, whether you can report an error that could create a serious problem without causing problems for yourself, and whether people here focus on solving problems rather than assigning blame. Averaged together, those three scored 5.07 with 31.0% favorable, which is 0.53 points below the accountability item.

A gap of 0.53 points company-wide isn't much of a finding, and if that were the whole analysis I wouldn't be writing about it. The finding is what happens when you split it.

Dumbbell chart showing the accountability score and the speaking-up score for each of 12 departments, with the gap between them ranging from negative 0.49 to positive 1.64.
Each row is a department. The left dot is that department's speaking-up score and the right dot is its accountability score, so the length of the connector is the gap between the two.

Reading down the chart, Operations sits at the top with an accountability score of 6.25, which is the highest of any department in the company, and a speaking-up score of 4.61, which is close to the lowest. That's a gap of 1.64 points among 232 people. Sales shows the same pattern at 1.08. At the other end, Finance and People & Culture both come out negative, meaning candor scores higher than accountability there, and nine of the twelve departments land less than half a point apart.

The manager-level picture is wider still. Among the 77 managers with at least a dozen responses, the gap ran from −1.02 to +2.28, and ten managers combined an accountability score above the company average with a speaking-up score below it. If you're a CEO looking at a 0.53 company number, you have nothing to act on. If you're looking at ten named managers whose teams say they're held to a high bar and can't safely report a mistake, you have a coaching agenda.

The three speaking-up items don't behave the same way

When we broke the speaking-up composite back into its three parts and compared each one separately against accountability, the composite turned out to be hiding a good deal of variation.

Chart comparing the accountability item against three individual speaking-up items, showing gaps of 0.25, 0.45 and 0.90 points.
The accountability item compared against each speaking-up item on its own, rather than against the average of the three.

Raising a concern with your own leader trails accountability by only 0.25 points. Reporting a serious error trails it by 0.45. But whether people focus on solving problems rather than assigning blame trails it by 0.90 points, which is three and a half times the first gap. Only 2.1% of employees gave a favorable accountability score while giving an unfavorable score on raising a concern with their leader, while 10.0% did so on the blame item.

That pattern is worth sitting with, because it says the relationship with the immediate manager is mostly intact and the thing that breaks is what happens organizationally once a problem surfaces. The correlations point the same direction. Accountability correlates 0.63 with being able to raise a concern with your own leader, and only 0.40 with the organization solving rather than blaming, so the accountability employees describe travels closely with their own manager and the blame response doesn't. The item doesn't identify who does the blaming, so I won't name a level, but whatever produces it isn't the same thing people are describing when they talk about their boss.

Departments differ in shape and not just in severity. Operations is worse on all three items, which is a straightforward problem. Sales is fine on reporting errors and poor on the other two, which is a different problem with a different fix. People & Culture is actually negative on two of the three, meaning candor beats accountability there, and it's the department you'd want to study rather than repair.

Worth asking

If your engagement survey reports accountability as a strength, has anybody checked whether the same people can report an error without it costing them? And has anybody looked at that comparison one manager at a time?

Strategy execution

Why a well-communicated strategy still doesn't get executed

63.7%Understand the strategy
22.9%Can actually execute it
310People out of 1,354

When a strategy stalls, the usual diagnosis is that people don't understand it, and the usual remedy is more communication. Another town hall, another deck, another set of cascaded talking points. Sometimes that's the right call. Often it's money spent on the one thing that was already working.

Executing a strategy asks five separate things of an individual employee, and our culture survey measures each of them with its own question. The person has to understand how they're expected to think and act differently. They have to believe the goal can be reached without compromising the company's values. They have to feel empowered to act when they see a problem or an opportunity. Their department needs enough people to meet the expectations placed on it. And when they find a process that's wasting time, they have to be able to get it changed.

Reported one at a time, those five items look like an organization in reasonable shape: 63.7%, 53.5%, 72.2%, 48.4% and 47.1% favorable. Two of them are soft, three are respectable, and none of them looks like an emergency. But strategy execution isn't an average. It's a chain, and a person who fails any one link can't execute regardless of how they scored on the other four.

Chart showing five strategy execution conditions, each with its standalone favorable rate and the smaller cumulative rate of employees who cleared it and every condition above it.
The light bar is each condition's favorable rate on its own. The dark bar counts only the people who cleared that condition and every condition above it, so it tracks the same 1,354 employees all the way down.

Start with all 1,354 employees. 862 of them understand how they're expected to work differently. Of those 862, only 604 also believe the goal is reachable within the company's values. Of those 604, 503 also feel empowered to act. Of those 503, 373 also say their department has enough people. And of those, 310 can also change a wasteful process when they find one. That's 22.9% of the workforce with everything required to actually execute.

The chart makes the drop points easy to see. The single largest loss happens right at the start, where 36.3% of employees don't clear the understanding question, so communication genuinely is part of the problem. But the second-largest loss is the values question, which costs another 29.9%, and the staffing question costs 25.8%. Those two have nothing to do with clarity. You could explain the strategy perfectly to somebody who thinks hitting it requires cutting corners, or to somebody whose team is three people short, and they still won't execute it.

This is the analysis I'd put in front of a CEO first, because it converts a vague complaint about execution into a count of people and a named blockage. If most of your loss is at the understanding step, communicate more. If most of it is at staffing, no amount of communication will help.

Worth asking

Of the people who understand your strategy, what percentage also have the authority, the staffing, and the ability to change a process? If you can't answer that, you can't tell whether your execution problem is a communication problem.

Ambitious goals

When ambitious goals start creating pressure to cut corners

5.25Ambitious goals push me to find better ways of working
4.55We can achieve the goal without compromising our values
4.35I can express concerns about the goal without consequences
4.30I can miss an ambitious goal without fearing for my job

Ambitious goals are supposed to be motivating, and in this organization they mostly are. The item “Our most ambitious goals push me to find better ways of working” scored 5.25 with 50.3% favorable, which is a healthy result and the sort of thing a leadership team would be pleased to see.

What that item can't tell you is the price people think they're paying. Understanding how you're expected to work differently to hit the goal came in at 4.95, which is already a step down, and three further items about the cost of the goal all scored lower than that. Whether employees believe the goal can be achieved without compromising the company's values came in at 4.55. Whether they can express concerns about the goal without negative consequences came in at 4.35. Whether they can miss an ambitious goal without fearing for their job came in at 4.30.

Bar chart of five items about the same ambitious goal, with the motivating item at 5.25, the clarity item at 4.95, and three cost items between 4.30 and 4.55.
Five items about the same ambitious goal. The top bar asks whether the goal motivates people, the second asks whether they understand what it requires, and the bottom three ask what the goal costs.

The combination that matters is the one where somebody is driven by the goal and has a problem with how it has to be reached. In this organization, 18.4% of employees agreed that ambitious goals push them to work better while also disagreeing either that the goal can be reached without compromising values or that they can raise concerns about it without consequences. That's 249 people. This is the one analysis on the page that uses a wider rule than the rest: agreement here means 5 or above rather than 6 or 7, because the group worth worrying about includes people who are only moderately driven.

The survey doesn't observe anybody actually cutting corners, and that distinction matters. What it identifies is the population in which corner-cutting becomes more plausible, since these are the people motivated to hit a number they don't believe can be hit cleanly, or who can't say so if they think it can't.

Splitting that 18.4% shows three different situations rather than one. 5.4% doubt the values question but say they could raise the concern if they wanted to, 8.0% say they can't raise concerns though they don't doubt the values, and 5.0% have both problems at once. The two groups that can't raise concerns are the ones I'd worry about first, because somebody who sees a problem and can't say so is the mechanism by which an ambitious goal quietly becomes a scandal.

By department, the share of employees in that at-risk group ran from 10.4% to 26.2%. That range is a reminder that pressure isn't distributed evenly by the company. It's distributed by the manager and the operating rhythm of a particular group.

Worth asking

When you set a stretch goal, does anybody measure whether people believe it can be reached without compromising standards? That belief is measurable, it varies by department, and it usually isn't on the engagement survey.

Leadership altitude

When good managers hide problems with senior leadership

5.55My own manager
4.55Senior leadership
11 of 12Departments show the gap

Most employee surveys ask about the immediate supervisor and about senior leadership, and then report both. What they don't usually do is compare them at the individual level, which turns out to be where the interesting result lives.

Across four immediate-manager items, the average was 5.35 with 40.5% favorable. Across the four matching senior-leadership items, the average was 4.54 with 18.8% favorable. That's a gap of 0.81 points and 21.7 favorability points, and the two sets of items correlate at only 0.48, which means how somebody feels about their own boss tells you comparatively little about how they feel about the executive team. (Two further items in those sections, both about accountability, sit outside these composites because they carry their own analysis further down the page.)

The clearest single comparison is a matched pair. “When I share my work problems with my leader, they respond constructively” scored 5.55 with 59.1% favorable. The senior-leadership version of the same question, “Senior leadership responds constructively when employees raise problems,” scored 4.55 with 32.2% favorable. Same behavior, two altitudes, a full point apart. 10.9% of employees rated their own manager favorably and senior leadership unfavorably on that identical behavior.

Chart comparing immediate manager scores against senior leadership scores for each department, with the gap positive in 11 of 12 departments.
The four immediate-manager items against the four senior-leadership items, department by department. The left dot is the senior leadership score and the right dot is the immediate manager score.

Eleven of the twelve departments point the same direction, with the gap running from 1.46 in Product down to 0.41 in Finance. Sales is the one exception at −0.26, where senior leadership rates a little higher than the immediate manager, and that fits something we'll come back to later, since Sales also has the lowest score in the company on raising a concern with your own leader. Everywhere else the pattern holds, and the consistency is itself the finding. A gap in one department is easy to explain as a local personality conflict. A gap running the same direction in eleven is much harder to dismiss that way.

The practical risk here is that good management masks the problem. A company with strong frontline managers will post decent overall leadership numbers, and the executive team can read those numbers as a verdict on themselves. In this organization the frontline managers are carrying a senior-leadership score that would look considerably worse on its own, and because both sets of items get averaged into one leadership category on most dashboards, nobody ever sees it.

Worth asking

Does your survey report immediate manager and senior leadership as separate scores, and if it does, has anybody compared the matched pairs? Averaging them together will hide exactly the thing an executive team most needs to know.

Values

Where the company's values stop applying

5.55My peers live the values
4.40Leaders are bound by them
12.1%Say peers live them while leaders are not held to them

Almost every organizational culture survey asks whether people live the values, and almost every one of them gets a decent answer. That's because the question is usually asked about peers, and peers generally do behave well toward each other. The more useful question is where in the organization the values stop being binding.

We arranged four items as a ladder, from what colleagues do every day up to whether leaders themselves are bound by the standards. Each rung asks about the same values in a different place.

Chart showing four values items descending from 5.55 for peer behavior to 4.40 for whether leaders are held to the same standards.
The same values, measured at four levels of the organization. The score falls at every step from peer behavior up to leader behavior.

What people's peers do every day scored 5.55 with 59.1% favorable. Whether senior leadership makes decisions consistent with the mission and values scored 4.75. Whether the people being promoted into leadership reflect the values scored 4.45. And whether leaders at all levels are held to the same standards of behavior scored 4.40 with 28.8% favorable. From the top rung to the bottom, that's a drop of 1.15 points and 30.3 favorability points.

Taken together, those four numbers say employees see the values applying much more strongly to peer behavior than to promotions and to accountability higher up. That's a specific and fixable problem, and it's invisible if you report a single values score, because the peer item props the average up.

The sharpest version of the finding is the overlap between the top rung and the bottom one. 12.1% of employees, which is 164 people, gave a favorable answer on whether their peers consider the people they serve and an unfavorable answer on whether leaders are held to the same standards of behavior. Those are the employees telling you the values are real at eye level and stop being real above it.

Worth asking

Do your company values apply to promotion decisions? Your employees have an opinion about that, and it's usually a different opinion than the one they have about whether their coworkers are decent people.

Career rules

The unwritten rules about who gets ahead

0.606Strongest correlation with knowing how to advance
0.255Weakest of the 34
6 of 8Lowest-ranked items are about speaking up

Every organization has an official story about how people get promoted and an unofficial one that employees actually learn to work with. The gap between the two is a real cultural feature, and you can measure it without asking a single question about politics or favoritism.

The method is a correlation analysis. We took the item “I know what I need to do to advance here,” which 46.1% of employees answered favorably, and asked which of the other 34 items moves most closely with a favorable answer. These are plain correlations and none of them establishes cause, but whatever tracks career clarity most tightly is a reasonable read on what employees have concluded the real rules are.

Ranked correlation chart showing which survey items move most closely with knowing how to get ahead, with development opportunities at the top and speaking-up items near the bottom.
All 34 other items ranked by how closely each one moves with knowing how to get ahead. Longer bars mean a stronger correlation, not a stronger cause.

Three items sit at the top and they're close enough together to be read as one answer: having opportunities to develop your skills at 0.606, the organization developing future leaders who preserve the culture at 0.604, and the people being promoted reflecting the values at 0.594. Then there's a clear break, and the fourth item comes in at 0.419. The employees who say they know how to get ahead are also the ones who say they can see a development path and that the promotion decisions are consistent.

The more interesting half of the chart is the bottom. Every one of the speaking-up items ranks in the bottom half. Being able to express concerns about the strategy ranks 31st of 34. Being able to report an error ranks 32nd. Whether people solve problems rather than assign blame ranks 33rd at 0.277, and being able to raise a concern with your own leader ranks dead last at 0.255. In plain terms, the people who know how to advance here are not disproportionately the people who feel safe raising problems, and the two things are close to unrelated.

I want to be careful about the interpretation, because a correlation of 0.255 doesn't prove that speaking up hurts your career. What it establishes is that career clarity and candor aren't traveling together, which means the informal advancement rules employees have inferred don't include candor as an ingredient. If leadership believes it's built a place where raising problems is a path to advancement, the data says employees haven't drawn that conclusion.

Worth asking

If you ranked every item on your survey by how closely it moves with knowing how to get ahead, what would come out on top? That ranking is a description of your real promotion criteria as employees experience them.

Empowerment

Feeling empowered versus actually being able to change anything

5.30I am empowered to take action
4.30I can actually get a wasteful process changed
23.3%Answered favorably on both, which is real empowerment

Empowerment is one of those words that surveys measure badly, mostly because the standard item asks about a feeling. “I am empowered to take action when I see a problem or an opportunity” scored 5.30 with 51.7% favorable in this organization, which sounds like a company where people can get things done.

The companion item asks about an outcome instead of a feeling. “When I find a process that wastes time, I am able to get it changed” scored 4.30 with 26.7% favorable. That's a full point lower, and the favorable rate is roughly half.

Dumbbell chart comparing feeling empowered against being able to change a process for each of 12 departments, with gaps from 1.16 down to 0.15.
Feeling empowered against being able to change a process, department by department. The left dot is the process-change score and the right dot is the empowerment score.

The department cut is unusual for this survey, because the gap is positive in all twelve departments rather than concentrated in a few. It runs from 1.16 in Facilities down to 0.15 in People & Culture, and nine of the twelve sit within a quarter point of a full point. When a gap shows up almost everywhere at roughly the same size, you're usually looking at something structural, like an approval process or a spending threshold, rather than at a handful of controlling managers.

Averages by themselves could be explained a few different ways, so the crosstab matters. 23.3% of employees answered favorably on both items, and those are the people who feel empowered and can point to something they changed. 5.8%, or 79 people, said they feel empowered while saying they can't get a wasteful process changed. That second group is small, and it's the group I'd want to talk to first, because they've been told they have authority and have discovered they don't.

This one matters for a practical reason. Empowerment initiatives are usually launched on the strength of the feeling item, and they usually consist of encouragement. When the feeling item is already at 5.30 and the outcome item is at 4.30, more encouragement isn't the intervention. Somebody needs to find out what actually happens when an employee tries to change a process, and who says no.

Worth asking

Does your survey ask whether people feel empowered, or whether they've been able to change something? Those two questions produce very different numbers, and only one of them describes what the organization is actually like.

Fairness

Whether leaders are held to the same standards as everyone else

5.60My leader holds people accountable for their performance
4.40Leaders at all levels are held to the same standards
13.1%Say accountability applies below them but not above them

This is the same accountability item from the first analysis, pointed in the other direction. When employees rated whether their leader holds people accountable for performance, the score was 5.60 with 60.6% favorable. When they rated whether leaders at all levels are held to the same standards of behavior, the score was 4.40 with 28.8% favorable.

Chart comparing accountability applied downward at 5.60 against whether leaders are held to the same standards at 4.40, a gap of 1.20 points.
Accountability as employees experience it applied to them, compared with whether they believe it applies upward as well.

The gap is 1.20 points and 31.8 favorability points, though the more telling number is the overlap. 13.1% of employees gave a favorable answer on whether their leader holds people accountable and an unfavorable answer on whether leaders are held to the same standards. That's roughly one employee in eight explicitly describing an accountability system that runs downhill and, as far as they can see, doesn't run back up.

What makes this worth acting on rather than filing as a grievance is where it lands in the correlation rankings. When we ranked all 34 items by how closely each moves with knowing how to get ahead, whether leaders are held to the same standards came in 7th. Against the outcome items generally it ranks 2nd of 34. That's unusually high for an item most engagement surveys don't ask at all.

One caution on interpretation. Employees see their own manager's consequences and rarely see what happens to a leader two levels up, so some of this gap is a visibility problem rather than a fairness problem. That distinction matters for the fix, because the answer to a visibility problem is telling people what happened, while the answer to a fairness problem is something considerably harder.

Worth asking

When a leader in your organization misses a commitment or behaves badly, do employees find out that anything happened? If the answer is no, your accountability score will keep looking fine while your fairness score keeps sinking.

Psychological safety

Why there's no such thing as one psychological safety score

1.65Spread across the six items
4.61The single average
4 of 12Departments a composite misdirects

Psychological safety gets reported as a single number on a great many dashboards, and that single number is usually an average of several items. Averaging is the problem, because in this organization the six psychological safety items ranged from 5.35 down to 3.70, a spread of 1.65 points, and the average of 4.61 doesn't describe any of them.

Chart showing six psychological safety items ranging from 5.35 to 3.70 against a single composite average of 4.61.
Six psychological safety items shown individually against the composite average that would normally be reported in their place.

Raising a concern with your own leader scored 5.35. Reporting a serious error scored 5.15. Raising a concern with anyone regardless of position or department scored 4.80. Questioning the strategy scored 4.35, and missing an ambitious goal without fearing for your job scored 4.30. The lowest item, which is reverse-worded and asks whether there are people outside your department whose reaction you worry about, scored 3.70 after reverse-scoring.

Those six numbers describe a coherent situation rather than a random scatter. Safety is highest inside the relationship with the direct manager, drops when the audience widens beyond that relationship, and drops furthest when the topic is the strategy or a missed number. A composite of 4.61 would send a leadership team looking for a general trust problem, when what the data actually shows is a specific one about lateral relationships and about goals.

The departmental cut adds a second layer. Every department has its own profile across the six items, and the profiles are different shapes rather than the same shape at different heights. Sales scores lowest of any department on raising a concern with its own leader at 3.93 while scoring above the company average on raising concerns with anyone, which is an unusual inversion. Operations scores near the bottom on the strategy and missed-goal items specifically. People & Culture is strong on the manager items and weakest on the missed-goal item. Four departments have a different worst item than the company does, so a company-level psychological safety score would point four of your twelve departments at the wrong problem.

Worth asking

Does your psychological safety number come from one item or from an average of several? And if it's an average, how far apart are the items underneath it?

Silos

The different problems that all get called silos

0.64Correlation between the two structural items
0.44Correlation with cross-department wariness
970Mentions of a department to avoid

Silos is the word organizations use for at least three separate conditions, and because the word covers all of them, the remedy tends to be a cross-functional offsite that addresses none of them.

Our culture survey measures three different things that people call silos. Whether employees from different departments are working toward the same goals scored 4.50. Whether people in other departments follow through on the commitments they make to you scored 4.55. And whether there are people outside your own department whose reaction you worry about when you need to raise an issue scored 3.70 after reverse-scoring, with 47.1% of employees agreeing that such people exist.

Bar chart of three silo-related items: goal alignment at 4.50, follow-through at 4.55, and cross-department worry at 3.70 after reverse-scoring.
Three items that all get labeled silos, shown as averages on the seven-point scale.

The correlations are what separate them. Goal alignment and follow-through correlate at 0.64, which is well above the 0.42 average correlation between items on this survey, so those two really are one problem with two symptoms. But each of them correlates only about 0.44 with the wariness item, which is close to the survey-wide baseline. Statistically, cross-department wariness is behaving like a separate condition, so fixing goal alignment alone is unlikely to touch it.

That distinction has a direct implication for what you'd do about it. Misaligned goals and broken commitments respond to structural fixes: shared metrics, clearer handoffs, service agreements between departments. Cross-department wariness is unlikely to respond to any of that, because the employee isn't confused about the goal. They're avoiding a specific group of people.

Which departments people are avoiding

Because the wariness item has a follow-up asking which departments, we can name them. The 1,354 employees produced 970 mentions, and laying those out in a grid shows both who gets avoided and who does the avoiding.

Matrix showing which departments hesitate to raise issues with which other departments, with the darkest columns at Compliance and Risk, Finance and Legal.
Rows are the department doing the worrying and columns are the department named. Cells with fewer than ten people are left blank so no small group can be identified.

Read down the columns and you get the departments people hesitate to approach. Compliance & Risk was named by 180 people in total, which is 13.3% of the entire workforce. Finance was named by 149, Legal by 122, and Information Technology by 116. The pattern is recognizable to anybody who has worked in a large organization, because those four are gatekeeper functions whose job is partly to say no, and being named here isn't automatically a sign that they're doing anything wrong.

Read across the rows and you get the departments doing the worrying. Operations, Customer Support and Sales fill most of the grid, and each of them names the same gatekeeper functions at the top of its own list, which suggests the three big operating groups are running into the same wall rather than each having a private feud.

The number that complicates the easy explanation is what those departments say about themselves. Inside Compliance & Risk, 69.8% of the 63 employees said there are people outside their department whose reaction they worry about, which is the highest rate in the company and well above the 47.1% average. The department most avoided is also the department most avoidant. That's harder to explain as a function of the role, and it's the sort of finding that would never appear on a survey report built from item averages.

Worth asking

When your organization says it has a silo problem, which of the three does it have? The structural version and the cross-department version look identical in a summary and need completely different responses.

Find out which of these ten your organization has.

Leadership IQ's culture survey asks the paired questions these analyses need, and reports the results by department and by manager rather than as one company number.

See Culture Survey Services

The difference

What a culture survey measures that an engagement survey doesn't

The practical difference isn't the questions so much as what you do with them. Most employee surveys report each survey question on its own, rank the items from best to worst, and hand leadership the bottom five to work on. That method can only find problems willing to announce themselves as a low score, which leaves out a surprising amount of what actually goes wrong in organizations.

Our culture survey asks a lot of the same things, and then compares them. Does accountability come with candor or without it? Do the people who understand the strategy also have the authority and the staffing to act on it? Do the values that govern how colleagues treat each other still apply to who gets promoted? Those comparisons need pairs of questions designed to sit next to each other, and they need department and manager identifiers attached to the responses, because most of these findings disappear entirely at the company level. The first analysis on this page is the clearest illustration: a company-wide gap of 0.53 points, which nobody would act on, turns out to run from −0.49 to +1.64 by department and from −1.02 to +2.28 by manager. The company average wasn't wrong. It was an average of two opposite cultures.

The business case

Why CEOs care about culture surveys

In my experience, most CEOs don't wake up thinking about employee engagement. They wake up thinking about the strategy they announced, the number they committed to, and why the organization seems to be moving slower than the plan assumed. When a culture survey earns a place on the executive agenda, it's usually because it can answer that question, and an engagement survey generally can't.

Strategy execution asks five separate things of one employee, and each gets measured by its own survey question. Reported separately those five numbers look encouraging. Followed through the same individuals, only 22.9% cleared every condition, which is the second analysis on this page.

That number is the kind of thing a CEO can act on, because it identifies which condition is failing and roughly how many people it's failing for. It also reframes what leadership should spend money on. If people understood the strategy perfectly well and still couldn't act, then communicating the strategy again is money spent on the one part that was already working.

After the survey

What to do with culture survey results

The findings above have an obvious quality once you see them, and that's a little misleading, because none of them would surface from a conventional survey report. Getting to them requires a few choices about how the survey is run and how the results get analyzed.

The first choice is keeping responses at the individual level. Six of these ten analyses depend on knowing that the same person answered one way on one question and another way on a second question, and you can't reconstruct that from item averages. A confidential survey can preserve respondent-level answer patterns without revealing anybody's identity to the organization, so protecting employees doesn't require throwing away the link between one person's answers.

The second is attaching department and manager identifiers to every response. The accountability gap was 0.53 points company-wide and 2.28 points under one manager, and the company number was an average of two opposite cultures. Reporting culture survey results only at the enterprise level will reliably hide the finding, and it's the reason so many organizations conclude their culture is “fine, with some room for improvement.”

The third is deciding in advance which pairs of items you intend to compare. Culture analysis works because the questions were written to sit next to each other, so accountability has a candor companion, empowerment has a traction companion, and the values ladder has four rungs asking about the same values in four places. If you assemble a survey by picking individually interesting questions, you'll end up with a list of items and no way to compare them.

Then there's what happens after the analysis. Reporting a finding to the whole company usually doesn't help, because these findings are concentrated. Ten named managers had an accountability-candor gap worth a conversation, and 79 people felt empowered without being able to change anything. Those are manageable populations. Handing the whole organization a slide that says psychological safety is 4.61 gives every leader the same non-specific homework, while telling four departments that their worst item isn't the company's worst item gives them something to work on Monday.

Survey design

How to design a culture survey that can find these problems

People often ask what makes a culture survey different from an employee engagement survey in terms of the actual questionnaire, and the honest answer is that a lot of the questions look similar. Our own culture survey includes plenty of engagement-style items about the manager, about pride in the organization, and about whether people would recommend the place. The difference is in what surrounds them and what gets done with them.

A few things matter more than the rest when you're designing one.

  • Write items in matched pairs. For every item measuring a desirable condition, include one measuring whether the condition survives contact with reality. Accountability pairs with candor. Feeling empowered pairs with having changed something. Understanding the strategy pairs with having the staffing to execute it.
  • Ask about the same behavior at different altitudes. The senior leadership items in this survey deliberately mirror the immediate supervisor items, which is what makes the 0.81-point gap readable as a finding rather than as two unrelated scores.
  • Use a seven-point Likert scale. A five-point scale compresses the middle and makes gaps of the size we're looking for harder to detect. Seven points give respondents room to distinguish between mild and firm agreement, which is where a lot of these comparisons live.
  • Include at least one reverse-worded item, and score it correctly. The cross-department wariness item is worded in the opposite direction on purpose, partly to catch inattentive responding and partly because it's the only comfortable way to ask that question.
  • Add one or two follow-ups that name names. The question asking which departments people hesitate to approach turned a 3.70 average into a grid naming which departments people avoid and which departments are doing the avoiding, and that grid is what makes the item actionable.
  • Keep it long enough to pair and short enough to finish. For the kind of paired analysis we run, I generally aim for something in the range of 35 to 50 items, and the survey behind these analyses had 39. Go much shorter and you run out of matched pairs. Go much longer and completion starts to become a burden. That's practitioner judgment rather than a measured threshold.

On how many questions and how often to field them, there's no universal right answer, though I'd generally rather have one carefully paired annual culture survey than four pulse surveys that each ask six disconnected items. Pulse surveys are good at tracking a number you already decided to watch. They're poor at finding a problem you didn't know to look for, which is the entire purpose of the analysis on this page.

Common questions

Frequently asked questions about culture surveys

What a culture survey is, how it differs from an employee engagement survey, and how to run one that can actually find these problems.

What is a culture survey?

A culture survey, sometimes called an employee culture survey or a workplace culture survey, is an employee survey designed to measure how an organization actually operates: how decisions get made, what happens when somebody raises a problem, whether the stated values govern real behavior, and whether people can act on the strategy. Different firms run them differently. What distinguishes our approach is the second step, where we compare answers against each other at the individual level rather than reporting each question on its own.

What's the difference between a culture survey and an employee engagement survey?

An employee engagement survey measures how employees feel about working at the organization, usually rolled up into an engagement score and a set of item scores. Our culture survey measures how the organization works, and it does that by pairing items and comparing them at the individual level. There is a lot of overlap in the questions themselves, and our culture survey includes engagement items, though the two produce different kinds of findings. Engagement tells you the temperature. Culture analysis tells you which machine is running hot and why.

What should a culture survey measure?

Company culture survey questions should at minimum cover the immediate manager relationship, senior leadership, psychological safety and speaking up, values and ethics, strategy and goals, empowerment and decision-making, cross-department collaboration, and career development. Each of those areas needs several items rather than one, because most of the useful findings come from comparing items inside an area or across two areas.

How many questions should a culture survey have?

For paired analysis of the kind shown on this page, I generally aim for somewhere in the range of 35 to 50 items, and the survey behind these analyses had 39. Go much shorter and you won't have enough matched pairs to run the comparisons. Go much longer and completion starts to become a burden. That's a practical preference rather than a measured threshold.

Should a culture survey be anonymous?

It should be confidential, meaning individual responses are never shown to anyone in the organization and results are only reported for groups above a minimum size. That's different from stripping out respondent identifiers entirely. Most of the findings on this page require knowing that the same person answered both questions in a pair, along with which department and manager they report to, so stripping those links out would prevent most of the paired analyses shown on this page.

What's a good response rate for a culture survey?

Rates vary a lot by organization, and in my experience the number matters less than whether the non-responders are concentrated. If a single department comes in at 30% while the rest of the company is at 80%, that department's silence is itself a finding, and it's worth investigating before you interpret anything else.

How often should you run one?

Annually is right for most organizations, with the caveat that running a culture survey and then doing nothing visible with the results is worse than not running one. If you're not prepared to act on what a survey finds within a couple of months, it's better to wait until you are.

Can you use culture survey questions from a template?

You can, and a good culture survey template will save you a lot of time, though it's worth checking that the template's items are actually designed to be compared. Many published question lists are collections of individually reasonable questions with no matched pairs in them, which means you can field the survey and still be unable to run the analyses described here.