Skip to content

Anti-Primer: Incident Psychology

Everything that can go wrong, will — and in this story, it does.

The Setup

A mid-level engineer is navigating a challenging situation involving incident psychology at work. The team is under pressure from a delayed project, tensions are high, and the engineer has not yet developed strong skills in this area. Small missteps compound quickly.

The Timeline

Hour 0: Avoiding the Difficult Conversation

Delays addressing an issue directly, hoping it resolves itself. It felt like the right move in the moment — urgency overrode patience. But the result is the problem festers and grows; by the time it is addressed, trust has eroded and positions have hardened.

Footgun #1: Avoiding the Difficult Conversation — delays addressing an issue directly, hoping it resolves itself, leading to the problem festers and grows; by the time it is addressed, trust has eroded and positions have hardened.

The person does not notice the misstep yet and keeps going.

Hour 1: Reacting Instead of Responding

Responds emotionally in a heated Slack thread without pausing to think. The pressure to see results quickly made this seem like the only option. But the result is the message escalates the conflict; screenshots are shared; the engineer's reputation takes a hit.

Footgun #2: Reacting Instead of Responding — responds emotionally in a heated Slack thread without pausing to think, leading to the message escalates the conflict; screenshots are shared; the engineer's reputation takes a hit.

The first mistake is still invisible, making the next one feel justified.

Hour 2: Assuming Intent

Interprets a colleague's terse message as hostile without seeking clarification. Nobody pointed out the risk because it looked harmless in isolation. But the result is builds resentment based on a misunderstanding; collaboration deteriorates on the shared project.

Footgun #3: Assuming Intent — interprets a colleague's terse message as hostile without seeking clarification, leading to builds resentment based on a misunderstanding; collaboration deteriorates on the shared project.

Frustration is building. The temptation to take shortcuts grows stronger.

Hour 3: Not Setting Boundaries

Agrees to take on additional work despite being at capacity, unable to say no. Past experience suggested this would work out fine, so no alarm bells rang. But the result is quality drops on all tasks; misses a critical deadline; burnout sets in within weeks.

Footgun #4: Not Setting Boundaries — agrees to take on additional work despite being at capacity, unable to say no, leading to quality drops on all tasks; misses a critical deadline; burnout sets in within weeks.

By this point, the compounding missteps have reached a tipping point. The damage is not a server on fire — it is eroded trust, wasted effort, and a situation much harder to recover from than it was to prevent.

The Postmortem

Root Cause Chain

# Mistake Consequence Could Have Been Prevented By
1 Avoiding the Difficult Conversation The problem festers and grows; by the time it is addressed, trust has eroded and positions have hardened Primer: Address issues early when they are small and manageable
2 Reacting Instead of Responding The message escalates the conflict; screenshots are shared; the engineer's reputation takes a hit Primer: Pause before responding to emotionally charged messages; draft and revise before sending
3 Assuming Intent Builds resentment based on a misunderstanding; collaboration deteriorates on the shared project Primer: Assume good intent; ask clarifying questions before drawing conclusions
4 Not Setting Boundaries Quality drops on all tasks; misses a critical deadline; burnout sets in within weeks Primer: Communicate capacity honestly; practice saying 'I can do X or Y, but not both by Friday'

Damage Report

  • Downtime: No system downtime, but relationship and project damage accumulates
  • Data loss: Not applicable in the technical sense, but trust and goodwill are lost
  • Customer impact: Team morale drops; collaboration deteriorates; project timelines slip
  • Engineering time to remediate: Weeks of effort to rebuild trust and repair working relationships
  • Reputation cost: Professional reputation damage; potential impact on performance reviews

What the Primer Teaches

  • Footgun #1: If the engineer had read the primer, section on avoiding the difficult conversation, they would have learned: Address issues early when they are small and manageable.
  • Footgun #2: If the engineer had read the primer, section on reacting instead of responding, they would have learned: Pause before responding to emotionally charged messages; draft and revise before sending.
  • Footgun #3: If the engineer had read the primer, section on assuming intent, they would have learned: Assume good intent; ask clarifying questions before drawing conclusions.
  • Footgun #4: If the engineer had read the primer, section on not setting boundaries, they would have learned: Communicate capacity honestly; practice saying 'I can do X or Y, but not both by Friday'.

Cross-References