Every major organisational change programme runs into the same tension. You need the people vested and affected to be genuinely involved, not for political reasons alone, but because they hold knowledge that will determine whether the change succeeds or fails. At the same time, involving five hundred people meaningfully, at the pace change actually moves, seems structurally impossible.
The standard resolution is a compromise that satisfies neither goal. People are "consulted" through town halls, surveys, and selected focus groups. Leadership thinks involvement happened. The people involved know it did not. The result is compliance, if you are fortunate, and resistance, if you are not. Either way, the knowledge in the organisation, the distributed intelligence about what will actually work and what will not, goes largely untapped.
Why the usual approaches produce tick-box results
Town halls inform. They do not involve. The dynamic of a large group facing senior leadership produces a narrow range of contributions: positive framing, safe questions, the one person willing to say something difficult. The meeting that follows, where people debrief to each other what they could not say in the room, is usually more analytically useful than the town hall itself.
Surveys scale but they flatten. They collect answers to questions that leadership thought to ask. They cannot surface the concern that was not anticipated, the insight that lives in the intersection between two roles, or the pattern that only becomes visible when many contributions are mapped in relation to each other.
Focus groups are more honest than either, because smaller groups with skilled facilitation can surface things that surveys and town halls miss. But they are expensive and slow, reach a small fraction of the organisation, and produce outputs that are difficult to integrate with each other.
None of these approaches were designed to do what large-scale involvement actually requires: get the distributed intelligence of the organisation to bear on a decision, in a form that leadership can actually use.
The people affected by a change hold knowledge that will determine whether it succeeds. The standard consultation process is almost perfectly designed to leave that knowledge inaccessible.
What genuine large-scale involvement requires
Three things that current approaches cannot provide simultaneously:
Scale without flattening. The process has to work with hundreds of contributors without reducing their input to percentages on a survey. Each perspective has to remain distinct: visible in its particularity, not dissolved into a theme.
Structure without prescription. People need to be able to contribute in their own terms, to the questions that actually matter to them, rather than responding to a predetermined set of questions. But those contributions need to be structured so that they can be read in relation to each other.
Speed without selection. Getting input from five hundred people at the pace a change programme moves cannot involve scheduling five hundred conversations or waiting three months for a consultation cycle to complete.
The architecture that produces these three things simultaneously is asynchronous, structured deliberation at scale, where contributions go in as people have genuine thought, are mapped in relation to each other as they arrive, and are analysed by AI as the picture develops rather than after the consultation closes.
What this looks like in practice
On Hunome, a large-scale change programme creates a SparkMap, a structured question or set of questions that opens the deliberation. People across the organisation contribute their perspective asynchronously, in whatever time they have, without the social pressure of observed settings.
Each contribution is mapped in relation to others as it arrives. Someone in operations challenges a premise from strategy. Someone in a regional office adds context that is invisible from the centre. The product identifies where these connections produce something neither perspective held alone: an emerging insight, a genuine tension, a risk that the organisation already understands but that leadership has not yet seen.
By the time the consultation closes, or continuously, if the deliberation is designed to remain open, leadership does not receive a summary of themes. They receive a map of what the organisation understands about the change: where there is genuine convergence, where apparent consensus masks real concern, where the people closest to execution see differently from the people designing the change.
The difference it makes to outcomes
The practical difference between tick-box consultation and genuine involvement is not sentiment. It is execution. Change programmes that build genuine shared understanding in advance of rollout encounter less resistance, require fewer adjustments after launch, and compound rather than stall. The people executing them had access to the reasoning, contributed to the picture, and understand why, not just what.
The organisations that manage this well do not have better consultation processes. They have a different model of what they are trying to produce. They are not trying to inform and get buy-in. They are trying to build shared understanding that the change can run on. Those are structurally different goals, and they require structurally different approaches.