Neuro-Logical Levels: A Planning Tool, Not a Workshop
Most people meet Neuro-Logical Levels in a workshop. Someone draws six stacked boxes on a flipchart, the room fills them in, everyone feels clearer, and the sheet goes in a drawer. By Monday, the week runs exactly as it did before.
That's a waste of a good tool. Used properly, Neuro-Logical Levels isn't a reflection exercise. It's a planning tool. It tells you why a goal keeps stalling, where to put your effort first, and what actually needs to be on your calendar this week.
This post walks through one goal, level by level, and shows how each answer turns into something you can schedule.
How the levels work as a planning tool
The model, developed by Robert Dilts, sorts any change into six levels:
- Purpose: why this matters, and to whom.
- Identity: who you need to be to achieve it.
- Beliefs & values: what you hold true about the work, and what you won't compromise.
- Capabilities: the skills and strategies it requires.
- Behavior: what you actually do, day to day.
- Environment: where, when, and with whom it happens.
The principle that makes it useful for planning is simple: a problem at one level is usually solved one level above it. A behavior problem ("I never get to the strategic work") is rarely fixed by a better calendar app. It's fixed by a capability you're missing, or a belief that keeps pulling you back into old habits.
So you use the levels in two passes:
- Top-down to design. Start at Purpose and work down. Each answer sets the requirements for the level below it.
- Bottom-up to diagnose. Start at Environment and work up. At each level, ask: "Does this support the level above it?" The first "no" is your real constraint.
One goal, six levels
The example below is an illustration, a composite of the kind of goal we see with owners, not a specific client.
Marcus owns a 25-person home-services company. His goal: open a second location within 12 months. It's been "this year's goal" for two years running. Here's what the levels show.
1. Purpose: why does this matter?
First answer: "To grow revenue."
That's true, but it's not specific enough to plan from. Pushed further, Marcus gets to the real reason: his company turns away customers on the north side of town every week, and his best technicians are leaving because there's nowhere to move up.
What goes in the plan: two success measures that don't depend on revenue alone. The new location is open and taking north-side calls, and one of his current lead technicians is running it.
2. Identity: who do you need to be?
Today: "I'm the best technician in the company." He still runs service calls most days, and customers ask for him by name.
Required: "I'm the owner who builds operators." Two locations can't run on one person's hands.
What goes in the plan: Marcus stops taking service calls two days a week, starting next month. That's an identity decision written as a calendar rule.
3. Beliefs & values: what do you hold true?
The belief in the way: "Nobody quotes a job like I do. If someone else quotes it, we'll lose money or lose the customer."
The value underneath it: reliability. Customers trust the company because the quote is the price.
This is the level where the goal has been stalling. As long as Marcus believes only he can quote, he can't step out of daily operations, and he can't open a location he won't be standing in.
What goes in the plan: keep the value and test the belief. He writes down his quoting standard (what he checks, how he prices, when he walks away) and has his lead technician quote ten jobs against it, with Marcus reviewing each one.
4. Capabilities: what skills does this require?
Listing what the goal requires, then marking what's missing, gives Marcus four gaps:
- A documented quoting standard others can follow.
- A location manager who can hire and schedule.
- A financial model for a second site: lease, trucks, staffing, break-even.
- Site selection based on where the turned-away calls actually come from.
What goes in the plan: each gap becomes a project with an owner and a date. Marcus owns the quoting standard and the model. His office manager pulls the turned-away call data. His lead technician starts management training.
5. Behavior: what do you actually do each day?
Current week: about 20 hours on service calls, 10 hours on quoting, and the rest on email, dispatch questions and payroll. Zero hours on the expansion.
What goes in the plan: six hours a week of protected time for the expansion, split into two three-hour blocks, plus 30 minutes on Friday to review progress. Everything else has to fit around those blocks, not the other way around.
6. Environment: where and with whom does it happen?
Current setup: his desk sits next to dispatch, his cell number is on every invoice, and the team calls him for every exception.
What goes in the plan: Tuesday and Thursday mornings are spent off-site. Dispatch routes questions to the lead technician first, and the office number replaces his cell on invoices.
The whole plan on one page
| Level | Question | Marcus's answer | What goes in the plan |
|---|---|---|---|
| Purpose | Why does this matter, and to whom? | Serve turned-away customers; give top techs a path up | Success = location open and run by a current lead tech |
| Identity | Who do I need to be? | From "best technician" to "owner who builds operators" | No service calls two days a week |
| Beliefs & values | What do I hold true? | "Only I can quote." Value: reliability | Written quoting standard; lead tech quotes 10 jobs |
| Capabilities | What skills does this require? | Quoting system, manager, financial model, site data | Four projects, each with an owner and date |
| Behavior | What do I do each day? | 0 hours a week on expansion | Two 3-hour blocks a week + Friday review |
| Environment | Where, when, with whom? | Desk beside dispatch; cell on every invoice | Off-site Tue/Thu mornings; calls routed to lead tech |
Now run the bottom-up check. The environment changes support the new behavior. The behavior supports building the capabilities. But the capabilities stall at the belief level: as long as "only I can quote" stands, the quoting standard never gets written. That's the constraint. So the first task on Marcus's list isn't scouting a site. It's writing down how he quotes a job.
Two years of "this year's goal" came down to one belief that nobody had written down.
Four mistakes that turn it back into a workshop
- Starting at the bottom. Changing the environment first (a new app, a new office) feels productive, but it doesn't hold if the levels above it haven't moved.
- Writing identity as a slogan. "I'm a leader" doesn't change a calendar. "I'm the owner who doesn't take service calls on Tuesdays" does.
- Writing beliefs as wishes. The useful beliefs are the ones that are in the way right now, stated honestly, not the ones you'd like to have.
- Stopping at the answers. Every level needs a "what goes in the plan" line. If an answer doesn't change what you'll do this week, it's not finished.
Run it on your own goal in 20 minutes
- Write one goal at the top of a page. Just one.
- Purpose: Why does this matter, and to whom? Keep asking "why" until the answer is specific.
- Identity: Who am I today in relation to this goal, and who do I need to be?
- Beliefs & values: What do I believe that's in the way? What value do I need to protect?
- Capabilities: What does this require that I or my team can't do yet?
- Behavior: Where does my week actually go right now?
- Environment: What around me makes the old pattern easy?
- Next to each answer, write one line: what goes in the plan.
- Check bottom-up. Circle the first level that doesn't support the one above it. Put that on your calendar first.
Where this fits. Neuro-Logical Levels is step one of the Focused Systems Method: Clarify & Align. The method then turns your answers into daily systems and handles the mindset work that keeps them running.
Want help running it? In a 30-Minute Strategy Session, we'll take one goal through all six levels together and find your constraint. Or work through it on your own with the Executive Planner.
Continue from strategic alignment into execution with 6-Step Reframing, the weekly review for leaders, or Executive Coaching.
