Category: General

Most leaders are quietly exhausted by an invisible trap: the belief that a job title dictates everything a person should or can do. When things fall through the cracks on a team, we tend to assume it’s a performance issue, a lack of initiative, or a bad culture fit.

More often than not, it’s a structural illusion. We have confused the person with the position, leaving critical work unowned while high performers burn out trying to be everything to everyone.

The Source / Framework

Psychotherapist Phil Stutz highlights the danger of fusing your core identity with a static snapshot of your external role. When you treat a temporary function as your entire identity, any failure in the process feels like a personal flaw, and any change feels like a threat.

In organizational life, frameworks like Sociocracy offer a direct solution to this psychological weight: decouple the person from the function. Traditional job descriptions bundle dozens of disparate activities into a static title like “Product Manager”. Role-based work, by contrast, separates work into lightweight, explicit responsibilities that anyone with the right capability can perform.

The Reframe

The territorial behavior, boundary wars, and classic “that’s not my job” pushback on your team aren’t signs of poor character. They are signals of unmapped responsibility and a symptom of “exclusive permission” thinking.

The reframe is powerful: Roles create positive responsibility, not exclusive territory. If someone holds the “Security” role, it simply means they have explicitly taken responsibility for doing that body of security work. It doesn’t mean nobody else is allowed to care about, discover, or fix a vulnerability.

Furthermore, holding a role defines work you do, not work you just make others do. True accountability is an active practice of performing the recurring work, not passive oversight.

Leadership Application

1. Unpacking the Core Elements

To fix these structural tensions, start by separating four distinct concepts in your organizational design:

• Person: An individual member of the organization bringing human energy.
• Capability: Something that person actively knows how to do right now.
• Role: A coherent body of work and responsibility in the system.
• Actor: Who or what (human, AI, external team) currently performs that role.

2. A Concrete Example: The Small Development Team

Imagine a software team of five people developing and operating a product. Instead of relying solely on titles like “Architect” or “Developer,” the team identifies the actual work required across three distinct role families:

• Delivery Roles: Work that directly creates value through the product, such as Product, UX, and Development.
• Stewardship Roles: Active work that protects an important quality of the system over time, such as Architecture, Quality, Security, and Documentation.
• Team-System Roles: Work that helps the team function, learn, and evolve, such as Meeting Facilitator, Decision Recorder, Onboarding Guide, and Team Improvement Steward.

In practice, a single team member can hold multiple roles. For instance, Alice might energize Product, UX, and Customer Feedback, while Diego energizes Development, Security, and Documentation. Diego holding the Security role doesn’t mean the team needs a full-time Security Engineer; it means Diego dedicates a portion of his active focus to performing security work. The roles I picked here as examples are too big. The following example shows how they could and should be a bit smaller.

3. Roles, Accountabilities, and Tasks: The Decision Recorder Breakdown

To design roles effectively, distinguish between the role’s purpose and its accountabilities. Let’s examine a specific team-system role, the Decision Recorder:

• Role (The Coherent Body of Work): Decision Recorder exists to make important decisions easy to find and understand across the organization.
• Accountabilities (Recurring Work & Ongoing Responsibilities):
  • Detect significant decisions as they happen.
  • Capture decisions along with their rationale and context.
  • Maintain the decision log history.
  • Surface obsolete or conflicting decisions over time.

4. Understanding Role Granularity

A crucial design question is deciding how broad or narrow a role should be. The guiding principle is: Split roles as far as useful, not as far as possible. A role should be small enough to delegate, but large enough to own.

• When to keep responsibilities together: Look at the Decision Recorder role above. You could theoretically split it into Decision Detector, Decision Writer, Decision Publisher, and Obsolete Decision Detector. However, these responsibilities are tightly connected. Atomizing them into microscopic roles creates handoffs, administrative fragmentation, and more coordination effort than clarity.
• When to split a role: Decompose a broad role when different accountabilities require distinct decision authorities, different capabilities, or operate at different cadences. As a product grows, a monolithic Product role might naturally be split into Customer Discovery, Product Prioritization, Product Outcomes, and Product Communication.

A Practical Takeaway

Holding a role means doing the work. A role defines the work you do, not the work you make others do. Stop managing by static job titles and start organizing around explicit, living responsibilities.

The Coaching Prompt

• What critical work is currently getting done through individual heroic effort rather than an explicit role?
• Where on your team is someone “accountable” for a result, but only doing passive oversight instead of actively performing the work?
• If you decoupled your team’s job titles from their daily focus, what 2–3 roles are they actually energizing right now?
• Are you treating any of your current responsibilities as “exclusive territory” rather than shared domains?

Have you ever noticed a bizarre corporate paradox? We hire brilliant, capable adults who manage mortgages, raise families, and navigate complex lives, but the moment they step into the office, we treat them like children.

We set up rigid permission structures. We solve their problems for them. We default to a classic “parent-child” dynamic. It feels safe, but it is exhausting for everyone involved and terrible for growth.

The Framework: From Hierarchy to Wholeness

I recently recorded an episode of Le Podcast on Emerging Leadership with Xavier Costa.

Xavier has spent over 40 years in leadership and is now doing something radical. Through the impact fund, Krisos, he buys traditional, command-and-control companies and transforms them into self-managing, purpose-driven “Teal” organizations.

