The 15 Commitments of Conscious Leadership

Taking Radical Responsibility

At any given moment, a leader occupies one of two states. "Above the Line" means open, curious, and genuinely willing to learn from whatever is happening. "Below the Line" means closed, defensive, and committed to being right or finding someone to blame. Most leaders spend far more time below the line than they'd guess.

The Drama Triangle and its above-the-line replacement

Below the line, people fall into one of three roles from psychologist Stephen Karpman's "Drama Triangle": Victim ("poor me"), Villain (the person or thing to blame), or Hero (the rescuer who fixes things, often at real cost to themselves). David Emerald's "empowerment dynamic" supplies the above-the-line swap for each one.

• Victim becomes Creator: instead of "why is this happening to me," the question shifts to "what am I creating here, and what do I actually want instead?"
• Villain becomes Challenger: a difficult person stops being a threat to defend against and starts being someone whose pushback sharpens your thinking.
• Hero becomes Coach: instead of rescuing people from their own problems, a Coach asks questions that let them own the solution.

Radical responsibility is not self-blame. Blaming yourself is the Victim role turned inward, still below the line, still generating shame instead of learning. Responsibility here is closer to "response-ability," the capacity to see your own part in a situation clearly enough to change how you respond to it.

The practice is one habitual question, asked the moment something goes wrong: how am I creating or perpetuating this? Even a leader who is genuinely 95 percent the victim of someone else's decision usually still holds a 5 percent lever worth examining, because that sliver is the only part they can actually change.

What this means for a launch postmortem

A missed launch date invites the Villain move: blaming an unresponsive engineering team or a shifting sales deadline. Asking "what's my 5 percent, the scope I over-committed to, or the risk I didn't escalate early enough" turns the postmortem into something the team can actually act on, instead of a debate about whose fault it was.

Learning Through Curiosity

The second commitment names the specific below-the-line habit that responsibility alone doesn't fix: the compulsion to be right. Below the line, disagreement feels like a threat, so energy goes into defending a position instead of learning from it. Above the line, that same disagreement becomes information.

Certainty as a reflex to interrupt

Being right functions like an addiction with its own withdrawal symptoms: a flash of defensiveness, a tightening in the body, a rebuttal forming before the other person finishes talking. Curiosity is the deliberate interruption of that reflex, most simply achieved by asking a genuine question instead of firing back an answer.

• Notice the body's first signal of going below the line, a clenched jaw, a raised voice, a closed posture, before acting on it.
• Replace an internal "that's wrong" with an internal "I wonder what's true about that for them."
• Ask a question you don't already know the answer to, not a leading question meant to prove your point.

This is also where the book locates real leadership skill: the ability to take a lesson from one situation and genuinely apply it in a new one. A leader who can't tolerate being wrong in the moment can't actually learn in real time, no matter how much domain experience they've accumulated elsewhere.

Practically, the shift is a question a leader can ask silently the instant certainty starts rising: "I wonder what I'm missing here." It doesn't resolve the disagreement. It just buys enough openness to actually hear the other side before deciding they're wrong.

What this means for a roadmap disagreement

A stakeholder pushing back hard on a roadmap decision usually triggers the urge to defend the spec line by line. Pausing to ask what they're seeing that you're not, genuinely, not rhetorically, often surfaces a real constraint, a sales commitment, a compliance deadline, that a defensive answer would have talked over entirely.

Feeling All Feelings

Most workplace norms treat emotion as something to manage or hide. This commitment argues the opposite: feelings carry information a leader can't afford to suppress, because suppressed feelings don't disappear, they leak out sideways as irritability, passive aggression, or quiet exhaustion.

What each feeling is for

• Anger signals a boundary has been crossed and something needs to change.
• Fear signals uncertainty and sharpens alertness to real risk.
• Sadness signals loss and helps a person let go of what's already gone.
• Joy signals something worth celebrating and repeating.

The practice for actually feeling a feeling, rather than just naming it, is physical: locate where it lives in the body, breathe into that sensation, let yourself feel it without attaching a story to it, and let whatever expression the body wants, movement, sound, stillness, match its intensity. Done this way, most emotions complete within roughly ninety seconds, the book's "90-Second Rule."

