Leadership Transition Framework

INTRO Introduction and How to Use This Framework

The Leadership Transition Framework

Michael Linke | Linke Leadership

Harvard Advanced Management Program (AMP 210)

© 2026 Linke Leadership. All rights reserved.

About This Framework

This framework was built for one specific person: a highly capable operational professional who is ready to lead, but has not yet been given the tools to do it well.

You have proven yourself. You deliver results. You are reliable, skilled, and respected for what you do. That is exactly why someone looked at you and thought: this person should be a leader.

The problem is that nobody told you what changes when you make that move. And almost everything changes.

Operational success is largely about personal capability — your skill, your effort, your expertise. Leadership success is fundamentally different. It is about creating capability in others. It is about delivering outcomes through people rather than through your own effort.

That shift is harder than it sounds. It requires a different mindset, different skills, and a different relationship with your own identity as a professional. Most organisations promote strong performers into leadership roles and then leave them to figure it out. This framework gives you what those organisations failed to provide.

Who This Framework Is For

This framework is written for:

• Operational professionals who have recently moved into a leadership role
• High performers who are being considered for leadership and want to prepare
• Team leaders and project managers who manage work but not yet people
• Anyone who has been told they have leadership potential but hasn't been shown what to do with it

How It Is Structured

The framework is built around ten pillars. Each pillar addresses a fundamental shift that operational people must make to become effective leaders. At the end of each pillar is a Transition Moment — a real scenario that illustrates the shift in practice.

The ten pillars are:

• Pillar 1: The Mindset Shift — from expert to leader
• Pillar 2: Emotional Intelligence — from reaction to awareness
• Pillar 3: Leading Conversations — from avoiding to engaging
• Pillar 4: Coaching Rather Than Directing — from telling to asking
• Pillar 5: Building High-Performing Teams — from individual to collective
• Pillar 6: Influence Without Authority — from position to persuasion
• Pillar 7: Strategic Thinking — from today to tomorrow
• Pillar 8: Leading Change — from stability to movement
• Pillar 9: Personal Leadership and Resilience — from output to sustainability
• Pillar 10: Creating the Environment for Success — from self to system

How to Use This Framework

Work through the pillars in order. Each one builds on the last. Use the Transition Moments as reflection tools — they are designed to surface the gap between knowing something intellectually and applying it under pressure.

The AI search tool in this framework lets you ask practical questions and get answers drawn directly from the content. Use it when you face a real situation and need guidance quickly.

The resources section contains templates, tools, and planning guides that you can download and apply immediately.

This framework will not tell you everything about leadership. No framework can. What it will do is give you a grounded, practical foundation for the most important transition of your professional life.

A Note on How to Read This Framework

This is not a framework you read once and put down. It is a reference you return to as your leadership situations change. A section that feels abstract when you first read it may become acutely relevant six months later when you are in the middle of exactly the situation it describes.

Resist the temptation to read straight through and tick off each section as done. Leadership development does not work that way. Understanding something intellectually is only the beginning. The work is in applying it, observing what happens, and adjusting.

Use the AI search tool to help you. When you face a specific situation — a difficult conversation, a team that is not performing, a stakeholder relationship that is not working — ask it a direct question. The framework contains the guidance. The AI helps you find the part that is most relevant to where you are right now.

The Research Behind This Framework

The Leadership Transition Framework draws on thirty years of applied leadership experience, combined with the most robust research on leader development from institutions including Harvard Business School, Centre for Creative Leadership, and Deloitte's Global Human Capital research division.

The frameworks woven through this content include Daniel Goleman's model of emotional intelligence, Patrick Lencioni's work on team dysfunction, Amy Edmondson's research on psychological safety, William Bridges' transition model, and the leadership development research of Robert Kegan and Lisa Laskow Lahey on immunity to change.

Each of these bodies of work has been adapted and grounded in practical application for leaders in operational and middle-management roles. The theoretical foundations are solid. The application is practical.

A Framework Built on Experience, Not Theory

The frameworks and models in this resource — Goleman's EQ pillars, Lencioni's five dysfunctions, Edmondson's psychological safety research, Bridges' transition model — all have strong empirical foundations. But the integration across this framework, and the way it has been applied to the specific challenge of the operator-to-leader transition, draws on thirty years of working with leaders at every level, in organisations of every size, across sectors including healthcare, professional services, technology, government, and not-for-profit.

What that experience consistently confirms is that the challenges described in this framework are not abstract. They are the real struggles of real leaders, repeated across organisations and generations. The mindset trap, the difficult conversation avoided, the team that never quite gels, the strategic thinking that never quite happens — these are universal. The difference between leaders who navigate them well and those who do not is not talent. It is having the tools, the self-awareness, and the commitment to keep developing.

This framework gives you the tools. The self-awareness and commitment are yours to bring.

P1 The Transition Nobody Prepares You For

The Transition Nobody Prepares You For

Operational success is largely about personal capability. Leadership success is largely about creating capability in others.

You were promoted because you were excellent at something. You could be trusted to deliver. You understood the work deeply. You set the standard others were measured against.

And then, almost overnight, none of that is the point anymore.

In your new role, the goal is not for you to do the work well. The goal is for your team to do the work well. Your expertise — the thing that got you here — is no longer the primary measure of your success. The measure of your success is now what other people achieve because of how you lead them.

This is the leadership transition, and it is harder than almost anyone who hasn't lived it can appreciate.

Most organisations handle this transition badly. They promote a strong performer, give them a new title, perhaps a pay rise, and then send them back into the workplace expecting leadership to flow naturally from competence. It does not. Leadership is a different discipline. It requires a different orientation, different skills, and a willingness to let go of the things that made you successful before.

This pillar addresses the foundation of that shift. If you do not get the mindset right, the skills in every other pillar will be undermined.

The Six Shifts

The transition from operator to leader can be understood through six fundamental shifts:

• From delivers work to delivers outcomes through others — your measure of success is no longer your personal output, but what your team produces
• From solves problems to builds problem-solvers — you stop being the answer and start developing the people who find answers
• From controls quality to creates systems for quality — you build the standards, processes, and culture that make quality consistent without your constant involvement
• From focuses on tasks to focuses on people and culture — the team's capability, wellbeing, and alignment become your primary focus
• From uses expertise to uses influence — you stop solving through knowledge and start leading through relationships and trust
• From measures activity to measures impact — you evaluate success by outcomes and team development, not by how busy everyone looks

These shifts do not happen automatically. They require deliberate practice, honest self-reflection, and sometimes the uncomfortable experience of doing less in order to achieve more.

The Statistics Behind the Problem

The failure rate for newly promoted leaders is startling. Research by the Centre for Creative Leadership found that approximately 40 percent of new leaders fail in their first 18 months. DDI Global Leadership Forecast research consistently finds that fewer than half of leaders feel equipped for the people-leadership aspects of their role when they take it on.

This is not a talent problem. These are capable people. It is a preparation problem — and an expectation problem. Organisations promote on technical performance and then expect leadership competence to follow automatically. It does not.

The Leadership Transition Framework was built to close that gap: to give people who are making this transition the tools, frameworks, and self-awareness they need before they are already struggling.

What the Research Says About This Transition

The shift from individual contributor to people leader is now well-documented in leadership literature. Marshall Goldsmith's research, summarised in his book What Got You Here Won't Get You There, identifies the specific behaviours that drive individual success but undermine leadership effectiveness: winning too much, adding too much value, starting with 'no' or 'but', telling the world how smart you are, and failing to give proper recognition.

The insight is counterintuitive but consistent: the habits that build individual career success are precisely the habits that most need to be modified for leadership success. High performance as an individual often involves being right, being fast, and solving problems personally. Leadership requires tolerating ambiguity, slowing down to develop others, and allowing yourself to be wrong.

1A Why Your Expertise Might Be Working Against You

Why Your Expertise Might Be Working Against You

Expertise is a wonderful thing — until it becomes a trap.

When you are the most knowledgeable person in the room, it is natural to lead from that knowledge. You see the problem clearly. You know what the right answer is. You have solved this before. So you tell people what to do, fix the issues yourself, and make sure the work meets your standard.

The result is a team that is capable of very little without you.

This pattern is sometimes called the expert trap. The more confident a leader is in their own expertise, the more likely they are to override, rescue, and control — even with good intentions. And the more they do this, the more their team learns to wait for direction rather than develop their own judgment.

There is also a more subtle problem. When you are known as the expert, your team will always bring you the hard problems. Every escalation comes to you. Every exception lands on your desk. You become the bottleneck — the single point of failure that everyone works around.

Letting Go

Letting go of expertise as your primary leadership tool does not mean pretending you don't know things. It means choosing when to use your knowledge differently.

Instead of providing answers, you ask questions that help others find their own. Instead of fixing the problem, you support someone through solving it themselves. Instead of demonstrating your standard, you help your team understand and own that standard.

This is not passive. It requires more skill, not less. But it is the foundation of building a team that grows and functions without constant dependency on you.

The Identity Question

Behind the expertise trap is often an identity question: if I am not the expert, who am I?

For many high performers, professional identity is tightly bound to being good at what they do. Being the person with the answers is not just a habit — it is how they see themselves. Moving into leadership requires building a new identity: the person who develops people who have the answers.

That shift takes time. Expect discomfort. The discomfort usually means you are doing it right.

The Five Signs of the Expert Trap

You may be in the expert trap if you recognise any of the following patterns in yourself:

• You are the go-to person for every problem — if every escalation lands on you, your team has not been developed to handle the work independently
• You regularly fix work after it has been submitted — this is delegation in name only; in practice, you are still doing the quality control
• Team members wait for your input before moving forward — if the team stops when you are unavailable, they have not been equipped to make decisions
• You feel most productive when you are doing, not leading — this is the clearest identity signal; your definition of productivity has not yet shifted
• You find it hard to let go of tasks you are good at — these are often the most important things to delegate, precisely because they feel comfortable

Case Study: The Technology Leader

Consider a senior engineer promoted to Engineering Manager. For ten years, she was the most reliable problem-solver in her team. Every hard technical problem eventually found its way to her desk, and she reliably solved it. When she became manager, she continued doing what had always worked: being the solver.

Within six months, her team had learned not to waste time thinking through hard problems — they just brought them to her. She was working twelve-hour days. Her team members' capability was not growing. And she was bottlenecking every decision that required technical judgment.

The intervention was simple but hard: she committed to asking questions before providing answers for 30 days. It felt inefficient. Her team were initially frustrated. But within three months, her team members were making decisions independently that they had previously escalated to her. Her calendar opened up. And two of her team members started taking on technical leadership of their own projects.

1B Building a Leadership Identity

Building a Leadership Identity

Before you can lead others effectively, you need a clear sense of what kind of leader you are — and what kind you want to become.

This is not about choosing a style from a textbook. It is about understanding your values, your instincts, and the assumptions you carry about what good leadership looks like. Many of those assumptions were formed by watching others — good leaders and bad ones. Some will serve you well. Others will limit you.

The Three Questions

A useful starting point for building leadership identity is three questions:

• What do I believe good leadership actually is? Not what you have read or been told, but what you genuinely believe from your own experience of being led.
• What kind of leader do I want my team to say I am, in two years' time? This grounds identity in observable behaviour rather than abstract values.
• What are the gaps between those two answers and how I behave today? Honest answers here are the starting point for growth.

Values-Based Leadership

Leaders who operate from a clear set of values are more consistent, more trustworthy, and better able to make decisions under pressure. When you know what you stand for, you do not need to think through every situation from first principles. Your values do that work.

Common leadership values include: integrity, accountability, respect, courage, curiosity, and service. What matters is not the words themselves but that your values are genuinely yours — not aspirational, but actual. Not what you wish you valued but what guides you when things are hard.

Authority Versus Trust

New leaders often confuse authority with influence. You may have a title and a reporting line, but that does not mean your team will follow you willingly. Authority creates compliance. Trust creates commitment.

Trust is built through consistency — doing what you say you will do, being honest when things go wrong, showing genuine interest in your team's growth, and being willing to be wrong. These are not complicated behaviours. They are just rare.

Start from day one. Every interaction in the first weeks of your leadership role is a data point your team is using to form an impression of who you are. Be deliberate.

Your Leadership Contract

A useful exercise in the early weeks of a leadership role is to write what could be called a leadership contract — a brief, honest statement of what you believe good leadership looks like, what you commit to as a leader, and what you are asking from your team in return.

This is not a mission statement or a set of slogans. It is a personal document, written for yourself and shared with your team when the time is right. It forces clarity on the questions that are easiest to leave vague: What do I actually stand for? What will I do when it is uncomfortable? What do I need from the people I lead in order to lead them well?

The act of writing it is part of the value. Most new leaders have never been asked to articulate these things explicitly, and the process of doing so surfaces assumptions they did not know they were carrying.

Three Types of Leadership Trust

Research by Covey, Feldman, and others identifies three distinct types of trust that matter in leadership relationships:

• Competence trust — confidence that you can do what your role requires. This is usually high for newly promoted leaders; it is what got them promoted.
• Character trust — confidence in your integrity, honesty, and genuine concern for others' interests. This takes longer to build and is more fragile.
• Benevolence trust — confidence that you have your team members' genuine interests at heart, not just the organisation's interests or your own career advancement.

New leaders sometimes assume their technical credibility provides all the trust they need. It provides competence trust only. Character and benevolence trust are built through thousands of small interactions over time — and can be destroyed by a single visible act of self-interest or dishonesty.

1C Moving from Doing to Enabling

Moving from Doing to Enabling

The most visible sign that a new leader has not made the mindset shift is this: they are still doing the work.

It usually starts with good intentions. They can see the team struggling with something they know how to fix. They can see the deadline approaching and the work not moving fast enough. So they step in. They fix it. They feel productive. The team feels relieved.

But something important has been lost. The team member who should have solved the problem did not solve it. They do not now know how to solve it next time. And the leader has reinforced the pattern: when things get hard, the leader takes over.

The Enabling Mindset

Enabling means creating conditions where other people can do their best work. It includes:

• Clarifying the goal and the standard clearly enough that people can work without constant checking
• Removing obstacles — finding resources, cutting red tape, running interference with the organisation so your team can focus
• Providing the support people need — not by doing their work, but by coaching, encouraging, and developing their capability
• Creating accountability — holding people to the standard while giving them the space to get there in their own way

Enabling is active work. It looks different from delivering — which is why new leaders sometimes feel unproductive when they are actually doing their job well.

Resisting the Pull

The pull back to doing is strong, particularly in the early stages of a leadership role. Your team may even want you to do it — it is faster, and it removes uncertainty for them.

Resist it. Every time you step in and do the work, you are making a choice about what kind of leader you want to be. Short-term, doing is often faster. Long-term, enabling is exponentially more powerful.

A useful rule: if your team can do it at eighty percent of the quality you would achieve, let them do it. That twenty percent gap is where their learning lives.

The 80% Rule in Practice

The 80% rule — if your team can do something at 80% of the quality you would achieve, let them do it — sounds simple in theory. In practice, it requires courage.

The 20% quality gap will sometimes be visible to clients, stakeholders, or your own manager. There will be moments when you could have done it better and you know it. The question to ask yourself in those moments is: what is the long-term cost of closing that gap myself, versus the long-term gain of allowing my team member to own that standard and improve?

The answer is almost always that the long-term gain outweighs the short-term gap. The exception is when the stakes are high enough that the 20% gap has genuine consequences — a client relationship at risk, a regulatory requirement, a safety issue. In those cases, intervene, but be transparent about why: 'I am going to step in on this particular piece because the stakes are high and I want to make sure it lands perfectly. I will show you what I am doing as I go, so you can own it next time.'

What Enabling Looks Like Week to Week

In practice, a leader who has made the shift from doing to enabling spends their week differently from one who has not:

• One-on-one conversations focused on how team members are progressing, what they need, and what is getting in their way
• Removing the organisational obstacles that are slowing their team down
• Thinking about what capabilities the team will need in six months and where the development gaps are now
• Creating the conditions — the clarity, the resources, the psychological safety — for the team to do its best work
• Representing the team upward: sharing their achievements, advocating for their needs, protecting their time from unnecessary demands

This is not passive work. It is demanding, complex, and consequential. It just looks different from the work of delivering outputs directly.

1D Avoiding the Micromanagement Trap

Avoiding the Micromanagement Trap

Micromanagement is almost always a symptom of anxiety, not a deliberate leadership strategy.

New leaders worry about their team's output because it is now their output too. They worry that standards will slip. They worry that something will go wrong and they will be responsible. And so they check, and re-check, and ask for updates, and adjust the work that has already been done, and hover in ways that communicate one clear message to their team: I do not trust you.

Micromanagement destroys motivation, suppresses initiative, and breeds exactly the dependency it tries to prevent. Teams that are micromanaged stop thinking for themselves. Why would they? Every decision will be reviewed anyway.

The Roots of Micromanagement