His core thesis is sharp: We have to stop parenting our teams. To transition to a self-managed organization, we must bring something deeply uncomfortable into the corporate world: Love.

The Reframe: The Signal in Your Need for Control

When a team member brings you a problem and you immediately solve it, it feels like good leadership. You’re being helpful, right?

Wrong.

The urge to step in and play the “fixer” isn’t a signal of your team’s incompetence. It’s an emotional signal of your own fear and ego. We use command-and-control because it makes us feel essential. It numbs our anxiety about the unknown. Xavier points out that an organization’s evolution is ultimately limited by the consciousness of its leadership. When a crisis hits, our ego’s first instinct is to regress to old, autocratic habits.

The alternative is love. Not the HR-violating romantic kind, but love as a structural standard: deep listening, radical transparency, and an unwavering confidence in the potential of your people. Fear hoards power. Love distributes it.

Leadership Application: The Adult-Adult Organization

Transitioning to a self-managed organization doesn’t mean a descent into chaos. It means replacing the parent-child hierarchy with structural equality. This requires hard, tangible changes:

• Radical Transparency: You open the books. Adults cannot make good decisions if you hide the financial realities from them.
  
• Rewarding EQ: In Costa’s model, emotional intelligence and teamwork are rewarded just as highly as technical abilities. Brilliant jerks don’t survive in a system built on trust.
  
• The Leader as a Lighthouse: A lighthouse doesn’t jump into the water to swim a ship to shore. It stands firm, provides clarity, and trusts the captain (the team) to navigate the rocks.
  
• Granular Roles Over Rigid Titles: In a self-managed system, the monolithic job description is replaced by highly specific, granular roles. This means one person can organically hold multiple roles, decoupling their identity from a static corporate title and allowing them to deploy their talents exactly where they are needed most. This also allows for highly efficient delegation (potentially to an AI agent, as roles are very clearly defined; we will have another installment of the newsletter focused on the roles).
  
• Capping the Wealth Gap: To build true trust, you cannot have executives earning 50 times what frontline workers earn. The salaries are capped at a strict 2.5x multiple between the lowest- and highest-paid. It instantly dissolves hierarchical resentment.
  
• True Profit Sharing: If you want people to act like owners, pay them like owners. The model mandates a 30% profit-sharing pool distributed among all employees.
  
• Distributed Governance: The traditional management is dismantled. Work is organized into cross-functional teams. To coordinate, these teams elect representatives to sit on three core committees: Strategic (for long-term vision), Operational (for day-to-day execution), and People/Care (for compensation, hiring, and culture). Power flows from the bottom up, not the top down.

The Takeaway

You cannot scale trust in a parent-child dynamic. To build a highly effective, self-managed team, you must park your ego, structurally share the wealth, and distribute the power.

The Coaching Prompt

Grab a journal or open a blank document, and ask yourself (and your leadership team) these questions this week:

1. The Ego Check: Where am I currently playing “parent” to my team by solving problems they are entirely capable of solving themselves?
2. The Trust Limit: If I were to open our financial books and implement a strict salary cap tomorrow, what is my biggest fear?
3. The Power Shift: What is one decision I currently make on my own that I could hand over to a cross-functional team this week?

Have you ever finished a fifty-hour week where you saved two projects from total collapse, dissuaded a colleague from doing something irreversible, and untangled a messy client handoff, only to realize you accomplished exactly zero of your official objectives?

You are not failing at time management. You are drowning in invisible work.

The work that isn’t written down is what actually keeps the company afloat. This vital labor includes emotional smoothing after tough conversations, informal mentoring and support, remembering birthdays or transitions, translating change decisions into human language, and holding team morale. Yet the people doing it are exhausted, while the folks who put on blinders and ignore the chaos get promoted.

The Source & Framework: From Feminist Scholarship to Glue Work

As a male leader, I have to be completely honest about my own blind spots here. It is incredibly easy for men in leadership to benefit from this hidden organizational labor without ever seeing it. Maybe because I am used to benefiting from this at home. Uncomfortable to admit it.

Before we call this a healthy team dynamic, we need to acknowledge where this concept truly comes from. These ideas are deeply rooted in feminist scholarship around reproductive labor, care work, and emotional labor. As highlighted in a recent webinar by the workplace mental health platform Plumm, women globally perform three times as much unpaid care work, which sets patterns for workplace invisible labor.

Thinkers like Joan C. Williams have long explored office housework, which is the crucial, non-promotable work disproportionately expected of women in organizations. Linda Babcock’s book The No Club explains why women take on this unrewarded work and how organizations fail to address it, while Emma’s comic The Mental Load brilliantly illustrates the invisible coordination and planning that drains energy.

The Reframe: It is Not a Boundary Issue; It is a System Issue

When people drown in this hidden work, standard productivity advice tells them to just set boundaries or say no.

But here is the truth. If everyone stops doing the invisible work, the team dies. The signal here isn’t that invisible work is a distraction. The signal is that our definition of valuable work is fundamentally broken.

Leadership Application: Put it in the Team Agreements

Let us be brutally honest about standard corporate HR practices. They are actively penalizing the people holding your culture together.

According to insights shared by Plumm, less than 25% of companies recognize this work in performance reviews. Look more closely, and the data is even worse: only 18% of companies formally recognize this work. The cost is a staggering 48% burnout rate when organizations do not commit to gender equality, compared to just 5% for those that do.

