All lessonsBusiness & Leadership

Reframing — The Leadership Skill That Changes Everything

Your worst business decisions are not information problems. They are frame problems. Learn the six directions of reframing and the pressure protocol that lets founders lead from choice instead of reaction.

2026-07-14 2,979 words 15 min read

Why Reframing Feels Like Gaslighting (And How the Wrong Level Breaks It)

You've tried to reframe a client, a founder, a senior hire. You picked the way they were thinking, turned it around, and handed them a shiny new meaning. And it landed flat. They didn't feel liberated. They felt invalidated. Sometimes they got quiet and agreeable — which is worse, because quiet and agreeable is how people disengage while nodding along.

That's not because reframing is fake. Reaframing is one of the most useful things a coach or leader can do. It fails because most people use the wrong type, aimed at the wrong level, with no algorithm behind the choice. They reframe at a level where the person cannot accept the new meaning, so the reframe collapses into something that sounds a lot like gaslighting.

Here's the raw truth: a reframe that ignores the level of thinking that created the problem isn't a reframe — it's a contradiction. And contradictions don't transform people. They just make you sound pushy.

This article gives you the missing piece. Two distinct reframing tools — content reframing and context reframing. A map of the six neurological levels where problems actually get created (Dilts' Neurological Levels). And a diagnostic — the SCORE model — that tells you exactly which level to reframe and why. When you know the level, the reframe stops being a guess and becomes a repeatable skill.

Honesty note, before we go deeper: NLP patterns — including reframing, neurological levels, and SCORE — are modeled frameworks built from observing what skilled communicators actually do. They are taught as practical, experience-tested tools, not as controlled-clinical proof. They work powerfully in skilled hands, but they are not laboratory-validated treatments. Treat them as structured skills to practice and test in the real world, not as medical claims.

The Two Flavours: Content Reframing vs Context Reframing

Most people think of "reframing" as one thing. It's two. They are different tools for different jobs, and using the wrong one is like driving a screw with a hammer — it might work by luck, but it won't work well, and it'll damage things along the way.

Content Reframing: Change the Meaning of the Behaviour Itself

Content reframing asks one question: What else could this mean? You take the same behaviour or situation and assign it a different meaning. The behaviour doesn't change — the interpretation does. This is a meaning-making tool, and it works best on the personal, internal level: how someone reads their own problem.

Worked examples:

  • "I'm too detailed" → "You're thorough. That's a quality-assurance asset."
  • "My team is resistant" → "Your team is protective of standards. They care about quality."
  • "I failed the presentation" → "You gathered data on what doesn't work. That's market research."
  • "He's stubborn" → "He's committed to his principles. Under what circumstances would that be an asset?"

Content reframing is the right tool when: someone is stuck in a negative self-assessment; a behaviour is being interpreted in only one way; you need to shift emotional state fast; and — critically — when the behaviour itself is neutral, and the problem is purely the meaning assigned to it.

The One-Word Reframe Drill: take any negative label and find its positive counterpart. Angry → Passionate. Stubborn → Committed. Anxious → Alert. Impulsive → Spontaneous. Rigid → Consistent. Practice it until it's automatic. It's the fastest content-reframing drill there is — and notice it only works when the label is the problem, not the underlying behaviour.

Context Reframing: Change Where the Behaviour Is Evaluated

Context reframing asks a different question: Where would this behaviour be useful? The behaviour stays exactly the same, but you change the context in which it's evaluated. What's a weakness in one setting becomes a strength in another.

Worked examples:

  • "I talk too much in meetings" → "In a brainstorming session, that verbal processing would generate the ideas the team needs."
  • "I'm too emotional" → "In a client-relationship role, that emotional sensitivity would help you read the room and build trust."
  • "My attention to detail slows things down" → "In compliance or quality control, that same attention to detail prevents disasters."
  • "I'm too direct" → "In crisis management, directness saves lives. The context decides whether directness is appropriate."

Context reframing is the right tool when: a behaviour genuinely is a problem in one context but valuable in another; someone believes a trait is universally "bad"; you want to preserve a behaviour that's actually useful but redirect where it's applied; and when you want to help someone see that their "flaw" is a strength in the right environment.

The core question of context reframing carries a presupposition worth noticing: "Where, when, or with whom would this behaviour be valuable?" The frame presumes the behaviour is valuable somewhere — the only question is where. That single shift moves the client from "I need to eliminate this" to "I need to redirect this."

The Trap: Why the Two Tools Get Confused — And How It Feels Like Gaslighting

Here's where most reframing goes off the rails. The two tools sound similar, so people assume they're interchangeable. They aren't. And the moment you fire the wrong one, the person feels it.

The Content-Reframe-Applied-To-A-Context Problem

The reel example "They are not inconsiderate — they made the trip, didn't they?" is a content reframe trying to do the job of a context reframe. The founder is describing a problem of context: a behaviour that keeps happening in the wrong setting and damaging the working relationship. You hand them a new meaning instead. The result is a formula for being pushy, not helpful. They don't doubt the behaviour anymore — they doubt you.

Gaslighting, in the everyday sense, is telling someone their own experience is wrong. A misfired reframe does exactly that. The person says, "I feel like my team resists everything I say." The reframe replies, "Actually, they care about quality." Even if that's true, the person just got told their lived reality is mistaken by someone who hasn't had to live it. That stings.

The Two Questions That Decide Which Tool to Reach For

Before you reframe anything, separate two things:

  • Is this a problem of meaning? The behaviour is neutral; the interpretation is painful. → That's content reframing territory.
  • Is this a problem of placement? The behaviour is genuinely hurting results in the current setting, but it would be a resource somewhere else. → That's context reframing territory.

Ask yourself, out loud, in the session: What level of thinking created this problem? That question is the entire game. The reframe must tackle the root level of thinking where the problem was created — not the level where you'd most like it to be.

You cannot reframe your way out of a placement problem with a meaning patch, any more than you can reframe your way out of a broken process with a motivational slogan. When the person feels their experience is real and the behaviour is actually hurting — and you tell them it's fine — you've broken trust, not built insight.

The Map: Dilts' Neurological Levels — Where Problems Are Actually Created

Two tools solve the "which type" question. But there's a deeper question underneath it: which level is the problem living at? That's where Dilts' Neurological Levels — often called Logical Levels — come in. This is the framework that turns reframing from a lucky guess into a deliberate craft.

Here's the reveal: Dilts' Neurological Levels and the SCORE model are critical because they give reframing its algorithm. Most reframing falls flat because there is no algorithm for it — no way to decide what to change. These two frameworks supply the decision structure.

The Six Levels, From Ground to Sky

Dilts organised experience into six nested levels. Each level is a different kind of "where" a problem can live, and each one demands a different reframe:

  • Environment — where and when it happens. The people, places, time, and circumstances around the behaviour. Problems here are about externals: "the market changed," "we're in the wrong office," "this city has no talent pool."
  • Behaviour — what the person actually does. The specific actions, habits, and responses. Problems here are about actions: "I keep procrastinating," "I micromanage," "I avoid the hard call."
  • Capability — the skills, strategies, and internal resources that drive behaviour. Problems here are about what a person can do: "I don't know how to raise money," "I've never led a team this size."
  • Beliefs and Values — what a person believes is true and what matters. Problems here are about meaning and permission: "I'm not the kind of person who can do this," "people can't be trusted," "growth isn't worth the risk."
  • Identity — the sense of who a person is. Problems here are about self-definition: "I'm a fraud," "I'm not a real leader," "I'm the kind who always gives up."
  • Purpose / Spirit — the sense of belonging to something larger than self. Problems here are about meaning beyond the individual: "Why does any of this matter?", "What's this for?"

How Each Level Creates a Different Kind of Problem

The levels stack, and the higher levels govern the lower ones. A belief constrains which capabilities you build. A capability constrains which behaviours you run. A behaviour produces an outcome in an environment. That's why a problem "created" at a belief level can't be genuinely solved by a behaviour patch.

  • A problem at Environment — "Our burn rate is too high because the market shifted" — is usually reframed with context or a strategy change, not by telling the founder their feelings are wrong.
  • A problem at Behaviour — "I keep reacting defensively in investor meetings" — needs a behaviour-level intervention: rehearse a different response, build a pause.
  • A problem at Capability — "I don't know how to structure a negotiation" — needs skill-building and strategy, not a positive label.
  • A problem at Belief — "I'm not cut out for this" — is where content reframing genuinely shines: change the meaning that's blocking the person.
  • A problem at Identity — "I'm a fraud who will get found out" — needs an identity-level reframe, often the deepest and most delicate work.

The practical rule: reframe at the level where the problem was created, not the level where you'd prefer to fix it. Most coaches habitually reframe everything as a belief or identity problem because that's where content reframing lives. When the real problem is a capability gap or an environmental constraint, a belief reframe is not just useless — it's insulting, because it implies the solution is to change their mind about a real obstacle.

The Diagnostic: The SCORE Model — Which Level Needs the Reframe?

Neurological Levels tell you where problems can live. The SCORE model is the diagnostic that tells you which one is active right now. SCORE stands for Symptoms, Causes, Outcomes, Resources, and Effects — and you run it as a structured scan before you ever reach for a reframe.

The Five Columns of the Diagnostic

  • Symptoms — the surface expressions of the problem. What does the person actually notice, feel, or report? "I keep losing key people." "I freeze in pitch rooms." "I'm exhausted by Friday." Symptoms are what the person brings in the door — and most coaching stops here.
  • Causes — the underlying source of the symptoms. What created and maintains them? This is the level scan. Money pressure is an environment cause. A missing skill is a capability cause. A "I can't do this" story is a belief cause. The cause tells you the level.
  • Outcomes — the desired end state. What does the person actually want, stated positively and specifically? Not "stop losing people" but "build a team I can keep and grow."
  • Resources — what's already available to reach the outcome. Skills, relationships, experiences, past wins, strengths. You cannot build an outcome on nothing — you build it from what's already loaded.
  • Effects — the higher-order consequences of reaching the outcome. What changes in their life and scope once this is solved? This is where purpose and identity live: "If I could keep a great team, I'd finally see myself as a real CEO."

How SCORE Decides the Reframe

The scan is not just a form to fill. It is a decision engine. Run it in order and let the columns point:

Step 1 — Identify the Cause level. Listen, then ask yourself: is this cause an environment constraint, a behaviour, a capability gap, a belief, or an identity story? The level of the cause decides the tool. Environment and capability causes rarely respond to reframing at all — they respond to strategy and skill. Behaviour causes respond to rehearsal and structure. Belief and identity causes are where content reframing does its real work. Placement problems in environment are where context reframing shines: the behaviour is a resource, just misfiled.

Step 2 — Check the Resources column before you reframe. You cannot reframe someone into believing they're capable when they have no evidence of capability. Reframing works when it points to something real the person already has — a strength, a track record, a moment that proves the new meaning is true. The reframe is a spotlight, not a fabrication. If the resource doesn't exist, the honest move is not to reframe — it's to build the capability first.

Step 3 — Let the Effects column set the level of the reframe. The person's own highest aspiration — the effect they most want — marks the level where a genuine reframe will land. If their dream is "I'd finally feel like a founder, not a fraud," the reframe belongs at identity, and a behaviour-level pep talk won't hold. Match the level of the reframe to the level of the desired effect.

This is the algorithm most practitioners are missing. Find the cause level → confirm a real resource → match the reframe level to the desired effect. Every reframe you do should pass through those three gates.