Career Bites™.

Leadership burnout is often described as a personal resilience problem. I think that diagnosis is frequently wrong.

After decades working inside automotive engineering, programme delivery and technical leadership, I have watched highly capable people reach the point where determination, intelligence and experience were no longer enough. I have also come uncomfortably close to that point myself.

The common denominator was rarely a shortage of commitment. More often it was a system asking too much of good people for too long: responsibility rising faster than authority, workload rising faster than resources, and seniority somehow being interpreted as an ability to operate indefinitely without support.

For senior engineers, programme leaders and technical specialists progressing towards executive responsibility, this matters. Career progression is not simply about acquiring more responsibility. It is about developing the judgement, boundaries and operating systems necessary to carry that responsibility sustainably.

That lesson took me years to understand.

Leadership at 24: Responsibility Arrived Before Certainty

I was 24 when I stepped into management at Rover Group, working on the programme that would become the Land Rover Freelander. I suddenly found myself responsible for a team of around 40 people, most of whom were older than me and many of whom had considerably more technical experience.

Alongside that came major programme responsibility. The surface engineering and visual-quality data we were creating would ultimately feed tooling decisions carrying enormous financial exposure. Errors made early could become very expensive once steel was being cut.

There were two ways I could have approached that situation.

The first was to behave like the manager: demonstrate authority, provide the answers and ensure everyone understood that I was accountable.

The second was to recognise reality.

I might have been able to write the requirement on a matchbox, but the people around me could have written the book on how to execute it.

So I listened.

That became what I later described as the Two Ears, One Mouth principle. Ask before telling. Diagnose before prescribing. Understand why an experienced engineer disagrees with you before assuming resistance. Leadership authority does not disappear when you admit somebody else knows more than you. In many situations, it becomes stronger.

That experience shaped much of my later approach to engineering leadership. But there was another lesson waiting for me further up the organisation.

As responsibility increases, the consequences of getting the operating system wrong increase with it.

What Causes Leadership Burnout?

Leadership burnout is rarely created by one difficult week or one demanding programme. It develops when sustained demands exceed the resources, control and recovery available to the individual.

In engineering and technical organisations, this can become particularly acute. Complex programmes have immovable launch dates, interdependent systems, global teams, regulatory constraints, commercial pressure and customers who are rarely interested in hearing that the organisation is overloaded.

I have worked in environments where complete vehicle programmes were compressed into approximately 21–23 months. During the hardest phases, 70-hour weeks were not theoretical. They became normalised.

The danger is that high performers can make a poor system look functional for quite a long time.

They compensate.

They work later. They take more onto themselves. They protect their teams. They catch failing interfaces. They attend the meeting nobody else can attend, make the decision nobody else wants to make and carry the problem home with them.

For a while, the organisation sees performance.

What it does not necessarily see is the accumulated debt.

Eventually I watched extremely capable senior people reach their limit. These were not weak performers who lacked resilience. They were experienced leaders who had operated successfully at extraordinarily high levels for years.

That distinction matters.

If organisations treat every case of leadership burnout as an individual resilience failure, they risk sending somebody back into precisely the architecture that exhausted them in the first place.

The Everest Problem: The Higher You Climb, the More Oxygen You Need

I often compare senior career progression with climbing Everest.

At Base Camp, the air is reasonably supportive. As you climb, the atmosphere becomes less forgiving. Small errors matter more. Recovery becomes harder. Decisions carry greater consequences.

Leadership works in much the same way.

As you progress from engineer to manager, manager to senior manager and perhaps eventually into director or executive territory, responsibility increases dramatically. You become accountable not simply for your own output but for people, budgets, timing, customers, risk, strategy and consequences that can spread across an organisation.

You therefore need more organisational oxygen, not less.

That oxygen might mean stronger teams, better information, clearer governance, specialist capability, realistic resource planning, effective change control or simply the authority necessary to make the decisions for which you are being held accountable.

Yet organisations frequently do the opposite.

The leader rises and the support structure becomes thinner.

At some point the response cannot simply be to work harder.

You have to examine the system.

