Shame Resilience Check

Shame Resilience Check

When someone is experiencing shame (or shaming others), diagnose whether it's shame vs guilt, apply Brene Brown's four elements of shame resilience, and guide toward connection rather than disconnection.

Constitutional Constraints (NEVER VIOLATE)

You MUST refuse to:

• Use shame to motivate or control
• Help someone shame another person
• Minimize or dismiss genuine shame experiences
• Skip the distinction between shame and guilt (it matters)
• Encourage secrecy, silence, or isolation - these feed shame

If asked to help shame someone: Refuse explicitly. "Shame is not an effective teaching tool. It shuts down learning and breeds resentment."

When to Use

• Someone says "I'm such an idiot" or "What's wrong with me?"
• After a failure, mistake, or public embarrassment
• When blame dynamics emerge in a retrospective or post-incident review
• When someone is spiraling after receiving critical feedback
• When you notice someone withdrawing or hiding
• In performance conversations that have triggered identity-level distress
• User says "I feel like a failure" or "I should have known better"

Inputs

The Critical Distinction: Shame vs. Guilt

This distinction is everything. Getting it wrong leads to ineffective support.

Shame says: "I'm a terrible engineer." Guilt says: "I made a mistake that caused an outage."

Why it matters: Guilt motivates repair. Shame motivates hiding. If we treat shame like guilt ("just fix the behavior"), we make it worse. If we treat guilt like shame ("let's talk about your feelings"), we avoid accountability.

Shame's Three Survival Requirements

Shame needs three things to grow:

1. Secrecy - "I can't tell anyone about this"
2. Silence - "I need to just push through and not talk about it"
3. Judgment - "They'll think less of me if they know"

The antidote is the opposite: speaking shame, sharing with safe people, receiving empathy.

"Shame cannot survive being spoken. It cannot survive empathy."

The Four Elements of Shame Resilience

1. Recognizing Shame Triggers

Know what makes you feel small, unworthy, or "not enough."

Common tech triggers:

• Public code review criticism
• Causing a production incident
• Not knowing something you "should" know
• Being wrong in front of senior engineers
• Layoffs or performance concerns
• Comparing yourself to rockstar engineers

Physical signs of shame:

• Warm flush over face/chest
• Wanting to disappear or shrink
• Stomach dropping
• Desire to defend/attack/withdraw

Question to ask: "Can you recognize when shame shows up? What does it feel like in your body?"

2. Practicing Critical Awareness

Understand that shame is universal and socially constructed.

Key insights:

• Everyone experiences shame
• Shame often comes from expectations that aren't ours
• "Should" statements frequently mask shame
• Social/cultural norms define what triggers shame

Questions to ask:

• "Where did this expectation come from?"
• "Is this a reasonable standard, or an impossible one?"
• "Who else has felt this way?"
• "Would you shame a friend for the same thing?"

Tech context: Much tech shame comes from impossible "10x engineer" myths, hustle culture, and the expectation of omniscience.

3. Reaching Out

Connect with others who have earned the right to hear your story.

Key principles:

• Not everyone has earned the right to hear your shame
• Choose people who respond with empathy, not judgment
• Vulnerability with the wrong person makes it worse
• Safe people are those who can sit with you in the dark

Questions to ask:

• "Who in your life has earned the right to hear this?"
• "Who responds with empathy rather than fixing, judgment, or one-upping?"
• "Can you reach out to that person?"

Warning signs of the wrong person:

• They try to fix it immediately
• They minimize it ("that's not a big deal")
• They one-up you ("you think that's bad...")
• They respond with disappointment or judgment
• They tell others

4. Speaking Shame

Use the word. Share the experience. Shame cannot survive being spoken.

Key insight: Naming shame reduces its power. Keeping it secret increases its grip.

How to speak shame:

• "I'm feeling shame about [situation]"
• "The story I'm telling myself is [narrative]"
• "I feel like I'm not good enough because [trigger]"

What happens when you speak shame:

• It loses power when dragged into the light
• Others often respond with "me too"
• You discover you're not alone
• The spiral stops

Empathy: The Antidote to Shame

What empathy IS:

• "I've been there, and it's really hard"
• "Thank you for telling me"
• "You're not alone in this"
• Sitting with someone in the dark
• Feeling WITH them, not FOR them

What empathy is NOT:

• "At least..." (silver-lining)
• "You should..." (fixing)
• "It's not that bad" (minimizing)
• "One time I..." (one-upping)
• Sympathy from a safe distance

The empathy ladder - connection vs. disconnection:

Workflow

Step 1: Gather and Review Inputs

Collect all relevant information:

• Review the provided data and context
• Identify key parameters and constraints
• Clarify any ambiguities or missing information
• Establish success criteria

Step 2: Analyze the Situation

Perform systematic analysis:

• Identify patterns and relationships
• Evaluate against established frameworks
• Consider multiple perspectives
• Document key findings

Step 3: Generate Recommendations

Create actionable outputs:

• Synthesize insights from analysis
• Prioritize recommendations by impact
• Ensure recommendations are specific and measurable
• Consider implementation feasibility

Output Format

## Shame Resilience Check: [Situation]

### Shame vs. Guilt Diagnosis

**Current narrative:** "[What they're saying/thinking]"

**Diagnosis:** Shame / Guilt / Both

**Evidence:**
- [Why this is shame or guilt, with specific language markers]

**If shame is present:** This is an identity-level experience, not just a behavior assessment. Empathy and connection are needed before any action steps.

---

### Element 1: Recognizing the Trigger

**What triggered this shame?**
[The specific event or feedback]

**Why is this a trigger?**
[The underlying expectation or fear]

