Above and below the line leadership comes down to one question, asked at the worst possible moment: right now, am I open and trying to learn, or closed and trying to be right? That’s the line. Every leader crosses it several times a day. What most leaders never work out is that the crossing isn’t private. Your team watches you do it, they know before you do, and they set their own response to pressure off yours.
I’ve spent more than 10,000 hours in coaching rooms with founders and their teams, and this is the pattern I’d put money on every time: the team doesn’t respond to the pressure. The team responds to what the pressure does to the leader.
This piece is about the move that changes that. Not learning the framework, most leaders can learn it in two minutes. Saying it out loud, in front of the people you lead, at the moment it costs you something.
01What is above and below the line leadership?
At any moment you’re in one of two places. Above the line: open, curious, committed to learning. Below the line: closed, defensive, committed to being right. There’s no middle ground. Above and below the line leadership means knowing which side you’re on, moment to moment, and being honest about it, because the quality of your thinking depends on your location, not your knowledge.
The model comes from The 15 Commitments of Conscious Leadership by Jim Dethmer, Diana Chapman and Kaley Klemp, and I’ve built it into a full protocol, The Location of Leadership, free in the Source Code library. That page teaches the model properly: the two locations, the 30-second locate, the shift. Go read it. This article is about a different question. What happens to a whole team when the leader stops running the check silently and starts naming it out loud?
An everyday example first, because the line is easier to feel than to define. A big client emails at 4pm: they’re reviewing the contract. Below the line, you forward it to your head of sales with “What did you do?” Above the line, you walk over and say “Okay, this scares me a bit. What do we actually know?” Same email. Same facts. Two completely different companies for the next 48 hours.
02Under pressure, your team reads you before they read the problem
Nobody tells founders this part. When something goes wrong in a company of 15 to 60 people, the first thing every person in that room does is check the leader’s face. Not the numbers. Not the plan. Your face. Humans are wired that way. Before your team decides what the problem means, they decide what it means to you.
So when you drop below the line, and you will, everyone does, the drop broadcasts. Your questions get sharper. You interrupt more. You start defending last quarter’s decision instead of examining this quarter’s problem. You’d call it stress. You’d call it urgency. Most leaders deny that it’s fear. They call it stress, they call it overwhelm, they call it “just being direct.” It’s fear. And your team smells it in about four seconds.
Then they respond the only rational way people respond to a defensive leader: they protect themselves. Bad news arrives later and softer. Ideas get pre-shrunk before they reach you. The person who knows the uncomfortable fact sits on it, because the last person who surprised you got interrogated. None of this shows up in any metric. It shows up three weeks later, when you find out the thing everyone else knew.
This is why “stay calm under pressure” is such useless advice. Your team doesn’t need you calm. Calm can be faked, and faked calm reads as danger anyway. What your team needs is to know where you are. Which brings us to the move.
03What changes when you name the line out loud
The move is one sentence, said in front of your team, at the moment you’d least like to say it:
“I think I’m below the line on this. Give me a second.”
That’s it. Not a speech. Not an apology tour. A location report.
I’ve watched this single habit change how teams handle pressure more than any process I’ve seen, and I’ve seen a lot of process. Here’s what it actually does, mechanically, to the people in the room.
It separates the danger from the leader. When you’re silently below the line, the team has two threats to manage: the problem, and you. All the energy that should go into solving goes into reading you, softening things for you, working around you. The moment you name your own state, you stop being the second threat. You’ve told them the storm has a weather report. Now everyone can face the actual problem, together, instead of facing you.
It makes honesty cheaper than performance. Amy Edmondson’s research on psychological safety, and Google’s Project Aristotle after it, found the same thing from different directions: the teams that perform under pressure are the ones where people can say risky things without paying for it. Google’s own two-year study of its teams, reported in the New York Times, put psychological safety at the top of the list, above talent, above experience. Naming your line is the cheapest psychological safety intervention that exists. If the founder can say “I’m defensive right now because I’m scared this makes me look like I missed it,” then the engineer can say “the release isn’t ready.” You’ve priced honesty at what it should cost: nothing.
It hands the team the language, and language is the tool. The first few times you name your line, it’s a confession. By the second month, it’s vocabulary. Someone in a heated product review says “I reckon we’re all a bit below the line on this one, can we come back after lunch?” and twenty minutes of posturing just didn’t happen. That sentence is doing what a whole conflict-resolution workshop tries to do, in eight seconds, because everyone in the room shares one honest map of what’s going on. Culture is what people do when you’re not in the room. When your team runs the locate without you, that’s the framework becoming culture.
It kills the victim, villain and hero roles before they start. Below the line, people grab one of three roles. Victim: “this always happens to us.” Villain: “whose fault is this?” Hero: “stand back, I’ll fix everything myself.” All three feel productive. None of them are, because all three are about the people instead of the problem. A leader who names the line publicly makes all three roles embarrassing to play. Hard to hunt for a villain when the boss just admitted to being scared.
None of this makes you soft, and it’s worth saying so, because that’s the fear that stops most founders from ever doing it. Naming the line doesn’t mean the standard drops. You can be above the line and still say “this work isn’t good enough.” In fact that’s the only place you can say it from and have it land as feedback instead of attack. Clear is kind. The line isn’t about being nice. It’s about which part of your brain is running the meeting.
Ready to see what this looks like inside a real coaching engagement? Book a Discovery Call.
04A founder, a bad number, and two versions of the same meeting
A composite from years of these rooms. A founder, 40 people, and the monthly numbers land 30 per cent under forecast, in front of the leadership team, with a board meeting nine days out.
Version one, the one I’ve watched a hundred times. His jaw sets. He starts asking questions that are really accusations wearing question marks. “Didn’t we say this pipeline was solid?” The head of sales starts defending her forecast. The head of product quietly decides this is not the meeting to mention the churn signal he spotted on Tuesday. Ninety minutes of energy goes into who’s right about the past. The actual problem, why the number moved and what to do in the next nine days, gets 15 minutes at the end, done badly, by tired people.
Version two is the same founder, a year into practising this. The number lands. He feels the same heat in his chest, same tightening, same urge to find the person who owes him an explanation. And he says: “Right, I want to name something. I’m below the line. That number scares me because I told the board a different one. Give me a minute, then let’s work the problem.”
Watch what his team does with that. Shoulders drop, visibly. The head of sales doesn’t have to spend the meeting defending herself, so she doesn’t. She opens with the three deals that slipped and what she believes actually happened. The head of product mentions the churn signal, the thing that in version one stays hidden for another month. Within 40 minutes they’ve found that two of the slipped deals share a cause, and there’s a plan with names on it before anyone leaves.
Same founder. Same number. Same fear. The only variable is that in version two, the fear got named instead of leaked. That’s the whole difference, and it compounds every month, because his team is learning something in every one of those meetings: pressure here is something we face together, not something we hide from each other.
That’s antifragility in the flesh, by the way. Not a team that avoids hits. A team that gets more honest, and therefore smarter, every time it takes one.
05How to make naming the line a team habit
Three steps, in order, and the order matters.
Go first, and go first for a while. You cannot install this by announcement. If you introduce the framework at an offsite and then never name your own line, you’ve just handed your team a stick to silently judge you with. The rule of thumb I give founders: name your own location out loud, in real meetings, at real cost, for a month before you expect anyone else to try it. You’re not teaching a model. You’re proving it’s safe.
Teach it in one sitting, plainly. Once you’ve been doing it, give the team the map. Two locations, no middle ground. Fear underneath, even when it’s dressed up as stress. The locate: pause, ask where am I, accept the answer without shame, then choose whether to shift. Send them to The Location of Leadership for the full version. Ten minutes. Don’t turn it into a program.
Never use it as a weapon. One hard rule: the line is for locating yourself, not diagnosing others. “You’re below the line” is an attack wearing the framework’s clothes, and one leader using it that way will poison the whole tool. The only move you make on someone else is an invitation: “Where do you reckon you are on this one?” If you hear the framework being used to score points, name that, above the line, the same day.
Do those three things and you’ll notice the same shift I see in every team that takes this on: pressure stops scattering people and starts gathering them. This is also the front door to a bigger change. A team that can be honest about state is a team you can actually coach, and coaching your team is how employees become owners. I’ve written the full case for that in The Coaching Standard: How to Turn Your Team Into CoFounders, and the practical companion on coaching your team to think like owners shows what the week-to-week reps look like.
06The line is the leadership
This is where it lands after 18 years of watching leaders under pressure. Your team will never respond to pressure better than you do. Not because they can’t, because they’re taking their cue from you, every single time, whether you like it or not. You can’t opt out of broadcasting your state. You can only choose whether the broadcast is honest.
So the framework isn’t really the two-minute model. The framework is the sentence. “I’m below the line on this, give me a minute.” Say it this week, in a meeting where it costs you something, and watch what your team does with the permission you just gave them.
If you want a coach in the room while you build this into how your company handles pressure, Book a Discovery Call.