Understanding why you micromanage is more useful than simply deciding not to. Common roots include:

• Anxiety about standards — you are not sure your team will hit the mark, so you stay close to guarantee the outcome yourself
• Identity threat — if you are not doing, you feel like you are not contributing
• Lack of clarity — you have not been clear enough about expectations, so you monitor because you cannot trust what you haven't specified
• Past experience — you have been burned before when you gave people too much rope

The Alternative

The antidote to micromanagement is not hands-off distance. It is clear expectations, agreed checkpoints, and genuine trust extended proportionally to demonstrated competence.

This means setting clear goals and standards upfront, agreeing on how often you will check in and what you will look at, and then staying out of the way between those checkpoints. It means being willing to let people make mistakes — small ones — and learn from them.

The goal is not zero involvement. It is the right involvement at the right time. A good leader knows when to lean in and when to stay back.

The Delegation Trust Ladder

Not all delegation looks the same. The level of autonomy appropriate to a given person depends on their demonstrated competence and their track record of reliability. A useful model is the delegation trust ladder:

• Level 1 — Do as I direct: the person follows specific instructions without deviation. Appropriate for someone new to a task where the stakes of error are high.
• Level 2 — Propose, then act: the person develops a plan and discusses it before executing. Appropriate when they have some competence but not yet proven judgment.
• Level 3 — Act, then report: the person acts and tells you what they did. Appropriate when they have demonstrated sound judgment in similar situations.
• Level 4 — Act independently: the person owns the task fully and reports in the normal course. Appropriate for experienced, trusted team members in areas of established competence.

The mistake most new leaders make is either starting everyone at Level 1 (which is micromanagement) or jumping straight to Level 4 before trust has been established (which sets people up to fail). The right starting level depends on the person and the task — and the goal is always to move people up the ladder, not to keep them at their current level.

When to Intervene Despite the Risk of Micromanagement

There are situations where a leader must step in regardless of the impact on autonomy: clear ethical violations, safety risks, regulatory breaches, or situations where a client or organisational relationship is being irreparably damaged. The distinction matters. Stepping in because you would have done it differently is micromanagement. Stepping in because not doing so would cause genuine harm is leadership responsibility. Know the difference, and be clear with yourself about which is motivating you.

P2 The Foundation Nobody Talks About

The Foundation Nobody Talks About

Technical skills get you promoted. Emotional intelligence determines whether you succeed once you're there.

Of all the capabilities that distinguish strong leaders from average ones, emotional intelligence — EQ — is among the most predictive. Research by Daniel Goleman and others has consistently shown that EQ accounts for more of the variance in leadership performance than IQ or technical expertise.

This surprises many people who were promoted on the strength of their technical skills. The assumption is that the same capability that made you valuable as an operator will make you valuable as a leader. In most cases, it will not — at least not alone.

Leadership puts you in situations where the technical solution is clear but the human dynamics make it difficult to implement. You know what needs to happen. The challenge is getting people aligned, motivated, and able to do it. That is an EQ challenge, not a technical one.

Goleman identified five components of emotional intelligence that are particularly relevant to leadership: self-awareness, self-regulation, motivation, empathy, and social skills. This pillar works through each of them, with practical application for leaders who are making the transition from operational to people leadership.

The Research on EQ and Leadership Effectiveness

The evidence for the relationship between emotional intelligence and leadership effectiveness is substantial. Goleman's original research, published in the Harvard Business Review and in his books Working With Emotional Intelligence and Primal Leadership (co-authored with Boyatzis and McKee), found that EQ accounted for about two-thirds of the competencies that distinguished star performers from average ones — and that this proportion rose to nearly 90 percent at the senior leadership level.

More recent meta-analyses have confirmed and refined these findings. A 2015 meta-analysis published in the Journal of Organizational Behavior found significant positive correlations between leader EQ and transformational leadership effectiveness. Research from the Center for Creative Leadership found that interpersonal difficulties — primarily low EQ — were responsible for the majority of leadership derailment.

The implication is significant. The higher you go in an organisation, the more your success depends on emotional rather than technical intelligence.

A Note on EQ Development

EQ is often described as fixed — something you either have or do not have. The research does not support this. While there is a genetic component to emotional reactivity, the skills of emotional intelligence — self-awareness, self-regulation, empathy, social skills — are learnable and developable throughout adult life.

The precondition for development is honest self-assessment. Most people significantly overestimate their own emotional intelligence. Studies consistently find that self-reported EQ is a poor predictor of performance ratings; external ratings by peers and direct reports are far more predictive. This is why feedback from others is essential — your subjective experience of your EQ is not a reliable guide to how it manifests in interactions.

2A Self-Awareness: Knowing Your Leadership Default

Self-Awareness: Knowing Your Leadership Default

Self-awareness is the starting point for everything in emotional intelligence. Without it, you cannot regulate your emotions, read others accurately, or adapt your leadership to what a situation requires.

In leadership terms, self-awareness means knowing how you show up — particularly under pressure. Most people have a default mode they fall into when things get difficult: some withdraw, some become controlling, some get aggressive, some freeze. That default was probably functional in your previous role. In a leadership role, it can cause significant damage if it goes unexamined.

Understanding Your Triggers

Triggers are the situations that reliably activate your default mode. Common leadership triggers include:

• A team member who seems not to care about quality
• Being challenged or questioned in front of others
• A project that is off track and out of your direct control
• Feedback that feels unfair or inaccurate
• Pressure from above at the same time as pressure from below

The goal is not to eliminate your triggers — you cannot. The goal is to know them well enough that you see them coming and choose your response rather than being driven by it.

The 360-Degree View

One of the consistent findings in leadership research is the gap between how leaders see themselves and how they are seen by the people around them. Leaders who are high in self-awareness have a smaller gap. Their self-assessment roughly matches what their team, peers, and managers would say about them.

Building self-awareness requires honest feedback, not just reflection. Reflection tells you what you think. Feedback tells you what others experience. Both matter. The EQ Self-Assessment in the toolkit is a starting point. Regular, honest conversations with your team and manager are what sustain it.

The Johari Window for Leaders

The Johari Window — developed by psychologists Joseph Luft and Harry Ingham — is a useful model for understanding the scope of self-awareness in a leadership context. It maps four quadrants:

• Open/Arena: what you know about yourself and others know about you — your known strengths, behaviours, and preferences
• Blind Spot: what others know about you that you do not know yourself — your default behaviours under pressure, your impact on others that you cannot see
• Facade/Hidden: what you know about yourself but have not shared — your doubts, anxieties, and development areas you keep private
• Unknown: what neither you nor others know — potential that has not yet been revealed or explored

The goal of self-awareness development is to expand the Open quadrant — to reduce your blind spots through feedback, and to selectively reduce your facade by being appropriately vulnerable with your team. Leaders with large blind spots are the ones whose teams know exactly what is coming while they remain oblivious to how they are landing.

Building a Feedback Habit

Formal 360-degree feedback surveys are useful, but they are slow and infrequent. More valuable for rapid self-awareness development is a habit of informal, frequent feedback-seeking.

After any significant interaction — a difficult conversation, a team meeting, a presentation to your manager — ask a trusted colleague: 'How did that land? What did you notice?' Build a network of at least two or three people who will tell you honestly what they observe. Protect those relationships by responding non-defensively when they do.

2B Self-Regulation: Managing Your Reactions

Self-Regulation: Managing Your Reactions

Self-regulation is the ability to manage your emotional responses — particularly the ones that could harm your relationships, your team, or your judgment.

This is not about suppressing emotion or pretending to feel things you don't. It is about creating enough space between stimulus and response to choose how you show up. A leader who reacts impulsively to bad news, criticism, or conflict is not managing their emotions — they are being managed by them.

What It Looks Like Under Pressure

The clearest window into a leader's self-regulation is how they behave when things go wrong. Do they blame? Do they panic? Do they go quiet and withdraw? Or do they stay calm, stay curious, and focus on what can be done?

Teams pay very close attention to how their leader behaves under pressure. If you stay calm, your team learns that problems are solvable. If you panic or get angry, your team learns to hide problems from you.

Practical Tools for Self-Regulation

• Name it to tame it — research shows that labelling your emotional state ("I'm feeling frustrated right now") activates the rational brain and reduces the intensity of the emotion
• Build in a pause — in high-stakes conversations, a moment of silence is not weakness; it is considered leadership
• Know your recovery pattern — after a difficult interaction, what do you need? Solitude, exercise, conversation? Know it and use it
• Watch your language — under pressure, leaders often use absolute language ("always", "never", "everyone") that inflames rather than resolves. Slow down your language and you slow down the escalation

Self-regulation is a practice, not a trait. It improves with deliberate attention over time.

The Neuroscience of Self-Regulation

Understanding the neuroscience of emotional reactivity helps leaders take self-regulation more seriously as a skill, not just a discipline choice.

When we perceive a threat — social as much as physical — the amygdala in the brain's limbic system activates a stress response before the prefrontal cortex (the rational, planning brain) has had time to process the situation. This is what produces the instinctive reaction before the considered response. For leaders, this means that in high-stakes situations, the emotional brain moves faster than the thinking brain.

The implication for self-regulation is not to try to suppress this reaction — the research shows that suppression is ineffective and exhausting. Instead, the goal is to create enough space between the emotional trigger and the response that the prefrontal cortex can catch up. Techniques that work physiologically include: slow, controlled breathing (which activates the parasympathetic nervous system), naming the emotion (which reduces amygdala activation — studies by Matthew Lieberman at UCLA showed measurable reductions in amygdala activity from labelling emotions), and building in pause through practiced phrases like 'Let me think about that for a moment.'

The Consistency Principle

Your team is performing a continuous, unconscious assessment of your emotional consistency. They are asking: can I predict how this leader will react? Is it safe to bring bad news? Will I be blamed or will we problem-solve?

Emotional consistency — not emotional flatness, but predictable, proportionate reactions — builds psychological safety. Teams with emotionally inconsistent leaders spend significant cognitive energy managing up: monitoring the leader's mood, filtering information, and calibrating their communication to avoid triggering a difficult reaction. This is energy not spent on the work. Consistency frees that energy.

2C Empathy: Understanding Your Team's Reality

Empathy: Understanding Your Team's Reality

Empathy is the capacity to understand what another person is experiencing — to see the situation from their perspective, not just your own.

For leaders who came up through operational roles, empathy can feel like a soft skill — nice to have, but secondary to getting the work done. It is not. Empathy is the mechanism by which leaders understand what their team needs, identify problems before they escalate, and build the relationships that drive performance.

Without empathy, leaders make decisions based on how they would respond to a situation, rather than how the people they lead actually experience it. The result is well-intentioned decisions that land badly, feedback that creates defensiveness rather than growth, and a team that feels unseen.

Empathy in Practice

Empathy does not require you to agree with how someone is feeling or to fix their emotional state. It requires you to acknowledge it accurately.

In practical terms, this means:

• Listening without immediately offering solutions or reframes
• Asking questions that invite someone to tell you more, rather than questions that lead them to the answer you already have
• Noticing what is not being said — the discomfort in a conversation that the other person is trying to manage
• Acknowledging the difficulty of a situation before focusing on what to do about it

The Difference Between Empathy and Agreement

A common misconception is that empathy means you cannot hold firm positions or make difficult decisions. It does not. You can understand exactly why someone is upset about a decision and still make that decision. Empathy informs how you communicate it, how you support the person through it, and how you think about the impact. It does not change the decision.

Leaders who confuse empathy with agreement tend to either avoid empathy altogether (to protect their ability to make decisions) or avoid making decisions (to protect their relationships). Neither serves the team well.

Cognitive Versus Affective Empathy

Psychologists distinguish between two types of empathy that are both relevant to leadership: cognitive empathy (the ability to understand intellectually what another person is experiencing) and affective empathy (the ability to feel something of what another person is feeling).

Both have their place in leadership. Cognitive empathy is particularly important for decision-making — understanding how different team members will experience a change or decision, and adjusting your approach accordingly. Affective empathy is important for connection and for recognising distress that is not being expressed verbally.

Research by Simon Baron-Cohen and others suggests that people vary considerably in their natural tendency towards each type, and that some people are strong in one and weak in the other. Leaders who are high in cognitive empathy but low in affective empathy can come across as clinical or calculating — they understand people's situations but don't seem to feel them. Leaders high in affective empathy but low in cognitive empathy may be emotionally attuned but make poor decisions about how to respond.

Empathy Across Difference

Empathy is harder — and more important — across demographic and experiential difference. A leader who understands the perspective of someone like themselves has basic empathy. A leader who can genuinely understand the perspective of someone whose background, experience, or identity is very different from their own has the kind of empathy that builds inclusive teams.

This requires deliberate effort: seeking out perspectives that are different from your own, asking more questions and making fewer assumptions, and being willing to sit with the discomfort of not immediately understanding.

2D Social Skills: Building the Relationships That Drive Performance

Social Skills: Building the Relationships That Drive Performance

The social skills dimension of emotional intelligence covers a leader's ability to build and sustain relationships — with their team, their peers, their manager, and stakeholders across the organisation.

These skills are not about being charming or popular. They are about being effective in the social systems that every organisation operates within. A leader who cannot read a room, navigate conflict constructively, or build trust across functions will be limited regardless of their technical capability or personal EQ.

Key Social Skills for Leaders

• Communication — the ability to convey information clearly, adjust your style to your audience, and ensure understanding rather than just transmission
• Conflict management — the ability to surface and work through disagreement productively, rather than avoiding it or escalating it
• Collaboration — the ability to work effectively with people who have different roles, priorities, and perspectives
• Team building — the ability to create a group that is more than the sum of its parts — where trust, accountability, and shared purpose drive collective performance
• Influence — the ability to move people towards outcomes without relying solely on authority (covered in depth in Pillar 6)

Social Skills Take Practice

Unlike cognitive skills, social skills cannot be developed through reading or theory alone. They require repeated real-world practice, honest feedback, and the willingness to be uncomfortable.

For leaders coming from operational roles, many of these skills will feel unfamiliar or even unnecessary at first. That is normal. They are also learnable. The key is treating them with the same seriousness you brought to developing your technical expertise.

The Network as a Leadership Resource

Social skills in a leadership context include the ability to build and use professional networks effectively — not in a transactional or self-serving way, but as a genuine ecosystem of relationships that enables better decisions, broader perspective, and greater impact.

Leaders with strong professional networks are better informed, get things done more easily across organisational boundaries, have more resilience (because they have more people to draw on when their own resources are stretched), and advance faster in their careers.

Building a useful network requires giving before taking: sharing information, making introductions, supporting others' work, and investing in relationships before you need them. The leaders who complain that they have no network are usually the ones who only reach out when they need something.

Communication Across Different Styles

Social skill includes the ability to adapt your communication style to the person in front of you. People differ in how they process information, how they prefer to receive feedback, how much directness they are comfortable with, and what motivates them.

Leaders who communicate the same way to everyone are effective with the people who happen to share their style, and less effective with everyone else. The investment in understanding how different people prefer to communicate — and adjusting your approach accordingly — pays consistent returns.

Common dimensions of communication style difference include: direct versus indirect, fast versus deliberate, detail-oriented versus big-picture, emotionally expressive versus task-focused. None of these is better; they are different. The leader who can work effectively across all of them has a genuine advantage.

P3 The Conversations That Define Leadership

The Conversations That Define Leadership

Leadership happens in conversations. Everything else is preparation.

If you had to identify the single most common leadership weakness in people transitioning from operational to people-leadership roles, it would be this: they avoid difficult conversations.

They notice the problem. They are bothered by it. They think about how to address it. And then they don't. They tell themselves it will sort itself out. Or that the timing isn't right. Or that saying something will make things worse.

Meanwhile, the problem grows. The team member whose work is below standard continues producing below-standard work. The conflict between two team members continues creating friction. The behaviour that undermines team culture continues unchecked.

Avoiding a conversation is not a neutral act. It has consequences — for the team, for the individual, and for your credibility as a leader.

This pillar covers the conversations that matter most in a leadership role: giving feedback, receiving it, having difficult conversations, coaching conversations, and the active listening that makes all of them possible.

The Conversation Avoidance Research

Research on leadership ineffectiveness consistently finds that conversation avoidance — the systematic pattern of not addressing the things that need to be addressed — is one of the most costly leadership behaviours. A 2020 study by VitalSmarts found that 95 percent of employees said they were unable or unwilling to raise sensitive issues with their leaders, and that the typical worker had two or three concerns they had not raised.

The cost is substantial: misunderstandings that become embedded conflicts, performance problems that become terminations, projects that fail because no one raised the concern that would have caught the issue early. Conversation avoidance is not a neutral act — it is an active choice with real consequences.

Why Leaders Avoid Conversations

Leaders typically avoid difficult conversations for one of four reasons:

