All lessonsState & Mindset

The Five Drivers That Burn Founders Out — And the NLP Drivers Check That Turns Them Off

I built companies on 80-hour weeks and called it discipline. Then my body cashed the cheque. Taibi Kahler's five drivers — Be Perfect, Please, Try Hard, Be Strong, Hurry Up — are the hidden software running leaders who cannot stop. Here is how to see yours and reset it.

2026-08-31 3,028 words 16 min read

The Moment I Called Burnout Discipline

I built my first companies on eighty-hour weeks. I was proud of it. I told myself the grind was the price of the outcome, and every time I saw the numbers move I took it as proof the equation worked.

Then the equation failed. Not slowly. Not with a warning. My body stopped taking the orders. I hit the wall most founders describe as exhaustion and I hit it at speed, flat against a point where more effort produced less, then nothing, then damage. I was not overworking my way toward leverage. I was overworking my way toward a shutdown that was one bad quarter away.

The uncomfortable truth is that nobody told me to work that hard. Nobody set the requirement. I installed it myself, one self-congratulatory night at a time, and I installed it so deep that I defended it as a virtue. That is what a driver does. It does not arrive as a therapist with a clipboard. It arrives as your own voice, sounding reasonable, telling you exactly what you have to do before you can rest.

There is a name for this in the discipline I teach. It came out of a psychologist named Taibi Kahler, who in 1975 published a paper on the recurrent behavioural patterns he kept seeing in therapy clients, patterns that survived insight, feedback, and resolution attempts. He called them drivers. Neuro-Linguistic Programming took the model up, and almost every practitioner since has used it, because it describes the exact software running the founders I meet in rooms year after year. Including me.

Here is what that looks like in practice. I remember sitting with a founder after his third near-miss on a fundraising round. He was not short on ability. He was short on a driver he could not name. Every question I asked, he answered by describing what he still needed to do, what he had not polished yet, what would look bad if it slipped. He was not planting a stake in the deal. He was running a script that said everything must be perfect before it deserves to exist. The round was not his obstacle. The script was.

Let me be direct about what we are dealing with. The driver is not a strategy. It is a permission sentence your unconscious plays before you act, and it spends decades sounding like the responsible thing to do. This article names the five drivers, shows you where each one came from, and gives you the calibrated reset that turns them off before your calendar does it for you.

Where the Five Drivers Came From

The drivers did not begin as an NLP concept. They began as clinical observation. In the early 1970s, Taibi Kahler was working within transactional analysis, the framework Eric Berne had built, and he noticed something Berne's script theory did not fully explain. Clients kept repeating the same maladaptive behaviour even after they understood the psychological history behind it. Understanding the past was not changing the present.

Kahler's 1975 article, published in the Transactional Analysis Journal, proposed that underneath these repeating scripts sat a set of behavioural drivers, short sequences people run so automatically they vanish from awareness. He identified five of them, each with its own motivating sentence: Be Perfect, Please, and what later became the matched set of Try Hard, Be Strong, and Hurry Up. The exact framing settled over time, but the core list held. These are not personality types. They are default operating modes, and every person has a lead driver and a tail of weaker ones.

NLP adopted the model because it fit the discipline's central move: when you study how people do something, you find a repeatable structure, and once you name the structure you can interrupt it. The drivers are structure. They are the behavioural architecture behind patterns people have been describing as character for their whole lives. A founder who cannot delegate is not stubborn. A founder who re-writes a slide for the eleventh time is not meticulous. Both are running a driver that will keep producing the same output until something interrupts the loop.

The research lineage matters here, and I want to be honest about it. Kahler's work is grounded in clinical observation and decades of applied practice, and it has been widely absorbed into coaching and leadership development. It is not, and I will not dress it up as, a controlled clinical trial. NLP is a modeling discipline. The mechanism sections of this article are modeled from real coaching and therapeutic practice, and they are offered as practiced teaching methodology, not as empirically proven intervention. The citations at the end support the underlying behavioural mechanisms referenced. What I can tell you from the inside is that I have watched these five sentences run entire companies, including my own, and naming them changes what you can do with them.

The Mechanism in Plain English: A Permission Sentence Before Every Act

Here is how a driver actually operates, stripped of jargon.

Before you take an action, your mind runs a quick internal check. Most of it happens below awareness. The check asks, in effect, whether you have permission to proceed. For most people most of the time, the check passes silently and the action happens. But when a driver is in charge, the check returns a specific, repetitive verdict, and the verdict tells you what is still missing before you can earn rest, approval, or safety.

