home / skills / coowoolf / insighthunt-skills / left-hand-column-detox

left-hand-column-detox skill

/team-leadership/left-hand-column-detox

This skill helps translate harsh internal thoughts into constructive external dialogue to defuse tension and drive respectful, candid conversations.

npx playbooks add skill coowoolf/insighthunt-skills --skill left-hand-column-detox

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.4 KB
---
name: Left-Hand Column Detox
description: A technique to translate harsh internal thoughts into constructive external dialogue. Say the thing you think you cannot say—but detoxify it first. Use when sensing tension or unspoken issues in meetings.
---

# The 'Left-Hand Column' Detox

> "Say the thing you think you cannot say... detoxify the left-hand column." — Claire Hughes Johnson

## What It Is

A technique adapted from Fred Kofman to translate harsh internal thoughts (the **left-hand column**) into constructive, external dialogue (the **right-hand column**).

## When To Use

- Sensing **tension in a meeting**
- Noticing a **"pink elephant" in the room**
- Spotting a **recurring performance issue**
- When feedback feels **"too harsh" or "unsayable"**

## The Two Columns

```
┌─────────────────┬─────────────────────────┐
│  LEFT COLUMN    │     RIGHT COLUMN        │
│  (Internal)     │     (External)          │
├─────────────────┼─────────────────────────┤
│ "Lenny botched  │ "I wonder if you felt   │
│  that interview"│  you missed an          │
│                 │  opportunity in that    │
│                 │  interview?"            │
├─────────────────┼─────────────────────────┤
│ "These teams    │ "I feel like there's    │
│  are fighting   │  something we're not    │
│  over turf"     │  talking about... do    │
│                 │  these teams own the    │
│                 │  same project?"         │
└─────────────────┴─────────────────────────┘
```

## Core Principles

### 1. Identify the Thought
Acknowledge the harsh internal thought (e.g., "Lenny botched that interview").

### 2. Filter for Intent
Check if your goal is to **help** or to **blame**.

### 3. Translate to Inquiry
Convert the judgment into a curious question ("I wonder if you felt you missed an opportunity in that interview?").

### 4. Say the "Unsayable"
Speak the filtered observation directly to clear the air and build trust.

## How To Apply

```
STEP 1: Notice Your Reaction
└── Feel frustration, judgment, or tension
└── Catch the internal thought

STEP 2: Write It Down (If Possible)
└── Left column: Raw thought
└── Right column: Constructive version

STEP 3: Check Intent
└── Am I trying to help or punish?
└── What outcome do I actually want?

STEP 4: Translate to Curiosity
└── Use "I wonder..." or "I'm curious..."
└── Frame as observation, not accusation

STEP 5: Speak It
└── "I want to share an observation..."
└── "Can we discuss something that might be uncomfortable?"
```

## Common Mistakes

❌ **Over-filtering** so much that the feedback becomes vague

❌ Blurting out the raw "left-hand" thought without detoxifying

❌ Using it as manipulation instead of genuine curiosity

## Real-World Example

Claire calling out a conflict between two teams in a meeting by asking, "I feel like there is something we are not talking about... do these two teams own the same project?"

---
*Source: Claire Hughes Johnson, Lenny's Podcast*

Overview

This skill teaches a simple method for turning harsh internal reactions into constructive, spoken observations. It helps you say what you think you cannot say by detoxifying the judgment into curiosity and clarity. Use it to surface unspoken issues while keeping dialogue productive and respectful.

How this skill works

You notice a raw internal thought (the left-hand column), check your intent (help vs blame), then rephrase it into a curious, nonaccusatory statement or question (the right-hand column). Practice writing the two columns, then speak the detoxified version to clear tension and invite collaboration. The approach emphasizes observation, curiosity, and desired outcomes.

When to use it

  • When you sense tension or a ‘pink elephant’ in a meeting
  • When feedback feels too harsh or hard to say aloud
  • When recurring performance or ownership issues show up
  • Before giving feedback that could sound like blame
  • When you want to build trust by addressing uncomfortable topics

Best practices

  • Write the left-hand thought first, then craft a curious reframe before speaking
  • Check your intent: aim to help, not to punish or score points
  • Use phrases like “I wonder…” or “I’m curious…” to soften judgment
  • Avoid over-filtering into vagueness—keep the observation concrete
  • Practice privately so you can deliver the detoxified line confidently

Example use cases

  • A product review where a teammate’s work missed the mark—reframe judgment into a question about intent or constraints
  • A cross-team meeting with passive tension—call out the unspoken issue and ask if ownership is clear
  • Performance coaching where feedback feels charged—translate blunt criticism into an offer to help improve
  • A retrospective where recurring blockers aren’t being named—voice the pattern as an observation and invite solutions
  • One-on-one conversations where you fear causing defensiveness—lead with curiosity and desired outcomes

FAQ

Won’t this just hide what I really mean?

No. The goal is not to dilute truth but to translate it into a form that others can hear and act on. Keep the observation concrete to avoid vagueness.

How do I stop sounding passive or vague?

Avoid over-filtering. Use specific examples, state the impact, and pair curiosity with a clear intent like wanting to help or resolve a problem.