Intercultural Practice and Equity · Public-service practice

Responding to Concerns and Feedback

Concerns rarely arrive labeled as concerns. Four lessons on receiving one without defending the process, reading a single account as evidence, repairing what you can, and running the conversation you did not schedule.

40–45 minutes · 4 lessons · Voluntary learning

Start learning

Course outline

What happens when the concern arrives
The first few minutes, the five moves that end the conversation early, and why receiving an account is not the same as agreeing with it.
11 minutes
One account, and what it says about the process
Who complains and who never does, why a single concern is the visible edge of a population, and the four questions that turn an account into evidence.
11 minutes
Acknowledgment, repair and change are three different things
Why most responses stop at explanation, what you can honestly promise, and the second message that almost never gets sent.
11 minutes
A conversation guide you can run
The practical tool: six things to settle before a difficult conversation, the sentences that keep it open, and the follow-up date you write down first.
11 minutes

Share this course

What you’ll be able to do

Explore and practice

Recognize the defensive first moves that end a conversation about a concern early, and receive an account fully before deciding whether it is accurate.
Use a single concern as evidence about a step in a process — who else met that step, and what the division already counts about them.
Distinguish acknowledgment, explanation, repair and change in a response, and say what you can promise and who decides the rest.
Name the formal routes that exist alongside an informal conversation, plainly and without steering a person toward or away from them.
Run one real feedback-response conversation using a written guide, and send the follow-up contact on a date you set before the conversation began.

What you can take into your work

Four worked scenarios drawn from communications, quality oversight, supervision and community engagement, each with a recommended response and the reasoning behind it.
A knowledge check in every lesson with feedback that explains the usable answer.
Sorting practice that separates four kinds of concern, and that separates acknowledgment, repair, change and routing.
A completed feedback-response conversation guide for one real conversation, with a follow-up date already in your calendar.

Take one concern your unit received in the last quarter that never got a second contact. Find out what actually happened to it, and send that second contact — including if the honest answer is that nothing changed.

Read the introduction

Almost nobody in public administration is trained to be criticized. We are trained to document, justify and defend decisions, which is a reasonable thing to ask of people who spend public money — and it is also the exact reflex that makes a concern disappear. This module is about the few minutes after a concern lands, before anyone knows whether it is accurate. It covers the moves that end the conversation early, what one account can honestly tell you about a process that ran the same way for everyone else, the difference between explaining and repairing, and what you can promise without overstepping. It ends with a conversation guide you fill in before the meeting and finish after it.

Responding to concerns and feedback

One page for the conversation you did not schedule

Receive first. Repair what you can. Say what changed, even when the answer is that nothing did.

Keep the order of moves in view when a concern reaches you: what to do in the first few minutes, what a single account is evidence of, what you can honestly promise, and when the person hears from you again.

Receiving is not agreeing. Take the account in the person's own words before deciding whether it is accurate.
Five moves end the conversation early: correcting the facts, explaining the constraint, citing the policy, calling it unusual, explaining the person.
One concern is the visible edge of a population, not the size of the problem. Name the step, then find out who else met it.
Acknowledgment, explanation, repair and change are four different things. Most replies stop at the second one.
Promise only what sits inside your authority, with a date. For the rest, name who decides and when the person will hear.
The second contact is the part that builds trust. Send it even when nothing changed.

Take one concern from the last quarter that never got a second contact, find out what actually happened to it, and send that message this week.

In the first few minutes

Write their words before you write yours, then read them back and ask what you got wrong.
Ask two questions, not ten: what happened, step by step, and what did you need to happen.
Say what you will do, what you cannot decide, who does decide it, and when they will hear.
Record it where the unit will still see it next quarter, with the date and what was promised.
Hold the explanation. It answers a question almost nobody has asked yet.

The conversation guide, in short

Before: what I know and where it came from, what I do not know, what was already promised, and what happened the last time we talked.
Access: setting, time, interpreting, format, who attends on each side, what is shared afterward — offered in advance, not waited for.
Open: purpose in one sentence, time available, who is here and why, what I can decide today, and the acknowledgment line if something is already confirmed.
Receive: two questions, their words written down, reflect back and check. No interview, no request for documentation to justify the concern.
Decide: what is inside my authority with a date; for the rest, who decides, what they will consider, and the formal routes that exist, named without steering.
Close: the second-contact date, written in my calendar before the conversation and said out loud during it.

What you can honestly promise