Each of the five drivers has its own verdict. The Be Perfect driver tells you nothing is finished until it is flawless, and flawless is not available, so nothing is ever truly finished. The Please driver tells you your safety depends on everyone approving of you, so you keep spending energy maintaining approval that was never in your control. The Try Hard driver tells you effort itself is the measure of worth, so you generate activity that passes for progress. The Be Strong driver tells you showing need is weakness, so you carry loads alone and call it independence. The Hurry Up driver tells you it is always almost too late, so you trade depth for speed and call it urgency.

Here is the part that makes the driver expensive. The driver is not asking whether the action serves the outcome. It is asking whether the action satisfies the sentence. That is why a founder can work eighty hours and still feel behind, why a founder can win the round and still feel unqualified. The outcome arrives and the driver does not care, because the driver was never about the outcome. It was about the permission sentence, and the sentence has no completion condition you can meet from outside.

I want to bring a second line of evidence in, because it explains why the driver holds so stubbornly. The cognitive therapist Albert Ellis spent his career documenting the power of absolute, evaluative beliefs, the internal imperatives he called the musts and the shoulds. Ellis's central observation, carried through decades of rational emotive behaviour therapy, was that emotional distress is rarely caused by the event itself but by the rigid demand we attach to it, the belief that things absolutely must go a certain way. The drivers are structurally identical. Be Perfect is a must about your own performance. Please is a must about what other people think. The founder who runs on these is not responding to the market. They are responding to an internal demand the market never issued, and Ellis showed that this kind of demand is the engine of anxiety, guilt, and chronic stress.

The mechanism, translated to the boardroom: your driver is a must wearing the costume of responsibility. You cannot outwork a must. You can only catch it running and interrupt it before it spends your energy.

The Founder Cost of Each Driver

Let me walk through what each driver actually costs a leader, because the abstract list hides real money.

Be Perfect blocks. The perfectionist founder does not ship, does not delegate, does not publish, because nothing is ready yet. The cost is missed windows, delayed launches, and a team trained to wait for permission that never comes. Perfectionism feels like standards. It functions like a parking brake.

Please flattens. The pleaser founder cannot deliver hard feedback, cannot push back on a partner, cannot say no to a bad deal, because their safety is welded to approval. The cost is a company shaped by whatever the last loudest person wanted. Pleasing feels like harmony. It functions like the absence of a spine.

Try Hard performs. The try-hard founder confuses motion with progress, busy with effective, effort with outcome. They are the most tired person in the room and the least able to explain what the room achieved. The cost is activity that produces activity and a definition of success that never clocked out.

Be Strong isolates. The strong founder will not ask for help, will not show a crack, will not admit the load is terminal. They become the single point of failure their own company cannot survive losing. The cost is the loneliness at the top made literal: decisions carried alone, errors compounded alone, burnout absorbed alone.

Hurry Up rushes. The hurry-up founder trades calibration for speed, depth for momentum, sleep for reaction. They are the first to move and the last to check the map. The cost is the decision you regret for years, made in the forty minutes you would not take to think.

You know the type because I have met all of them in myself. I ran Try Hard and Be Strong as a combined system for years. I measured my worth in hours worked and in carrying problems alone that I could have shared. The eighty-hour weeks stopped not because I decided they were wrong but because I finally named what was driving them, and naming a thing is the first move toward choosing it instead of obeying it.

Why Willpower Fails and Calibration Works

If the driver is a permission sentence, the obvious remedy seems to be telling yourself to stop. It does not work, and it does not work for a structural reason.

Willpower is a conscious command aimed at a behaviour, but the driver lives below the behaviour. You can resolve at nine in the morning not to re-read the slide, and at nine-fifteen your unconscious runs the Be Perfect sentence and your hand opens the file again. You lost the argument before you had it, because you were arguing with your behaviour while the driver ran your perception of what the slide needed. This is why every founder who says "I will not work weekends this quarter" and then works weekends is not weak. They are running a driver they have not yet learned to see.

The NLP answer is not to fight the driver with force. It is to interrupt it with calibration. Calibration means noticing the exact moment the permission sentence starts, before the behaviour it orders. The driver always announces itself with a repeatable internal cue, a tightening, a phrasing, a familiar refrain, your mind reaching for the same verdict. Catch the cue and you have caught the loop before it spends the month.

There is a second reason enforced rest backfires. When you deny yourself the outcome the driver demands, the driver does not quiet down. It escalates, because it believes the outcome is the point and that you are endangered without it. The Be Perfect driver denied perfection does not relax. It tightens. So the reset is not about deprivation. It is about replacing the driver's verdict with a deliberate one, and doing it consistently enough that the old sentence loses its standing. This is exactly the supervised repetition the discipline is built on. You do not read your way past a driver. You practise the interrupt until the new behaviour outruns the old command.