If you are a leader, you cannot wait for HR to fix their rubrics. You have to bypass the broken system today by making glue work an integral part of how your team operates:

• Bake it into team agreements: Stop treating emotional and cultural labor as a volunteer side hustle. Explicitly write mentoring, onboarding, and team support into your foundational team charters and expectations.
• Make it part of the visible flow of work: If it takes time and energy, it belongs on the board. Put emotional smoothing and internal team support right next to product deliverables in your sprint planning. Make the invisible entirely visible.
• Redistribute and protect: Ask yourself what can be taken off, not just what can be added. Systematically rotate note-taking and culture tasks. Before dumping a new initiative on your cultural glue, ask, “Before adding this, what can we remove?”

A Practical Takeaway

Invisible work is the nervous system of your culture. If the organization relies on it to survive, you must integrate it into your team agreements and make it a formal, visible part of your workflow.

The Coaching Prompt

Grab a pen and ruthlessly evaluate your team dynamics by asking yourself these three questions:

• Who is absorbing the extra emotional load?
• Who mentors informally but isn’t recognized for it?
• Who goes quiet in intense change conversations?

We’ve all had that moment. The deadline is tight, the pressure is on, and you feel the overwhelming urge to just say, “Because I’m the boss, do it.”

It feels efficient. It feels safe. But it’s actually a massive leadership failure.

Why do we default to authority? Because authority is a shield. It protects us from the messy, unpredictable reality of human emotions. But here is the counter-intuitive truth: the tighter you grip your authority, the less actual influence you have.

The Framework: The Death of the “Boss”

In the latest episode of the podcast, I sit down with leadership expert Marcel Schwantes to unpack this exact dynamic in: “From Boss to Leader: Human-Centered Leadership.”

Marcel is a master at dismantling old-school, fear-based management models. In this episode, we dig into why the industrial-era playbook of command-and-control is dead, and how the most effective leaders today are leveraging something that sounds soft but is actually fiercely strategic: care.

The Reframe: Friction is a Signal, Not a Threat

Let’s talk about the anxiety of giving up control. When you transition from being a “boss” (who dictates) to a “human-centered leader” (who facilitates), it can feel like you’re losing your edge. Your brain’s threat system fires up: “If I’m empathetic, they’ll walk all over me.”

Let’s reframe that fear. Empathy is not coddling. Empathy is an advanced data collection tool.

When your team is disengaged, procrastinating, or pushing back, they aren’t just being difficult. That friction is a signal. It is vital data telling you that the environment lacks psychological safety, clarity, or alignment.

• The Boss ignores the signal and demands compliance.
• The Leader reads the signal and removes the obstacle.

Leadership Application: Compliance vs. Commitment

What does human-centered leadership look like on a Tuesday morning? It means shifting your primary metric.

A boss relies on positional power. This gets you compliance: people doing the bare minimum to avoid getting in trouble. But compliance doesn’t scale, and it certainly doesn’t innovate.

A human-centered leader relies on relational power. They ask, “What do you need from me to make this happen?” This gets you commitment. It requires setting crystal clear boundaries and ruthlessly high expectations, but pairing them with deep, unshakeable support. You aren’t lowering the bar; you are actively helping your people clear it.

The Practical Takeaway

TL;DR: Authority gets you compliance. Connection gets you commitment. Stop trying to manage your people like line items and start leading them like complex humans.

The Mantra: “I am here to clear the path, not to control the steps.”

The Coaching Prompt

Theory is useless without action. Take 5 minutes ask yourself these four questions:

1. Where am I currently relying on my title (rather than my influence) to get things done?
2. Think of someone who is underperforming: What context, clarity, or support might they be missing from me?
3. What is the emotional signal behind the biggest point of friction on my team right now?
4. How can I prove to one person today that I care about their long-term growth, not just their immediate output?

Listen to the full episode with Marcel Schwantes, and let’s get to work.

Most of us are addicted to over-delivering. We think adding more features, more slides, more planning, and more process makes our projects safer and our leadership more effective. We were taught in school that doing more gets you the A+.

But what if your obsession with doing “more” is actually the exact thing holding your team back?

The Source: Jon Kern on Le Podcast on Emerging Leadership

In the latest episode of our podcast, I sat down with Jon Kern, an aerospace engineer turned software architect and one of the original co-authors of the Agile Manifesto.

Jon didn’t help create Agile because he loved corporate frameworks. He helped create it as a pragmatic, lightweight defense mechanism against bureaucratic lunacy. Early in his career testing jet engines for the Defense Department, he realized that rigid, heavyweight processes (like trying to predict a year of R&D in advance) were worse than useless: they were actively destructive.

The Reframe: The Strategic Value of “Laziness”

We typically view laziness as apathy or a lack of drive. But Jon advocates for a different kind of laziness: Strategic Laziness.

In development and leadership, being “lazy” means finding the smartest, smallest possible thing to build (or do) to get immediate feedback. It is a rebellion against doing too much work, too far in advance.

When we over-prepare, we usually do it out of anxiety. We build massive plans to soothe our fear of the unknown. The signal hidden inside the urge to over-engineer is that we are afraid to test our assumptions against reality. Strategic laziness forces you to stop hiding behind bloated plans and start treating your requirements as hypotheses.