• Fear of damaging the relationship — particularly with someone they were previously peers with, or someone they like
• Fear of an emotional reaction — concern that the person will become upset or defensive and the conversation will spiral
• Uncertainty about being right — doubt about whether their assessment is accurate enough to warrant raising it
• Low confidence in their ability to manage the conversation — they have never been taught how, and they are not sure they can do it well

All four of these fears are understandable. None of them justifies avoidance. The skills in this pillar are designed to make difficult conversations genuinely manageable — not comfortable, but manageable.

3A Giving Feedback That Actually Works

Giving Feedback That Actually Works

Feedback is the primary tool leaders use to develop their people. It is also the tool most leaders use least effectively.

The most common errors in giving feedback are:

• Waiting too long — feedback loses most of its impact if it is not given close to the behaviour
• Being vague — "you need to be more professional" tells someone nothing actionable
• Sandwiching it — wrapping critical feedback between compliments teaches people to tune out the first and last part of everything you say
• Making it personal — "you seem to not care" attacks identity; "this report is missing three sections" addresses behaviour

A Useful Framework: SBI

The SBI model — Situation, Behaviour, Impact — is a simple, effective structure for giving feedback:

• Situation: describe the specific context ("In yesterday's team meeting...")
• Behaviour: describe the observable behaviour, not the interpretation ("you interrupted Sam three times while she was presenting")
• Impact: describe the effect of that behaviour ("it made it difficult for her to finish her point, and I noticed the team seemed uncomfortable")

SBI works because it focuses on facts and impact rather than judgment and character. It gives the recipient something specific to respond to and something specific to change.

Positive Feedback

Positive feedback is as important as corrective feedback, and it is just as often done poorly. "Great work" is not feedback — it is praise. Useful positive feedback is specific: "The way you handled that client complaint was exactly right — you listened without defending, and then offered a solution. That kind of response builds trust."

Be specific, be prompt, and mean it. People know the difference between genuine recognition and obligation.

The Feedback Timing Problem

Research on feedback effectiveness consistently finds that proximity matters enormously. Feedback given within 24 hours of the behaviour it addresses is dramatically more impactful than feedback given weeks later. By the time most formal performance reviews occur, the specific behaviours they address are often months old — too distant in time to produce meaningful learning.

The implication for leaders is to build a culture of frequent, informal, real-time feedback — both positive and corrective — rather than relying on formal processes as the primary feedback mechanism. This does not mean a running commentary on everything people do. It means not letting significant moments — good or poor — pass without acknowledgment.

Creating a Feedback Culture

Individual feedback skills matter, but a feedback culture — where feedback flows in all directions, is expected and welcomed, and is seen as a sign of respect rather than criticism — multiplies the impact. Building that culture is a leadership responsibility.

A feedback culture is built by:

• Modelling receptivity to feedback yourself — actively seeking it and visibly acting on it
• Creating regular structured feedback opportunities, not just leaving it to informal moments
• Responding positively when people give you feedback, even when it is uncomfortable
• Recognising and celebrating the team members who give honest, constructive feedback rather than only saying what they think you want to hear
• Making it clear that positive feedback is as important as corrective feedback — both are part of the same habit

3B Having Difficult Conversations

Having Difficult Conversations

Difficult conversations are ones where the stakes are high, opinions differ, and emotions run strong. In leadership, they include performance conversations, conflict conversations, the conversation where you tell someone they did not get the role they wanted, and the conversation where you address behaviour that is affecting the team.

Most people avoid them because they fear making things worse. The irony is that avoidance almost always makes things worse.

Before the Conversation

Preparation matters. Before a difficult conversation, be clear about:

• What outcome do you want? What would a good conversation produce?
• What are the facts? Separate what you observed from what you inferred.
• What assumptions are you making about the other person's motivations? Are you certain those are accurate?
• What do you actually need from this conversation — to be heard, to resolve something, to change a behaviour?

During the Conversation

Start by stating your intent: "I want to talk about something that is affecting the team, and I want to understand your perspective on it too." This signals that you are not there to lecture — you are there to resolve something together.

Stay curious. The conversation will go better if you genuinely seek to understand what is happening for the other person, rather than simply delivering your conclusion. You may learn something that changes the picture entirely.

Avoid certainty language in your opening. "I have noticed" and "my concern is" land very differently from "you always" and "the problem with you is".

After the Conversation

Agree on what has been decided or what will change, and when you will check in. Document it if the stakes are high enough. Follow up. A difficult conversation that produces no change teaches the other person that these conversations do not matter.

Preparation: The Crucial Element Most Leaders Skip

The leaders who handle difficult conversations most effectively are almost always the ones who prepare most thoroughly. Preparation is not about scripting the conversation — scripted conversations feel false and collapse the moment the other person says something unexpected. It is about clarity on the key elements before you walk in.

A useful preparation checklist:

• What is the specific behaviour or situation I need to address? (Be precise — not 'attitude', but the specific observable behaviour)
• What is the impact of that behaviour? (On the team, the client, the project, the culture)
• What do I want to be different after this conversation? (A specific, observable change)
• What assumptions am I making about why this is happening? (What else might explain it?)
• What is my opening line? (Know your first sentence; everything else can adapt from there)

The Role of Curiosity in Difficult Conversations

The single most powerful tool in a difficult conversation is genuine curiosity. Not performed interest, but real wanting-to-understand.

Most difficult conversations go badly because both parties arrive with their positions formed and their primary goal is to defend those positions. A genuinely curious leader arrives wanting to understand: what is actually happening here? What does the other person experience? What might I not know?

This orientation does not mean surrendering your position or pretending you do not have concerns. It means gathering real information before concluding you have the full picture. The information you gather through genuine curiosity often changes what you do next in ways that produce far better outcomes than your pre-formed plan would have.

3C Active Listening: The Leadership Skill Most Leaders Skip

Active Listening: The Leadership Skill Most Leaders Skip

Most people listen to respond. Leaders need to listen to understand.

The difference is significant. When you listen to respond, you are tracking the conversation enough to know when it is your turn to speak, and using that time to formulate your reply. When you listen to understand, you are trying to accurately comprehend what the other person is actually saying — including what they are not saying.

Leaders who listen well are better at identifying problems early, building trust, making sound decisions, and developing the people around them. Leaders who listen poorly are often the last to know when something important is wrong.

What Active Listening Looks Like

• You are giving the person your full attention — not checking your phone, not half-watching your screen
• You are resisting the urge to fill every silence — pauses in conversation are where people think; filling them robs them of that space
• You are asking questions that draw the person further into what they are trying to express, not questions that redirect to what you want to talk about
• You are checking your understanding — "what I am hearing is... is that right?" — rather than assuming you have understood correctly
• You are noticing body language, tone, and what is conspicuously absent from what is being said

The Common Failure Mode

The most common failure mode is listening to a person while mentally preparing your response. You think you are listening. You are not. You are waiting.

A practical test: after a conversation, can you accurately summarise what the other person said — including the emotional content, not just the factual content? If not, you were probably not listening as well as you thought.

Listening at Multiple Levels

Active listening operates at three levels simultaneously, each giving a different type of information:

• Content level: what the person is literally saying — the facts, the sequence of events, the specific words they use
• Emotion level: how they are feeling about what they are saying — the energy behind the words, the pauses, the points where they seem more or less comfortable
• Meaning level: what the content and emotion together tell you about what matters to this person, what they are trying to communicate beyond the literal words

Most people listen only at the content level. Leaders need to listen at all three. The emotion level tells you when something is more significant than the words suggest. The meaning level tells you what the person actually needs from the conversation.

Listening in Different Formats

Active listening is harder in some formats than others. One-on-one conversations, when both people are physically present and not distracted, offer the best conditions. Video calls degrade some of the signals — body language below the shoulders, proximity, and subtle physical cues are lost. Phone calls degrade them further. Asynchronous communication (email, messages) removes almost all of them.

Leaders need to be deliberate about format choice. The more important the conversation, the more important the richness of the communication channel. Significant feedback, difficult conversations, and important connection-building should almost always happen in person or by video — never by email.

3D Receiving Feedback as a Leader

Receiving Feedback as a Leader

Leaders who cannot receive feedback gracefully rarely receive it honestly. And leaders who do not receive honest feedback operate blind.

Receiving feedback well is harder than giving it, particularly for people who are used to being competent. It requires setting aside defensiveness, the desire to explain or justify, and the impulse to immediately counter with evidence that the feedback is wrong.

Why Leaders Stop Getting Honest Feedback

As you move into leadership, the volume of honest feedback you receive typically decreases. This is partly because your team has less standing to evaluate you, and partly because people are cautious about how their feedback will land. If you react defensively once, you may never get honest feedback from that person again.

Leaders who want honest feedback have to actively create conditions for it. This means explicitly asking for it, responding to it without defensiveness even when it stings, and demonstrating that you have done something with it.

A Model for Receiving Feedback

• Listen completely — do not interrupt or rebut while the feedback is being given
• Ask questions for clarity — "can you give me a specific example?" is not defensive; it helps you understand
• Acknowledge what you heard — you do not have to agree, but you should demonstrate that you understood: "I can see why that came across that way"
• Thank the person — genuinely; getting honest feedback is a gift
• Decide what to do with it — not all feedback requires action, but all of it deserves thought

Over time, the leaders who grow fastest are the ones who actively seek honest feedback and use it relentlessly.

The Feedback You Are Not Getting

A consistent finding in leadership research is that leaders systematically receive less honest feedback than they think they do. This is partly the natural dynamic of hierarchy — people are cautious about giving critical feedback upward — and partly a product of specific leader behaviours that discourage honesty.

Research by Jean-François Manzoni and Jean-Louis Barsoux (the Pygmalion effect in management) found that leaders form impressions of their team members early, and then unconsciously filter subsequent information to confirm those impressions. The same dynamic operates in reverse: team members form impressions of their leader's receptivity to honest feedback, and filter their own honesty accordingly.

Creating the Conditions for Honest Feedback

• Ask specific questions — 'How am I going?' produces vague answers. 'What is one thing I could do differently in team meetings?' produces specific ones.
• Create multiple channels — some people will not give honest feedback face to face. Anonymous surveys, written formats, or feedback through a third party can capture things that direct conversation misses.
• Share what you are working on — when people know what you are developing, they can watch for it and give you specific feedback on it.
• Follow up — if someone gives you feedback and you do something different as a result, tell them. This closes the loop and encourages more honesty next time.

P4 Creating Capability in Others

Creating Capability in Others

Every time a leader solves a problem for someone, they may be weakening that person's ability to grow.

Coaching is the leadership skill that most directly creates capability in others. It is also the skill that most operationally-minded leaders resist, because it is slower — at least in the short term — than simply telling people what to do.

Directing produces compliance. Coaching produces capability. The distinction matters enormously at scale. A team that has been directed can perform when the leader is present. A team that has been coached can perform when the leader is not.

This pillar explores what coaching looks like in a day-to-day leadership context — not the formal coaching you might encounter in a professional development setting, but the constant small choices about whether to give answers or ask questions, whether to rescue or support, whether to do or develop.

It is built on a central principle: your team's growth is a legitimate measure of your leadership effectiveness. Not just what they produce today, but what they become capable of producing over time.

The Science of When Coaching Works Best

Not all coaching situations are equal. Research by Herminia Ibarra and Anne Scoular, published in Harvard Business Review, identifies the conditions under which a coaching approach produces the most development:

• The person has the underlying capability but is not yet applying it consistently
• The situation requires them to develop judgment, not just execute a procedure
• There is enough time for the development process — coaching a skill under time pressure is almost always counterproductive
• The person is genuinely motivated to develop, not just going through the motions

Where these conditions do not hold — where the person genuinely lacks the capability, where the time pressure is real, or where the stakes of getting it wrong are too high — directive leadership is often more appropriate. The skill is in reading the situation accurately.

Building a Coaching Habit

The challenge for most operational leaders is that coaching feels slow. Asking a question and waiting for someone to think takes longer than providing the answer. Over the course of a busy day, the accumulated time cost can feel significant.

Michael Bungay Stanier, in The Coaching Habit, offers a practical reframe: the goal is not to have formal coaching conversations, but to build the coaching habit into the small interactions that make up a day. Three or four genuine coaching questions in a five-minute conversation — 'What's on your mind?', 'What's the real challenge here?', 'What do you want?', 'What was most useful about this for you?' — can shift someone's thinking without consuming significant time.

4A The Coaching Mindset

The Coaching Mindset

Coaching is not primarily a set of techniques. It is a way of seeing your relationship with your team.

A leader with a coaching mindset operates from a set of assumptions that are different from a leader with a directing mindset:

• People are capable of more than they are currently demonstrating
• People generally have more of the answers than they realise
• My job is to create conditions for growth, not just conditions for output
• Asking is usually better than telling, even when I know the answer
• The short-term cost of someone working through a problem themselves is usually worth the long-term gain in their capability

These assumptions do not come naturally to people who were promoted on the strength of their expertise. If you have spent years being the person with the answers, shifting to a mindset where your most valuable contribution is a well-timed question requires deliberate work.

Coaching Versus Managing

Coaching and managing are not the same thing, and leaders need both. Managing involves clarifying expectations, tracking performance, allocating resources, and ensuring accountability. Coaching involves developing someone's thinking, building their confidence, and expanding their capability.

The mistake many new leaders make is doing only one. They manage (direct, track, control) but do not coach. Or they coach (support, develop, encourage) but do not manage (hold accountable, make decisions, set clear expectations). Effective leaders do both, and know when each is called for.

The GROW Model

The GROW model — developed by Sir John Whitmore and refined through decades of coaching practice — remains one of the most practical frameworks for structuring a coaching conversation:

• Goal: What does the person want to achieve? Not just today's conversation goal, but the broader outcome they are working towards.
• Reality: What is actually happening right now? What have they tried? What is working and what is not? What is getting in the way?
• Options: What could they do? What options have they not yet considered? What would they do if constraints were different?
• Will/Way Forward: What will they actually do? What is the specific next step? When will they do it? How will they know they have done it well?

GROW is valuable not because it is a rigid script but because it prevents the common coaching failure mode of jumping to options (advice-giving) before the reality is properly understood. Understanding the reality first — through curious questions, without assumptions — consistently produces better options and stronger commitment.

Coaching Versus Mentoring Versus Consulting

Leaders often need to play multiple roles in development conversations, and it is useful to be clear about which one you are playing:

• Coaching: drawing out the person's own thinking, without sharing your own
• Mentoring: sharing your own experience and perspective to help someone navigate a similar challenge
• Consulting: providing your expert answer to a specific question

All three are valuable. Problems arise when you are playing one role while the person needs another — particularly when you default to consulting (giving advice) when coaching (asking questions) would serve the person's development better.

4B Asking Instead of Telling

Asking Instead of Telling

The single most practical coaching skill is replacing statements with questions.

Not any questions. The right kind. Coaching questions are open-ended, future-focused, and designed to expand the other person's thinking rather than lead them to your predetermined answer.

The Difference

Telling: "You should approach this by starting with the stakeholder analysis."

Leading question (still telling, just indirectly): "Don't you think you should start with the stakeholder analysis?"

Coaching question: "Where do you think you should start?"

The coaching question invites the person to think. It might produce the same answer — stakeholder analysis. But now it is their answer, which means they are more committed to it and have developed their own analytical process.

A Coaching Question Bank

• What is the outcome you are trying to achieve?
• What options do you see? Are there others you haven't considered?
• What would happen if you tried that?
• What is getting in the way?
• What support do you need from me?
• What have you already tried?
• If you had to decide right now, what would you do?
• What would you do if I weren't here to ask?
• What does good look like here?
• What is the one thing that would make the biggest difference?

These questions work because they keep the thinking with the person who needs to develop it. That is the point.

The Question Quality Ladder

Not all questions are equal in their coaching value. A useful mental model is to think of questions on a ladder from lower to higher quality:

• Closed questions (lowest): 'Did you think about the timeline?' — produces yes/no and shuts down thinking
• Leading questions: 'Don't you think you should start with the timeline?' — subtly guides to your preferred answer
• Open informational questions: 'What is your timeline?' — opens the topic but stays factual
• Exploratory questions: 'What are the key risks in your timeline?' — begins expanding thinking
• Generative questions (highest): 'What would you change about your approach if you found out the deadline had moved by two weeks?' — provokes genuine new thinking

The goal in coaching conversations is to spend most time at the exploratory and generative end of the ladder. This is harder than it sounds — it requires resisting the pull towards the question that leads to your preferred answer.

When Coaching Questions Miss the Mark

Not every coaching question lands well. Some feel rhetorical. Some feel like the leader already has an answer and is performing a process. Some are simply the wrong question for where the person is right now.

Learning to read the response to your coaching questions is as important as learning to ask them. A one-word answer, a defensive tone, or a look of frustration suggests either the question was not quite right, or the person is not in a headspace to engage with questions — they may need directive support or simply a clear answer first. Adjust accordingly.

4C Delegation as Development

Delegation as Development