What extends an emotion well past ninety seconds is thinking. A single wave of anger passes quickly; a resentful story replayed in your head every hour regenerates that same wave indefinitely. The difference between feeling a feeling and recycling a thought about it accounts for most of what gets labeled a chronic "emotional problem" at work.

Three centers of intelligence

Conscious decisions draw on three centers at once: the head's analysis, the heart's felt sense of a relationship, and the gut's instinct about a situation. A leader who consults only the head is routinely overriding real information the other two centers already have.

What this means for a missed launch number

When a launch misses its number, the instinct is often to skip straight to "here's the plan going forward" without letting the team feel the actual disappointment. Naming it directly, this stings, and it's fair to feel that, clears the emotion in minutes instead of letting it curdle into blame across the next planning cycle.

Speaking Candidly

Honest communication requires three qualities present at once: truth (what you actually think and feel, unsoftened), openness (how much you reveal versus withhold), and awareness (consciousness of your impact on the listener while you speak). Miss any one and candor collapses, into bluntness without awareness, or diplomatic vagueness that isn't technically a lie but isn't candid either.

The unarguable statement

The sharpest practical tool here is the "unarguable statement": saying only what the other person cannot reasonably dispute, because it's your direct, first-person experience rather than a claim about them. "I noticed my heart racing when you raised your voice" is unarguable. "You were being aggressive" invites a debate about whether that's even true.

The first keeps a conversation open; the second usually shuts it.

Listening as half of candor

Candor applies to listening too. "Conscious listening" means staying above the line while someone else speaks, not rehearsing a rebuttal, not silently building a case, just tracking what's actually being said and how it lands in your own body.

• State the fact, then your interpretation of it, then the feeling that interpretation produced, in that order.
• When judging someone else's flaw strongly, arrogance, dishonesty, laziness, ask how that trait might also be true of you; the traits that provoke the strongest reaction are often ones you've disowned in yourself.
• Own a reaction as your own experience rather than an objective verdict on the other person.

Practiced together, these tools replace a common failure mode, diplomatic dishonesty, technically polite feedback so hedged it changes nothing, with something both kinder and more useful.

What this means for a hard performance conversation

Telling an underperforming peer "you're not committed to this project" is a verdict that invites a defense. "I noticed three deadlines slip this month, and I'm worried about the launch" is unarguable, and it's far more likely to open an actual conversation about what's really going on.

Eliminating Gossip

Gossip, by this book's definition, is any conversation about a person's issue that doesn't include that person. It's treated as one of the most corrosive habits in an organization, not because it's unkind, though it usually is, but because it substitutes for the conversation that would actually resolve something.

Facts, stories, and the clearing

A fact is something a camera could record, an observable event. A story is the interpretation layered on top: the meaning, the judgment, the assumed motive. "She missed the deadline" is a fact. "She doesn't respect my time" is a story, and most workplace drama comes from treating a story as if it were a fact.

• Before raising an issue, separate what actually happened from the meaning you've assigned to it.
• Take the issue, facts and story both, directly to the person involved, not to a sympathetic third party.
• Notice that simply listening to gossip without redirecting it is still participating in it.

The book's tool for resolving a live issue is the "clearing": stating the facts, the story you've built on top of them, and the feelings that story produced, directly to the person involved, then genuinely letting them respond, and checking "is there more?" until the issue is actually complete rather than half-said.

This commitment follows candor for a reason: once telling the truth directly starts feeling normal, going around someone to talk about them starts to feel like the harder option instead of the easier one.

What this means for cross-functional friction

Venting to another PM about a designer who keeps missing reviews feels harmless, but it changes nothing and quietly poisons how that PM sees the designer too. A direct, five-minute clearing with the designer, here's what happened, here's the story I built, here's how I'd like it to go, usually resolves what weeks of hallway commiserating never would.

Practicing Integrity

Integrity is the commitment that holds the previous five together, since it's really about wholeness: making sure what's happening inside you, your true feelings, your unspoken truths, your actual agreements, matches what's happening in your outward behavior. Every gap between the two blocks energy that could otherwise go into leading.

