I can tell within the first ten minutes of a community engagement session whether the organisation running it actually wants community input or just needs to document that they asked. The community can tell too. And once they've identified it as checkbox engagement, you've lost them - not just for this project, but for the next one.
The pattern is so common it has its own rhythm. An organisation, usually government or a large corporate, has a project that requires community engagement. Maybe it's a regulatory requirement. Maybe a funder insists on it. Maybe someone in the project team genuinely believes in it. Regardless of the motivation, the engagement is structured identically: present the proposal, invite feedback, collect comments, write a report confirming engagement was undertaken, proceed with the original plan.
This is not engagement. It's a compliance exercise wearing engagement's clothes.
78%
of community organisations surveyed reported that government engagement processes 'did not influence the final decision'
Source: Community Waikato, Community Engagement Survey, 2024
That number reflects a deep and warranted cynicism. Communities, particularly Māori and Pacific communities, have decades of experience with engagement processes designed to validate decisions already made. The feedback is collected. The report is written. The outcome doesn't change. And the next time the organisation comes calling, the community has less reason to show up.
How Checkbox Engagement Works
Checkbox engagement has reliable features. Recognise them and you can identify it before it starts.
The decision is already made. The engagement session presents a near-final proposal with minor options for community input. The fundamental direction isn't open for discussion. The community's role is to choose between predetermined alternatives or suggest adjustments at the margins.
The format is extractive. Feedback flows in one direction. The organisation asks questions, records answers, and leaves. There's no dialogue. No back-and-forth. No co-creation. The community provides raw material that the organisation processes into whatever supports its existing plan.
The timeline is convenient for the organisation. Engagement sessions are scheduled to fit the project timeline, not the community's availability. A two-hour evening session on a weekday might work for the project team. It doesn't work for whānau with children, shift workers, kaumātua who don't drive at night, or communities where important discussions happen over days, not hours.
Follow-up is absent. After the engagement session, the community hears nothing until the decision is announced. No interim updates. No response to specific concerns. No evidence that any input was incorporated. The silence communicates clearly: your contribution was noted and filed.
Why It Matters More for Māori and Pacific Communities
Checkbox engagement is corrosive everywhere. For Māori and Pacific communities, it carries additional weight.
These communities have specific historical experience with engagement that wasn't genuine. Treaty consultation processes that didn't influence outcomes. Health service consultations that didn't change how services were delivered. Resource consent processes where community objections were acknowledged and overridden.
Each failed engagement deepens the trust deficit. And each deepening makes the next genuine engagement harder. When I run engagement for the Ministry of Education, I'm not starting from neutral. I'm starting from whatever the community's last experience of government engagement was. If that experience was checkbox, I'm starting from negative.
Every checkbox engagement process makes the next genuine engagement harder. The deficit compounds. Communities don't forget being used as props in someone else's compliance exercise.
Hannah Terangi Wynne
Strategic Communications Advisory
What Genuine Engagement Looks Like
Genuine community engagement is uncomfortable for organisations because it requires giving up control. Specifically:
The outcome is genuinely open. If the community's input can't change the direction, don't call it engagement. Call it notification. There's nothing wrong with notification - sometimes decisions are made and communities need to be informed. But pretending notification is engagement is dishonest, and communities recognise dishonesty instantly.
The process belongs to the community. Let the community determine how engagement happens. What format? What timeline? Who facilitates? Where does it happen? When the organisation controls the process, the process reflects the organisation's priorities, not the community's.
Feedback creates obligation. If you ask for community input, you're obligated to respond to it. Not just collect it. Respond. Explain what you heard, what you changed as a result, and - critically - what you didn't change and why. Accountability closes the loop.
Relationships persist beyond the project. If the only time you talk to a community is when you need their engagement for a project, you don't have a relationship. You have a transaction. Genuine engagement is built on relationships that exist before and after the specific project.
In Māori contexts, this maps directly to tikanga. The hui process, the ongoing relationship between mana whenua and those operating in their rohe, the obligation of manaakitanga - these aren't cultural add-ons to engagement. They're the framework for how engagement should work. Organisations that understand this produce better engagement. Organisations that don't, produce checkboxes.
The fix isn't complicated. It's just uncomfortable. Stop engaging communities to validate your plan. Start engaging communities to make your plan better. The difference is whether you're willing to change direction based on what you hear. If you're not, save everyone's time and skip the hui.