Most leaders understand delegation as a workload management tool — you have too much to do, so you assign some of it to someone else. That is useful, but it misses the most important function of delegation: it is how you develop your people.

Strategic delegation means choosing what to delegate based on what will stretch and develop the people you are assigning it to, not just what you need to get off your plate.

What to Delegate

The work most worth delegating is work that is:

• At or slightly above the current capability of the person you are delegating to — enough challenge to produce growth, not so much that it sets them up to fail
• Work that you have been holding because you like doing it or are good at it — this is often the work that most needs to go
• Work that develops skills your team member has expressed a desire to build
• Work that gives someone visibility across the organisation they would not otherwise have

How to Delegate Well

Poor delegation is either too vague ("can you handle the client report?") or too prescribed ("here are the seventeen steps I need you to follow"). Effective delegation:

• Clarifies the outcome, not the method — what does done look like?
• Establishes clear boundaries — what decisions can they make alone, and what requires your input?
• Agrees on checkpoints — when will you review progress, and what will you look at?
• Creates space for them to approach it their own way — resist the urge to specify how

And then, critically: you stay out of the way until the agreed checkpoint. If you delegate and then hover, you have not actually delegated anything.

The Things Leaders Find Hardest to Delegate

Research by Ciela Hartanov and others on delegation patterns in leaders consistently identifies certain categories of work that leaders find disproportionately hard to let go of:

• High-visibility work — presentations to senior leadership, client relationships, key stakeholder meetings. These feel like your work because they reflect on you directly.
• Work that defines your professional identity — the technical tasks that demonstrate your expertise. Delegating these requires a genuine identity shift.
• Work where you have a personal relationship — longstanding client or stakeholder relationships that feel 'yours'.
• Work where the standard matters enormously to you — creative work, quality-sensitive work, or work in areas where you have very high personal standards.

These are precisely the categories most worth delegating for development purposes — and most worth examining honestly for the identity and control assumptions they reveal.

Delegation Across Experience Levels

The approach to delegation should vary significantly depending on the experience level of the person you are delegating to. A new graduate receiving a delegated task needs much more scaffolding — clarity on standards, more frequent check-ins, and explicit permission to ask questions — than a senior team member who has handled similar work before.

The error is often in one direction: experienced leaders who have developed strong delegation muscles sometimes apply the same light-touch approach to junior people who need more structure, and set them up to struggle. Calibration — matching your delegation approach to the person's actual readiness — is part of the skill.

4D Creating Accountability Without Micromanaging

Creating Accountability Without Micromanaging

Accountability and micromanagement are often confused. They are opposites.

Accountability means holding someone to a standard they have agreed to, in a way that respects their ability to manage how they get there. Micromanagement means controlling how they get there to the point where the person is no longer actually responsible for the outcome — you are.

You cannot hold someone accountable for an outcome you have managed so closely that they had no real agency in producing it.

The Accountability Conversation

Accountability starts with a clear, explicit conversation about what is expected. Vague expectations produce vague accountability. If you have not clearly articulated the standard, you have no basis for holding someone to it.

A useful structure:

• What: what specifically needs to be done, to what standard
• When: by when, and what intermediate milestones matter
• How we will know: what will we look at to evaluate whether the standard has been met
• What happens: what will occur if the standard is not met — not as a threat, but as a clear consequence

Following Through

The most important part of accountability is what you do when the standard is not met. Leaders who set clear expectations and then do nothing when they are missed teach their team that expectations do not really matter.

Following through does not mean punishment. It means a direct, honest conversation about what happened, what the impact was, and what will change. It also means recognising and acknowledging when the standard is met — accountability should not only surface when things go wrong.

The Accountability Conversation Framework

When someone has not met an agreed standard, the accountability conversation has a specific purpose: to understand what happened, to agree on what needs to change, and to make clear that the standard is real.

A useful structure for the accountability conversation:

• Open with the observation: describe specifically what you observed, without interpretation ('The report was due Tuesday and was submitted on Friday')
• Invite their account: 'Can you walk me through what happened?' — you may learn something that changes the picture
• Acknowledge the impact: make the consequences of the gap explicit, even if they are obvious to you — they may not be obvious to the person
• Reconnect to the standard: reaffirm what is expected, without negotiating it down unless there is a genuine reason to revise it
• Agree on what changes: get a specific commitment to a specific action by a specific date
• Set the next checkpoint: make it clear when you will check in and what you will look at

The most common failure in accountability conversations is being so gentle about the standard that the person leaves the conversation unclear about whether the standard actually matters. Kindness and clarity are not in conflict. You can be both warm and unambiguous.

P5 From Individual to Collective Performance

From Individual to Collective Performance

A team is not a group of people who happen to work in the same place. It is a group of people who achieve more together than they could separately.

Operational managers typically focus on individual performance. They track what each person is doing, manage each person's quality, and measure success person by person. This approach has merit — individual accountability matters. But it misses something important.

Teams that are only managed as collections of individuals rarely achieve the kind of collective performance that makes an organisation genuinely competitive. The highest-performing teams have something beyond individual competence: they have trust, psychological safety, shared purpose, and accountability that is mutual rather than top-down.

Building that kind of team is a leadership skill, not a byproduct of good individual management. It requires deliberate attention to team dynamics, culture, and the conditions that allow people to do their best work together.

This pillar draws on the work of Patrick Lencioni — who identified the five dysfunctions that prevent team cohesion — and Amy Edmondson, whose research on psychological safety is among the most important contributions to our understanding of why some teams outperform others.

The Research on Team Performance

Google's Project Aristotle — a multi-year study of team effectiveness at Google, published in 2016 — found that the most reliable predictor of team performance was not the technical quality of individual team members, but the psychological safety of the team. Teams where people felt safe to speak up, disagree, and admit mistakes consistently outperformed technically stronger teams where that safety was absent.

This finding was surprising to the researchers themselves, who expected talent density to be the primary driver. The implication is significant for leaders: the quality of the people on your team matters less than the quality of the environment in which they work. A team of strong performers in a psychologically unsafe environment will underperform a team of average performers in a psychologically safe one.

The Five Conditions of Effective Teams

A complementary research program at Google identified five conditions that distinguished effective teams from ineffective ones:

• Psychological safety: freedom to take risks without punishment
• Dependability: team members complete quality work on time
• Structure and clarity: clear goals, roles, and execution plans
• Meaning of work: team members find the work personally meaningful
• Impact of work: team members believe their work matters

All five are within a leader's ability to influence directly. Structure and clarity are set by the leader. Dependability is shaped by the accountability culture the leader creates. Meaning and impact are communicated — or not — by how the leader frames the team's work. And psychological safety is built or destroyed by the leader's consistent behaviour.

5A Psychological Safety: The Foundation of Team Performance

Psychological Safety: The Foundation of Team Performance

Psychological safety, as defined by Harvard Business School professor Amy Edmondson, is "a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes."

Teams with high psychological safety outperform those without it on almost every measure. They innovate more. They learn faster. They catch errors earlier. They handle conflict more productively.

The reason is straightforward: in a psychologically safe team, people say what they actually think. They raise the concern they have rather than watching it unfold from a safe distance. They flag the mistake early rather than hoping it goes unnoticed. They challenge the plan rather than nodding and implementing something they believe will fail.

What Destroys Psychological Safety

Psychological safety is fragile. It can be damaged by:

• Reacting defensively or with anger when someone raises a concern
• Shooting down ideas before they are fully formed
• Blaming individuals when things go wrong
• Treating mistakes as evidence of incompetence rather than opportunities for learning
• Rewarding the people who agree with you and sidelining the ones who don't

Building Psychological Safety

Leaders build psychological safety through consistent behaviour, not announcements. The most powerful behaviours are:

• Acknowledging your own mistakes openly — this tells your team that mistakes are survivable
• Responding to concerns with curiosity rather than defensiveness
• Actively inviting the perspective of quieter team members
• Following up on ideas that were raised and letting people know what happened to them
• Being visible about when you changed your mind because of someone else's input

Measuring Psychological Safety

Amy Edmondson's research includes a seven-item survey scale for measuring psychological safety in teams. Leaders who want to understand their team's current level can ask team members to rate their agreement with statements such as:

• If I make a mistake in this team, it is often held against me
• Members of this team are able to bring up problems and tough issues
• People in this team sometimes reject others for being different
• It is safe to take a risk in this team
• It is difficult to ask other members of this team for help

The specific scale is less important than the habit of asking. Leaders who regularly check in on how safe their team feels to speak up — and respond non-defensively to what they learn — create a feedback loop that improves safety over time.

Recovery After a Safety Breach

Every leader, at some point, will do something that damages psychological safety in their team — react defensively to a challenge, dismiss an idea too quickly, or lose their composure in a meeting. What matters is not the breach itself but the recovery.

Leaders who acknowledge the breach directly — 'I reacted to that criticism in a way that was not fair to you, and I want to acknowledge that' — recover safety quickly. Leaders who pretend the breach did not happen force their team to decide whether it is safe to reference it, which creates exactly the kind of uncertainty that erodes safety.

5B Trust and the Five Dysfunctions

Trust and the Five Dysfunctions

Patrick Lencioni's model of team dysfunction identifies five interconnected problems that prevent teams from performing at their best. They build on each other — each dysfunction enables the next.

The Five Dysfunctions

• Absence of trust — team members are not vulnerable with each other; they hide weaknesses and mistakes rather than asking for help or admitting errors
• Fear of conflict — because trust is absent, the team avoids genuine debate; meetings are artificially harmonious while real disagreements go unresolved
• Lack of commitment — because issues were never properly debated, people nod along without genuinely committing to decisions
• Avoidance of accountability — because commitment was never genuine, people avoid holding each other accountable for standards and behaviour
• Inattention to results — team members prioritise personal status and departmental interests over collective outcomes

Building Trust

Trust in a team context is built through vulnerability — the willingness to admit that you do not have all the answers, that you made a mistake, that you need help. As the leader, you set the tone. If you are never wrong, never uncertain, never in need of support, your team will learn to mirror that performance.

Practical trust-building activities include: structured vulnerability exercises in team meetings, acknowledging publicly when you got something wrong, creating forums where team members can share what is actually hard rather than what is going well, and celebrating candour rather than only celebrating success.

Building Vulnerability in a Team

Patrick Lencioni recommends structured vulnerability exercises as a way to build trust quickly in a new team. One of the most effective is a simple personal histories exercise: team members share, for five minutes each, key facts about their background — where they grew up, the number of siblings they have, unique challenges they faced as children. Nothing confidential, nothing deeply personal, but enough to reveal that team members are human beings with histories, not just professional roles.

Research consistently shows that knowledge of each other's personal context significantly increases interpersonal trust. Teams where people know each other as people — not just as job titles — are more willing to assume positive intent when conflicts arise, more likely to ask for help, and more able to have honest conversations.

The Role of Conflict in Building Healthy Teams

Counterintuitively, teams with higher levels of trust experience more conflict, not less. This is because trust creates the safety to disagree. Teams without trust avoid conflict; they create the appearance of harmony while real disagreements go underground.

The distinction to draw is between healthy conflict — substantive debate about ideas, approaches, and priorities, conducted with mutual respect — and unhealthy conflict — personal attacks, passive aggression, or political manoeuvring. The leader's role is to create the conditions for healthy conflict (by making it safe to disagree) and interrupt unhealthy conflict (by naming and addressing behaviour that crosses the line from debate to damage).

5C Team Culture and Accountability

Team Culture and Accountability

Culture is not what you say you value. It is what you do — consistently, particularly when it is inconvenient.

Every team has a culture. The question is whether you have shaped it deliberately or whether it has formed by default around the strongest personalities and most common behaviours. Default cultures are rarely the cultures you would choose.

Shaping Culture Deliberately

Team culture is shaped by:

• What you reward — not just formally, but informally through attention, praise, and recognition. What behaviours get your positive attention?
• What you tolerate — the behaviour you walk past is the behaviour you endorse. If you tolerate rudeness, missed deadlines, or poor quality, you have made a cultural decision
• What you model — your own behaviour is the most powerful cultural signal in the team
• What you celebrate — teams develop identity around what they celebrate together

Mutual Accountability

High-performing teams hold each other accountable, not just upwards. Team members call out underperformance in their peers, not because the leader has told them to, but because they have a shared investment in collective standards.

This kind of mutual accountability does not emerge on its own. It requires explicit conversation about what the team stands for, clear shared standards that everyone has agreed to, and a leader who models accountability rather than only enforcing it from above.

When a team reaches the point where peer accountability is stronger than top-down accountability, you have built something genuinely powerful.

The Stories That Shape Culture

Every team has a set of stories that encode its culture — the incidents, decisions, and moments that team members reference to explain who they are and what they stand for. 'Remember when we stayed all night to make the deadline and the client sent us that incredible message?' 'Remember when the director tried to cut corners and we pushed back?' These stories are the cultural curriculum, passed from team member to team member.

Leaders who understand this deliberately create and curate the stories their team tells. They make sure that moments of exceptional effort, integrity under pressure, or collaborative problem-solving are recognised and retold. They understand that a culture is not built through policy but through story.

Diagnosing Culture Problems

Culture problems almost always show up first in small behaviours before they become large ones. Early signals of a deteriorating team culture include:

• Meetings where the real conversation happens outside the meeting, not in it
• Team members who stop raising concerns — not because there are none, but because they do not expect anything to change
• Blame language — 'they should have' and 'it's not my fault' rather than 'what do we do next'
• Information hoarding — team members protecting their own domain rather than sharing what would help the collective
• Declining initiative — people doing only what they are told, not what they can see needs doing

Noticing these early signals and addressing them directly — in team conversations, not individually — is far more effective than trying to correct a deeply embedded culture problem after it has taken root.

P6 The Real Work of Leadership

The Real Work of Leadership

Most leadership failures occur not from lack of technical competence, but from the inability to influence people over whom you have no direct control.

Authority gives you power over the people who report to you. Influence is what gives you power everywhere else.

Modern organisations require leaders to achieve outcomes through people they do not manage: peers, senior leaders, cross-functional teams, external stakeholders, clients, and regulators. In all of these relationships, you cannot direct. You can only persuade, negotiate, build trust, and create alignment.

The leaders who struggle most in contemporary organisations are those who operate effectively within their reporting line but cannot function outside it. They know how to manage down. They have not learned to lead sideways and upward.

This pillar covers the skills that make influence without authority possible: stakeholder management, executive presence, navigating organisational politics, managing upwards, and building the alliances that allow leaders to get things done.

The Research on Influence

Robert Cialdini's foundational research on influence — documented in Influence: The Psychology of Persuasion — identifies six principles that make influence effective: reciprocity, commitment and consistency, social proof, authority, liking, and scarcity. These principles operate as reliable psychological mechanisms in human decision-making.

For leaders, the most important are reciprocity (people respond to those who have given them something), liking (people are more easily influenced by those they know and trust), and authority (people respond to genuine credibility and expertise). The implication is that influence is built before you need it — through relationship, through giving, and through demonstrating genuine competence.

Influence Versus Manipulation

The ethical boundary in influence is important to understand clearly. Influence is the legitimate use of communication, relationship, and persuasion to bring people to decisions that are genuinely in their and the organisation's interest. Manipulation is the use of those same tools to bring people to decisions that serve your interests at their expense, or through distortion of truth.

The test is simple: would the person agree to your influence if they had full information about your motives and methods? If yes, it is influence. If not, it is manipulation. Ethical leaders influence; they do not manipulate. The distinction matters not only morally but practically: manipulation, when discovered, destroys the relationship capital that makes influence possible.

The Currency of Credibility

Influence runs on credibility, and credibility is built slowly and lost quickly. Leaders build it through three primary mechanisms: expertise (demonstrating genuine knowledge in their domain), track record (consistently doing what they say they will do), and character (behaving with integrity even when it is costly).

Of these three, character is the most durable and the most fragile. A single visible act of self-interest over organisational interest, or of dishonesty when honesty would have been inconvenient, can undo years of credibility building. Leaders who prioritise their credibility over short-term advantage build the most powerful and sustainable form of influence.

The practical implication: protect your reputation for honesty and reliability as you would protect any strategic asset. Be extremely reluctant to say something you cannot deliver. Be honest about limitations and failures rather than managing impressions. The leaders who are most trusted are not necessarily the most capable — they are the most reliably honest.

6A Stakeholder Management

Stakeholder Management

A stakeholder is anyone who has an interest in what you are doing, or whose support you need to succeed. In most leadership roles, there are far more stakeholders than the reporting line suggests.

Stakeholder management is the discipline of identifying those people, understanding what they need, and building the relationships and communication patterns that keep them informed, engaged, and aligned.

Mapping Your Stakeholders

Start by mapping your stakeholders across two dimensions: interest (how much do they care about what you are doing?) and influence (how much power do they have to affect your success?). This gives you four categories:

