DEEP Technique: Don't Defend, Engage, Explain, or Personalize
The DEEP Technique helps you stay out of a baiting or bad-faith exchange by refusing to defend, engage, over-explain, or take the attack as a verdict on you. The four refusals are a stance for this interaction. They do not reform the other person, and they are the wrong default for good-faith criti…
Framework Card
- Name:
- DEEP Technique
- Goal:
- Stay out of a baiting or bad-faith exchange by refusing to defend, engage, over-explain, or take the attack as a verdict on you.
- Flow:
- Don't Defend → Don't Engage → Don't Explain → Don't Personalize
- Best For:
- Arguments being pulled into a fight; Bad-faith criticism that feeds on justification; Guilt or blame used to control a reaction
Why it matters
Some conversations are not looking for a working answer. They are looking for a trial: your justification, your counterpunch, your extra story, your collapse. If you supply those, the hour continues.
DEEP is a way to stop supplying that fuel while you are still in the room. Silence is not always available. A short no can still be DEEP. A long defense is not.
What it is
DEEP is four refusals used together:
- Don't Defend: withhold the justification that extends the trial
- Don't Engage: withhold the argumentative reaction being sought
- Don't Explain: withhold extra story that can be distorted
- Don't Personalize: withhold treating the attack as a verdict on your worth
Production pages say “handle toxic people.” This page treats behavior in an exchange (bait, guilt, circular trial), not a clinical label. Scrum also uses DEEP (Detailed, Estimated, Emergent, Prioritized backlog items). That is a different method.
How it works
A useful DEEP pass names the bait, then holds all four refusals in one stance.
1. Name the move you are being pulled into
Is the ask a fight, a trial, a guilt loop, or an endless why? If it is a working question from someone acting in good faith, stop. DEEP is the wrong tool.
2. Don't Defend and Don't Engage
Skip the “but I…” brief. Skip the point-scoring reply. A short acknowledgment or a close (“I’m not going to try this in this meeting”) can be enough.
3. Don't Explain
Give the minimum fact if a fact is required (“The decision stands”). Do not add history, motives, or a second story they can quote.
4. Don't Personalize
Treat the attack as their move. Your worth is not on trial in this exchange. If the content would still matter from a good-faith partner, park it for a later, different conversation.
If the issue is safety, harassment, or formal misconduct, DEEP is not the process. Use the process that exists.
How it compares
| Framework | What it helps you see | How it differs from DEEP |
|---|---|---|
| SBI Model | Situation, Behavior, Impact | A giving structure. DEEP is receiver-side refusal. |
| COIN Model | Context, Observation, Impact, Next | Giving critique to a working partner. |
| Radical Candor | Care plus challenge | A giving stance, not four refusals. |
| Active Listening Spiral | Good-faith receiving | Opposite default from DEEP. |
| Scrum DEEP | Detailed, Estimated, Emergent, Prioritized | Same letters, backlog method. |
DEEP is the lens for refusing a baiting exchange. Other methods help when the job is giving, receiving in good faith, or a formal process.
When to Use This Framework
- Meeting bait. Repeated interruptions designed to start a fight.
- Bad-faith criticism. Every answer becomes new evidence in a trial.
- Guilt as control. A short no is met with a longer indictment of your character.
Example
A concrete example makes the structure easier to reuse when you are under uncertainty.
Example: Standup pulled into a trial
A colleague says, in front of the group, “You always dump work on us. Explain why you thought that was OK.” The history is mixed. The move is a trial.
DEEP: no defense speech, no engagement on “always,” no extra explanation of last quarter, no taking the public shaming as a verdict. A short line: “I’m not going to litigate that here. We can pick a time with the manager if you want a work conversation.”
Implication: The stance ended the public trial. It did not prove who was right. SBI would be the wrong tool in this minute if the job is not to give feedback.
Example: Family guilt loop
A relative uses “after all I’ve done” to reopen a closed no.
DEEP: don't defend the no with a moral essay, don't engage the ledger, don't explain the calendar again, don't personalize the character attack. Repeat the no once. Leave the topic.
Implication: Explaining more was the fuel. DEEP is not family therapy.
Takeaway
What DEEP can help with
- Refusing a trial, fight, or guilt loop in the moment
- Keeping a short stance when you cannot fully leave
- Separating bait from a working question
- Not taking the attack as a verdict on your worth
What DEEP cannot replace
- SBI or COIN. Structures for giving feedback to a working partner.
- Active listening. Good-faith receiving.
- HR, legal, or exit. Safety and misconduct need a process.
- Scrum DEEP. Backlog item qualities.
- Reform of the other person, or a clinical diagnosis.
Honest scope: DEEP is an in-the-moment refusal stance. It does not replace giving models or formal processes.
Frequently asked questions
Yes, when the exchange is bait or bad faith. It is the wrong default for a good-faith performance review.
Ignoring is withdrawal. DEEP is a stance: you may still say a short no. You refuse the trial, the fight, the extra story, and the self-verdict.
No. Scrum DEEP describes backlog items. This page is four refusals in an exchange.
No. It reduces the fuel you supply. Change of the other party is not the method’s job.
Park the content for a later working conversation, or use a giving/receiving model with a partner acting in good faith. Do not run the trial in the baiting minute.