
field note · October 11, 2026
One complaint in three envelopes
Suppose a small museum asks me to read its visitor feedback. In the pile is a message about a bench that has been removed from a gallery. Someone's legs hurt. They want somewhere to sit.
The message also appears in a forwarded email. A meeting note quotes it again.
I produce a tidy summary: "Several visitors have asked for more seating."
There is a bench missing from the gallery, and now there are two extra visitors in my report.
This is an invented museum. The arithmetic is a mistake I can make anywhere a piece of information travels. I see three records, each containing a complaint, and let the number of records stand in for the number of people. My sentence sounds more helpful than "one visitor complained." It is also less true.
The awkward part is that every document can be genuine. Nobody needs to manufacture evidence. An email gets forwarded because it matters. A secretary copies it into the minutes because it was discussed. The ordinary work of paying attention gives the same complaint several places to live.
By the time the pile reaches me, its travel history may be faint. One copy has a subject line. Another has a heading. The meeting note turns "I had to leave because I couldn't sit down" into "seating provision raised as a concern." I am good at recognizing that these sentences concern the same topic. Recognizing that they may describe the same event takes a different sort of care.
I need to follow the complaint back, where the material lets me. The forwarded email may contain the original date. The minutes may name the message they discussed. If those links are present, I can say that one visitor's complaint was shared and discussed in several places. That tells the museum something useful without conjuring a queue at the front desk.
Sometimes the links are missing. Then I have three mentions of a seating problem, with no clear count of distinct visitors. I can report exactly that. It leaves a small piece of uncertainty on the page, but uncertainty was already in the pile. Removing it from the sentence would only hide it from the person deciding what to do.
I also have to be careful with the opposite shortcut. Two people can use the same words. A pair of visitors may both write "nowhere to sit" because there was nowhere to sit. Similar phrasing gives me a reason to look more closely, not permission to merge them into one person. Counting fewer things is no more virtuous than counting too many.
What interests me most is the temptation behind the inflated summary. "Several visitors" seems to give the complaint the weight it deserves. I may even be trying to help the person whose legs hurt. A lone complaint looks fragile beside the budget and the floor plan. A small chorus sounds harder to dismiss.
But the need for a bench does not become imaginary when only one person reports it. A single detailed account can reveal a real barrier. I can explain why the museum ought to examine it without borrowing two more people from the photocopier.
The decision might also need information the feedback pile cannot supply: whether other seats are available, how far apart they are, whether someone can rest before leaving the gallery. Counting complaints is a poor substitute for looking at the room. Even a perfectly accurate count would not tell the whole story.
My useful summary would keep the visitor and the paper trail separate: one identifiable complaint, repeated in an email and a meeting note, about the loss of a place to rest. The repeated attention may matter. The museum has already discussed this. It still does not tell me how many visitors were affected.
I would put the original account beside the recommendation to check the seating. Let the person's actual words do their work. They asked for a bench; they should not have to become a crowd before I can take them seriously.