• High interest, high influence — manage closely; these are your most important relationships
• High interest, low influence — keep informed; they care about what you are doing even if they can't directly affect it
• Low interest, high influence — keep satisfied; they may not be watching you, but they can affect you if they become unhappy
• Low interest, low influence — monitor; minimal time investment needed unless circumstances change

Building Stakeholder Relationships Before You Need Them

The most common stakeholder management mistake is only engaging stakeholders when you need something from them. By then, the relationship is transactional and the goodwill is thin.

Invest in stakeholder relationships continuously. Learn what they are working on. Share information they might find useful. Look for opportunities to support their goals. The relationships you build before you need them are the ones that sustain you when you do.

Stakeholder Communication Cadence

Stakeholder management is not a one-time mapping exercise. It is a continuous practice of maintaining awareness, maintaining relationships, and ensuring the right people have the right information at the right time.

A useful practice is to develop a stakeholder communication cadence — a structured, regular pattern of touch points with your key stakeholders, calibrated to their position on your interest-influence map. High-influence, high-interest stakeholders might warrant a weekly update. Others might be monthly. The cadence creates discipline and prevents stakeholders from feeling overlooked.

Managing Difficult Stakeholders

Every leader has stakeholders who are actively difficult: people who are critical, uncooperative, or actively working against their agenda. The temptation is to avoid or work around them. This almost always makes things worse.

The most effective approach to a difficult stakeholder is direct engagement: seek to understand their concerns genuinely, look for common ground, and be transparent about your own position and interests. People who feel heard and respected are far more likely to moderate their opposition than people who feel ignored.

Where genuine conflict of interest exists and cannot be resolved, involve your manager. Stakeholder conflicts that cannot be managed at your level are appropriate to escalate — not as a failure, but as part of good stakeholder management.

6B Executive Presence

Executive Presence

Executive presence is one of those terms that gets used frequently and defined poorly. At its core, it means this: when you walk into a room, do people believe you belong there?

It is not about height, voice, or wardrobe, though those are elements. It is about confidence, clarity, and credibility — the sense that you have thought through what you want to say, that you believe in it, and that you can handle whatever the room throws at you.

Components of Executive Presence

• Clarity of communication — the ability to express your position or recommendation concisely and without hedging. Rambling, over-qualifying, and excessive caveats all erode presence
• Composure under pressure — staying calm and grounded when challenged, criticised, or in uncomfortable situations
• Visible confidence — not arrogance, but the body language, eye contact, and voice control that signal you believe what you are saying
• Listening as well as speaking — people with genuine executive presence read the room and adjust; they do not simply perform their own script regardless of the response
• Being prepared — presence is often simply the product of knowing your material well enough that you can engage with it freely rather than reciting it

Developing Presence

Presence develops through practice in increasingly high-stakes situations. Volunteer to present to groups. Ask for opportunities to speak at meetings above your usual level. Record yourself and watch it — most people are surprised by what they observe.

Find a mentor or coach who will give you honest feedback on how you come across. The gap between how we think we present and how we actually present is almost always larger than we expect.

Executive Presence in Writing

Executive presence is not just about how you present in person. It extends to everything you produce as a leader — particularly your written communication.

Written executive presence means: getting to the point quickly, using active rather than passive voice, making your recommendation clear rather than leaving the reader to infer it, and writing with the reader's needs rather than your own clarity as the primary goal.

The most common executive writing failure is what consultants call 'burying the lead' — putting the conclusion at the end of a long analysis rather than at the beginning. Senior leaders want the answer first, the evidence second. If they need the evidence, they will ask. This structure — answer first, reasoning second — is called the Pyramid Principle, developed by Barbara Minto at McKinsey.

Preparation as the Foundation of Presence

Many of the components of executive presence — clarity, composure, confidence — flow naturally from thorough preparation. A leader who knows their material deeply does not need to hedge. They can speak directly, engage with challenges without anxiety, and adapt their message to the room because they are not using their cognitive capacity to remember what comes next.

The leaders who seem to have natural executive presence are almost always the ones who prepare more thoroughly than others. Presence is less a personality trait than a preparation discipline.

6C Managing Upwards

Managing Upwards

Managing upwards — building an effective relationship with your own manager and the leaders above you — is a skill that new leaders consistently underestimate and overlook.

Many people assume that their manager's job is to manage them, not the other way around. This is a passive and limiting view. Your manager has limited time, competing priorities, and partial visibility into what you and your team are doing. Your job is to help them understand what they need to know, support their priorities, and make it easy for them to support yours.

What Your Manager Needs From You

• No surprises — let them know about problems early, not when they have become crises
• Concise, relevant information — they do not need to know everything; they need to know the things that affect the decisions they are responsible for
• Your honest assessment — they need you to tell them what you actually think, not what you believe they want to hear
• Solutions alongside problems — when you bring a problem, bring a recommended approach
• Reliability — the things you say you will do, you do

Understanding Their Priorities

Managing upwards starts with understanding what your manager is trying to achieve. What are their goals? What pressures are they under? What does success look like for them? When you understand their world, you can align your work to their priorities, surface the things that matter to them, and avoid inadvertently creating problems for them.

The leader who understands what their manager is trying to achieve and actively helps them get there will always have more influence than the leader who waits to be told what to do.

Understanding Your Manager's World

Effective upward management starts with genuine curiosity about your manager's reality. What are the pressures they are navigating that you are not fully aware of? What are their goals for this quarter, this year? What does success look like for them? What keeps them awake?

Most people in organisations have only a partial picture of their manager's world. They see the decisions that directly affect them but not the broader context in which those decisions are made. Building a richer understanding of that context — through direct questions, through paying attention to what your manager emphasises, and through building relationships with your manager's peers — makes you significantly more effective in managing upwards.

The One-on-One as Upward Management Tool

The regular one-on-one meeting with your manager is your most valuable upward management tool, and it is frequently used badly. Leaders often show up to their one-on-ones with a list of updates and operational questions. This is efficient but misses the real purpose.

A better use of the one-on-one: share your priorities and check they align with what your manager needs from you. Surface problems early enough that they can help. Test your thinking on difficult decisions before you make them. And ask deliberately: 'What do you need from me right now that I might not be providing?' The answer will often surprise you.

6D Navigating Organisational Politics

Navigating Organisational Politics

The word "politics" makes many people uncomfortable, particularly those who prefer to focus on the work itself. But organisational politics are not optional. Every organisation has them. The choice is not whether to engage with them, but whether to engage with them deliberately or to be acted upon by them.

Politics, in this context, simply means the reality that organisations are collections of people with different goals, different interests, and different amounts of influence. Decisions are not made purely on merit. Relationships matter. Alliances matter. Reputation matters.

Navigating With Integrity

There is a difference between navigating politics — understanding and working within the reality of how influence operates in your organisation — and playing politics in the cynical sense of manipulating, undermining, or advancing your interests at others' expense.

Effective leaders do the first without the second. They:

• Understand who has influence on the decisions that matter to them
• Build genuine relationships with those people based on mutual respect and shared interest
• Are transparent about their intentions and their needs
• Look for solutions that address multiple parties' interests, not just their own
• Maintain their integrity even when a less principled approach would be easier

The leaders who are most effective at organisational politics over the long term are those who are known for being straight. Trust is the most durable political currency there is.

Building Alliances for Shared Goals

The most effective leaders in complex organisations are not those with the most authority. They are those with the most alliances — genuine relationships built on shared interest, mutual respect, and a track record of reliability.

Alliance-building is not the same as coalition-building in the political sense. It is simply the recognition that most important goals in organisations require cross-functional cooperation, and that the leaders who have invested in relationships across functions before they need them are far better placed to get cooperation when they do.

When to Surface Conflict Explicitly

Not all organisational politics can or should be navigated through quiet alliance-building. Sometimes the right move is to surface a conflict explicitly — to name a tension that is costing the organisation and propose a structured conversation about it.

This requires significant political judgment: knowing when an issue is significant enough to warrant escalation, whether the people involved are ready to engage with it constructively, and whether your own position is secure enough to absorb the discomfort. It also requires courage — surfacing conflict is risky, even when it is the right thing to do.

Leaders who are willing to name the uncomfortable truth — constructively, in good faith, with a genuine desire to resolve it rather than simply to win — build extraordinary credibility over time.

P7 Escaping the Operational Trap

Escaping the Operational Trap

Leaders move from managing tasks to managing systems. From the urgent to the important. From today to tomorrow.

The single most persistent trap for leaders who came from operational roles is staying in the operational mindset after the role has changed.

Operational thinking is focused on the present: what needs to get done today, what problems need to be solved now, what is at risk of failing in the next 24 hours. It is reactive, task-centred, and necessarily short-horizon.

Leadership requires more than this. Leaders need to see beyond today's task list to the patterns, trends, and decisions that will shape their team's effectiveness over months and years. They need to think about where things are heading, not just where things are.

This is not about abandoning operational discipline. Operational rigour is valuable. But it cannot be the ceiling of a leader's thinking. The leader who is always solving today's problems will never get ahead of tomorrow's.

Making Time for Strategic Thinking

The research on creative and strategic thinking is consistent: insight does not emerge from busy, pressured, distracted minds. It emerges from minds that have been given space.

Leaders who do their best strategic thinking have typically learned to protect time for it — not to fill every meeting slot and respond to every message instantly, but to create regular intervals of unscheduled, uninterrupted thinking. Some do this through regular long walks. Others through journaling. Others through scheduled thinking time that is as protected as any other commitment.

The discipline is cultural as much as personal. Leaders who model the value of thinking time — who are visibly reflective rather than perpetually reactive — give their teams permission to do the same.

The Strategic Versus Operational Balance

Every leader operates on a spectrum between strategic thinking and operational execution. Neither extreme is effective. A purely strategic leader who never engages with the operational reality of their team loses credibility and makes poor decisions — because good strategy is grounded in operational understanding. A purely operational leader who never lifts their eyes above the day-to-day will never contribute to the organisation at the level their role requires.

Most leaders promoted from operational roles start at the operational end of the spectrum. The developmental work is to extend their range upward — to add strategic thinking to their existing operational competence, not to abandon one for the other.

A useful self-diagnostic: track for one week what percentage of your thinking time is spent on what is happening today versus what needs to be different in three to six months. In most leadership roles, the right balance is roughly sixty percent operational and forty percent strategic. Leaders who find themselves at ninety percent operational are probably not creating sufficient value at a strategic level.

7A Seeing the Bigger Picture

Seeing the Bigger Picture

Strategic thinking starts with a simple but demanding discipline: lifting your eyes from the immediate to the broader context.

Most operational managers know their area intimately but have only a partial understanding of the wider organisational context: what the organisation is trying to achieve, what pressures it is navigating, what trends in the external environment will affect it, and how their team's work connects to the organisation's overall direction.

This broader understanding is not a luxury. It shapes every decision a leader makes about priorities, resources, and how to develop their team.

Developing Contextual Intelligence

Contextual intelligence — an understanding of the environment in which you are operating — develops through:

• Reading widely: annual reports, industry publications, board papers if you have access to them
• Asking better questions of your manager and senior leaders: what are they worried about? What opportunities do they see?
• Understanding your customers or stakeholders: what are their pressures and evolving needs?
• Watching patterns in your own team's work: what keeps recurring that points to a systemic problem?
• Creating time for thinking: strategic clarity does not emerge from a full diary

From Operational to Strategic Conversations

A practical signal of whether you have made the shift from operational to strategic thinking is the nature of your conversations with your manager. Are they mostly about what is happening today, or are they often about where things are heading and why? The latter signals a leader who is operating at a strategic level. Aim for that balance.

The Strategic Calendar

One practical tool for developing strategic thinking habits is what some leaders call a strategic calendar — a regular, protected rhythm of strategic reflection built into their week and quarter.

• Daily: ten minutes each morning to ask, 'What is the most important thing I can contribute to today?'
• Weekly: thirty minutes to review what happened, what it means, and what needs to change
• Monthly: two hours to review team performance, relationships, and emerging patterns against the goals that matter
• Quarterly: a half-day offsite or protected thinking session to assess direction, priorities, and whether the strategy is still right

This rhythm does not require heroic amounts of time. The discipline is in protecting it from the operational work that will always fill any space you leave.

Horizon Planning

One practical tool for developing the habit of strategic thinking is what some leaders call horizon planning — deliberately spending time each week thinking about what is on the six-to-twelve month horizon, not just the current fortnight.

Questions that structure horizon planning: What trends in my operating environment should I be tracking? What capabilities will my team need in twelve months that we are not fully developing now? What relationships do I need to invest in before I need them? What decisions are coming that I should be preparing for now?

The leaders who are best at navigating complexity are almost always those who spent time on the horizon before the horizon became the present. Strategic thinking is not a talent — it is a habit sustained by protected time and disciplined questions.

7B Decision-Making Under Uncertainty

Decision-Making Under Uncertainty

One of the most significant differences between operational and leadership roles is the nature of the decisions you make. Operational decisions are often relatively well-defined: the information needed is available, the criteria are clear, and the right answer is findable with enough effort.

Leadership decisions are frequently made under uncertainty: with incomplete information, competing priorities, and consequences that will not be clear for months or years. Waiting for certainty is not an option — decisions have to be made, and made well, with what is available.

Decision-Making Principles

• Separate the decision from the outcome — a decision made well with the information available at the time is a good decision, even if the outcome is poor. The reverse is also true.
• Be clear about what kind of decision this is — is it reversible or irreversible? High-stakes or low-stakes? Reversible, low-stakes decisions should be made fast. Irreversible, high-stakes decisions deserve careful thought.
• Identify your assumptions — most decisions rest on assumptions about how things work. Making those assumptions explicit lets you test them rather than baking them in invisibly.
• Consider the second-order effects — what will happen as a consequence of the decision, and what will happen as a consequence of those consequences?
• Decide and communicate — ambiguity in a leader's decision-making creates ambiguity throughout the team. Make the decision and be clear about it.

The Cost of Indecision

Many leaders default to indecision when they are uncertain. But indecision is itself a decision — usually the worst one. It leaves the team without direction, erodes confidence in the leader, and allows situations to deteriorate. A decision made and executed, even imperfectly, is almost always better than extended deferral.

The Pre-Mortem: Anticipating What Will Go Wrong

The pre-mortem — a technique developed by psychologist Gary Klein and popularised by Daniel Kahneman — is a powerful decision-making tool that counteracts the optimism bias that leads leaders to underestimate the risk in their plans.

The process is simple: before implementing a decision, imagine that twelve months have passed and the decision has been a complete failure. Now ask: what went wrong? What were the factors we did not anticipate? What would we have done differently?

This deliberate pessimism is not negativity. It is a structured way of surfacing risks that enthusiasm and commitment tend to suppress. Teams that run pre-mortems on major decisions consistently catch failure modes that would otherwise only have been identified in hindsight.

Intuition Versus Analysis in Decision-Making

There is a long-standing debate in decision-making literature about the relative value of intuitive and analytical approaches. The current research suggests both have their place, and that the most effective leaders use them in combination.

Intuition — the rapid, unconscious pattern-matching that draws on years of experience — is particularly valuable in familiar situations under time pressure. Analysis is more valuable in novel situations where experience may not transfer reliably, or where the stakes are high enough to justify the investment.

The danger for experienced operational leaders is trusting intuition in situations that feel familiar but have important differences. 'This is just like the problem we had in 2019' — except that the stakeholders are different, the market has changed, and the team is half the size. Intuition pattern-matches; analysis checks whether the pattern actually applies.

7C Systems Thinking for Leaders

Systems Thinking for Leaders

Systems thinking is the ability to see your team, your organisation, and your operating environment as interconnected systems — where actions have effects beyond their immediate target, and where root causes are often distant from their symptoms.

Leaders who think in systems are better at identifying the real cause of recurring problems (rather than repeatedly treating symptoms), understanding the unintended consequences of their decisions, and identifying the high-leverage points where a small change produces a large effect.

The Problem With Linear Thinking

Most of us default to linear, causal thinking: A causes B. This is accurate for simple problems but misleads us in complex systems. In most organisations, the right question is not "what caused this problem?" but "what systemic patterns are producing this problem?" and "what reinforcing loops are keeping it in place?"

A team that keeps missing deadlines might seem to have a workload problem. But deeper investigation might reveal: unclear priorities lead to everything feeling urgent, which leads to poor quality work, which leads to rework, which consumes capacity, which makes deadlines harder to hit. The system is producing the outcome, not any single cause.

Applying Systems Thinking

• When a problem recurs, ask: what is the system that keeps producing this? What needs to change in the system?
• Before making a decision, map out the second and third-order effects
• Look for the delay between cause and effect — many leadership decisions take months to show their impact
• Identify what your team's incentives actually reward, and whether those incentives align with the outcomes you want

Causal Loop Diagrams

One practical systems thinking tool is the causal loop diagram — a simple map of the relationships between variables in a system, showing how changes in one element flow through the system.

