Give the person a way to answer back
A system can understand a complaint and still give its author no power to change the outcome.
Public reading preview. Factual, interpretive, editorial and rights reviews remain pending.
Being described accurately is a modest ambition for a person. We also want to be able to say that the description misses something. A customer, a collaborator, or a member of a community may accept the facts in a record while disagreeing with the conclusion drawn from them. A leader has to decide whether that disagreement can reach the work.
Imagine a hypothetical neighborhood arts festival using AI to help sort proposals. One application describes a gathering where older residents will teach children songs while repairing objects from family homes. The system places it under a category for household activities. The organizers are choosing performances and exhibitions. The proposal is set aside.
The applicant receives a courteous explanation. She replies that the songs, stories, and repairs are one artistic practice in her community. The form gives her no way to question the category. Her message produces another explanation of the same eligibility rules. Everyone is communicating. Her meaning has nowhere consequential to go.
The festival may still decide against the proposal. Space is limited, and a right to be heard cannot guarantee selection. But the organizers should be able to reconsider what kind of activity they are evaluating. Otherwise they are asking a person to participate only on condition that she accept the institution's account of what she has brought.
In the Pentecost account in Acts 2:5–11, people hear the proclamation in their own languages. I find a demanding image there: understanding can cross difference without requiring every voice to become the same. The passage concerns a religious event; an appeal process is my practical application, not its subject.
An organization can take that image seriously by examining the work of translation it imposes on other people. A person may have to learn your categories before you will recognize a concern. AI can make that burden harder to see because the response is fluent and apparently sympathetic. The institution seems to have listened long before it has reconsidered anything.
The alternative requires a place where the person's account can alter the institution's account. That may mean retaining the original wording beside the summary, asking a clarifying question, or letting someone with relevant knowledge change a category. The important thing is that the reply can affect what happens next.
There is an opportunity here as well as a risk. Translation and summarization can help a small festival hear proposals its volunteers would otherwise struggle to understand. An assistant could show several plausible interpretations instead of silently choosing one. The leader's task is to arrange that help so a person can still correct the interpretation that matters.
The practice
Choose one ordinary decision in which your team classifies someone else's request: a creative submission, a service exception, or a community suggestion. Work with a public or invented example rather than copying somebody's private circumstances into an exercise. Allow twenty minutes to draw its route through your team.
Write the person's original account at the top of a page. Under it, record the summary or category that drives the decision. Draw an arrow to the action that follows. Now add the route a person would take to say that the interpretation is wrong. Mark the point where that correction can actually change the action.
Beside that point, name someone who can reconsider the interpretation. State what they need to see and how the person will learn what happened. An inbox alone is insufficient. Someone needs enough time and authority to do something other than restate the original answer.
Ask a colleague who did not design the route to try it with the invented case. In the festival example, could they explain that the proposed workshop is also a performance? Could that explanation reach a person able to reconsider the category? Keep the exercise's output: a one-page reply route with an owner and a visible reconsideration step.
Keep the route proportionate. A small event cannot offer an unlimited hearing on every preference. Set a clear scope and response expectation. Distinguish a factual or interpretive challenge from a request that simply repeats a wish. Fair treatment includes being honest about what the team can revisit.
At the next review, look for a correction that changed the team's understanding, even if the final decision remained the same. Also look for people abandoning the route because it is too obscure. The aim is an institution that can learn from the person its systems have made easier to process.
Adapted from Nikos Acuña’s supplied manuscript. Prepared with AI assistance. Preview v1.0.
Final editorial approval pending. Sources are linked in the margin.