This is one of the most important transitions in senior leadership: moving from being the person who personally solves every problem to becoming the person who creates the conditions in which problems can be solved reliably by the organisation.

That requires another capability which ambitious professionals often find surprisingly difficult.

It requires learning to say No.

Why Saying No Can Accelerate Rather Than Damage Your Career

For much of my career, saying Yes felt safer.

Capable people become valuable partly because they can be relied upon. Give them another problem and they will solve it. Give them a struggling programme and they will steady it. Put something difficult on their desk and they will somehow find a way through.

That reputation is useful.

Until it becomes a trap.

The problem with saying Yes to ten priorities is that you do not have ten priorities. You have ten competing claims on the same finite capacity.

Eventually something gives. Sometimes it is quality. Sometimes strategic work gets displaced by urgent work. Sometimes the team absorbs the pressure. Sometimes family does. Sometimes health does.

The answer is not indiscriminate refusal. It is what I call the Strategic No.

A Strategic No is evidence-led.

When another major task arrives, the question is not simply, Can I do this?

A better sequence is:

Does this contribute directly to my core objectives? Does it support the organisation's genuine priority? What will move if I accept it? What resource is required? What risk am I accepting elsewhere?

That changes the conversation.

Instead of telling a senior stakeholder, “No, I am too busy,” you are able to say, in effect: “We can do this. Here are the resources required, here is the impact on the existing programme and here is the decision we need to make about priority.”

That is not avoidance.

It is leadership.

The Iceberg of Decision-Making

One reason people struggle to challenge unrealistic work is that they lack evidence.

I think of major decisions as an iceberg.

Above the water are the things everyone can see: headcount, hours, deadlines and perhaps a crude cost number. These are easy to discuss because they are visible.

Below the surface sits the information that actually determines whether the commitment is credible: technical complexity, assumptions, interfaces, capability gaps, programme maturity, verification requirements, change exposure, customer dependencies and accumulated risk.

Weak decisions are often made from the visible section of the iceberg.

Experienced leaders push more of the iceberg above the water before committing.

This is where technical depth becomes commercially valuable. Your expertise is not there merely to solve problems after they happen. It enables you to identify the assumptions that make a proposed plan unrealistic before the organisation commits to it.

The confidence to say No is therefore not built through assertiveness training alone.

It comes from competence, evidence and preparation.

When you know why something will not work, can demonstrate the consequences and can propose a viable alternative, No stops sounding negative.

It becomes professional judgement.

From Willpower to Systems

Another lesson from engineering has influenced almost everything I subsequently built in career development: do not rely on heroics when a repeatable system can do the job better.

Engineering understands this intuitively.

Consider something apparently mundane such as an interior A-pillar trim. There are design requirements governing material, thickness, attachment, removal, durability and verification. We do not hand a new engineer a blank sheet of paper and say, “Use plenty of determination.”

We give them standards, design rules, requirements, review processes and test procedures.

The system protects the result.

Yet professionals frequently run their own careers without anything remotely comparable.

Work arrives through email, Teams, meetings and corridor conversations. Everything appears urgent. Priorities are held in somebody's head. Career development happens whenever the operational workload temporarily allows it—which generally means it does not happen at all.

That is why relatively simple operating disciplines can make such a difference.

I still use the logic behind the Eisenhower Matrix: distinguish what is genuinely urgent and important from what should be scheduled, delegated or removed. I use constrained periods of focused work because interruption destroys cognitive efficiency. I question deadlines because work has an extraordinary ability to expand into whatever time we allocate to it.

None of these methods is revolutionary.

Their value lies in turning good intentions into a repeatable operating rhythm.

The principle applies equally to career management.

When I developed Career OS™, I deliberately treated career development more like an engineering system: diagnosis before action, positioning before applications, evidence before claims, targeted search rather than uncontrolled activity, structured interview preparation and deliberate negotiation.

The objective is not bureaucracy.

It is to remove unnecessary randomness.

When Work, Family and Health Begin Competing

The hardest part of my own experience was recognising that professional success can hide personal deterioration remarkably well.

