A Catch-22 is a no-win situation in which the conditions for solving a problem prevent the solution. At work, people use it for circular requirements: you need A to obtain B, but you need B before you can obtain A.
“We’re in a Catch-22: security needs production data to approve the test, but we can’t access production data until security approves it.”
The phrase usually criticizes the structure of a process, not a person's effort.
Where does Catch-22 come from?
The expression comes from Joseph Heller's 1961 novel Catch-22. The title names a fictional rule operating through circular logic. The novel's broader setting and themes are more complex than the modern workplace shorthand, but the title became a common English noun for an inescapable, contradictory situation.
Merriam-Webster defines catch-22 as a problematic situation whose only solution is denied by a condition inherent in the problem. The dictionary also records a broader sense involving an illogical or mutually dependent condition.
The capitalization and hyphen vary in informal writing, but Catch-22 is the familiar title form. Do not assume every listener has read the novel; many know only the expression.
What makes something a real Catch-22?
The central mechanism is circular dependency or self-defeating eligibility:
- You need approval to gain access.
- The approver requires evidence that can be produced only with access.
- No ordinary path satisfies both requirements.
A difficult choice is not automatically a Catch-22. If two options both have disadvantages, that may be a trade-off or dilemma. If a task is simply hard, it is an obstacle. Catch-22 is most precise when the rules trap the person inside a loop.
What might you hear at work?
“Candidates need experience, but they can’t get experience without being hired. It’s a Catch-22.”
The speaker describes an entry barrier with mutually reinforcing requirements.
“We need a local bank account to set up payroll, and the bank wants proof of payroll. That feels like a Catch-22.”
Feels like appropriately hedges the comparison until the exact process is confirmed.
“This isn’t a Catch-22; we can use the sandbox data for approval.”
Someone has identified a third path that breaks the loop.
A lot to take in? It is.
But Rome wasn't built in a day. Build your American workplace English one expression and cultural reference at a time—with curated explanations and structured practice in Lyra Practice.
Start a session →“The project is caught in a Catch-22.”
This is understandable, although we’re in a Catch-22 or the process creates a Catch-22 often sounds more natural.
What can you say naturally?
To name the loop:
“We may have a Catch-22: each approval depends on the other.”
To ask for precision:
“Which two requirements make the situation circular?”
To move toward a solution:
“Could either owner grant a limited exception so we can produce the evidence?”
To respond when you do not know the reference:
“Do you mean the requirements block each other?”
The last question captures the workplace meaning without requiring literary knowledge.
Recognition before production
When you hear Catch-22, look for two conditions that make each other impossible to satisfy. The speaker may also be using the phrase loosely for a frustrating constraint, so ask for the loop rather than correcting them immediately.
When you use it, state the actual dependencies in the next sentence. “It’s a Catch-22” communicates frustration; “Access requires approval, while approval requires access evidence” gives colleagues something they can redesign.
The phrase is common enough to be understood in many U.S. workplaces, but familiarity varies by age, language, and reading background. In a global policy document, circular dependency or a literal explanation may be clearer.
Tone, hierarchy, and policy
Calling a process a Catch-22 can sound like criticism of the people who designed or enforce it. Hedge when you have incomplete information:
“I may be missing an approved path, but these two requirements appear circular.”
That invites correction and avoids claiming the policy is irrational before checking it.
In compliance, security, immigration, benefits, or legal contexts, an apparent contradiction may have an exception or formal escalation route. Do not bypass controls because a situation feels absurd. Document the requirements and ask the authorized owner.
Avoid applying the phrase to someone's identity, disability, immigration status, or personal choices as though their circumstances were a joke. Focus on the institutional conditions.
For another literary reference about surveillance and control, see “Big Brother is watching” at work. For a metaphor about one hidden weakness, see Achilles’ heel.
The practical takeaway
A Catch-22 is a circular, no-win condition—not merely a hard decision. Recognize the reference, identify the requirements that block each other, and describe them literally. At work, the most useful next question is: “Which rule can an authorized owner clarify, sequence differently, or exempt?”