Closing Our Own Loops: Are We Learning Anything?
Another survey. Another public meeting. Another engagement report.
But does anyone know what we learned from the last ten?
We talk a lot about closing the feedback loop with participants. And we should. People deserve to know what happened with their input and how it informed decisions.
But what about closing the loop within our own organizations?
Are we learning from how we engage? Are we building on what communities have already told us? Or are we wrapping up one project and moving on to the next?
There are two types of audits that can help us answer those questions.
Are We Learning How to Engage Better?
When people talk about engagement audits, they're usually referring to an evaluation of an organization's engagement practices and processes.
How are engagement efforts planned? What methods are being used? Who participates, and who doesn't? Are departments coordinating their efforts? How is community input incorporated into decisions?
These evaluations can identify methodological weaknesses, inconsistent practices, and opportunities for improvement.
The City of Raleigh, for example, partnered with Public Participation Partners (P3) to evaluate its engagement practices and identify opportunities for improvement. The project earned the 2021 APA North Carolina Marvin Collins Public Engagement Award and produced a Public Participation Playbook that gives City staff a common framework for planning engagement, selecting appropriate participation methods, and clarifying the public's role in decision-making.
Rather than addressing problems one project at a time, organizations can learn from their collective experience and improve how they engage moving forward.
In short: How are we getting the data, and how can we do it better?
Are We Learning From What We've Heard?
Now consider everything a local government might have collected from residents over the past five years.
Surveys. Public meeting comments. Focus groups. Neighborhood plans. Comprehensive plans. Online engagement platforms. Consultant reports.
That's a lot of information, often scattered across departments, project folders, and platforms.
So, what do we actually know?
Not what we think we know. Not what someone remembers hearing at a meeting three years ago. What information do we have, what does it tell us, and what can we reasonably conclude from it?
That's where a different kind of audit comes in. Let's call it an input audit.
Rather than examining engagement practices, an input audit examines the information those efforts have produced. It identifies what has been collected, what we've learned, and where gaps remain.
And it's not simply an inventory. The quality of that information matters.
A finding from a representative survey and a concern raised during a public meeting can both be valuable, but they don't necessarily tell us the same thing. Understanding how information was collected helps determine what conclusions it can reasonably support.
In short: What data do we have, and what can we learn from it?
Learning Shouldn't End When the Project Does
Organizations tend to plan and evaluate engagement one project at a time. But residents don't necessarily experience it that way.
They remember answering questions about traffic during one study, then being asked similar questions during another. They remember sharing concerns at a public meeting, only to see those same issues raised again years later.
And they wonder whether anyone was listening.
We often talk about engagement fatigue as though residents are simply tired of participating. But perhaps some of that fatigue comes from being asked to repeat themselves without seeing evidence that previous input mattered.
An input audit can help organizations recognize recurring concerns, build on existing knowledge, and identify where new engagement would actually add value.
It also creates an opportunity to close the loop—not just by reporting what was heard during one project, but by demonstrating that community input continues to inform decisions beyond the life of that project.
Of course, communities change, priorities evolve, and previous engagement may have missed important perspectives. Existing input isn't always sufficient.
But shouldn't we know what we already have before deciding what else we need?
Closing Our Own Loops
Community engagement shouldn't just produce reports. It should produce knowledge.
Knowledge about how to engage more effectively. And knowledge about the communities we're trying to serve.
A process audit helps us improve how we collect community input. An input audit helps us understand and make better use of what we've already collected.
Both are important. Both can lead to better engagement and stronger decisions.
Closing the loop shouldn't only mean reporting back to the community. It should also mean taking what we've learned—about our methods and our communities—and using it to inform what happens next.
Maybe it's time we started closing our own loops, too.
Wondering what your organization could learn from its own engagement efforts? NineteenEleven Consulting helps organizations take a closer look at their engagement practices, existing data, and opportunities to make better-informed decisions. Let's talk.




Comments