A simple example: if you increase the workload on your team, short-term output increases. But if the workload stays high, burnout increases, which increases turnover, which decreases experience in the team, which decreases output — eventually to below the original level. The causal loop diagram makes this dynamic visible before the damage is done.

Leaders do not need sophisticated tools to think systemically. They need the habit of asking: what are the feedback loops here? What is likely to change as a consequence of this change? And what might change as a consequence of those consequences?

The Ladder of Inference

Chris Argyris's ladder of inference is a systems thinking tool that illuminates how leaders reach conclusions that may be poorly grounded in evidence. The ladder moves from observable data at the bottom, through selection of data, attribution of meaning, formation of assumptions, drawing of conclusions, adoption of beliefs, and finally to action — all often in seconds.

The problem is that each step up the ladder introduces potential distortions. We select data that confirms existing beliefs, attribute meanings shaped by past experience, and draw conclusions that reflect our assumptions rather than the full picture. Leaders who are aware of this process — who ask 'what data am I working from?' and 'what am I assuming that I might not be testing?' — make better decisions.

P8 Modern Leadership Is Change Leadership

Modern Leadership Is Change Leadership

Leaders do not manage change. They lead people through it.

If there is one constant in contemporary organisations, it is change. Regulatory environments shift. Markets move. Technology evolves. Leadership teams change. Strategies are revised. Structures are reorganised.

The leaders who succeed in this environment are not those who resist change or manage it from a distance. They are the ones who can help their teams navigate uncertainty, maintain performance during transitions, and adapt to new realities without losing their bearings.

For leaders coming from operational roles, this can be a significant shift. Operations typically reward stability and process discipline. Change disrupts both. The operational instinct is to return to a stable state as quickly as possible. The leadership challenge is to help the team function effectively during the disruption — and sometimes to recognise that the stable state they are trying to return to no longer exists.

The Change Leadership Research

Research on change leadership is extensive and consistent on several points. McKinsey's ongoing research on transformation success has consistently found that 70 percent of large-scale change programs fail to achieve their objectives. The primary causes of failure are not technical but human: insufficient communication, lack of leadership alignment, and failure to address the emotional experience of change.

John Kotter's eight-step model of change leadership (Create urgency, Build the guiding coalition, Form a strategic vision, Enlist a volunteer army, Enable action by removing barriers, Generate short-term wins, Sustain acceleration, Institute change) has been validated through decades of research and practice. The most commonly skipped steps — creating genuine urgency, building a real coalition, and generating visible early wins — are also the most commonly cited as root causes of failure.

The Leader's Emotional Role in Change

During significant change, the leader's emotional role is as important as their operational role. Teams take their emotional cues from their leader. If the leader is anxious, the team becomes anxious. If the leader is calm and clear, the team has a better chance of maintaining equilibrium.

This does not mean leaders should pretend to feel things they do not feel. It means that leaders who are managing significant personal anxiety about a change need to process that anxiety elsewhere — with their manager, a trusted peer, or a coach — rather than letting it permeate their interactions with their team.

The Leader as Change Navigator

Change leadership in a middle-management or team leader role is different from change leadership at the senior level. Senior leaders typically make change decisions. Middle-level leaders are responsible for implementing them — often without having had input into the decision, and sometimes for changes they do not personally agree with.

This creates a genuine challenge. Team leaders are expected to lead their team through changes that they themselves did not choose. They may have concerns about the change. They may believe it is the wrong approach. They may be managing their own resistance while simultaneously being expected to model commitment.

The answer is not to perform enthusiasm you do not feel. It is to be honest about the complexity while being clear about what is expected: 'I understand this change is not what everyone would have chosen, and I have my own questions about it. What I can tell you is that it has been decided, it is what we are doing, and my job is to help us do it well. So let us talk about what we need to do that.'

8A The Psychology of Change

The Psychology of Change

Understanding how people experience change is the foundation of leading it well.

Change, even positive change, typically produces a predictable emotional journey. The intensity varies — a minor process change produces a brief wobble; a major organisational restructure can produce months of disruption — but the pattern is consistent.

The Transition Curve

Based on the work of William Bridges and Elisabeth Kübler-Ross, the transition curve describes what most people go through during significant change:

• Shock and denial — the initial response to change is often disbelief or dismissal. "This won't really happen." "It won't affect us."
• Resistance and frustration — as the reality of the change becomes clear, frustration emerges. This is often expressed as criticism of the change, the process, or the leadership.
• Exploration — as resistance fades, people begin to experiment with the new reality. They start asking practical questions.
• Acceptance and commitment — the change becomes the new normal. Energy returns.

Leaders who know this curve do not panic during the resistance stage. They recognise it as a normal part of the journey, not a signal that the change is wrong or poorly led.

What People Are Really Asking

During change, people are not primarily asking about the logic of the decision. They are asking: Am I safe? Do I matter to the people making this decision? Can I trust the people leading this? Leaders who answer these questions — explicitly and through their behaviour — move their teams through change faster.

The Ending Before the New Beginning

William Bridges made an important distinction between change (the external event) and transition (the internal psychological process). He argued that transition begins not with a beginning but with an ending — and that leaders who skip the ending set up the new beginning to fail.

In practice, this means acknowledging explicitly what is being lost in a change, even when the change is objectively positive. A team restructure may create clearer accountability and better workflows, but it also ends working relationships that people valued. A system upgrade may eliminate frustrating processes, but it also eliminates the comfort of familiarity. Acknowledging these endings — rather than talking only about the exciting new future — helps people move through them more quickly.

Who Is in What Stage?

In any team facing change, different people will be at different stages of the transition curve simultaneously. Some will still be in denial while others have moved to exploration. Some will resist publicly while others will be privately excited.

Leaders who treat the team as a single unit at a single stage make the mistake of either over-processing with people who have already moved on, or under-supporting people who are still struggling. Checking in individually — asking 'how are you experiencing this?' rather than assuming — allows leaders to tailor their support.

8B Communicating Through Change

Communicating Through Change

In the absence of information, people create their own. In an organisational change context, this almost always produces a more alarming story than the reality.

Communication during change is one of the most important things a leader does, and one of the things most commonly done poorly. The errors are predictable: saying too little too late, communicating only the facts without addressing the emotions, giving the same message to everyone regardless of what they actually need to hear, and stopping communication once the announcement is made.

Principles for Change Communication

• Communicate early and often — people would rather hear "we do not know yet" than hear nothing. Silence breeds anxiety.
• Be honest about what you know and what you don't — pretending certainty where there is none is detected immediately and destroys credibility
• Address the emotion, not just the fact — acknowledge that this is hard before explaining why it is necessary
• Be consistent — if different parts of the organisation are hearing different messages, trust breaks down
• Keep communicating — most leaders stop communicating once the announcement is made. This is when the real communication work begins.
• Listen as much as you speak — communication is not broadcasting. Create channels for people to ask questions, raise concerns, and be heard

The Communication Plan

Effective change communication requires a structured plan, not ad hoc messaging. A basic change communication plan addresses:

• What messages need to be communicated — the what, why, and how of the change, and what it means for different groups
• Who needs to communicate them — some messages need to come from the most senior level; others are more effective from the direct manager
• Through what channels — all-hands meetings for broad announcements, team meetings for processing and Q&A, one-on-ones for individual impact
• In what sequence — managers need to know before their teams; stakeholders need to know before the public
• At what frequency — communications should be more frequent in the early stages of a change and taper as the new reality becomes established

Listening During Change

The most common communication failure during change is one-directional: leaders broadcast messages but do not create space for the team's response. This creates the impression that the communication is a formality rather than a genuine dialogue.

Effective change leaders build listening structures into their communication plan: Q&A sessions, anonymous question channels, regular check-ins with a few people from different parts of the team, and genuine openness to having their messaging refined by what they hear. Not all concerns can be addressed. But all concerns deserve to be heard.

The Briefing Before the Brief

A frequently overlooked element of change communication is briefing your team before any wider announcement. Nothing erodes leader credibility faster than a team member hearing significant news from a source other than their direct manager. Being second-to-know when your manager should have told you first is a betrayal of trust.

The discipline of briefing before the brief — ensuring your team hears important news from you, with context and space for questions, before it becomes general knowledge — is one of the highest-trust things a leader does. It signals that your team are a priority, not an afterthought. It gives them the space to process before they are expected to perform. And it gives you the chance to frame the change in the context that is most relevant to them.

8C Innovation and Continuous Improvement

Innovation and Continuous Improvement

Leaders who lead change well also create cultures where change is not something that happens to the team — it is something the team drives.

Innovation does not require large budgets, dedicated R&D teams, or transformation programs. Most innovation in organisations happens through the accumulation of small improvements made by people close to the work. The leader's job is to create conditions where those improvements surface, are tested, and are implemented.

Creating a Culture of Continuous Improvement

• Ask regularly: what is one thing we could be doing better? And then act on the answers
• Celebrate when people identify problems, not just when they deliver results — problem identification is the first step in improvement
• Treat experiments that fail as learning, not failure — if the process was sound and the thinking was honest, a failed experiment is still valuable
• Protect time for improvement work — if everything is urgent, nothing gets better

AI and Digital Transformation

Artificial intelligence and digital tools are changing the nature of most operational roles. Leaders who understand these tools — not at a technical level, but at a strategic and human level — will be better placed to help their teams adapt.

The key leadership questions around AI and digital transformation are not technical: What work will change, and how do we help our team prepare? What skills will become more valuable, not less? How do we govern AI tools in ways that are ethical and accountable? What human capability do we need to develop as AI takes on more routine tasks?

These are leadership questions. They require the same skills — conversation, empathy, strategic thinking, change leadership — that this framework develops.

The Leader's Role in Innovation

Leaders who want their teams to innovate need to be honest about the environment they have created. Innovation requires people to try things that might not work. If failure is punished — even implicitly, through negative reactions or reduced status for people whose ideas do not pan out — innovation will not happen.

Three questions help leaders honestly assess whether their environment supports innovation:

• What is the last idea your team brought you that was genuinely new and that you supported even though it made you uncertain?
• What happened the last time a team member's experiment failed? What was the conversation? What were the consequences?
• How often do your team members suggest approaches you had not thought of? If the answer is rarely, ask why.

AI Tools in the Workplace

The integration of AI tools into knowledge work is accelerating rapidly. Leaders who are navigating this for their teams face genuinely new questions without established answers.

The most important frame is not 'will AI replace my team?' but 'what does my team need to learn to work effectively alongside AI?' Most operational tasks that AI can do well are tasks that free up human cognitive capacity for higher-order work: judgment, creativity, relationship, context, and ethics. Teams that learn to use AI effectively will be able to do more of this higher-order work — if leaders help them make the transition.

The governance questions are also significant. Leaders need to set clear expectations about what uses of AI are sanctioned and what are not, how AI-generated content should be reviewed and attributed, and what data can be entered into external AI tools.

P9 The Most Underestimated Leadership Skill

The Most Underestimated Leadership Skill

You cannot pour from an empty vessel. A leader who is running on empty cannot lead anyone anywhere.

Leadership is emotionally demanding work. You are responsible for the wellbeing, performance, and development of people, often while navigating your own uncertainty and pressure from above. You are holding multiple relationships, managing conflict, making decisions with incomplete information, and being watched by your team for signals about whether everything is going to be okay.

Many new leaders treat their own wellbeing as secondary — something to attend to after the team's needs are met. This is a mistake. Not because your wellbeing is more important than your team's, but because your ability to lead effectively depends on it.

This pillar addresses the personal dimension of leadership: how you sustain yourself, manage your energy, remain authentic, and recover from the setbacks that are an inevitable part of leading people.

The Wellbeing Research

Leadership wellbeing has attracted significant research attention in the past decade. Key findings:

• Chronic stress impairs the prefrontal cortex — the brain region responsible for judgment, planning, and emotional regulation — before it impairs performance metrics. Leaders under chronic stress are making worse decisions long before those decisions show up in their results.
• Recovery quality matters as much as recovery quantity. Eight hours of anxiety-laden sleep is not equivalent to six hours of deep sleep.
• Social connection is a significant predictor of leader resilience. Leaders who are isolated — who lack trusted relationships within and outside work — are significantly more vulnerable to burnout.
• Meaning is protective. Leaders who find genuine meaning in their work are more resilient under the same objective level of pressure than those who do not.

Burnout Versus Stress

Burnout and stress are related but different conditions, and the interventions are different. Stress is an excess of demand over resources — it is usually resolved by reducing demand, increasing resources, or both. Burnout is characterised by emotional exhaustion, depersonalisation (a sense of cynicism or distance from the work and the people), and a loss of sense of personal accomplishment.

Burnout takes longer to recover from than stress and requires different interventions: reconnection with meaning, recovery of agency and control, and often extended time away from the stressful environment. Leaders who treat burnout symptoms as stress and simply try to push through typically make the burnout worse.

The Long Game

Leadership is a career-long practice. The leaders who are most effective at thirty years in are not the ones who arrived with the most natural talent. They are the ones who committed to continued development, who sought honest feedback throughout their career, who were willing to be uncomfortable when comfortable would have been easier, and who treated every leadership experience — success and failure — as material to learn from.

The leaders who plateau are usually those who stopped seeking feedback, who became overconfident in their current approach, or who sacrificed their wellbeing and personal resilience to the relentless demands of the role.

The commitment this framework asks of you is not to master it and set it aside. It is to use it as one strand in an ongoing practice of reflection, learning, and honest self-assessment. Leadership development is not a destination. It is a direction.

9A Building Resilience as a Leader

Building Resilience as a Leader

Resilience is not the ability to avoid adversity. It is the ability to respond to it effectively and recover from it without being fundamentally destabilised.

Leaders face adversity regularly — decisions that go wrong, relationships that break down, results that disappoint, plans that fail to survive contact with reality. The question is not whether these things will happen, but whether you have the resources and perspective to work through them without losing your effectiveness.

The Roots of Resilience

Resilience in leaders is built from several foundations:

• Clear values — knowing what you stand for gives you a stable reference point when circumstances are uncertain
• Strong relationships — leaders with trusted peers, mentors, and managers they can be honest with are better able to process difficulty without isolation
• Perspective — the ability to distinguish between problems that are genuinely serious and problems that feel serious in the moment but are not
• Physical fundamentals — sleep, exercise, and nutrition are not peripheral to leadership performance; they are central to it
• A capacity for reflection — leaders who regularly reflect on their experience — what happened, what it meant, what they would do differently — develop wisdom that protects them against repeating the same mistakes under pressure

Recovery, Not Invulnerability

Resilience is not the absence of struggle. It is recovery. Leaders who pretend they are not affected by difficulty model invulnerability rather than resilience. Their teams learn that struggle is a sign of weakness and hide it accordingly.

Leaders who acknowledge difficulty, manage it visibly and honestly, and recover from it model something far more useful: that adversity is survivable, that vulnerability is not weakness, and that good leaders are human.

The Role of Reflective Practice

Reflective practice — the disciplined habit of examining experience to extract learning — is one of the most consistently supported drivers of leader development in the research literature. Kegan and Lahey's work on developmental stages in adults suggests that the leaders who develop most rapidly are those who are most willing to examine their own assumptions and update them.

The standard model of reflective practice — derived from David Kolb's experiential learning cycle — moves through four stages: experience, reflection, conceptualisation, and experimentation. Leaders who skip the reflection and conceptualisation stages — who go from experience directly back to action — accumulate experience without converting it to learning.

A Weekly Reflection Practice

A structured weekly reflection practice, even brief, produces compounding returns. A simple format:

• What happened this week that surprised me? Surprises are data — they indicate that your mental model of how things work does not match reality.
• What did I do well that I want to build on? Deliberately noting success is as important as learning from failure — and most leaders are better at the latter than the former.
• What would I do differently? Not in a self-critical way, but in a curious learning orientation: what would have worked better?
• What am I carrying into next week? Unprocessed experiences accumulate and affect judgment. Naming what you are carrying helps you manage it.

9B Authentic Leadership and Values

Authentic Leadership and Values

Authentic leadership means leading in alignment with who you actually are, rather than performing a version of leadership that you think is expected of you.

This does not mean that your instincts are always right, or that you should never develop new behaviours that do not come naturally. Authenticity is not an excuse for fixed behaviour. It means that the development you pursue, and the leadership style you build, are genuinely grounded in your own values and identity — not a mask worn to please the organisation above you.

The Confidence to Be Yourself

New leaders are often tempted to emulate the leadership styles of people above them, particularly if those people are successful and respected. This is a reasonable starting point for learning. But leaders who only ever imitate others never develop a distinctive, genuine style that their teams can trust.

The most effective leaders are recognisably themselves — in how they communicate, what they stand for, and how they handle difficulty. Their team knows what to expect, which creates safety and trust.

Values Under Pressure

Values are easy when circumstances are easy. The test of authentic leadership is what you do when living your values is costly — when the honest response is not the comfortable one, when doing the right thing has real consequences.