Agreements as an energy system

The most concrete version of this commitment is agreement-keeping: doing exactly what you said you'd do, by when you said you'd do it, including agreements made with yourself. Even small, seemingly harmless broken agreements, chronic lateness, a promised follow-up that quietly slides, erode trust and drain energy across an entire team, not just one relationship.

When a leader genuinely can't keep an agreement, the fix isn't guilt, it's renegotiation: raising it with the other party before the deadline passes, and making a new, explicit agreement rather than letting the old one silently expire. Silence is what actually breaks trust; a renegotiation, communicated early, usually doesn't.

The whole body yes

Before making a new commitment, check for a "whole body yes," agreement from your rational mind, your emotional state, your will, and your physical body all at once. A commitment made from the head alone, while the gut is quietly saying no, tends to be the kind that gets broken later.

• Run a periodic integrity inventory: unexpressed feelings, unspoken truths, and broken or unrenegotiated agreements piling up, each one a small energy leak.
• Treat a broken agreement as data about what commitment to make differently next time, not just an apology to issue.

What this means for a stakeholder deadline

Promising a stakeholder a feature "by end of quarter" without a genuine whole body yes, when your gut already knows the eng team is stretched thin, sets up a predictable broken promise. Renegotiating the date the moment that risk becomes clear costs far less trust than staying silent until the deadline actually passes.

Generating Appreciation

The first six commitments mostly stop drama: closing the leaks that blame, defensiveness, suppressed feeling, indirect communication, gossip, and broken agreements all create. This commitment opens a second phase, putting the energy drama used to consume toward something generative, starting with appreciation.

The mechanics of a real appreciation

Attention itself is the mechanism: paying sustained, specific attention to what's genuinely working in a person or situation makes more of it show up, not through magic, but because most people are quietly starved for anyone noticing their actual contribution.

• Sincerity: appreciation has to be a real feeling, not a technique deployed to soften bad news.
• Unarguable truth: ground it in something you actually observed, not a vague compliment.
• Specificity: name exactly what the person did, not a generalized trait.
• Brevity: a real appreciation is short enough to say in one breath.

Research on relationship stability suggests roughly five positive interactions are needed to offset one negative one, and most leaders, trained to hunt for problems, run a badly negative ratio without realizing it.

Receiving is the harder half

Receiving appreciation matters as much as giving it. Many capable people deflect a compliment reflexively, "oh, it was nothing," which is a small act of dishonesty: it denies something true and quietly refuses the other person's contribution. The practice is disarmingly simple: when appreciated, say thank you, and let it land.

What this means for a launch retro

A launch retro that jumps straight to what broke, without naming what the team actually did well, trains people to associate shipping with dread instead of pride. Opening with two or three specific, sincere appreciations, the rollback plan you built saved us Tuesday, changes what the team brings to the next launch.

Excelling in Your Zone of Genius

This commitment borrows and extends a framework from Gay Hendricks' The Big Leap: four zones describing how a person relates to any given activity. Most capable professionals get stuck one zone short of where they'd be most valuable and most alive.

The four zones

• Zone of Incompetence: things done poorly and disliked; the answer is to stop, delegate, or do them differently.
• Zone of Competence: things done about as well as most people; safe, but essentially interchangeable work.
• Zone of Excellence: things done very well and rewarded for, but that don't actually energize; most successful leaders spend their careers here.
• Zone of Genius: things that come almost effortlessly, that energize before, during, and after doing them, and that only you do in quite your own way.

The trap is the Zone of Excellence specifically, because it's genuinely rewarded with praise, promotions, and money, which makes it feel like success even while it quietly drains the person doing it. Genius work gets crowded out by excellent work precisely because excellent work is safer and gets validated faster.

The upper limit problem

Hendricks' "Upper Limit Problem" names the unconscious beliefs that cap how much success, ease, or happiness a person will allow themselves, showing up as self-sabotage right when things start going unusually well. Common versions include feeling fundamentally flawed, fearing disloyalty to people whose lives look smaller, or believing that outshining others isn't safe.

