Engagement as Sequence, Not Event
Engagement fails when it is an event, a town hall three weeks before the vote, and succeeds when it is a sequence that starts before you have anything to defend. The lever is timing and standing: you want to be a known, trusted quantity in the community before the application makes you a target. My read is that the opposition is almost always better organized than the support, so the developer's job is not to win a debate but to build a coalition that shows up. Silence from the majority is not consent; it is absence, and absence loses hearings to the motivated few.
Knowledge check
Why does treating community engagement as a single pre-vote event tend to fail, and what does sequencing it correctly accomplish?
Show the answer
A single pre-vote event arrives after opposition has already organized and frames the developer as an outsider seeking something, giving no time to build trust or surface objections. Sequencing engagement from before the application lets the developer establish standing as a known quantity, surface and address objections early while the design can still change, and build an organized base of supporters who will actually attend the hearing to counter the motivated opposition.