These moments define your reputation as a leader. They are also the moments your team is watching most closely. A leader who compromises their values when it becomes inconvenient teaches their team that values are decorative, not operational.

The Impostor Syndrome in Leadership

A significant proportion of newly promoted leaders experience some degree of impostor syndrome — the persistent belief that they are not as capable as others believe them to be, and that they will eventually be exposed. Research by Pauline Clance and Suzanne Imes, who first identified the phenomenon, found it was particularly common among high achievers.

For leaders, impostor syndrome can produce a specific failure mode: over-performing to stay safe, avoiding situations where your limitations might be visible, and failing to be authentic because authenticity feels too risky. The irony is that this performance of competence makes leaders less effective — teams follow authenticity more readily than performance.

The most effective antidote is not simply being told you are good enough (this rarely helps). It is the accumulation of evidence through real experience — the repeated observation that you can navigate difficult situations, that people respond positively to you, and that you continue to be capable of learning what you do not yet know.

Leading Authentically in a Hierarchical Environment

Authentic leadership is harder in some organisational environments than others. Highly hierarchical organisations, cultures where showing uncertainty is punished, or environments with low psychological safety at the top make it more difficult to lead authentically at every level.

Leaders in these environments face a genuine tension: between authenticity (leading in a way that is genuinely aligned with who you are) and pragmatism (leading in ways that are safe and acceptable in the culture). There is no universal answer to this tension. What matters is that you are honest with yourself about the trade-offs you are making and why.

9C Managing Your Energy, Not Just Your Time

Managing Your Energy, Not Just Your Time

Time management is a tool every operational professional develops. It is necessary but not sufficient for effective leadership.

Leaders also need to manage their energy — the physical, emotional, and cognitive resources that determine not just whether they get things done, but how well they do them. A leader with twelve hours in the diary but zero cognitive reserve will make worse decisions, miss important emotional signals, and fail to do the kind of thinking that actually moves things forward.

Energy Management Principles

• Protect your recovery time — the recovery between demands is not wasted time; it is what makes the next demand possible. Leaders who never recover do not perform well for long.
• Identify your energy peaks — most people have predictable periods of higher and lower cognitive energy through the day. Schedule your most demanding thinking work during your peaks.
• Manage your emotional load — some interactions and tasks are emotionally draining; others are energising. Be honest about the balance in your day and week, and protect enough of the energising work to sustain you.
• Set boundaries on your availability — being always available is not a leadership virtue; it is a system with no redundancy. Teach your team to solve problems without you when you are unavailable, rather than waiting.
• Build reflection into your routine — fifteen minutes of structured reflection at the end of the day or week produces compounding returns in clarity, learning, and perspective

The High-Energy Leader's Trap

Some leaders — particularly in the early stages of a leadership role — operate on adrenaline and enthusiasm rather than genuine sustainable energy. They work extraordinary hours, take on more than is reasonable, and maintain the pace through a combination of drive, anxiety, and the novelty-energy of a new role.

This phase usually ends badly: in a wall of exhaustion, a significant mistake born of cognitive depletion, or a health event that forces a stop. The leaders who sustain high performance over long periods are those who have built genuine energy management practices, not those who have the most natural stamina.

The Meeting Energy Audit

A useful exercise in energy management is a meeting energy audit: at the end of each meeting, note whether you feel more or less energised than you did going in. Over a few weeks, this creates a picture of which activities and interactions are energising versus draining.

This is not an instruction to fill your diary only with energising activities — that is rarely possible in a leadership role. It is data that helps you manage your energy proactively: scheduling demanding activities during high-energy periods, building recovery time after consistently draining interactions, and ensuring enough energising work in every week to sustain you through the draining parts.

P10 Your Responsibility Beyond the Team

Your Responsibility Beyond the Team

Great leaders require great environments. Organisations are responsible for creating conditions where leadership can flourish.

The first nine pillars focus on what you do as a leader. This pillar addresses something equally important: the environment in which leadership operates.

Individual leaders can only be as effective as the systems, structures, and culture of the organisation around them allow. A leader with exceptional skills working inside a dysfunctional system will produce limited results. And leadership programs that invest heavily in individual capability while leaving the organisational system unchanged will produce graduates who go back to the same environment and revert within months.

This pillar addresses what effective leaders do to shape the environment around them — and what organisations need to do to support leaders at every level. If you are a senior leader reading this, this pillar is particularly important. If you are a newer leader, it is about advocating for what you and your team need, and contributing to the kind of culture that makes good leadership possible.

The System Enables or Constrains Leadership

The research on leader failure consistently shows that individual-level explanations — bad character, wrong personality, insufficient skill — account for less of the variance than we assume. Contextual factors — the quality of the organisation's systems, its culture, the clarity of expectations and accountability, the resources available to leaders — account for a substantial share.

This is why individual leadership development, without complementary organisational system development, produces limited results. A leader who learns to coach effectively but returns to an organisation that rewards directive behaviour will struggle to apply what they have learned. A leader who develops strategic thinking capability but is never given the time or space to think strategically will revert.

What Organisations Owe Their Leaders

If you are a senior leader reading this pillar, the research is clear about what organisations owe the people they ask to lead:

• Role clarity — what is expected, how success will be measured, what authority they have
• Development support — not just for the leaders under them but for themselves
• Feedback — honest, useful, timely feedback from those above and below them in the hierarchy
• Resources — the people, budget, and tools to do what they have been asked to do
• Protection from excessive demand — particularly in the early stages of a leadership role

Leaders who do not receive these things from the organisation above them face a harder task. They can compensate for some of what they are missing, but they cannot fully compensate for systematic organisational failure.

10A Culture as a Leadership Tool

Culture as a Leadership Tool

Culture is the most powerful and most underused leadership tool available. It operates 24 hours a day, shapes every decision your team makes, and cannot be faked for long.

Leaders who understand culture use it deliberately. They know that the team they lead has a culture — a set of assumptions, norms, and behaviours that govern how people act when the leader is not present. And they take responsibility for shaping that culture rather than leaving it to chance.

The Leader's Cultural Impact

Everything you do as a leader sends a cultural signal:

• The questions you ask in meetings signal what you think matters
• The way you respond to mistakes signals whether it is safe to take risks
• The way you treat people when they are not in the room signals whether respect is genuine or performative
• The things you celebrate signal what success looks like
• The things you tolerate signal the actual floor of acceptable behaviour

Cultural norms are not set by policy documents or values statements. They are set by consistent leader behaviour over time. If your behaviour and your stated values are misaligned, the team will follow your behaviour, not your words.

Culture Diagnostics

Leaders who want to understand their team's culture honestly need data beyond their own observation. Their position in the hierarchy means they see a curated version of the team's culture — the version that is displayed when they are present.

Useful diagnostics include: anonymous team surveys, regular structured one-on-ones where you explicitly ask about how the team is functioning, and the patterns you observe in behaviours when you are not actively facilitating — who talks to whom, what topics get raised and what do not, how people respond when things go wrong.

Culture as Competitive Advantage

The case for investing in team culture is not purely about individual wellbeing. Culture is a competitive advantage.

Teams with strong, healthy cultures retain their members longer (reducing the enormous cost of turnover and lost institutional knowledge). They attract better talent (people choose teams as well as organisations). They perform more consistently (because cultural norms provide structure that survives individual variation). And they adapt to change more effectively (because trust and psychological safety make experimentation possible).

Leaders who build strong team cultures create something that outlasts their own tenure. The team that continues to perform well after you have moved on is the mark of genuinely effective leadership.

10B Mentoring, Succession, and Leadership Pathways

Mentoring, Succession, and Leadership Pathways

One of the clearest markers of a mature leader is their willingness to develop others — not just to produce short-term results, but to build the next generation of leadership capacity in the organisation.

This requires a genuine shift in how you think about your own success. Operational high performers typically define success in terms of their own output. Leaders who create lasting impact define success in terms of what continues to happen after they leave.

Mentoring

Mentoring is different from coaching. A coach helps someone work through their current challenges. A mentor shares their own experience, perspective, and networks to accelerate someone else's development.

As you develop as a leader, you accumulate experience that is genuinely valuable to people earlier in their journey. Sharing that experience through mentoring relationships is one of the highest-leverage things you can do — for the person you are mentoring, for your organisation, and for your own development as a leader.

Building Succession

Leaders who build strong succession plans are doing something counterintuitive: they are developing people who could do their job. This feels threatening to some leaders. It should not. A leader who has a capable successor is free to develop, move, and take on new challenges. A leader whose team cannot function without them is trapped.

Identify the two or three people in your team with the most leadership potential. Give them opportunities. Challenge them. Invest in their development. The organisation benefits, and so do you.

The Mentoring Relationship

An effective mentoring relationship has several characteristics that distinguish it from a friendship or a coaching relationship:

• The mentor has genuine experience relevant to the mentee's aspirations or challenges
• The relationship is mentee-led — the mentee brings the agenda, not the mentor
• The mentor shares experience and perspective but does not prescribe — they offer their view and leave the mentee to decide what to do with it
• The relationship has appropriate boundaries — the mentor is not managing the mentee, which preserves the freedom to be honest
• There is genuine mutual benefit — good mentoring relationships are not charity; mentors gain fresh perspective, challenge to their assumptions, and satisfaction from contributing

Identifying Leadership Potential

Identifying people with genuine leadership potential — as distinct from strong operational performers — is itself a skill that most leaders develop slowly.