To find your own Zone of Genius, ask thirty or more people who know you well when they've seen you most alive and effective, and separately review your own history for moments you both loved the work and were unusually good at it.

What this means for your own weekly calendar

Strategy work, spotting the real problem behind a pile of feature requests, is often the Genius zone; writing the weekly status deck is Excellence, done well but draining. The fix isn't working harder at the deck, it's finding who on the team can own it so the strategic thinking gets the leader's actual attention.

Living a Life of Play and Rest

Play and rest are leadership disciplines here, not indulgences squeezed in around real work. Play is an absorbing activity done for its own sake, with no objective beyond the doing of it, where self-consciousness and the sense of time both fall away.

Energy, not time

A leader's own energy state sets the emotional weather for an entire team. A chronically depleted, joyless leader produces a chronically depleted, joyless culture, regardless of what the mission statement says about having fun. Play, done deliberately, is how creative energy gets resupplied instead of running permanently on reserve.

• Improvisation, the "yes, and" habit borrowed from improv, as a way of meeting what actually happens instead of forcing a predetermined plan.
• Trying on a different attitude in a stuck situation, on purpose, to loosen a fixed perspective.
• Genuine rest, sleep, breaks, unstructured downtime, treated as productive rather than as time stolen from productivity.

Workaholism gets named directly: compulsive overwork, checking email obsessively, an inability to stop thinking about work, is described as an addiction used to avoid uncomfortable feelings rather than a sign of dedication. The tell is whether work still happens when a person is well rested and at peace, or only as a way to outrun something else.

The chapter's real argument is energy management over time management: physical, emotional, mental, and spiritual energy all renew on their own cycles, and no amount of calendar optimization compensates for ignoring that.

What this means for crunch week

The week before a major launch tends to reward whoever cancels the most personal time and answers Slack at midnight. That pattern produces a worse launch, not a better one; a leader who protects a real recovery block during crunch models the only sustainable version of urgency the team can actually copy.

Exploring the Opposite

Commitments 10 through 12 turn inward, toward the deeper attachments believed to generate most of a leader's below-the-line behavior in the first place. This one starts with story: the meanings and interpretations a person layers onto events, which feel like objective truth but are actually constructed.

Turning a story around

Nothing that happens is inherently good or bad. A missed promotion, a difficult board member, a failed launch, all of these are neutral events until a person assigns a story to them. Believing your own story as though it were simply reality, rather than one interpretation among several, generates most of the suffering this commitment is aimed at.

The central tool is adapted from Byron Katie's "the Work": a four-question inquiry, is it true, can you absolutely know it's true, how do you react when you believe it, who would you be without it, followed by "turnarounds," deliberately restating the story as its opposite and finding at least one way that version is also true.

• "My co-founder is undermining me," turned around, becomes "I am undermining my co-founder," or "I am undermining myself," each worth examining honestly.
• The goal isn't deciding the turnaround is more true than the original, it's loosening the grip of certainty either way.

Practiced seriously, this doesn't hand a leader a better story to replace the old one. It teaches holding any story more lightly, staying curious about your own interpretation instead of defending it as fact.

What this means for a stakeholder standoff

"This stakeholder is deliberately blocking my roadmap" feels like fact in the middle of a tense review. Turned around, "I am blocking my stakeholder," or "I am blocking myself," often surfaces a real, fixable gap, maybe they were never actually briefed on the tradeoff you assumed was obvious.

Sourcing Approval, Control, and Security

This commitment names three needs that drive an enormous amount of unconscious leadership behavior: the desire for approval (to be liked, valued, and belong), control (to manage outcomes and other people), and security (to feel safe, financially, physically, and relationally).

Why the outside never fills it

The argument is structural, not moral: wanting something implies currently lacking it, so a leader chasing external approval, control, or security is, by definition, operating from a felt sense of not having enough of it, no matter how much they actually receive. A promotion doesn't end the wanting, it just resets the target.

The proposed shift is sourcing all three internally instead: approving of yourself, trusting your own judgment enough to tolerate not controlling outcomes, and feeling secure in who you are independent of your title or what other people currently think of you. This isn't presented as easy, but as the only version that can't be taken away by someone else's decision.

