Meta Model · Pattern 6 of 13
Universal Quantifiers
One experience is generalised into a rule that admits no exceptions.
Recover: Counterexamples and exceptions
What it is
Absolutes make a problem total and permanent. Finding a single exception changes the internal representation: moving a client from 'always' to 'most of the time' has already loosened the generalisation.
Recognition / tip-offs
What has been distorted, generalised or deleted
- Generalised: one or several experiences now cover every case
- Deleted: every exception the speaker has lived through
- Deleted: the specific event that started the generalisation
Client-language use
"She never listens to me", "Nobody ever understands me." Said with real feeling — so exceptions are found gently, not triumphantly.
How to challenge it
Repeat the universal back with questioning intonation, then hunt one exception. One is enough.
- “Never?”
- “Everyone?”
- “Not a single time?”
- “Can you think of one exception?”
- “Was there ever a time when it wasn't like that?”
Practitioner judgement: challenge what is useful, not every pattern you can hear.
What to recover
You are recovering counterexamples and specificity. Do not stack up evidence against the client — one exception, explored, does more.
Client autonomy first — offer language the client can verify and decline.
Examples
“Why does everyone always ignore my ideas?”
Missing Who specifically, when, and the times ideas were taken up.
Challenge: “Everyone? Always? Whose idea was taken up most recently?”
Also a presupposition — that ideas are ignored is built into the question.
“You never listen to me.”
Missing The specific occasion, and every time listening did happen.
Challenge: “Never? Was there a time I did listen?”
“Nobody ever really understands me.”
Missing Who specifically, and what understanding would look like.
Challenge: “Nobody? Has one person ever understood one thing?”
Common confusion and overlap
- Confusing it with Lack of Referential Index: 'people' is unspecified, 'all people' is universal
- Sounding like you are proving the client wrong
- Stopping at the exception instead of exploring what was different about it
Practice this pattern
Hear it
0%
Unpack it
0%
Question it
0%
Build it
0%
Use it live
0%