By Ritvars Mētra, Founder of ReadinessCompassThe programme runs a monthly readiness pulse. Eleven months in, the scores have moved by less than half a point in any direction, response rates have fallen from 61 per cent to 29, and the monthly slide has become something people scroll past.
The usual diagnosis is survey fatigue, and the usual remedy is to survey less. Both are close to the truth and slightly wrong.
Cadence should follow decisions, not the calendar
A monthly pulse is a calendar artefact. It exists because reporting is monthly, not because readiness changes monthly.
The better question is what decisions are coming, and when each one needs evidence. A programme with a scope decision in March, a training-approach decision in June and a go/no-go in October needs measurement before each of those, at a depth that matches what is being decided. Between them, additional rounds produce numbers nobody will act on — which is the actual cause of the fatigue.
This is the same discipline that separates a decision instrument from a reporting ritual. If no answer to the March pulse would change anything before June, the March pulse is a status update wearing a survey’s clothes.
Measure things at the speed they move
Different readiness constructs change on completely different timescales, and putting them all on one cadence guarantees that some are measured too often and others too late.
| What you are measuring | How fast it moves | Sensible interval |
|---|---|---|
| Awareness of the change | Fast, then saturates | Once early, once before go-live |
| Capability to perform the task | Fast — days after practice | Before and after each training or rehearsal event |
| Confidence and perceived readiness | Moderate, and reactive to events | Quarterly, or before a gate |
| Manager reinforcement behaviour | Moderate | Monthly, and only in affected teams |
| Capacity and workload | Fast, and tied to the business cycle | Whenever the portfolio changes, not on a fixed date |
| Trust in leadership | Slow | Twice a year at most |
Measuring something more often than it changes does not give you a clearer picture. It gives you a series of small fluctuations that a programme will then interpret — and a governance meeting that discusses a 0.2 movement in a sentiment score is actively worse than one that has no number at all.
Fatigue is mostly futility
People will complete a great many surveys for an organisation that visibly acts on them, and very few for one that does not. What gets called fatigue is usually an accurate assessment that answering achieves nothing.
The cost shows up before the response rate does. Jon Krosnick’s work on satisficing in attitude measures describes what happens when the effort of answering properly exceeds a respondent’s willingness to spend it: they produce a satisfactory answer rather than an optimal one — agreeing with the assertion, failing to differentiate across items, saying “don’t know”, or selecting more or less at random.
So the first casualty of an over-frequent survey is not participation. It is accuracy among the people who still respond, and that degradation is invisible: the scores stay in the same plausible mid-range while meaning progressively less.
Two indicators worth watching in any repeated instrument: the proportion of responses with no variation across items, and the proportion completed in under a plausible minimum time. Both rising across waves is the signal to stop, whatever the response rate says.
A cadence that works
- One proper baseline, early enough that the answer can still change scope. Fifteen items, full population, segmented.
- Targeted checks between gates — three or four items, one function, triggered by an event rather than a date. A rehearsal, a training wave, a reorganisation.
- A pre-gate round before go/no-go, identical in wording and order to the baseline so the comparison is real.
- One post-go-live round at around six months, when support has been withdrawn and the behaviour has settled. This is the round almost everyone skips and the one that tells you whether anything held.
Four rounds across a programme, not eleven. The targeted checks carry most of the operational value because they are small enough to run quickly and specific enough to act on the same week.
Keep the instrument still
One rule matters more than the interval: if you want to compare waves, the items and their order must not change between them.
Reordering or rewording a survey between rounds means any movement you observe may be an artefact of the instrument rather than a change in the organisation. Improve the survey between programmes, not between waves of the same one — and if you must change an item mid-flight, report it as a break in series rather than a trend.
The organisations that get real value from pulse measurement are rarely the ones measuring most often. They are the ones where each round was tied to a decision, the instrument stayed still, and something visibly changed afterwards.
More on readiness measurement in the Change Readiness Hub, or see how to design the instrument itself.