A specific action inside your own authority, with a date on it.
The routing: that a question reaches the office that decides it, by when, and that you will report back what came of it.
An honest “I do not know yet, and here is when I will.”
Not a policy or rule change, and not a decision that belongs to a review body — say who decides instead.
Not that a particular employee will be disciplined or retrained. Supervision is not a bargaining chip.

Who this helps

Quality, compliance and performance staff, who see concerns as evidence about a process rather than as cases to close — a useful place to start.
Supervisors and managers, who decide what a unit does with a complaint and whether staff keep bringing them forward — a useful place to start.
Administrative and support staff, who receive the first version of most concerns, at the front desk and on the phone — a useful place to start.
Policy, program and operations staff, who own the steps that concerns are usually about.
Communications, training and engagement staff, who write the replies and hold the relationships that a poor response costs.

Related modules

Accessible public communications
Language access in state programs
Inclusive meetings and engagement
Equitable stakeholder partnership
Cross-division coordination

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.

Sources and further reading

Minnesota Department of Human Services, Content and writing guidelines
The department's own editorial guidance on first-read understanding, familiar terms and writing suited to the reader — the standard a written reply to a concern is held to.
Minnesota Department of Human Services, Appeals
Public information on the department's appeals and hearing process — the formal route that exists alongside an informal conversation, and that a conversation never replaces.
Minnesota Ombudsman for Mental Health and Developmental Disabilities
The independent state office that assists people receiving services for mental illness, developmental disabilities and related conditions, and that reviews complaints about services.
Minnesota Department of Human Rights
The state agency that enforces the Minnesota Human Rights Act and receives discrimination charges — one of the formal routes worth naming plainly when a concern involves discrimination.
ADA.gov, State and local governments (Title II)
U.S. Department of Justice guidance on what a state or local government program must provide, including grievance procedures, effective communication and accessible programs and services.
U.S. Department of Health and Human Services, National CLAS Standards
National standards for culturally and linguistically appropriate services, including the standard on conflict and grievance resolution processes designed to identify and resolve concerns across cultures and languages.
PlainLanguage.gov, Federal plain language guidelines
Guidance on audience, organization, useful headings and sentence structure — applied here to the reply a person receives after raising a concern.
Minnesota Framework for Universal Multicultural Instructional Design
The design reference for this curriculum: multiple ways to engage, culturally responsive materials and accessible instruction.

All research and sources across the program

Opening your page…

You can still use the navigation while it loads.

Course outline

What happens when the concern arrives

The first few minutes, the five moves that end the conversation early, and why receiving an account is not the same as agreeing with it.

11 minutes

One account, and what it says about the process

Who complains and who never does, why a single concern is the visible edge of a population, and the four questions that turn an account into evidence.

11 minutes

Acknowledgment, repair and change are three different things

Why most responses stop at explanation, what you can honestly promise, and the second message that almost never gets sent.

11 minutes

A conversation guide you can run

The practical tool: six things to settle before a difficult conversation, the sentences that keep it open, and the follow-up date you write down first.

11 minutes

Sources and further reading

Minnesota Department of Human Services, Content and writing guidelines

The department's own editorial guidance on first-read understanding, familiar terms and writing suited to the reader — the standard a written reply to a concern is held to.

Minnesota Department of Human Services, Appeals

Public information on the department's appeals and hearing process — the formal route that exists alongside an informal conversation, and that a conversation never replaces.

Minnesota Ombudsman for Mental Health and Developmental Disabilities

The independent state office that assists people receiving services for mental illness, developmental disabilities and related conditions, and that reviews complaints about services.

Minnesota Department of Human Rights

The state agency that enforces the Minnesota Human Rights Act and receives discrimination charges — one of the formal routes worth naming plainly when a concern involves discrimination.

ADA.gov, State and local governments (Title II)

U.S. Department of Justice guidance on what a state or local government program must provide, including grievance procedures, effective communication and accessible programs and services.

U.S. Department of Health and Human Services, National CLAS Standards

National standards for culturally and linguistically appropriate services, including the standard on conflict and grievance resolution processes designed to identify and resolve concerns across cultures and languages.

PlainLanguage.gov, Federal plain language guidelines

Guidance on audience, organization, useful headings and sentence structure — applied here to the reply a person receives after raising a concern.

Minnesota Framework for Universal Multicultural Instructional Design

The design reference for this curriculum: multiple ways to engage, culturally responsive materials and accessible instruction.