9 minutes
Noticing Denial in a team's default practice Denial often shows up as a shared team default, not one person's flaw. How to name what you notice about a practice without labeling the person.
What you’ll be able to do Recognize when a team's default practice reflects Denial-style thinking and raise it in a way that invites noticing rather than defensiveness. Compare the responses to this question and explain your choice: What is the most useful next step? Document a next step for Noticing Denial in a team's default practice: Identify one recurring team practice — a form, a script, a notice — that assumes a single kind of recipient, and raise it with the owner as a specific, observable pattern rather than a character judgment. A team default, not just a personal trait Because Denial is about what has not yet registered as real, it rarely announces itself as an opinion. It shows up instead as a routine nobody has reconsidered: the one language a notice goes out in, the one script an intake interview follows, the one assumed household shape on a form. Everyone on the team can be kind, competent, and busy while the routine itself has never been checked against who is actually on the other end of it.
This is why raising Denial in a colleague works better as a question about the practice than a statement about the person. "Have we checked this" invites a look. "You're not seeing this" invites a defense. Both may be pointing at the same gap, but only one leaves room for the other person to notice it themselves.
Signs a team default may be operating from Denial A single format, language, or channel is used for everyone, and nobody can say when it was last reconsidered.
"Nobody has complained" is treated as proof the practice works, rather than one weak signal among several.
A generalization about "our clients" is offered with confidence but without a specific, checkable example behind it.
Questions about who might be missed are met with reassurance rather than curiosity.
Ways to raise it without labeling anyone Ask for the check, not the confession
"Have we looked at the data on this" is easier to hear than "you're assuming too much," and it produces the same useful information.
Bring one concrete case, not a general theory
A single specific example — one household, one form, one missed notice — moves a conversation further than an abstract claim about bias ever will.
Offer to do the legwork
Volunteering to pull the number or run the check lowers the cost of being wrong for the person whose default is being questioned, which makes it easier for them to say yes.
Separate the pattern from the person
"This form only exists in English" is a fact about a document. "You don't care about non-English speakers" is a claim about a person. Only the first one is usually true, and only the first one is useful to say out loud.
Question the routine, not the person What you can change You control whether you frame a team default as a checkable fact or a personal failing.
What to watch for Do not open with a diagnosis of someone's awareness. Open with a specific, checkable question about the practice itself.
Your next step Before your next meeting, identify one team default worth checking and bring a specific way to check it, not just a concern.
Carry this forward Denial in a team usually looks like a shared default — one template, one language, one assumed client story — more than one person's individual attitude.
Naming what you notice about a practice ("this notice only goes out in English") is safer and more productive than naming what you assume about a colleague's character or intentions.
The goal of raising Denial in a colleague or team is to open a door to noticing, not to win an argument or prove you have moved further along the continuum than they have.
A team can look busy and effective while still operating from Denial about who its actual audience is.
A workplace scenario decision about a team default, and a knowledge check on raising a pattern without labeling a person.
Identify one recurring team practice — a form, a script, a notice — that assumes a single kind of recipient, and raise it with the owner as a specific, observable pattern rather than a character judgment.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