• Notice a want for approval, control, or security as it arises, and name which of the three it is.
• Ask whether you're willing to release the grip of needing it in order to feel okay, not the goal itself, just the neediness around it.
• Check whether a decision is being made to look good to someone else, or because it's genuinely the right call.

What this means for sign-off culture

Needing a VP's explicit sign-off before shipping every deck is a control-and-approval pattern dressed up as diligence. A leader who's sourced enough internal security can present a confident recommendation and let the VP disagree without that disagreement threatening how the leader feels about their own judgment.

Having Enough of Everything

The last of the inward-facing commitments confronts scarcity directly, the felt sense that there's never enough time, money, love, or resources to go around, named as one of the most common drivers of below-the-line leadership.

Three scarcity stories

• There's never enough of whatever you value, so someone else having more inherently means you have less.
• More is always better, so growth and accumulation go unquestioned as goals in themselves.
• This is just how it is, a resigned hopelessness that treats scarcity as a fixed law rather than a mindset.

Against these, sufficiency isn't an amount, it's a stance, a chosen context rather than a measured quantity. "There is enough, and we are enough" works as a deliberate declaration, not a claim that resources are literally infinite, but that scarcity thinking is optional even when resources are genuinely limited.

The practical shift is largely one of attention: noticing what's actually available right now, rather than measuring the present against an imagined future shortfall. A leader anxious about running out of time in a negotiation tends to negotiate worse than one who trusts there's enough time to get it right.

This is also where the book's collaboration argument sharpens: teams operating from scarcity default to zero-sum thinking, treating a colleague's win as their own loss, while teams operating from sufficiency can actually collaborate. Genuine win-for-all outcomes, covered two commitments later, become possible only once this scarcity story is set down.

What this means for a capacity fight

A quarterly planning fight over shared engineering capacity usually runs on an unstated scarcity story, if their team gets headcount, mine loses out. Naming that story out loud, then asking what a genuinely sufficient allocation would even look like, opens options that pure turf-defense never finds.

Experiencing the World as an Ally

The final three commitments turn outward again, toward how a leader relates to other people and to circumstance itself. This phase asks what becomes possible once the first twelve commitments are actually in practice, and it starts with a real reframe of adversity.

The ally question

Rather than treating a difficult colleague, a failed launch, or a downturn as an obstacle to survive, one practical question does the work: if this person or circumstance were a perfect ally, placed here specifically to teach something I can't yet see, what would that lesson be?

The point isn't pretending the difficulty is secretly good news. It's noticing that the meaning assigned to a hard situation, obstacle versus teacher, is itself a choice, the same insight from exploring the opposite, now applied specifically to people and events that feel like they're working against you.

This commitment depends on the earlier ones landing first. Radical responsibility and curiosity are prerequisites; without them, "the world is my ally" collapses into denial, a way of avoiding real accountability rather than a genuine reframe. Practiced honestly, it's the opposite: taking your own contribution seriously enough that even the hardest relationships start looking like curriculum instead of punishment.

• A leader who works this commitment stops spending energy resenting the people and events that challenge them.
• That freed energy goes instead into asking what those challenges are actually there to develop.

What this means for a harsh customer signal

A scathing churn interview or a competitor's launch that eats your differentiation overnight both read as threats in the moment. Treated as allies, they become the sharpest, cheapest research a roadmap could ask for, information a friendlier signal would never have surfaced.

Creating Win for All Solutions

