Asking, and the harder business of answering

Few practices in higher education are as thoroughly established, and as rarely examined, as the gathering of student feedback. Surveys arrive at the end of modules, at the close of the year, after particular events, and at intervals set by external requirements, accumulating into something few institutions could fully describe if asked. The instinct to listen is a good one, and the principle that students should have a voice in their own education is now so widely accepted that it can feel beyond question. Yet the very familiarity of the practice may be part of the difficulty. When a thing is done because it has always been done, the question of what it is for tends to go unasked.

A recently published sector framework sets out to ask precisely that question, and its central proposition is worth sitting with. It argues that student survey feedback creates value only when it is treated as a system, one with an articulated purpose, a clear account of who is involved and a settled understanding of what is supposed to happen as a result. Put that way, the claim sounds almost obvious. The interest lies in how seldom institutions can actually meet it. Most have a great many surveys and rather less by way of a system, an arrangement whose parts work together towards a thought-through end.

The framework identifies three recurring problems, and what makes them instructive is the way they tend to be treated in isolation. The first is low response rates, which are usually met with reminders, incentives and exhortation. The second is disagreement among staff about what the data actually mean, which surfaces whenever results are uncomfortable and is often managed by quietly setting the awkward numbers aside. The third, and perhaps the most telling, is that students are asked for their views repeatedly throughout a term, with little confidence that anything follows from the asking. Each is real, and each is ordinarily addressed as a separate operational irritation. The more useful reading is that they may be symptoms of one underlying condition, a feedback apparatus grown by accretion rather than by design.

Why declining response rates may be a question, not a problem

Consider response rates through this lens. A falling rate is generally framed as a problem of student behaviour to be corrected, through better timing, gentler reminders or a prize draw. It is at least worth entertaining the alternative reading, that students decline to respond because experience has taught them that responding changes little. An institution recently reviewing its module evaluation found that students knew how to give feedback but had little confidence that it led anywhere, and that finding has an uncomfortable logic to it. People stop contributing to a process whose outputs they never see. If that interpretation holds, and it is offered as a possibility rather than a certainty given that the evidence is associative, then a low response rate is not a failure of persuasion but a fairly rational verdict on the system that produced it.

The disagreement among staff over interpretation may be similarly revealing. It is tempting to treat such disputes as a nuisance, a matter of colleagues resisting inconvenient findings. They may instead indicate that the purpose of a given survey was never clearly established, so that the same numbers can be read as a verdict on teaching, a measure of satisfaction, a proxy for something else entirely or simply as noise. Where there is no agreed account of what the instrument is for, there can be none of what its results mean, and the argument that follows is not really about the data. It is about the absence of a shared purpose that the data were meant to serve.

There is a longer principle beneath this, one that predates the framework and gives it a firmer footing than any single publication could. The expectation that institutions should close the feedback loop, that they should not merely collect views but demonstrate what has changed as a result, has been part of the sector’s quality assurance vocabulary for many years. What the recent work adds is that closing the loop is not a final step bolted on at the end but a design principle that ought to shape the whole arrangement from the outset. A system built without it will tend to produce the very symptoms institutions then spend their energy trying to treat.

The prior question

The harder matter, and the one the framework brings into focus, is that the prior question of what the feedback is for is the one institutions seem least practised at asking. This is not a failure of diligence. It is, if anything, a consequence of conscientiousness: the surveys multiply because each addition is well-intentioned and each seems to address a particular need. The difficulty is that no single act of collection requires anyone to articulate the purpose of the whole, and so the whole comes to lack one. Asking it is uncomfortable because it exposes how much gathering has happened without a settled view of the answer, and an honest audit may reveal surveys whose results no one acts upon, audiences asked the same thing twice, and intentions never recorded.

It is worth acknowledging that the framework is produced in partnership with a provider of survey software, so its claims are perhaps best taken as a useful way of thinking rather than as independent findings. The underlying proposition, however, does not depend on the partnership. It rests on a fairly old idea, that a practice without a purpose tends to drift, and that listening which leads nowhere is not really listening at all.

None of this resolves the practical questions that institutional leaders must weigh. It may, though, reframe them. The question is perhaps less how to raise response rates or settle interpretive disputes, and more whether an institution can say, plainly and in advance, what its feedback is for and what it commits to doing with what it hears. Can a board, or a senior team, describe the feedback system it presides over as a system at all, rather than as an inheritance? And if the honest answer is that it cannot yet, might that be the more useful place to begin than with the next round of reminders?