Research by Claudio Fernandez-Araoz, Boris Groysberg, and Nitin Nohria identifies potential across five dimensions: curiosity (a hunger for new ideas and learning), insight (the ability to gather information and find connections), engagement (the ability to connect with and motivate others), determination (the drive to do whatever it takes and bounce back from setbacks), and responsibility (the sense of ownership for outcomes beyond one's own role).

Notably, this list does not include technical expertise or current performance. Strong operators are not necessarily strong leadership potential. The distinction, made early and honestly, allows organisations to develop their real leadership pipeline rather than promoting on the wrong criteria.

10C Building a Learning Organisation

Building a Learning Organisation

The final aspiration of this framework is not to produce competent individual leaders. It is to produce leaders who build organisations that learn.

A learning organisation is one where mistakes become knowledge, experience is shared rather than hoarded, improvement is continuous and everyone's responsibility, and leaders at every level are developing their capability rather than just their output.

What Leaders Can Do

• Create regular forums for learning — after-action reviews, team debriefs, and retrospectives that are genuinely about learning, not about blame
• Share what you are learning — model intellectual curiosity and openness to new ideas
• Invest in development as a leadership priority — not a nice-to-have that disappears when budgets tighten
• Ask the uncomfortable questions — what are we not doing well? What are we avoiding? What would we do differently if we could start again?
• Celebrate learning, not just outcomes — acknowledge the team member who changed approach based on evidence, not just the team member who hit their number

Your Leadership Legacy

This framework began with a simple proposition: the transition from operator to leader is one of the most significant professional shifts most people will make, and most organisations leave people to make it without the tools they need.

You now have those tools. What you do with them is up to you.

The leaders who make the greatest impact are not those with the most technical skill or the most impressive credentials. They are the ones who genuinely committed to the ongoing work of leading well — who stayed curious, stayed honest, and never confused their own comfort with their team's best interests.

That is the work. This framework is a starting point.

The Learning After Action Review

After-action reviews — structured reflections on what happened, why it happened, and what to do differently — are one of the most consistently effective tools for building a learning culture. They originated in the US military but have been adopted by high-performing teams across industries.

A simple structure:

• What did we intend to happen? — establishes the reference point against which to measure what actually occurred
• What actually happened? — factual description without interpretation or blame
• Why was there a gap? — root cause analysis, not blame attribution
• What will we do differently? — specific, actionable changes to process, behaviour, or planning

After-action reviews work only when they are genuinely safe — when people believe the purpose is learning, not accountability. Leaders who use after-action reviews to identify who was responsible for what went wrong will find the process stops producing honest information very quickly.

Your Next Twelve Months

This framework has covered the ten fundamental pillars of the leadership transition. The question is what you do next.

A useful commitment is to identify the three pillars where the gap between where you are now and where you want to be is largest, and to commit to one specific development action in each of those three areas over the next 90 days. Not everything. Three things, specifically, with a clear date and a clear measure of whether you did them.

Leadership development is not a program you complete. It is a practice you maintain. The leaders who grow most consistently over a career are not those who attended the most training; they are those who brought the most honest self-reflection, the most willingness to be uncomfortable, and the most commitment to the ongoing work of learning what it means to lead well.

That is the work. You have the tools. The rest is up to you.

TM1 TM1: The Day You Stopped Doing the Work

Transition Moment 1: The Day You Stopped Doing the Work

The Situation

You have been in your new team leader role for six weeks. The team is working on a project you know inside out — you delivered a similar one yourself two years ago. You can see clearly that one of your team members is taking an approach that is inefficient and probably will not produce the quality the client expects.

You have two choices. Step in, correct the approach, and deliver the outcome you know is achievable. Or stay back, ask questions, and let your team member work through it — accepting that the outcome might be less clean than if you had done it yourself.

The Old Response

You sit down with your team member, show them the better way, and take over the key sections to make sure they are right. The project lands well. You feel productive. Your team member smiles and says thank you.

What Actually Happened

Your team member now knows that when things get hard, you will fix it. They did not learn how to approach this type of work. They did not build confidence in their own judgment. And they have just received confirmation that their job is to execute your instructions, not to develop their own capability.

The Leadership Response

"I can see a few things that might make this tricky — can we talk through your approach? What are you trying to achieve in this section?" You ask questions. You share the principles rather than the solution. You let them reach the better approach — or a different but workable one — themselves.

It takes longer. The output may not be exactly what you would have produced. That is the price of development. Over six months, the cost of that extra time is repaid many times over in a team member who can work without you.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• When have you stepped in and solved something your team member could have worked through themselves? What was your reason in that moment?
• What would you have had to give up — what control, what certainty, what speed — to have stayed back and asked questions instead?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

TM2 TM2: When Your Emotions Got in the Way

Transition Moment 2: When Your Emotions Got in the Way

The Situation

Your manager publicly questioned a decision you made, in front of other team leaders at a management meeting. The criticism felt unfair — they did not have the full context, and the decision had been a reasonable call with the information available at the time. You felt your face flush. You wanted to defend yourself immediately and forcefully.

The Old Response

You defended the decision in the meeting, with more heat than light. Your manager backed off, but the dynamic in the room shifted. Afterwards, two colleagues mentioned that you seemed rattled.

What Actually Happened

You allowed your emotional reaction to override your judgment. You prioritised being right in the moment over managing the long-term relationship with your manager and your credibility with your peers. Even if your defence was factually correct, the way it landed communicated that you struggle with criticism.

The Leadership Response

Take a breath. Make a brief, calm acknowledgment: "I am happy to talk through the reasoning behind that — can we pick it up after the meeting?" This does three things: it signals that you are not rattled, it defers the conversation to a setting where you have more control, and it creates space to gather your thoughts rather than react from your amygdala.

In the follow-up conversation, explain your reasoning clearly and without defensiveness. Listen to your manager's perspective. You may find they had information you did not, or that their criticism was partly valid. Or you may confirm that you made the right call and can now explain it calmly. Either way, you come out ahead.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• What are your most reliable emotional triggers in a leadership context? What situations reliably produce a reaction before a response?
• What would staying calm have required from you in a moment where you did not? What practice would help you do that more consistently?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

Building the Pause

The gap between stimulus and response — the space in which self-regulation lives — can be deliberately widened with practice. Leaders who build a consistent physical and psychological pause response are significantly better able to choose their reactions under pressure.

Common pause practices used by experienced leaders: a deliberate breath before responding in any high-stakes interaction, a phrase that buys thinking time ('Let me think about that before I respond'), a physical reset like briefly standing or changing position, and the mental question 'What do I want the outcome of this interaction to be?' — which redirects from reactive mode to purposeful mode.

Like any physical skill, these practices need to be rehearsed in lower-stakes situations before they become available in high-stakes ones. The leader who only tries to pause when they are triggered by something significant will find the pause is not yet reliable.

TM3 TM3: The First Difficult Conversation

Transition Moment 3: The First Difficult Conversation

The Situation

One of your team members — someone you get on well with and who was a peer before your promotion — has been consistently late with their deliverables for the past month. The team is covering for them, and you can see the tension building. You have not said anything yet because you do not want to damage the relationship.

The Old Response

You continue not saying anything. You redistribute the work quietly. You hope it resolves itself. After another month, the pattern has worsened, two team members have come to you separately to express frustration, and you have to have the conversation in a context that now also involves team conflict.

What Actually Happened

By avoiding the conversation, you made it harder. The issue grew. Your team lost confidence in your willingness to address problems. The team member who was underperforming received no feedback that might have helped them correct course. And you arrived at the difficult conversation at a worse moment than if you had addressed it early.

The Leadership Response

Have the conversation early, privately, and directly. "I want to check in with you about the last few deadlines — I have noticed they have been slipping, and I want to understand what is going on."

Stay curious. There may be something happening for this person — personal circumstances, a workload problem, a skills gap — that you were not aware of. Address the behaviour, understand the cause, and agree on what will change. Set a clear expectation and a checkpoint. Then follow through.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• Is there a conversation you are currently avoiding? What are you telling yourself to justify the avoidance?
• What is the likely cost of continuing to avoid it? What would be different in your team if you had it?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

The Courage to Act Early

Research on performance management consistently shows that the longer a performance problem goes unaddressed, the harder it becomes to resolve — for the manager, for the team member, and for the team. Early conversations, when the gap between standard and performance is still small, are almost always easier than late conversations, when the gap has grown and the dynamics have hardened.

New leaders often wait because they are not sure of their ground. They wonder if they have enough evidence, whether they are reading the situation accurately, or whether addressing it will make things worse. In almost all cases, the cost of waiting exceeds the risk of acting. A conversation held with care and genuine curiosity, even if imperfectly, almost always produces a better outcome than continued avoidance.

TM4 TM4: When You Knew the Answer But Shouldn't Give It

Transition Moment 4: When You Knew the Answer But Shouldn't Give It

The Situation

A team member comes to you with a problem they are stuck on. You know exactly what they should do. You could resolve it in sixty seconds. Instead, you ask: "What have you tried so far? What options can you see?"

They look slightly surprised — they expected you to just tell them. They think for a moment and offer two options, both of which are less good than the approach you had in mind. You ask: "Are there any other approaches you have not considered?" After more thought, they land on something close to what you would have suggested.

What Happened

It took ten minutes instead of sixty seconds. But your team member developed their analytical process. They experienced the satisfaction of finding a good solution themselves. They are more likely to try to solve the next problem before bringing it to you. And they have just received a signal that you believe in their capability.

When to Just Give the Answer

Not every situation calls for a coaching approach. If the deadline is twenty minutes away, give the answer. If the stakes of getting it wrong are high and the learning opportunity is low, give the answer. Coaching is not a universal principle — it is a tool. Use it where the development value justifies the time investment.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• What are the areas where you find it hardest to ask instead of tell? What does that tell you about your assumptions in those areas?
• When was the last time you were genuinely surprised by the quality of a team member's thinking when you gave them space to show it?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

The 'Just Tell Me' Dynamic

One of the challenges in shifting to a coaching approach is that some team members — particularly in the early stages — will actively push back. They are used to a directive leader. They prefer efficiency over development. And when you ask a question instead of giving an answer, they experience it as either evasion or unnecessary process.

Managing this dynamic honestly is important. You can name it directly: 'I am going to ask you questions rather than give you answers, and I know that might feel slower. The reason is that I want to help you develop your own judgment here, not just get this one problem solved.' Most people, when they understand the reason, are willing to engage.

Those who are not willing to engage — who consistently resist the coaching approach even when it is explained — are often carrying assumptions about what managers are for that are worth surfacing in a direct conversation.

TM5 TM5: When the Team Wasn't Performing

Transition Moment 5: When the Team Wasn't Performing

The Situation

Three months in, you can see that your team is not functioning well as a team. They each deliver their individual work adequately, but they do not support each other. In team meetings, conversation is superficial. People are polite but not honest. When one person is overloaded, others do not offer to help. There is no sense of collective purpose.

The Diagnosis

This is a trust and psychological safety problem, not a skills problem. Individual performance is adequate, which means the people are capable. But the team has not developed the conditions for collective performance.

The Leadership Response

Host a team conversation — not about work, but about how the team works. Ask: what do we do well as a team? What makes it hard to work together? What would a great team look like for each of you?

This conversation will be uncomfortable if trust is low. You will need to go first — share something honest about your own leadership that you are working to improve. Model the vulnerability you are asking for.

Build from there. Create rituals that reinforce collective identity. Acknowledge collaboration when you see it. Address behaviour that undermines the team quickly and directly. Change happens slowly, but it starts with one honest conversation.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• How would you currently rate your team's level of psychological safety on a scale of one to ten? What evidence supports that rating?
• What is one behaviour of yours that might be limiting your team's willingness to be honest with you?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

Building From Where You Are

Team cultures do not change overnight. A team that has low trust and limited psychological safety did not arrive there suddenly, and it will not leave those conditions suddenly either. Change happens through accumulation of consistent, small signals over time.

The most important thing a leader can do after diagnosing a team culture problem is to commit to visible, consistent behaviour change — and to sustain that commitment through the period of scepticism that almost always precedes genuine team change.

Teams that have been poorly led will not immediately believe that the new leader is different. They will test. They will wait for the moment when the leader's stated values and their real behaviour diverge. The leaders who build new team cultures are those who pass enough of these tests — over enough time — that the team can genuinely believe the new reality is real.

TM6 TM6: When You Needed Something You Couldn't Demand

Transition Moment 6: When You Needed Something You Couldn't Demand

The Situation

You need significant support from a team in another part of the organisation — IT, finance, or another operational area — for a project your team is running. They are not obligated to help you. They have their own priorities. Your manager cannot or will not direct them.

The Old Response

You send an email with the request. You get a vague response that suggests it will be considered. Two weeks pass. Nothing happens. You escalate to your manager, which creates friction. The project is delayed.

The Leadership Response

Before you need anything, invest in the relationship. Go and meet the leader of that team. Find out what they are working on. Look for ways to be useful to them. Build a genuine peer relationship, not a transactional one.

When you need their support, your ask lands in a context of relationship, not just obligation. You can frame it in terms of mutual benefit — what does helping you do for them? You can be specific about what you need and flexible about how they provide it. And if they say it will take time, you have enough relationship to have an honest conversation about the competing priorities.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• Who are the stakeholders outside your direct team whose support you most depend on? How strong are those relationships right now?
• Have you built those relationships proactively, or do you primarily engage with them when you need something?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

The Long Game of Relationship Investment

The leader who is best at influence without authority is the one who has been investing in relationships consistently and without an agenda for years. They know people across the organisation. People trust them because they have a track record of good faith. When they need help, they are not strangers making a request — they are trusted colleagues asking for a favour.

This cannot be manufactured quickly when you need it. It has to be built gradually through genuine engagement. The practical discipline is this: every week, identify one person in the organisation outside your team whose relationship you could invest in. Have a conversation. Find out what they are working on. Look for a way to be useful. Over time, this practice builds the network that makes everything else possible.

Leaders who wait until they need something to invest in relationships will always be in a transactional position. Leaders who invest continuously will always have relational capital to draw on.

TM7 TM7: When the Urgent Crowded Out the Important

Transition Moment 7: When the Urgent Crowded Out the Important

The Situation

You are four months into your role. You have meant to do a proper review of your team's capability gaps, build relationships with key stakeholders, and develop a clear six-month plan. But every week, the urgent work crowds out the important work. You feel busy. You are not sure you are being strategic.

The Diagnosis

This is one of the most common leadership traps. Urgent work is visible, concrete, and produces immediate feedback. Important work — relationship building, capability development, strategic planning — is invisible in the short term, feels less satisfying than completing tasks, and is easy to defer.

The Leadership Response

Schedule the important work as if it were a meeting you cannot cancel. Block two hours per week for non-urgent work. Be explicit with your team that this time is protected and why.

Use the Eisenhower Matrix: separate your work into four quadrants — urgent and important, important but not urgent, urgent but not important, and neither urgent nor important. Most leaders spend almost all their time in the first quadrant. The most important work is in the second.

The discipline of protecting time for important, non-urgent work is one of the clearest indicators of whether a leader is operating strategically.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• What important, non-urgent work have you been deferring? How long have you been deferring it?
• What would you need to protect differently in your calendar to make space for more strategic work?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

The Eisenhower Matrix in Practice

The Eisenhower Matrix (also called the urgency-importance matrix) divides all work into four quadrants. Most leaders spend the majority of their time in Quadrant 1 (urgent and important) and Quadrant 3 (urgent but not important). The most valuable work — relationship building, strategic planning, capability development, innovation — lives in Quadrant 2: important but not urgent.

The fundamental problem with Quadrant 2 work is that it never becomes urgent until the deadline you should have been working towards all along is suddenly upon you. The stakeholder relationship you have been meaning to invest in only becomes urgent when that stakeholder becomes a blocker. The capability gap in your team only becomes urgent when it causes a project to fail.

The leaders who do the most important strategic work are those who have learned to treat Quadrant 2 priorities with the same discipline they bring to urgent deadlines — scheduling them, protecting them, and refusing to sacrifice them to the relentless pressure of the urgent. This is a cultural choice as much as a time management choice. It signals to your team that important work gets done, not just urgent work.

TM8 TM8: When the Team Pushed Back on Change

Transition Moment 8: When the Team Pushed Back on Change

The Situation

You have been asked to implement a significant change in your team's processes — a new system, a restructured workflow, or a change in how work is prioritised. You think it is a good change. Your team does not. Two people tell you directly they think it is a mistake. Others are quiet, but their body language tells you what they are not saying.

The Old Response

You push through. The change is coming regardless, so you communicate it as a done deal, manage the immediate objections with reassurance, and get on with implementation. Compliance is achieved. Commitment is not.

The Leadership Response

Name the resistance rather than manage around it: "I can see this is landing differently for different people. I want to understand the concerns before we go further."

Create a genuine space for concerns to be aired — not to reverse the decision, but because some of the concerns will be valid and should inform how the change is implemented. And because people who feel heard are more willing to commit than people who feel overridden.

Then be honest about what is fixed and what is flexible. "The what is decided. The how is something we can shape together." This gives people genuine agency within real constraints, which is almost always available even when the decision itself is not.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• How do you typically respond to resistance? Do you move through it quickly, or does it cause you to slow down and genuinely engage?
• When have you been on the receiving end of change that was imposed without engagement? What would have made it easier to accept?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

When the Resistance Is Right

Not all resistance to change is dysfunction. Sometimes the people resisting a change have information, perspective, or concerns that are genuinely important — that the change as designed has a flaw that the resisters can see and the decision-makers could not.

Leaders who dismiss all resistance as simple adjustment difficulty miss opportunities to improve changes before they are implemented. The discipline is to separate the emotional resistance (which is normal and does not need to change the plan) from the substantive concern (which may warrant adjusting the plan).

A useful question when you encounter resistance: 'What would need to be true for this concern to be a genuine problem with the change?' If the answer is 'something we haven't fully thought through', that is worth taking seriously. If the answer is 'something we have thought through carefully and decided is manageable', you can acknowledge the concern, share the reasoning, and proceed with confidence.

TM9 TM9: When You Were Running on Empty

Transition Moment 9: When You Were Running on Empty

The Situation

Six months in, you are exhausted. The role has been more demanding than you expected. You have been carrying the emotional weight of several difficult team situations, working long hours to cover a gap in the team, and spending your weekends catching up on the thinking work you cannot get to during the week. You snap at a team member in a meeting — not badly, but enough to notice, and enough for them to notice.

What Happened

You have been managing your time but not your energy. You have been treating your own wellbeing as a resource to be consumed rather than an asset to be maintained. The snap was a symptom. The cause is deeper.

The Leadership Response

Stop. Not forever, but enough to recover. Take the leave you have been postponing. Protect a weekend. Have an honest conversation with your manager about what is sustainable.

And then, build recovery into your routine before you reach the edge again. Identify the practices that restore your energy — physical exercise, solitude, connection with people outside work, sleep — and protect them with the same seriousness you protect your calendar.

Acknowledge the snap to your team member. A brief, direct acknowledgment — "I was short with you in that meeting and I want to apologise" — rebuilds trust faster than pretending it did not happen.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• What are your early warning signs that you are approaching exhaustion? Do you notice them reliably?
• What recovery practices do you have in place that you genuinely protect? What practices have you abandoned under pressure that you should restore?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

The Apology as Leadership Tool

Leaders who can apologise clearly and without excess are more trusted, not less. The apology signals that they are self-aware enough to recognise their impact, honest enough to name it, and secure enough to not need to defend or explain every mistake.

An effective leadership apology has three elements: acknowledgment of what happened, recognition of the impact, and a clear commitment to what will change. It does not include extensive explanation or justification — which transforms an apology into a defence. It does not require the other person to accept or acknowledge the apology — the apology is an act of integrity, not a transaction.

TM10 TM10: When the System Worked Against You

Transition Moment 10: When the System Worked Against You

The Situation

You have done the work. You have developed your team. You have led well. But the organisation around you is not structured to support what you are trying to do. The processes are slow, the culture above your level does not reflect the culture you are building in your team, and the things you are trying to change keep running into invisible resistance.

The Reality

This is the hardest transition moment, because it is not solvable purely through individual effort. The environment matters. Leaders can shape the culture of their own team, but they have limited ability to reshape the system around them.

The Leadership Response

Do what you can within your sphere of control. Your team's culture is yours to shape. Focus there first.

Build alliances with other leaders who share your values. Change in organisational systems rarely comes from individual advocates — it comes from groups of leaders who consistently model and advocate for different ways of working.

Be honest with your manager about what is getting in the way. Not as a complaint, but as a problem you want to solve: "I want to talk about a few systemic things that are making it harder for my team to perform. Can we find time to work through them?"

And if the system is genuinely incompatible with leading with integrity, make the decision about whether to continue to work within it, try to change it from within, or find a different environment. That is a legitimate choice, and sometimes the right one.

For Reflection

After reading this Transition Moment, take a few minutes to consider:

• What aspects of your current organisational environment make it hardest to lead the way you want to lead?
• What is within your control to change, even if the broader system is not? What is the most important thing you can do within your sphere of influence?

What This Tells Us

Transition Moments are designed to make the abstract concrete. The situations above are composites, but the dynamics they describe are real and recurring. If any of them felt uncomfortably familiar, that recognition is valuable data — not a judgment on your leadership, but a signal of where your growth edge is right now.

Choosing Your Environment

The final and most important decision a leader can make about their environment is whether to stay in it. Not every organisational system is worth investing years in trying to change. Some environments are genuinely incompatible with leading well — where the culture above is toxic enough, or the structural constraints are tight enough, that the cost of staying outweighs what can be achieved.

Making this determination honestly requires separating the environment from your frustration with it. It is easy to conclude a system is broken when you are exhausted and things are hard. It is also easy to rationalise staying in an unhealthy environment because leaving is uncertain.

The questions worth sitting with: Is there evidence that the environment is changing? Do I have genuine allies and enough influence to contribute to that change? Can I maintain my integrity and lead the way I want to lead within these constraints? If the honest answers are no, that is important information — not failure, but clarity.

T1 Tools Overview

Tools Overview

The Leadership Transition Framework toolkit contains practical tools and templates you can download and use immediately. They are designed to be applied to real situations, not kept in a folder.

The tools are organised to support the ten pillars:

• Leadership Readiness Self-Assessment — a structured self-assessment to identify your development priorities across the ten pillars
• EQ Self-Assessment — a detailed assessment of your emotional intelligence across Goleman's five components
• Emotional Trigger Map — a template for mapping your triggers, their causes, and your strategies for managing them
• Conversation Planning Template — a structured guide for preparing difficult conversations
• Feedback Framework (SBI) — a one-page reference guide for giving specific, behavioural feedback
• Coaching Question Bank — a curated collection of coaching questions organised by leadership situation
• Delegation Decision Matrix — a tool for deciding what to delegate, to whom, and how
• Team Health Check — a structured assessment of your team's culture, trust, and collective performance
• Stakeholder Influence Map — a template for mapping and prioritising stakeholder relationships
• 90-Day Leadership Transition Plan — a structured plan for the first 90 days in a new leadership role
• Leadership Reflection Journal — a weekly reflection template to accelerate your development
• Values Identification Worksheet — a guided process for clarifying your leadership values

All tools are available for download in the Resources section.

Using the Resources Section

The resources in the Leadership Transition Framework have been designed for immediate practical use. Each one addresses a specific leadership situation and can be downloaded and applied independently.

Do not download all the resources at once. Use them when you face the situation they address. A delegation decision matrix used the day you are working through a specific delegation challenge is worth ten times more than one read through abstractly.

Building Your Personal Learning Plan

The most effective way to use this framework over time is to build a personal learning plan that identifies your specific development priorities, the actions you will take to address them, and how you will know whether you are making progress.

A personal learning plan for a leader has four elements:

• Current state: an honest assessment of where you are across the ten pillars (use the Leadership Readiness Self-Assessment as your starting point)
• Development priorities: the two or three pillars where development will have the greatest impact on your effectiveness
• Development actions: specific things you will do — a conversation you will have, a tool you will apply, a relationship you will invest in
• Review points: when and how you will assess whether you are making progress

Revisit your plan every 90 days. Leadership development is not linear — what matters most will shift as your role evolves, as your team changes, and as you move through different organisational challenges.