11 minutes
Mistrust is a record, not a mood Communities that are hard to convene are usually not being difficult. They are being accurate about what happened last time. That is information a division can act on.
What you’ll be able to do Explain community mistrust as an accumulated record of institutional behavior, and identify the specific behaviors that build or spend trust in a DSD engagement, contract or communication. Compare the responses to this question and explain your choice: What is the most accurate reading, and what follows? Document a next step for Mistrust is a record, not a mood: Find the last time your area asked a community group for input. Write the report-back that never went out, including the parts where nothing changed and why, and name the date it will be sent and the person who will send it. What mistrust is made of Mistrust is usually treated as a feeling to be managed: a communications problem, a relationship that needs warming up, a group that had a bad experience somewhere. That reading is comfortable and it is almost always wrong.
Mistrust is a record. It is what an institution actually did, remembered by the people who had to live with the result. A community consulted three times about one redesign and never told what changed is not being negative; it is being accurate. A family told a service would continue and then sent a closure notice is not misunderstanding the division's intentions; it is reporting the division's behavior.
You inherit that record. You did not write it, you cannot resign from it, and every new contact your area makes is read against it. That is not fair to you as a person, and it is the condition the work happens in. The only thing that moves a record is more record: behavior that can be checked, repeated over time, by the institution rather than by one sympathetic staff member who might be reassigned next spring.
The stages named below describe how a division reads a room. They are a way of noticing an institutional habit, and never a label, a score or a record about any individual.
Five ways a division reads the same room Denial Polarization Minimization Acceptance Adaptation
“We have good relationships in that community.” The room looks calm because the people who stopped coming are not in it. Absence is read as agreement, and nobody asks who used to attend.
“They arrive hostile. Whatever we do is wrong.” The division's discomfort becomes the subject of the meeting, and the content of what people said is lost. The mirror image is equally unhelpful: treating the division as uniquely bad explains nothing and fixes nothing.
“Every group says it was not consulted. That is just how government is.” A specific, documented history gets flattened into a general complaint, which is a way of making it nobody's to answer.
“What happened here before? What did we say we would do, and what did we actually do?” The record becomes information the division can work with. This is the first point at which anything changes.
The division changes how it consults, because it can now see the engagement from the other side well enough to design differently: reporting back before asking again, paying for expertise, moving its own dates, and building the review point into the plan rather than promising one.
Builds trust, spends trust, or neither on its own Sending a short note to everyone who commented, naming what changed because of their comments and what did not.
Choose a category Builds trust Spends trust Neither on its own Holding a listening session, thanking people warmly, and publishing nothing afterward.
Choose a category Builds trust Spends trust Neither on its own Paying community advisors at a professional rate for their time and expertise.
Choose a category Builds trust Spends trust Neither on its own Asking a culturally specific organization to review a plan over a holiday week with four days' notice.
Choose a category Builds trust Spends trust Neither on its own Saying plainly that the answer is no, with the reason and the name of whoever decided.
Choose a category Builds trust Spends trust Neither on its own Sending a senior leader to open a meeting and leave before the discussion starts.
Choose a category Builds trust Spends trust Neither on its own Adding one community member to an advisory roster.
Choose a category Builds trust Spends trust Neither on its own Translating a notice into several languages.
Choose a category Builds trust Spends trust Neither on its own Keeping a date the division set, including the date it promised to report back.
Choose a category Builds trust Spends trust Neither on its own Check matches Reset Things people say, and what they usually mean “We have been asked this before.”
Usually literal. Before you defend the new request, find the old one and what was sent back. If nothing was, that is the first thing to fix.
“Nobody has ever raised this with us.”
Weak evidence of anything. People who depend on a service have a realistic reason not to risk the relationship, and people who gave up on being heard stop raising things first.
Consultation fatigue
The cost of repeated asking without reporting back. It is a cost the division imposes on volunteers and small organizations, and it shows up as declining invitations rather than as complaints.
Report back
Telling people what happened to what they said, including the parts where nothing changed and why. It is cheap, it is rarely done, and it is the single behavior communities name most often.
Compensation
Paying people for expertise, time, travel and care arrangements. Unpaid advice from people with less money than the institution asking for it is not partnership.
Report back before you ask again What you can change You control whether your area answers the last request before it makes the next one.
What to watch for Do not open a new engagement with a community that is still waiting to hear what happened to the last one. The new invitation is read as evidence, and it is.
Your next step Before your area's next request for community input, find the previous one and send the report-back that never went out, even if it is late, and even if the honest answer is that nothing changed.
We are not hard to work with. We are tired of being asked. Tell us what you did with the last answer and we will give you another one.
Composite community partner perspective, illustrative A private reflection, for you alone. How could the people most affected shape this work earlier, as paid co-designers rather than as reviewers at the end? Whose expertise is missing from the way my area decides who to ask? Nothing you write here is collected, seen or kept.
Carry this forward Mistrust is usually accurate about something. It is memory of what an institution did, carried by the people who had to live with the result.
You inherit the record. You did not write it, you cannot resign from it, and every new contact your area makes is read against it.
Trust moves only on behavior that can be checked: reporting back before asking again, paying for expertise, keeping a date the division set, and saying plainly when the answer is no.
A listening session that absorbs anger and changes nothing spends trust. So does an invitation to educate staff for free, and so does asking staff to represent the communities they belong to as unpaid work.
Access work such as translation or a new advisory seat is necessary and, on its own, neutral. What people watch is whether anything they said ever changed a decision.
A scenario about a culturally specific organization setting conditions before it will host a listening session, sorting practice on what builds and spends trust, and a knowledge check on consultation debt.
Find the last time your area asked a community group for input. Write the report-back that never went out, including the parts where nothing changed and why, and name the date it will be sent and the person who will send it.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Carry this into practice Examine how positional power shapes disagreement and practice responses that support accountability and repair.
Return to the experience: What did you notice or try, whose perspective informed it, and what would you keep or adjust?
Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