The Leadership Application: Purpose vs. Process

You cannot ask your team to be “lazy” and agile if they don’t know what they are actually trying to achieve.

If a team doesn’t understand their core business purpose, they become mere order-takers. And order-takers will just blindly build every feature, tick every box, and follow every process, no matter how bloated it gets.

Jon’s rule is simple: Start with a clear, 25-word purpose.

When your team has a razor-sharp flag in the distance, they are empowered to exercise micro-judgments. They can look at a massive project requirement and say, “To achieve our purpose, we don’t actually need to build all of this yet. Let’s just do this tiny piece and see what the customer thinks.”

Even in the modern frontier of AI and “Vibe Coding”, which Jon actively uses to automate rigorous testing and compliance, this discipline holds true. You can use AI to do the heavy lifting, but you still must “coerce” the tools into following sound engineering fundamentals. Agility requires a clear purpose and relentless consistency.

The Practical Takeaway

Mantra: “I can out-small anyone.”

Whenever you are faced with a massive, ambiguous project, do not ask, “How do we get all of this done?” Ask, “What is the smallest, embarrassingly tiny piece of value we can deliver right now to get real-world feedback?”

The Coaching Prompt

Grab a notebook or bring these to your next 1:1. Answer honestly:

• The 25-Word Test: Can you clearly articulate your team or project’s core purpose in 25 words or less?
• The Bloat Audit: Where are you currently doing too much work, to too great a depth, too far in advance of actual feedback?
• The Next Small Step: What is the tiniest, smartest thing you could test or build this week to prove (or disprove) a major assumption?

I was on stage in Lyon last week at the Tech’Work conference, talking about a concept that radically shifts how we build teams.

We were discussing the “Above the Line / Below the Line” framework. When we are below the line, we are in survival mode: defensive, closed, and committed to being right. This is biology, not a character flaw. It’s normal. But when we pause, breathe, and step above the line, we choose a conscious response: open, curious, and committed to learning.

The audience was highly engaged, mapping out the behaviors of both states. But during the interactive session, two brutally honest comments from the audience hit the floor like lead weights:

1. “Too much empathy is bad because you just end up doing all the work in place of other people.”
2. “Some people just don’t want to take responsibility.”

You can practically hear the exhaustion and resentment dripping from those statements. If you’ve ever led a team, you’ve probably felt both. We are told to be “empathetic” and “empowering,” but the reality often feels like we are just babysitting.

So, what is the signal hidden in this frustration?

The Source: The Drama Triangle and Unconscious Commitments

To unpack this, we need to look at two heavy-hitting psychological models.

First is the Karpman Drama Triangle. When we drop below the line, we often fall into three roles: the Victim (powerless), the Persecutor (blaming), or the Rescuer (saving the day).

Second is the concept of Unconscious Commitments from the Conscious Leadership Group. Often, the outcomes we complain about the most are the exact outcomes our hidden behaviors are perfectly designed to create.

The Reframe: Friction as a Signal

When we complain about empathy and responsibility, we are misdiagnosing the problem. Here is the reframe:

The Empathy Trap is actually a Boundary Problem. When the leader in Lyon said, “Too much empathy means I do all the work,” they were describing the Rescuer role, not empathy. Empathy is understanding someone’s struggle. Rescuing is doing their work for them to alleviate your own discomfort with their struggle. Over-functioning for your team isn’t a surplus of caring; it is a deficit of boundaries.

The Responsibility Myth is actually a Mirror. When we declare, “Some people just don’t want to take responsibility,” we have slipped into the Victim role. We are blaming their character rather than looking at the system. The hard, transformative truth is recognizing our own unconscious commitment to the dynamic. If your team isn’t stepping up, what is the payoff for you? Often, it’s the ego-boost of being the “indispensable fixer.”

Leadership Application: Evolving the System

Leadership is a property of the system, not a personality trait. If people aren’t exhibiting leadership, the system is actively preventing it.

To create the conditions for leadership to emerge, you have to stop playing the Rescuer. Yes, some individuals, bruised by previous micromanagers or toxic cultures, will need time to trust that taking a risk won’t get them fired. They need proof.

But you cannot provide that proof if you keep doing their work. You have to step back, establish firm boundaries, and allow them to feel the natural friction of their role. You must accept that an old version of your leadership, the one that swooped in to save the day, is no longer useful. It got you here, but it is actively sabotaging your team’s growth for the future.

A Practical Takeaway

Empathy without boundaries is just enabling. You cannot rescue someone into taking responsibility.

The Coaching Prompt

Grab a notebook or open a blank document, and ask yourself these questions about your current team dynamics:

• Where am I confusing empathy with doing the work for someone else?
• If I am complaining that my team won’t take ownership, what is my unconscious commitment to being the “fixer”?
• What is the “payoff” I get from a team that constantly needs my help?
• What is one clear boundary I can set today to shift the system from enabling to empowering?

“Get on the bus or get left behind.”

“We need to build a burning platform.”

“If they don’t like the new direction, they know where the door is.”

How many times have you heard these phrases tossed around during a corporate restructuring, a messy pivot, or a sudden round of layoffs? We’ve been conditioned to believe that driving organizational change requires a kind of executive shock-and-awe. We issue top-down mandates, weaponize performance metrics, and use the unspoken anxiety of the next economic downturn to force compliance.

