Order of Operations

Why community engagement fails before the first session runs

Most community engagement failures don’t happen in the sessions. They happen months earlier — in the sequence of decisions made while designing the engagement.

Consider a scenario most practitioners will recognise.

Eighteen months of community engagement. Six public sessions, strong attendance, bilingual materials, an online survey that returned over 400 responses. A polished summary report. The project team is proud — and by every visible measure, the engagement was a success.

Then the final decision comes down, and the community is furious. Not because they weren’t consulted. Because the things they turned up and trusted the team with — the things they said mattered most — aren’t in the outcome. A petition follows. A council complaint. A local media story about tick-box engagement. The project team replays the process, looking for where it went wrong. They look in the wrong place.

In community engagement, we spend a great deal of time debating methods. Which tools are most inclusive? How do we reach hard-to-reach groups? How many sessions is enough? These are important questions — but they are downstream questions. The answers only matter if the foundational decisions that precede them have been made correctly, and in the right order.

Sequence in community engagement is not just logistics. It is logic. Each step creates a genuine input that the next step depends on. Reverse two steps and you don’t create an inconvenience — you introduce an error that compounds through everything downstream. The process can look healthy on the surface while being structurally compromised underneath.

What follows is the sequence that works — and an honest account of what goes wrong when each step is skipped, rushed, or done out of order. It is not a list of things engagement practitioners don’t know. It is a list of things the system makes it easy to get wrong, even with experience and good intentions.

Engagement that isn’t tethered to real decisions isn’t community engagement. It’s consultation theatre.

The ten-step sequence

STEP 1 Map the decision space — before anything else

Why it matters: Before designing your engagement, understand what decisions are actually being made, who holds authority over them, and when they will be made. This is the anchor point for everything that follows. Engagement not tethered to real decisions and real timelines cannot meaningfully influence outcomes — regardless of how well it is run.

When skipped or rushed: Engagement is designed around internal project schedules rather than decision milestones. By the time communities are consulted, the viable decision space has quietly narrowed. Communities sense this even when they cannot articulate it precisely, and trust erodes in ways that are very difficult to rebuild.

→ Go deeper: Before You Design Anything: What Is Actually on the Table?

STEP 2 Establish scope and constraints honestly

Why it matters: What is genuinely open for community influence? What is fixed by legislation, prior commitment, or technical constraint? This is an ethical prerequisite. You cannot set honest engagement objectives without knowing what communities can actually influence. And if you don’t establish this clearly, you will — even with good intentions — overclaim.

When skipped or rushed: Constraints that were not disclosed upfront emerge during or after the engagement. Communities feel misled, not because anyone intended to deceive them, but because the engagement implied more openness than existed. The damage to trust is disproportionate to the constraint itself. A small undisclosed limitation can unravel an otherwise well-run process.

STEP 3 Define engagement objectives — not questions, objectives

Why it matters: Engagement objectives answer a different question to engagement activities. They ask: what do we need to understand from this community, and what will we do with that understanding? A well-constructed objective tells you what good data looks like, which groups you need to hear from, and how you will know whether the engagement succeeded. Without this, everything downstream is built on assumption.

When skipped or rushed: Methods are chosen by habit rather than purpose. Teams reach for familiar tools without asking whether those tools will produce the data the objectives actually require. The engagement runs, content is collected, and it is often only during analysis that the team realises the information gathered doesn’t quite answer the question that matters.

STEP 4 Choose the level of engagement — and honour it as a commitment

Why it matters: Consult, Involve, Collaborate. These are not points on a scale from lesser to better practice. They are different promises to your community about the degree of influence they will have. The right level is the one that is honest given your objectives, constraints, and decision-making structure. Choosing the level before objectives are clear — or choosing it to signal openness rather than reflect reality — creates a commitment you may not be able to keep.

When skipped or rushed: Teams choose Involve or Collaborate because it feels more respectful, without the organisational mandate to honour it. When communities experience the gap between what was promised and what was delivered, no amount of post-process explanation recovers the relationship. Overclaiming engagement level is one of the most common — and most damaging — sequencing errors in local government practice.

→ Go deeper: A Promise, Not a Preference — Choosing your level of engagement and honouring it

STEP 5 Map your stakeholders — before designing any content

Why it matters: Stakeholder mapping does three things that are prerequisites for almost everything that follows: it identifies who needs to be heard, surfaces the power dynamics that will shape participation, and reveals the barriers that will determine what methods can actually reach each group. It must happen before you write a single question or book a venue. Done after content design, mapping becomes a check on a process already partially built — and will tend to confirm rather than challenge choices already made.

When skipped or rushed: Engagement design defaults to who is easiest to reach. Questions are written for people with existing project awareness. Sessions are scheduled at times that suit those already engaged. The groups with the highest stake and the least institutional voice are systematically under-reached — not through deliberate exclusion, but through a process designed before anyone asked who actually needs to be there.

Stakeholder mapping done after content design tends to confirm the choices already made, not challenge them.

