Four-step resentment protocol

When This Fires

• When you notice resentment building — toward a person, situation, or repeated pattern
• During values discovery as a complement to peak experience analysis (Extract values from recurring conditions across 5+ peak…)
• When resentment is persistent and you can't articulate why — the protocol surfaces the underlying value
• When setting boundaries and needing to identify what specifically needs protecting

Common Failure Mode

Staying at Step 2 (trigger) without reaching Step 3 (value): "I'm resentful because they interrupted me." This identifies the event but not the value. The value might be respect, autonomy, being heard, or intellectual contribution — each would lead to different boundary-setting. Without naming the value, you address the symptom (interruption) rather than the need (whatever the interruption violated).

The Protocol

(1) Notice: detect the resentment. Physical signals: tension, irritability, mental replaying of the event. If you catch yourself rehearsing what you should have said → resentment is present. (2) Trigger: identify the specific event: "When [specific person] did [specific action] in [specific context]." Be precise — vague triggers hide the value. (3) Value: ask "What did that violate?" What do I care about that this action threatened? Name it explicitly: respect, autonomy, fairness, competence recognition, honesty, creative freedom. (4) Externalize: write it down: "[Date] — Trigger: [event]. Violated value: [name]." (5) Accumulate entries over weeks and months. When the same value appears in 3+ entries from different contexts → it's a core value (When the same value is violated across 3+ independent…).