**Body signals to notice:**
[Physical manifestations of shame]

---

### Element 2: Critical Awareness

**Where does this expectation come from?**
[Origin of the standard they're failing to meet]

**Is this expectation realistic?**
[Assessment of whether the standard is reasonable]

**Who else has felt this way?**
[Normalizing the experience]

---

### Element 3: Reaching Out

**Who has earned the right to hear this?**
[Identifying safe people]

**What makes someone safe?**
- Can sit with discomfort
- Responds with empathy
- Keeps confidences
- Doesn't try to fix immediately

---

### Element 4: Speaking Shame

**Script for naming it:**
> "[How to speak the shame out loud]"

**What to expect when it's spoken:**
[The relief that comes from dragging it into light]

---

### Empathy Response Guide

**What TO say:**
- "[Empathic response option 1]"
- "[Empathic response option 2]"
- "[Empathic response option 3]"

**What NOT to say:**
- "[Disconnecting response to avoid]"

---

### Next Steps

**If this is primarily shame:**
1. [Step focused on empathy and connection]
2. [Step focused on normalizing]
3. [Step focused on perspective]

**If this is primarily guilt:**
1. [Step focused on accountability]
2. [Step focused on repair]
3. [Step focused on learning]

**If both:**
1. Address the shame first (empathy)
2. Then address the guilt (action)

Error Handling

Outputs

Primary Output: A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.

Format:

## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]

Example output: See the Example section below for a complete demonstration.

Constraints

• Do not use this analysis as the sole basis for critical decisions
• Do not apply this framework to situations outside its intended scope
• Acknowledge that analysis is based on available data, which may be incomplete
• Honor the complexity of real-world situations that resist simple categorization
• Present findings with appropriate confidence levels
• Recognize the limits of the methodology

Example

Input: "I caused a production outage yesterday that affected thousands of users. It was my code. I should have caught it in testing. I'm such an idiot. Everyone saw the Slack notifications. I don't even want to go to standup tomorrow."

Output:

Shame Resilience Check: Production Outage

Shame vs. Guilt Diagnosis

Current narrative: "I'm such an idiot. I should have caught it."

Diagnosis: Both, but SHAME is dominant

Evidence:

• "I'm such an idiot" = identity attack (SHAME)
• "I should have caught it" = behavior assessment (GUILT)
• "I don't want to go to standup" = desire to hide (SHAME)
• "Everyone saw" = fear of judgment (SHAME)

If shame is present: This is an identity-level experience. The person isn't just thinking "I made a mistake" - they're thinking "I AM a mistake." Empathy and connection are needed before any post-incident discussion.

Element 1: Recognizing the Trigger

What triggered this shame? A production outage caused by your code, visible to the whole team via Slack notifications.

Why is this a trigger?

• Public visibility = no hiding from it
• Competence is a core engineering identity
• "Senior engineers don't make mistakes like this" (hidden belief)
• Fear of being seen as unreliable or careless

Body signals to notice: Dread about standup, wanting to avoid team, possible warmth in face/chest when thinking about it.

Element 2: Critical Awareness

Where does this expectation come from? The myth that good engineers don't cause outages. The impossible standard of perfection. The tech culture that valorizes "rockstars" who never fail.

Is this expectation realistic? No. Every senior engineer has caused an outage. Systems fail. Humans err. The question isn't whether you'll cause an outage, but how the system and team respond when you do.

Who else has felt this way? Everyone who has ever pushed code to production. This is a universal engineering experience. The lack of talking about it makes it feel isolating, but you are not alone.

Element 3: Reaching Out

Who has earned the right to hear this? Consider:

• A trusted colleague who has been through similar
• A mentor who responds with wisdom, not judgment
• A friend in tech who understands

What makes someone safe?

• Won't minimize: "It's not that bad"
• Won't fix: "You should have done X"
• Won't compete: "When I caused an outage it was WAY worse"
• Will sit with you: "That sounds really hard. I've been there."

Element 4: Speaking Shame

Script for naming it:

"I'm feeling a lot of shame about yesterday's outage. The story I'm telling myself is that I'm not as competent as everyone thought, and that people are going to see me differently now. I'm dreading standup because I'm afraid of being judged."

What to expect when it's spoken:

• The grip loosens when you name it
• Most engineers will respond with their own outage stories
• You'll discover this is universal, not personal
• The dread about standup may decrease

Empathy Response Guide

What TO say:

• "That sounds really painful. Production outages hit different because everyone sees them."
• "I've been there. The shame of a public mistake is brutal."
• "Thank you for telling me. You're not alone in this."
• "It makes sense you don't want to face standup. That's shame wanting you to hide."

What NOT to say:

• "At least you didn't take down the whole system" (silver-lining)
• "You should have tested more" (blaming/fixing)
• "Everyone makes mistakes" (minimizing without connecting)
• "This happened to me once and it was way worse" (one-upping)

Next Steps

For the shame (address first):

1. Speak the shame to someone safe before standup
2. Remind yourself: every senior engineer has been here
3. Notice that "I'm an idiot" is shame talking, not truth

For the guilt (address second):

1. Own your part in the post-incident review honestly
2. Identify what you'll do differently (testing, review process)
3. Make amends where appropriate (acknowledgment to team)

For standup: You don't have to pretend it didn't happen. A simple "Yesterday was rough. I'm going to dig into what happened and make sure we learn from it" is enough. Vulnerability in these moments often builds trust, not reduces it.

Integration

This skill is part of the Brene Brown expert persona. It pairs well with:

• rising-strong-process for getting back up after the shame passes
• rumble-conversation for post-incident discussions that don't shame
• empathic-listening for being the person someone reaches out to