We call it “driving alignment.” Let’s call it what it actually is: corporate coercion.

We use these heavy-handed tactics because we assume force is the most efficient way to get results. But modern history, human psychology, and data tell a completely different story.

The Source: 100 Years of Uprisings

On a recent episode of the Hidden Brain podcast, political scientist Erica Chenoweth dropped a data-backed bomb on our collective assumptions about power. Chenoweth studied over a century of global revolutions and insurrections to determine what actually forces a system to change.

Her research revealed two staggering facts:

• Non-violent movements are twice as likely to succeed as violent ones.
• The 3.5% Rule: No government or regime in her data set failed to change once 3.5% of the population became actively, visibly engaged in the movement.

Chenoweth also uncovered a dark tactical truth. Authoritarian regimes intentionally use violence and intimidation not just to hurt their active opponents, but to terrify the “neutral middle” of the population. The goal is to make joining the movement look so dangerous that the average citizen decides to stay home and stay quiet.

When we use coercive language, tight ultimatums, and fear-based pressure in business, we are running the exact same autocratic playbook. And it backfires beautifully.

The Reframe: The “Neutral Middle” is Your Bedrock

When a new initiative drops, leaders tend to divide the company into two camps: the enthusiastic early adopters and the “resisters.” Anyone who doesn’t immediately drink the Kool-Aid is viewed as passive, checked out, or a barrier to progress.

That is a short-sighted leadership blind spot.

Let’s reframe the emotional signal of the “neutral middle.” These employees aren’t lazy, and they don’t hate growth. They are corporate survivors.

They have deep institutional memory. They’ve watched three different “transformations” come and go under different leaders. Their neutrality isn’t a lack of commitment. It is a healthy mechanism of self-protection. They are trying to shield their energy, their focus, and their daily output from a chaotic management wave so they can actually do the work.

The neutral middle has good intentions. They are the essential bedrock holding the business together while executives play with new frameworks. If you treat their caution as a threat, you will push them directly into active resistance.

Leadership Application: How to Activate Your 3.5%

If you want real, sustainable evolution in your organization, you have to stop trying to force 100% compliance through fear. Instead, you need to attract a critical mass.

• Ditch the Coercive Language: Eliminate phrases that imply people are disposable if they don’t instantly fall in line. Fear produces superficial compliance, but it utterly destroys the psychological safety required for actual innovation.
• Build a Cross-Functional 3.5% Coalition: Your critical mass shouldn’t just be the executive team or a specialized squad of “change champions” who look like corporate cheerleaders. Your 3.5% must be a micro-coalition across all levels and roles. Find the informal culture carriers: the quiet senior engineers, the respected front-line managers, the operations experts. If they buy in, the system shifts organically.
• Lower the Cost of Entry: Dictators hate humor and flexibility because it strips away their power. In organizations, instead of high-stakes mandates, use what Chenoweth calls “dilemma actions”—lightweight, low-friction experiments. Invite teams to try a new process for just two weeks as a trial. Keep it conversational, flexible, and iterative.

When you make the change safe, low-risk, and genuinely collaborative, the neutral middle will naturally lean in. You don’t need to drag them onto the bus. They will walk over to see why it’s worth riding.

A Practical Takeaway

Mantra for the week:

“Compliance can be forced; commitment must be attracted. Stop hunting for resisters, and start building your 3.5%.”

The Coaching Prompt

Ask yourself or your leadership team these questions this week:

1. Look at your current top-priority initiative. What coercive language or fear-based pressure (implicit or explicit) are you using to drive it forward?
2. Who are the informal, trusted influencers in your organization, outside of the executive team, who need to be part of your critical 3.5%?
3. How can you reframe the skepticism of your neutral team members? What valuable thing are they currently trying to protect?

“Hey, what are your thoughts?”

It happens in almost every meeting. You are sitting there, minding your own business, when a colleague or executive throws a conversational hand grenade your way.

Suddenly, the spotlight is on you. Your heart rate spikes. Your brain frantically scrolls through every piece of data you’ve ever acquired, trying to find the “perfect” thing to say. And when you finally open your mouth, what comes out feels less like a strategic insight and more like a word salad.

We look at people who are effortlessly articulate in these moments and assume they possess a rare, genetic gift. We tell ourselves, “I’m just not good on my feet.” But that panic isn’t a sign of incompetence. It’s a structural failure.

The Source: Why Your Brain Freezes

In his book Think Faster, Talk Smarter, Stanford communication expert Matt Abrahams highlights the real culprit behind our impromptu speaking anxiety: Cognitive Load.

When you are put on the spot, your brain is suddenly forced to do two incredibly difficult things at the exact same time:

1. Listing: Generating the raw content (the facts, the ideas, the data).
2. Sequencing: Deciding the order in which to say them.

It’s the mental equivalent of trying to bake a cake while simultaneously writing the recipe from scratch. Your mental RAM maxes out, your internal system crashes, and you resort to “umms,” “ahhs,” and rambling.

The Reframe: Structure is Freedom

Here is the shift: Stop trying to think of what to say, and start choosing how to say it.

That sudden spike of adrenaline you feel when put on the spot isn’t a bug; it’s a feature. It is raw energy looking for a container. If you don’t give that energy a boundary, it turns into anxiety. But if you give it a framework, it turns into focus.

