Asking People What Is Wrong Is a Promise
The second survey tells you more than the first one ever did.
Not because the questions improved. Because by the second survey, your workforce has evidence about what happens to an answer.
I have watched this from both chairs. I have been the executive who commissioned the survey and I am now the person organizations hire to run one, which means I have seen the full life cycle of an honest answer more times than is comfortable. The pattern does not vary much.
The first survey produces a strong response rate and an unusual amount of candor. People write paragraphs in the open text fields. Some of them write things they have never said out loud in eleven years of employment. That volume is almost always read as engagement, and it gets reported to the board that way.
It is not engagement. It is hope, and it has a shelf life of about one quarter.
Here is what leaders underestimate. The act of asking is not neutral. It is not data collection that sits outside the organization while it happens. Asking is itself an event in the climate, and it makes a claim, the same way every message makes a claim. It says leadership wants to know. And the moment you say you want to know, you have taken on an obligation to do something with what you are told.
A survey with no visible consequence does not return the organization to where it was before the survey. It moves the organization backward. Before, staff could believe that leadership had not asked because leadership did not realize anything was wrong. After, they know leadership asked, received the answer, and proceeded as before. You have converted a tolerable uncertainty into a settled conclusion.
Which is why the most damaged organizations I walk into are almost never the ones that never measured anything. They are the ones that have measured three times.
The tell is the response rate on the next round. It drops, and leadership reads the drop as apathy or survey fatigue, and there is a whole vocabulary available for explaining it that costs nobody anything. Survey fatigue is a real phenomenon in organizations that survey constantly for no reason. In an organization that surveys annually, a falling response rate is not fatigue. It is a considered decision by people who did the math on the first one.
I would go further. The response rate is often more informative than the instrument. The instrument tells you what people are willing to report. The response rate tells you whether they believe reporting accomplishes anything, and that second question is closer to what climate actually is.
None of this is an argument against measuring. It is an argument for deciding what you are prepared to do before you ask, which almost nobody does in the right order.
The order that works looks like this. Before the survey goes out, leadership names the two or three things that are genuinely on the table. Not the whole list of what people might raise. The things that could actually change within two quarters given real constraints. Then, and this is the part that gets skipped, leadership says out loud what is not on the table and why. The funder contract is what it is. The overnight shift exists because clients exist at night. Those are not going to change and pretending otherwise wastes everyone's honesty.
Then you report back. All of it, including the findings you are not going to act on, named as findings you are not going to act on. People are far more tolerant of an unresolved problem than of an unacknowledged one. What they will not forgive is telling them their answer mattered and then behaving as though it did not.
A closing thought for anyone about to launch one this quarter. If the honest answer to what will change as a result of this is nothing, then do not run it. The information is not worth what the silence afterward will cost you.
You are not measuring climate when you survey. You are participating in it.




Comments