→ Go deeper: Stakeholder Mapping: Who Needs to Be in the Room?

STEP 6 Design questions and content by stakeholder group

Why it matters: Once you know who your stakeholders are and what barriers they face, you can design your engagement content. What a long-term resident needs to be asked is different from what a local business owner needs to be asked, even on the same project. Content tailored to each group produces richer, more usable data. A single instrument designed for a general audience produces data that represents whoever was most motivated to respond.

When skipped or rushed: One-size-fits-all engagement tools are used because they are efficient. The result is data that reflects the groups most comfortable with the format — rarely the full spectrum of affected stakeholders. The analysis that follows describes a community; it just may not be the one that most needs to be heard.

STEP 7 Select tools and methods through the lens of barriers

Why it matters: For each stakeholder group, tool selection should start with one question: what barriers does this group face, and what method overcomes them? In practice, most tool selection is driven by familiarity, budget, and team capacity — which produces the same methods project after project, regardless of whether those methods work for the communities being engaged.

When skipped or rushed: The same groups are systematically under-reached across multiple projects. Teams notice the pattern in participation data but attribute it to community disinterest rather than process design. The barriers are consistent. The methods just haven’t been chosen to address them.

→ Go deeper: Stop Choosing Engagement Methods By Habit — The barrier-first approach

STEP 8 Build your evaluation framework before implementation begins

Why it matters: Define what success looks like before the first session runs. Process measures: did we reach who we intended? Outcome measures: did the input shape the decision? Evaluation designed after the fact is not evaluation. The standards against which you measure were set retrospectively to reflect what the process achieved, not what it was designed to achieve.

When skipped or rushed: Post-process evaluations measure what is easy to count: sessions held, participants, responses received. These metrics are visible and verifiable. They say very little about whether the engagement was meaningful, reached the right people, or influenced anything. Projects are reported as successful on metrics that were never the point.

→ Go deeper: Why Your Engagement Evaluation Is Probably Post-Rationalisation

STEP 9 Track the connection between input and decisions in real time

Why it matters: As engagement runs, the thread connecting what communities say to what decisions are made must be maintained actively, not reconstructed later. Log feedback themes as they emerge. Note how they are being considered. Without this discipline, closing the feedback loop at the end becomes an exercise in approximation — and communities who participated with specific concerns cannot see where those concerns landed.

When skipped or rushed: Teams reach the end of an engagement process knowing broadly what they heard but unable to demonstrate specifically how particular input influenced particular decisions. The feedback report is general. Experienced community members know the difference between a genuine account of how their input was used and a summary that could have been written before the engagement ran.

STEP 10 Close the feedback loop — always, specifically, and on time

Why it matters: After decisions are made, go back to the communities who participated: this is what we heard, this is how we considered it, this is what we decided, and why. The feedback loop is not a courtesy. It is the delivery on the promise made when you invited people to participate. It is also the foundation on which every future engagement your organisation runs will either build or crumble.

When skipped or rushed: The organisation moves to implementation without communicating back. Community members who invested time and trust have no way of knowing whether it mattered. Many will assume it didn’t. That assumption will shape their response to the next invitation — and the one after that. The cumulative effect across an organisation’s engagement history is a community that is progressively harder to reach, not because of apathy, but because of accumulated experience.

→ Go deeper: The Step That Determines Whether Communities Trust You Next Time — Closing the feedback loop

→ Go deeper: The Slow Erosion — What happens when feedback loops are never closed

Sequence is strategy

None of the failures described above require bad intentions, inadequate resources, or inexperienced teams. They are structural. They happen when process design is treated as logistics rather than as a discipline with its own internal logic and dependencies.

The practitioners who consistently run high-quality engagement have internalised this sequence. They do not treat it as a checklist to move through. They understand why each step must precede the next — and they design with that understanding from the moment they are briefed, not from the moment the first session is scheduled.

This is also why the most effective engagement teams are increasingly moving toward structured engagement workspaces — environments designed to guide practitioners through the sequence deliberately, rather than relying on individual memory and experience under deadline pressure. When the sequence is built into the way you work, it stops being something you have to remember to do and becomes something you simply do.

That thinking is at the heart of CE Canvas.

Sequence in community engagement is not just logistics. It is logic.

In this series: Order of Operations

1. Before You Design Anything: What Is Actually on the Table? — Mapping the decision space

2. A Promise, Not a Preference — Choosing your level of engagement and honouring it

3. Stakeholder Mapping: Who Needs to Be in the Room? — The foundation of inclusive engagement

4. Stop Choosing Engagement Methods By Habit — The barrier-first approach

5. Why Your Engagement Evaluation Is Probably Post-Rationalisation — Building evaluation in, not on

6. The Step That Determines Whether Communities Trust You Next Time — Closing the feedback loop

7. Engagement Theatre: What It Looks Like From the Inside — Warning signs and how to course-correct

8. The Slow Erosion — What happens when feedback loops are never closed

Download Companion Resource