This commitment takes the sufficiency mindset from having enough and applies it directly to negotiation and conflict. Three outcomes are available in any disagreement: win-lose (someone gets what they want at the other's expense), compromise (both sides sacrifice something to reach a middle ground), and win for all, a genuinely new option that serves everyone better than either side's original position.

Beyond win-lose and compromise

Compromise is usually mistaken for the best available outcome, when it's actually a failure of imagination reached too early, before anyone has gotten curious enough to find a third option. Win for all requires the earlier commitments working together: candor to say what you actually want, curiosity to understand what the other side wants, and sufficiency to believe there's room for both.

• Slow down before proposing a solution and get genuinely curious about the other party's underlying interest, not just their stated position.
• Treat the disagreement as a creative problem with an unknown number of possible solutions, rather than a fixed pie to be split.
• Stay in the conversation past the point where a comfortable compromise first appears, since that's usually where win-lose thinking starts sounding reasonable again.

The result described isn't a nicer-sounding compromise, it's a structurally different outcome, one where both parties end up better off than either of their original positions, available far more often than most negotiators assume, precisely because most negotiators stop looking the moment compromise becomes possible.

What this means for a scope negotiation

Engineering wants to spend the quarter on tech debt while sales wants three specific features shipped now. The compromise, half a debt sprint plus one rushed feature, usually satisfies neither. Getting curious about why sales needs those features, a specific renewal at risk, sometimes reveals a narrower fix that also clears real debt.

Being the Resolution

The final commitment reframes what to do about anything believed to be missing, in an organization, a team, or the wider world. Instead of treating a gap as a problem to diagnose or a failure to assign blame for, the missing thing becomes an invitation: become it yourself, rather than waiting for someone else to supply it.

Being before doing

The practical question is "what is this situation inviting me to be or become," asked before any question about what to do next. Action taken from the right internal state, patience, honesty, generosity, whatever the situation actually calls for, tends to be effective almost automatically, while action taken from blame or urgency rarely fixes what it's aimed at, even when it's technically the "right" action.

This closes the book's arc deliberately. A leader who has done the earlier work, taking responsibility, staying curious, feeling their feelings, speaking and hearing the truth, keeping agreements, appreciating what's working, working from genius, resting, holding stories lightly, releasing the need for approval, trusting there's enough, treating the world as an ally, seeking outcomes that serve everyone, is no longer waiting for the environment to change before leading well.

• Being the resolution isn't a claim that one person single-handedly fixes a broken system.
• Complaining about what's missing while embodying its opposite cancels out any real contribution.
• The more sustainable move is becoming, personally, the quality the situation is missing.

What this means for a silent team

A team that won't push back on a bad roadmap call isn't missing a "feedback culture" someone else needs to install. It's missing a leader who models disagreeing openly first, in the room, before asking anyone junior to take that risk themselves.

The Entire Book in One Framework

Every commitment is a specific technique for doing one thing: staying above the line, in curiosity and openness, instead of below it, in defensiveness and blame. The first six commitments stop the drama that keeps a leader stuck below the line.

The next three reinvest the energy that drama used to consume. The following three examine the deeper attachments, to being right, to external approval, to scarcity, that keep pulling a leader back below the line. The last three turn that inner work outward into how a leader relates to other people.

Conscious leadership isn't a personality trait some people have and others lack. It's a moment-by-moment choice between defending a story and staying curious about it, available in any single interaction, regardless of how the last one went.

10 Most Important Takeaways

• Leadership happens in two states, "Above the Line" (curious, open) or "Below the Line" (defensive, blaming); every commitment is a technique for choosing the first one on purpose.
• Below the line, people default to Victim, Villain, or Hero; above the line, those become Creator, Challenger, and Coach.
• Radical responsibility means asking "how am I creating this," not self-blame, which is just victimhood turned inward.
• Suppressed feelings don't disappear, they leak out sideways; fully feeling an emotion in the body usually resolves it in about ninety seconds.
• Separate facts (what a camera would record) from stories (the meaning you added), and take issues straight to the person involved instead of gossiping.
• Integrity means keeping your word, including renegotiating an agreement before you break it, since even small broken agreements drain trust across a whole team.
• Most capable leaders get stuck in their Zone of Excellence, rewarded but draining, instead of their Zone of Genius, effortless and energizing.
• Wanting approval, control, or security from outside yourself guarantees you'll never feel you have enough of it; all three have to be sourced internally.
• Scarcity is a mindset, not a fact; sufficiency is what makes real collaboration and win-for-all outcomes possible instead of zero-sum tradeoffs.
• The final commitment is to stop waiting for someone else to fix what's missing and become that quality yourself.

A team's culture is rarely a strategy problem in disguise, it's usually a leader's own consciousness, reproduced. The most durable lever for changing a team isn't a new process, it's a leader choosing, moment to moment, to stay curious instead of certain.