The Consultation That Changed Nothing
Why organisations design processes that look like listening
There is a particular kind of silence that follows a consultation. Not the silence of consideration, where something heard is being weighed. The silence of completion, where a process has been concluded and the findings have been filed. The residents submitted their responses. The staff completed the survey. The service users attended the focus group. And then, at some point later — sometimes months, sometimes longer — a decision was announced that bore little visible relationship to what anyone said.
Most people who have been consulted by a large organisation have experienced this. Many have stopped expecting otherwise. That learned scepticism is not apathy. It is a rational response to a pattern that repeats across sectors with enough consistency to suggest it is not accidental.
The pattern has acquired a name — consultation fatigue — but the name understates what is actually happening. Fatigue implies a willingness that has been worn down. What most organisations have produced is something more deliberate: a process designed to look like listening without requiring the organisation to change course as a result of what it hears.
The mechanics of being heard without being heard
The structure of most consultations gives the game away.
Questions are written by the organisation, which means the answer categories reflect the organisation’s existing understanding of the problem. Respondents are asked to rate, rank, or select from options that were designed before anyone outside the room was consulted. Free-text fields exist, but are rarely analysed systematically — they are too difficult to process at scale and too unpredictable in what they might surface. The consultation closes, the quantitative results are tabulated, and the report that emerges reflects the organisation’s original position with a margin of adjustment around the edges.
This is not cynicism dressed as analysis. It is the logical consequence of designing a consultation process around the outputs you need to produce rather than the understanding you need to reach. In local government, that output is a mandate — a defensible record that affected parties were involved before a decision was made. In the NHS, it is a compliance requirement — evidence of patient and public involvement in service design. In the private sector, it is an engagement score — something to report to the board or include in a regulatory submission. Each has a legitimate purpose. None of them requires the organisation to be genuinely changed by what it hears.
The people being consulted know this. The communities most affected by decisions are typically the ones with the least trust in the processes designed to involve them — because they have the most experience of those processes. When a community has watched a planning consultation produce a predetermined outcome, or seen a workforce survey followed by a management communications campaign rather than structural change, the rational response is to disengage. Not because the issues don’t matter to them. Because they have learned that engaging produces no different outcome than not engaging.
What the same pattern looks like across sectors
In local government, the planning consultation is the clearest case. Residents are invited to comment on a proposal that is already substantially formed. The statutory requirement is to consult; there is no equivalent requirement to be materially influenced by what is said. Communities that oppose a development learn to flood the process with responses because volume is the only variable that demonstrably affects outcomes — not the quality of the argument, not the specificity of the concern, not the evidence that the proposal conflicts with the community’s stated needs.
In healthcare, service redesign consultations run on similar logic. A trust deciding to reconfigure services will conduct patient engagement as part of the process. The engagement is genuine in the sense that it happens; it is limited in the sense that the financial and operational case for the reconfiguration is typically established before the engagement begins. What the consultation can change is the detail. What it rarely changes is the direction.
In the private sector, the employee consultation — particularly in a restructure or acquisition — operates under legal requirements in the UK that mandate a period of consultation before certain decisions are implemented. The requirement is to consult; it is not to reach agreement, and it is not to change course if the arguments against the proposal are sound. HR teams are well practised in running consultations that satisfy the legal threshold while protecting the operational decision already made.
In the charity sector, the gap is perhaps most uncomfortable to acknowledge. Organisations built on the principle of community voice frequently struggle to implement it in practice. Governance structures centre the board and the executive. Impact measurement centres the funder’s reporting requirements. The beneficiary’s account of their own experience sits at the end of a chain of representation — reported by a caseworker, summarised by a manager, condensed into an impact metric by a communications team — that has progressively removed the original voice by the time it reaches anyone with decision-making authority.
The thing that peer validation changes
The problem is not only that organisations fail to act on what they hear. It is that the processes they use mean they often do not hear clearly in the first place.
A consultation that asks closed questions gets closed answers. A free-text field that sits at the end of a fifteen-minute survey gets responses from the minority who feel strongly enough to write something additional. An engagement that channels responses through a manager or a facilitator introduces the interpretation of the intermediary before the data reaches analysis. By the time findings are presented to the people who will make the decision, the original voice has been translated several times.
The methodological shift that matters here is not just collecting open responses — it is validating them within the community before they reach the analyst. When people can see each other’s responses and indicate what resonates, two things happen that closed surveys cannot produce. First, the synthesis reflects the community’s own sense of what matters, rather than the researcher’s coding scheme. Second, people who contribute to a process and see their contribution acknowledged by peers are less likely to conclude that the exercise was performative. The experience of being heard is partly structural — it depends on whether the process was designed to hear or designed to record.
Gobby is one tool built on this logic — open responses rather than closed questions, peer-powered voting so participants can indicate what resonates, AI-assisted synthesis that reflects the community’s own sense of priority rather than the analyst’s coding scheme. It is still used by a minority of organisations. The majority continue to run processes that produce defensible records rather than genuine intelligence. The technology to do otherwise is not the constraint. The will to act on what might be heard is.
That is the harder problem, and no tool solves it. What better processes do is remove the organisation’s ability to claim it didn’t know. If the findings are specific, community-validated, and clearly stated, the decision to set them aside becomes a conscious choice rather than an administrative oversight. That is a different kind of accountability — and it is the reason some organisations prefer the consultation that changes nothing.
My opinion
I have been in enough of these rooms to know the difference between an organisation that doesn’t know how to listen and one that has decided not to. Most consultation theatre is the second kind. Tools like Gobby do something useful: they remove the claim of ignorance. If the findings are specific and community-validated, the decision to set them aside is no longer an oversight. It is a choice. And the organisations that consistently make it know exactly what they are doing.
You’re reading The Next Evolution by Neil Catton, articles that explore the human world and the intersection of technology, they try and ask difficult questions - not to scare - but to inform. If someone forwarded this to you, you can subscribe free at neilcatton.substack.com.
Neil Catton is the author of The Next Evolution, The Cognitive Crucible and The Shadow System - available on Amazon, and writes at the intersection of technology, ethics, and human purpose.