One-liner: “Thanks for the feedback, let’s keep it on the sheet”, ending live discussion under the guise of order.
Also known as / related terms: Parking-lotting (weaponized), performative acknowledgment, procedural closure, “noted” deflection.
What it is
“Noted,” and then never mentioned again.
The legitimate facilitation technique of a “parking lot”, setting aside tangential items on a visible list so a meeting stays on track, is repurposed here as a way to end substantive discussion while appearing procedurally fair. The concern is thanked, logged, and visibly “captured,” which looks like good process. But the acknowledgment is the entire response: there is no commitment to revisit it, no owner, and no date.
Organizational theorist Nils Brunsson’s The Organization of Hypocrisy (1989) describes how organizations routinely decouple talk, decisions, and action, with talk itself allowed to serve as the visible output, satisfying the demand to be heard without any obligation for decisions or action to follow. The interpersonal version runs on something smaller and more immediate: gratitude functions as a conversational close. Objecting to being thanked reads as graceless in the moment, so the redirect completes unopposed, not because anyone agreed with it, but because there’s no polite way to say “being thanked isn’t what I asked for.”
What it looks like (workplace)
A team member raises a real concern about how credit was allocated on a project. The facilitator says, warmly: “Love that you flagged this, let’s get it in the parking lot so we can stay on agenda.” The parking lot currently holds forty-one items. None has ever been reopened in its two-year history.
How it actually unfolds when confronted
- Confrontation, live and witnessed. A concern is raised in the meeting itself, where the audience in the room is the concern’s actual leverage.
- The gracious capture. “Thanks so much for raising that, let’s add it to the sheet and keep moving” completes unopposed, because objecting to being thanked reads as graceless. Brunsson’s decoupling is doing exactly what it’s built to do here: the talk (being thanked, being logged) satisfies the demand, and nothing about decisions or action follows from it.
- The follow-up trap. Circling back happens later, one-on-one, without the room that gave the concern its weight. “It’s on the list,” or silence, Stonewalling wearing a spreadsheet. Repeated asking converts the confronter into “the person who keeps going on about the sheet,” the durable tag Labeling describes.
- Outcome. The item dies quietly in the tracker. The tracker itself becomes proof of good process, “concerns were heard and logged”, the same logic Manufacturing the Record runs on: a document standing in for the thing it was supposed to produce.
One-off or pattern?
One instance of this proves nothing. A bad week, real time pressure, or a manager who genuinely lacks context produces the same sentence. Three things separate the tactic from the accident:
- Repetition. The gracious “let’s add it to the sheet” reappears across unrelated concerns, each one thanked, logged, and never actually revisited.
- Direction. Chasing the tracked item down later lands on whoever raised it, earning a reputation for not letting things go, never on the facilitator.
- Asymmetry. Following up on the item costs the raiser repeated effort and a label; logging it with a warm thank-you costs the facilitator nothing.
Seen it once, write it down and wait. Three instances, on three unrelated subjects, over weeks, is a pattern worth documenting.
Why they do it
Visible, procedural acknowledgment satisfies the social expectation of having “heard” the concern. At the same time it ensures the concern never gets the resourced, scheduled attention that would make it actionable, exactly the talk-decisions-action decoupling Brunsson documented, deployed here for one item instead of an entire institution.
How to protect yourself
Being thanked is not the same as being answered.
- Ask for the missing accountability elements on the spot: “Who owns this item, and when will we revisit it?”
- If a tracking sheet is invoked, ask to see it and confirm the item is genuinely logged, not just verbally waved at.
- Follow up in writing after a set interval: “Circling back on the item from [date], where does this stand?” This is what keeps stage 3’s follow-up trap from closing quietly.
- Recognize that being thanked for feedback is not the same as the feedback being addressed; don’t let politeness read as resolution.
Cross-links: Stonewalling (what the tracking sheet becomes once the meeting ends); Premature Finality Framing and Displacement to “Management”/Authority (the sibling deferrals, by declaration and by escalation); Labeling (the “keeps going on about it” tag stage 3 installs); Manufacturing the Record (the sheet’s second life as proof concerns were heard).
Sources:
Primary research and original sources
- Nils Brunsson, The Organization of Hypocrisy: Talk, Decisions and Actions in Organizations (John Wiley & Sons, 1989), Internet Archive listing, the organizational-theory account of how talk, decisions, and action get decoupled in institutions.
Background and general explainers
- SessionLab, Parking Lot (facilitation method), legitimate use of the technique, useful baseline for spotting when it’s being misused to permanently shelve a concern.
- CHS Alliance, Ten Psychological Tactics for Avoiding Accountability, performative acknowledgment without follow-through as an accountability-avoidance pattern.
Label note: Descriptive-original coining. Builds on the legitimate facilitation technique (“parking lot”), repurposed as an avoidance tactic, and on Brunsson’s established organizational-theory concept of talk/decision/action decoupling, honestly applied here to a single-conversation scale rather than an entire institution.
- 1Concern RaisedA real concern is raised during the meeting.
- 2Noted And ParkedThanked, logged on a tracking sheet, and the meeting keeps moving.
- 3Never RevisitedNo owner and no date, so acknowledgment stands in for a response.