One-liner: “We’ll decide this in the management meeting”, invoking a vague authority to stall.
Also known as / related terms: Bureaucratic deflection, appeal to authority (fallacy, when misused), red-tape stalling, escalation-as-avoidance.
What it is
A vague higher-up, summoned to stall.
The person redirects a decision that is, in fact, within their own authority (or that needs no further approval) to an unnamed, unscheduled, or unaccountable higher body: “leadership will weigh in,” “that’s for the management meeting to decide.” This differs from a legitimate escalation, which names the specific decision-maker, the forum, and the date.
The move works because an absent authority can’t be cross-examined. You can push back on a person standing in front of you; you cannot argue with a meeting that hasn’t happened yet, a body with no fixed roster, or a decision process that exists only as a phrase. It borrows the shape of a real organizational courtesy, the honest deferral to a decision-maker who genuinely needs to weigh in, and uses that shape to end the conversation instantly and politely, without anyone having to defend the actual decision.
What it looks like (workplace)
Asked to explain a decision that disadvantaged a team member, a lead says, unhurried and pleasant: “That’s honestly above my pay grade, it’ll get picked up at the leadership sync.” “Which sync?” “The next one.” Three weeks later, no agenda item references it, no date was ever set, and no leadership sync convenes to discuss it, or, in some versions, at all.
How it actually unfolds when confronted
- Confrontation. A decision within the person’s own authority is challenged, with witnesses present.
- The invocation. “That’ll get sorted at the leadership sync” ends the conversation instantly and politely, an authority that cannot be questioned because it isn’t in the room.
- Limbo. Follow-ups meet silence or “it’s on the list,” the same holding pattern described in Stonewalling and Procedural Redirection / Surface Acknowledgment. If a decision does eventually happen, it happens in a room the confronter was never invited into, the setting Meeting After the Meeting describes directly.
- Outcome. Raising it again starts to look obsessive, and earns the durable tag of someone who “won’t let things go,” Labeling that follows the confronter into unrelated conversations. The original decision stands by default, never actually defended.
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 unnamed “leadership sync” or “management meeting” gets invoked again on decisions that were already within the person’s own authority.
- Direction. The stall lands on whoever keeps asking for a date and a name, never on the person who never had to defend the decision.
- Asymmetry. Chasing down the meeting, the date, and the attendee list costs the follower hours; inventing the meeting costs the speaker 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
Invoking an authority beyond the room ends the conversation immediately, without the person having to defend, explain, or change anything themselves. And if the “management meeting” never quite happens, or happens without the confronter present, the deflection becomes permanent in practice while looking, on paper, like a normal escalation.
How to protect yourself
A real escalation has a name, a date, and a room.
- Ask for the specifics on the spot: “Which meeting, which date, who’s attending, and can I see it on the agenda?”
- If no concrete answer is available, treat the “escalation” as a stall, not a resolution, and say so plainly.
- Follow up in writing after the stated deadline: “Following up, did this get addressed in the meeting you mentioned?”, this is what keeps stage 3’s limbo from extending indefinitely.
- Don’t let an invoked authority substitute for a decision the person in front of you is actually empowered to make.
Cross-links: Displacement of Action (the same hand-off, aimed upward instead of downward); Premature Finality Framing (the mirror move, claiming a decision already happened instead of claiming it hasn’t happened yet); Stonewalling (the silence that maintains the stall through follow-up); The Meeting After the Meeting (the room where the invoked authority actually operates); Procedural Redirection / Surface Acknowledgment (the tracked-and-forgotten variant of the same stall).
Sources:
Background and general explainers
- CTB (Community Tool Box, U. Kansas), Overview of Opposition Tactics: The Ten D’s, catalogs procedural/bureaucratic delay tactics used to stall accountability and decisions.
- Gresham Sykes and David Matza, “Techniques of Neutralization” (1957), American Sociological Review, Wikipedia overview, the origin of “appeal to higher loyalties,” a criminological concept this entry extends, honestly, to an organizational stalling tactic rather than a moral-disengagement excuse.
Label note: Descriptive-original coining, grounded in the established concept of bureaucratic deflection / stalling. The optional framing via “appeal to higher loyalties” (Sykes and Matza, 1957) is this site’s own extension of a criminological neutralization technique to a workplace deflection tactic, not a use those authors themselves made.
- 1ConfrontedAsked to explain or decide something within their own authority.
- 2Vague EscalationRedirects it to an unnamed higher body with no date, forum, or attendees.
- 3Indefinite StallThe conversation ends at once and the decision is suspended indefinitely.