As Abrahams notes, structure sets you free. When you choose a structural map before you start speaking, you automate the sequencing part of your brain. This frees up 50% of your cognitive capacity to focus entirely on your message. You don’t need a silver tongue; you just need a track to run on.

The Leadership Playbook: 3 Frameworks to Lean On

The next time you are caught off guard, do not just start talking. Take a breath, silently pick one of these three structural blueprints, and fill in the blanks:

1. The Everyday Anchor: What? So What? Now What?

This is the undisputed heavyweight champion of impromptu speaking. It works for project updates, giving feedback, or answering a sudden question from a client.

• What: State the cold, hard facts or the current situation.
• So What: Explain why this matters. What is the impact on the team, the budget, or the timeline?
• Now What: Define the immediate next step or call to action.

2. The High-Stakes Pivot: Challenge – Opportunity – Resolution

When things go wrong and everyone looks to you for answers, use this to reframe a crisis into a strategic moment.

• Challenge: Acknowledge the problem or obstacle directly without sugarcoating it.
• Opportunity: Pivot to what can be learned, or what new door this challenge opens.
• Resolution: Propose the definitive action step to move forward.

3. The Vision Builder: Past – Present – Future

Perfect for milestones, kicking off unexpected initiatives, or when you need to align a team that has lost its bearings.

• Past: Where did we start? What is the context?
• Present: Where are we standing right now? What is the immediate reality?
• Future: Where are we going? What does success look like?

The Practical Takeaway

The One-Second Blueprint: The moment you are put on the spot, pause for one full second. In that silence, whisper a mantra to yourself: “I am doing a ‘What, So What, Now What’.” Deciding the structure before you open your mouth is the difference between wandering aimlessly and leading with authority.

The Coaching Prompt

Bring these questions to your next reflection session, or use them to coach a team member who struggles with visibility in meetings:

1. Where do I ramble most? In which specific scenarios (e.g., upward management, peer debates, client pushback) do I feel my cognitive load redlining?
2. What is my default defense mechanism when caught off guard? Do I over-explain with data, shut down and say too little, or pass the mic to someone else?
3. How can we build a “structure-first” culture on our team? How can we use frameworks like What? So What? Now What? in our async updates or daily standups to save everyone’s mental RAM?

Let’s talk about the lie we tell ourselves when we’re stressed:

“If I just think about this problem for another three hours, I’ll finally solve it.”

We replay past conversations like we’re a director trying to edit a bad movie, or we project into the future, convinced that worrying is just “proactive preparation.” We convince ourselves that this mental gymnastics is useful.

Spoiler alert: It’s not. It’s a maze. And the deeper you run into it, the harder it is to find the exit.

The Source: Thoughts are Weather, Not the Sky

In her book Just a Thought, Dr. Amy Johnson introduces a liberating paradigm shift about how our brains actually function.

As human beings, we are evolutionary marvels wired for survival. Your thinking mind isn’t trying to torture you when it loops on a mistake you made in a meeting last Tuesday; it’s simply trying to keep you safe.

The problem is that your brain doesn’t know the difference between a physical predator and a difficult client email. It treats both as existential threats, flooding your system with thoughts designed to “fix” the danger.

The Reframe: The Suggestion Box

Here is the twist: Rumination isn’t a sign that you are broken; it’s a sign that your survival brain is working perfectly. The loop of worry is just an emotional signal. It’s your brain saying, “Hey, I care about this outcome, and I feel unsafe right now.” But just because your mind hands you a thought doesn’t mean you have to buy into it. Your brain is a suggestion box, not a dictator. Thoughts are not solid objects; they are transient energy. They only become a maze when we grab onto them, unpack our bags, and decide to live there.

Nothing external can lift you out of that maze. No new strategy, no extra data, and no amount of reassurance. The exit is entirely internal: it’s realizing that a thought is just a thought, and you have the power to let it pass.

Leadership Application: Stop Time-Traveling

In leadership, staying stuck in the maze is a quiet productivity killer. When we ruminate, we aren’t leading; we are time-traveling.

• We are either in the past, trying to manage a reality that has already occurred.
• Or we are in the future, trying to control a reality that doesn’t exist yet.

When you are trapped in the past or the future, you are completely unavailable to the people you are leading in the present.

Letting go of the thought loop and returning to the room takes practice. It feels counter-intuitive because your brain tells you that dropping the worry means you’re being irresponsible. But true human-centric leadership requires the discipline to say, “Thank you, mind, for trying to protect me. But I am choosing to be right here, right now.”

A Practical Takeaway

The Leader’s Mantra: “It’s just a thought. It doesn’t need a meeting.”

The tl;dr: You cannot stop your brain from producing thoughts any more than you can stop the sky from producing clouds. But you can stop mistaking the clouds for the sky. Drop the debate with your own mind and anchor back into the present moment.

The Coaching Prompt

Ask yourself, or your team, during your next 1-on-1, these four questions to break the cycle of rumination:

1. What is the actual data here, and what is just the “survival story” my mind is spinning about it?
2. Am I actually preparing for the future right now, or am I just using worry to feel like I’m doing something?
3. If I chose not to believe this specific thought today, what action would I take right now?
4. What does my team need from me in this exact moment that I am currently missing?