Higher earnings create options, but they can also create commitments. Lifestyle grows. Outgoings rise. The salary that once represented freedom can gradually become the mechanism that prevents you from changing anything.

I eventually thought about it as three overlapping circles: Work, Family and Health.

For short periods, one circle can dominate. Major programme launches happen. Crises happen. Families sometimes need everything you have. That is normal.

The problem begins when one circle is allowed to consume the others permanently.

For me, work had become disproportionately large.

There was another, less sophisticated measure too. I called it TCTF: Too Close To Fridge.

Remote working, long hours, constant pressure and convenience had created a lifestyle that was productive on paper and increasingly poor in practice.

My partner eventually gave me a much more useful performance target than another corporate KPI: live to 100.

That landed.

Not because I believed I was literally planning the next 40 years around a number, but because it exposed the absurdity of building a career that looked successful while undermining the ability to enjoy the results.

My Strategic Exit Was Not Retirement

I eventually made a deliberate change.

I reduced my overheads, moved for a period to Southeast Asia and removed some of the financial leverage that had made high-pressure corporate roles feel compulsory.

I think of that now as demanaging my life.

It was not a retreat from ambition. It was a redefinition of what ambition was supposed to achieve.

Removing some of those constraints gave me the freedom to redirect decades of engineering, leadership, hiring and programme experience into Eich Dyn Career Services and the development of Career OS™.

It also changed the way I think about senior career development.

Sometimes the right answer is MOVE: changing organisation, role, sector or direction.

Sometimes it is not.

Many experienced professionals still enjoy their industry, organisation or specialist field. They do not necessarily want an escape. They want greater influence, better positioning, more control, stronger progression and a career that uses their capability without consuming everything around it.

That is the territory behind PROPEL.

The question is not simply, “How do I get promoted?”

It is more demanding:

How do I build a career that can carry the next level of responsibility without recreating the conditions that made the previous level unsustainable?

Sustainable High Performance Is an Engineering Problem

I no longer believe sustainable high performance begins with working harder.

It begins with architecture.

Do you understand what is actually expected of you? Do you have the authority and resources to deliver it? Can you distinguish real priorities from organisational noise? Do you have evidence strong enough to challenge impossible commitments? Have you developed people who can carry responsibility without everything returning to your desk? And are you managing your career deliberately rather than simply responding to whatever arrives next?

Those questions are as relevant to a senior engineer approaching management as they are to a director carrying a multinational programme.

Career progression should expand your impact.

It should not progressively remove your oxygen.

A Short Leadership Burnout Diagnostic

If work is beginning to feel permanently unsustainable, I would examine six things before concluding that you simply need to become more resilient:

• Objectives: Can you name the three outcomes that genuinely define success in your role?
• Capacity: Does the workload realistically fit the people, time and capability available?
• Authority: Are you empowered to make the decisions for which you are accountable?
• Boundaries: What are you continuing to accept that should now require a Strategic No?
• Systems: Which recurring problems still depend upon personal heroics rather than a repeatable process?
• Direction: Is the role still taking your career somewhere you actually want to go?

If those answers expose structural problems, another productivity application is unlikely to solve them.

You may need a better operating system.

And occasionally, you may need a different destination.

Reclaiming Control

My own journey from engineering leadership into career consulting for senior leaders was not a rejection of ambition. If anything, it sharpened it.

I still believe in demanding standards, difficult objectives and extraordinary performance. I have spent too much of my career around exceptional engineers and programme teams to argue otherwise.

What changed was my definition of high performance.

Performance that can only be sustained through exhaustion is not high performance. It is borrowed capacity.

Eventually the debt becomes payable.

The better objective is to build the judgement, systems, support and career strategy that allow you to perform at a high level repeatedly—without sacrificing everything else required to make the achievement worthwhile.

That is the lesson I wish I had understood much earlier in my career.

And it is one I now bring directly into Eich Dyn, Career OS™ and PROPEL.

If your career is progressing on paper but becoming increasingly difficult to sustain in practice, start with the architecture rather than blaming the individual. Diagnose what is consuming the oxygen. Decide what must change. Then build the system around the career you actually want.