Anxiety is creeping into leadership circles. A late-2025 study by The Conference Board suggests that AI can now handle up to 90% of routine career coaching tasks.

I’ll be honest: the knee-jerk fear of obsolescence was exactly my response recently. A client told me she was looking into AI to scale coaching across her organization. In her company, coaching has historically been locked behind a velvet rope, available only to those who reach a certain hierarchical level. She wanted to democratize it.

I was skeptical, but I investigated. And frankly, I was blown away. I found a platform that is incredibly effective if you want your people to practice soft skills, like navigating a difficult conversation with a colleague, or nailing a sales pitch, rather than practicing on actual prospects and customers.

My initial fear quickly gave way to a counterintuitive observation: AI isn’t here to kill human coaching or leadership; it’s here to save us from our own transactional mediocrity. The algorithm is forcing a brutal but necessary question: If a machine can do my job, was I operating like a machine?

The Framework

The Integral Institute offers a brilliant framework for navigating this shift. They divide our development needs into two distinct lanes:

• Top-of-Funnel (How do I think about this problem?): The realm of performative, cognitive coaching.
• Bottom-of-Funnel (Who am I becoming as a leader?): The realm of existential, transformational coaching.

Researcher Tatiana Bachkirova (HEC Paris) draws the absolute dividing line at “embodied empathy.” AI possesses flawless syntactic empathy: It knows exactly what words to string together to validate an emotion. But it has never lived through anything. It doesn’t know risk, loss, or mortality.

The Reframe: The Signal Behind the Threat

The fear of being replaced isn’t a bug; it’s a signal. It tells us we’ve spent way too much time in the “performative” zone: optimizing skills, running role-plays, and offering cognitive behavioral tweaks. AI excels here. It treats symptoms, optimizes metrics, and operates 24/7 without burning out.

The positive side of this “threat” is liberation. By offloading habit tracking and cognitive prep to an algorithm, human leaders and coaches are forced to step up and do their actual jobs: navigating the messy reality of human identity. An AI can give you ten perfectly structured frameworks for delegating tasks, but it cannot help you when your nervous system is terrified of losing control.

Leadership Application: The Hybrid Model

In organizational life, this demands a shift in how we build and support our teams. The future belongs to a tiered, hybrid model:

• Phase 1: AI as the Pre-Coach (Performative). The tool is used for onboarding, baseline skill assessments, and goal-tracking. It handles the “presenting problem.”
• Phase 2: The Human as the Alchemist (Transformational). This is where you step in. You use the AI’s data as a baseline, but focus entirely on the human. You read the shifting energy in a room, spot systemic power dynamics that an algorithm is blind to, and possess the courage to sit in the discomfort of silence to force a real breakthrough.
• Phase 3: AI as the Accountability Partner (Continuous). Post-breakthrough, the AI steps back in to provide the daily nudges and micro-learning needed to turn a transformational epiphany into a sustained habit.

The Takeaway (TL;DR)

If coaching and leadership are just about giving advice and tracking KPIs, the algorithm wins. If they are interpretive, embodied, relational practices meant to reinvent how a human operates in the world, you are irreplaceable.

Leave the tasks to the bots; keep the identity for the humans.

The Coaching Prompt: The Impact Audit

Take five minutes before your next 1:1 or team meeting and ask yourself:

1. Looking at my meetings last week, which ones were just information transfer or checklist tracking (things an AI could easily do)?
2. When a team member struggles, do I rush to hand them a “solution framework” (bot mode), or am I capable of sitting in the discomfort and listening for the “unsaid”?
3. Am I trying to optimize this person’s symptoms, or am I trying to help them transform their professional identity?

P.S. If you are curious about the AI simulation tool I mentioned earlier—the one that blew me away for safe, scalable soft-skill practice—just reply to this email. I will gladly introduce you to the people behind the solution. Ironically enough, they are fantastic and very human.

P.P.S. Speaking of doing the deep, human work: if you haven’t yet taken the ​Emerging Leadership Navigator​ from last week’s newsletter for a spin, consider this your gentle nudge. It’s designed specifically to help you map out your own leadership bottlenecks and identity shifts: exactly the kind of “bottom-of-funnel” inner work an algorithm can’t do for you.

We all have a default setting. When the pressure dials up at work, we unconsciously retreat into the tasks that feel safe. The visionary strategist ignores the operational messy work; the relentless executor ignores team morale; the empathetic people-pleaser avoids hard business metrics.

We usually dress this up as “playing to our strengths.” But if we are being honest, it is often just a sophisticated way of neglecting the parts of our role that make us uncomfortable. The friction, exhaustion, or stagnation you might be feeling right now isn’t a sign that you are failing, it’s a signal that a critical dimension of your work is being starved of your attention.

The Source

More than a decade ago, I was working with a team that was hitting a wall. They were talented, but they were deeply misaligned on where their energy should be going. To help them map out their blind spots, I built a tool to force reflection on the neglected aspects of their roles.

Over the years, I’ve refined this framework through individual coaching and team sessions. It works just as well for Individual Contributors as it does for Managers. I call it the Emerging Leadership Navigator.

As you can see in the profile map below, it breaks your role down into four distinct compass points:

• Business: The strategy, the market, and the value you are delivering.
• People: The relationships, the culture, and the emotional intelligence required to lead.
• Execution: The delivery, the grind, and getting things across the finish line.
• System: The processes, the structures, and how things scale.

The Reframe

When you look at a radar chart like the one above, the instinct is to judge the gaps between where you are (Self-Perception) and what the role requires (Importance).

But let’s reframe that gap. That negative space isn’t a character flaw or a permanent weakness. It is pure signal. If you are feeling overwhelmed, the gap is showing you exactly where the bottleneck is. The anxiety of feeling “behind” is simply the emotional signal that you have outgrown your current default setting and it’s time to intentionally step into a new quadrant.

Leadership Application

Leadership does not emerge by being perfect at all four dimensions simultaneously. That’s a recipe for burnout. Leadership emerges when you create the conditions for awareness.

When you map your role using the Navigator, you suddenly make the invisible visible. You might realize that as an IC, you’ve been over-indexing on Execution while entirely neglecting the System that could make your life easier. Or as a manager, you might realize you are focusing so heavily on the Business that the People dimension is eroding. Recognizing this misalignment is the first step to correcting it.

I recently decided to make this tool accessible to everyone by creating a simplified online version. You can read more about the philosophy behind it ​here​, and you can start your inquiry right here: ​The Emerging Leadership Navigator​

Note: I would love to hear your feedback on the tool itself, or simply hear how it made you reflect on your role differently. Hit reply and let me know.

A Practical Takeaway

TL;DR: You can’t navigate out of a rut if you don’t know where you are on the map. Mantra: “The friction I feel is the exact dimension of leadership I am avoiding.”

The Coaching Prompt

Before you click into the tool, ask yourself (or your team) these three questions this week:

1. Of the four dimensions (Business, People, Execution, System), which one do I naturally retreat to when I am stressed?
2. Which dimension am I currently avoiding because it makes me feel incompetent or uncomfortable?
3. If I shifted just 10% of my energy this week into my most neglected dimension, what specific problem would it solve?

We’ve all got that one colleague. The one who sends our blood pressure spiking the second they open their mouth in a meeting. Our default response? We label them as difficult, passive, or overly rigid, and we vent about it to our work bestie later.

But what if your intense frustration with them isn’t about their incompetence, but a massive flashing signal pointing toward your untapped potential?

The Source: Daniel Ofman’s Core Quadrant

Dutch management expert Daniel Ofman developed a remarkably intuitive framework called the Core Quadrant. In studying human behavior, Ofman noticed that our greatest interpersonal clashes don’t happen because we are fundamentally broken, but because we misunderstand the nature of our own innate strengths.

As ​Ofman explains in this video​, we are all born with effortless core qualities, things like determination, flexibility, or caring. But as he says, “There is no light without shadow.”

The Reframe: The “Too Much of Something Beautiful” Principle

When we look at our frustrations through Ofman’s lens, the emotional signal changes completely. Let’s break down the anatomy of a conflict using a common leadership trait: Determination.

• The Core Quality: You are naturally driven. Pushing projects across the finish line is effortless for you.
• The Pitfall (Too much of a good thing): Under stress, your determination tips over into your shadow side. You become Pushy or Demanding.
• The Challenge (The Antidote): To balance your pitfall, you need to develop its positive opposite. The antidote to being pushy is developing Patience. If you can be “patiently determined,” you become unstoppable.
• The Allergy (What you despise in others): Here is where the magic happens. What happens when someone takes Patience too far? They become Passive. This is your Allergy. Passive people drive you absolutely insane.

Here is the quote from Ofman that completely shifts this paradigm:

“If people would only realize that whenever you see something in another person that you don’t like, by definition it is always too much of something beautiful, it would change the world.”

That colleague who drives you crazy because they are “too passive”? They are just over-expressing the exact trait (patience) that you desperately need to develop.

The Leadership Application

In organizational life, we unconsciously look for our “Challenge” in others. The visionary founder partners with the methodical operator. The fiercely determined director hires the exceptionally patient manager.

This complementarity is incredibly powerful… until the pressure hits.

When stress enters the system, we retreat into our extremes. Suddenly, the determined leader views their patient partner as “lazy,” and the patient partner views the determined leader as a “bully.” You are allergic to their pitfall, and they are allergic to yours. It’s a predictable script that plays out in boardrooms every single day.

The goal of human-centric leadership isn’t to eradicate the people who annoy you. The goal is to stop judging your allergy and start mining it for the underlying “beautiful” trait. You don’t need to become passive, but you do need to learn the patience that lives underneath it.

A Practical Takeaway

Your intense emotional reactions to others are rarely about them; they are a diagnostic tool for your own imbalances.

Mantra: “My greatest frustrations are pointing to my greatest areas for growth.”

The Coaching Prompt

Grab a notebook and take 3 minutes to map this out before your next team interaction:

1. Identify the Trigger: Who is the one person at work who consistently triggers your “allergy” (frustration, anger, eye-rolls)?
2. Name the Label: What specific negative label have you placed on their behavior (e.g., passive, chaotic, overly rigid, wishy-washy)?
3. Find the Beauty: What is the positive, “beautiful” core quality hidden beneath that annoying behavior? (e.g., If they are “wishy-washy,” the core quality is “flexibility”).
4. The Integration: How can you integrate 10% more of that positive quality into your own leadership style this week?