Not for anything I can name exactly. It’s quieter than ambition and softer than longing. Something closer to — tenderness. A little more grace. From the world, maybe. Or maybe from myself. Some mornings I can’t tell which direction the reaching is going.

I have learned, slowly and not without resistance, that those are often the same thing. That what I reach for outward is usually what I have not yet offered inward.

Projection dressed as longing. Expectation wearing the face of need.

Somewhere in my late twenties, early thirties, I was going through what I can only describe as a quarter life crisis. The kind where the life you built starts to feel like someone else’s and you don’t know yet whose it should be instead.

I was reading A New Earth around that time. And somewhere in that same season, I came across a Hafiz quote for the first time. I don’t know if they arrived together or separately. What I know is that they landed in the same period of my life, when something was opening, and they became part of the same awakening.

The quote was about the sun. How the sun gives its light completely, endlessly, without keeping any account. It does not say to the earth: you owe me. It does not wait for gratitude. It does not withhold warmth from the ungrateful. It simply gives because giving is its nature. Because it cannot do otherwise.

I put the book down and sat with that for a long time.

Because I recognized, in the negative space of that image, everything I had been doing wrong. All the invisible accounting I had been keeping. The ways I gave and then quietly monitored whether the giving was returned. The tenderness I offered while part of me waited to see if it would be matched.

The sun never says you owe me.

That was the moment.

It took years to understand that insight in my mind. It took longer to understand it in my body. The understanding arrived through books and quiet reckonings. The remembering arrived somewhere else entirely…

I have been doing tai chi since I was young, on and off, the way you do something that was never really a choice — it was just what the mornings looked like in my family.

My first introduction was not graceful. My mother would pull me out of sleep by tugging my arms and legs, patting them down, telling me she wanted me to be tall. I was confused. I was half asleep. I pretended to resist.

But I looked forward to those mornings more than I ever said out loud. The warmth of her hands. The particular way she moved through the living room afterward — swinging her arms, patting her legs, unhurried, like the world had nowhere urgent to be. I didn’t have a name for what she was doing. I just knew it meant morning had arrived and she was there and everything was okay.

I miss those days now in a way that surprises me sometimes.

I am, for the record, five foot three. The tallest woman in the immediate family. So perhaps it worked.

My mother did this. Her mother before her. I watched it for years before I ever did it myself. It went into my body before my mind had a chance to evaluate it.

There are no words in tai chi. No journaling prompts. No framework. Just the body moving through a form that is older than anything I could have learned in a training room.

What I have noticed, returning to it recently, is that it does something the intellectual practices don’t quite reach. It doesn’t teach you that enough is already here. It makes you feel it. The slowness. The weight of your own body moving through space. The breath arriving without being asked for.

You cannot rush tai chi and remain in it. The form requires you to be where you are.

That is the practice underneath the practice. Not the movements. The returning.

I still have mornings where the wanting is loud. Where the gap between where I am and where I imagined I would be feels wider than usual. Where I want more — more recognition, more certainty, more of whatever it is that would make the reaching stop.

I do not think those mornings will disappear entirely. I am not sure they should. The wanting is part of what keeps me moving. The question is only whether it is driving or whether I am driving it.

On the mornings I do tai chi, I remember.

Not because the movement teaches me anything new. Because it returns me to something I already know and keep forgetting. That the body is here. That the breath is here. That my mother moved through this same form and her mother before her and something in that line of women knew, without being able to explain it, that the way through the hard mornings was not to acquire more but to return to what was already present.

Sometimes I find it in unexpected places too. In the people who love me well. My partner — the way they stretch in the morning, dance in the kitchen, pay careful attention to how my coffee is made. The attention that arrives before I know I need it. And something in me recognizes it. Home arriving quietly, through someone else’s hands, when I am not looking for it.

The sun never says you owe me.

I have been carrying that image for more than twenty years. It still does what it did the first time.

Some mornings I forget briefly that enough is already here. Some mornings I feel like I deserve more.

And then I do tai chi. I think of my mother. I think of her mother.

And I remember that the most radical thing I can do on a morning when the wanting is loud is to slow down. To move through the form. To let the body remember what the mind keeps forgetting.

That enough is already here.

This is not that version.

This is the version where you stay home on a Saturday night because you would rather send one more thing out into the world than wonder later if you left something on the table. Not because you are certain it will work. Not because you feel inspired. Because the not-trying is worse than the trying, and you have decided to live by that math even when it exhausts you.

I have been in a season of sending things out. Putting my real story into the world, over and over, to people who may never see it. Writing letters that require me to show up fully, to say here is what I have done and here is why it matters and here is why I believe I am the right person for this. Then waiting. Then writing another one.

It is humbling in a way I did not anticipate.

Not because the work is beneath me. Because the silence is. You put something honest into the world and you get nothing back, and the silence does not mean no and it does not mean yes. It means wait. And waiting, when you have invested something real, takes a specific kind of discipline that nobody prepares you for.

A teacher once said to me: your words won't work if your presence doesn't work.

I have turned that over a hundred times in the last few months. Because the question underneath all of this is not whether the words are good. I know the words are good. The question is whether the presence behind them is real enough, grounded enough, honest enough to carry them across the distance between me and the person reading them. Whether something of me actually arrives.

That is a spiritual question dressed up as a professional one.

I have been developing what I can only describe as a muscle of not caring what happens next. Not indifference. Something different. The ability to send something out with full investment and then release it completely. To do the work as if it matters, because it does, and then let it go as if it is out of your hands, because it is.

Some days that muscle is strong. Some days I wake up and I am already bracing.

The honest thing is that I want certain things very much. There are places I have written to where the mission connected to something I have carried for a long time. Something personal. Something that required me to tell the truth about who I am and where I came from. Those are the hardest ones to wait on. Because you did not just send your credentials. You sent yourself.

What I keep coming back to is this: the only thing I can control is the quality of my effort and the honesty of what I put forward. I cannot control who reads it, when they read it, or whether what they need matches what I bring. I can only keep showing up and keep telling the truth.

So I stay home. I write one more. I send it.

Then I make jeera tea, close the laptop, and sit with the not-knowing for a while.

That is the practice. Some days it feels like enough. Some days enough is harder to locate than others. But I have learned that the days I keep going anyway are the ones that matter most, not because of what comes back, but because of who I am becoming in the reaching.

Your words won't work if your presence doesn't work.

So I work on the presence. The words take care of themselves.

That belief is exactly what makes real dialogue so hard to build.

I was once in a room at a political convention. Not as a delegate. As a facilitator. I had been brought in to run a structured dialogue session and I will be honest: I walked in carrying assumptions about what I was going to encounter. What I found instead was that underneath every position in that room, underneath the language and the policies, were fears I recognized completely. Fear of being left behind. Fear that the world your children would inherit would not have room for them. Fear that nobody in power actually saw you.

I had those fears too. I just had different politics wrapped around them.

That was the moment I understood what dialogue, done well, actually does. It does not change what people believe. It reveals what they share underneath what they believe. And it turns out that underneath is where people actually live.

A few years ago I was working with an ER physician through a HeartMath program. He came into the session the way emergency medicine physicians often come into rooms: moving fast, scanning for problems, running at a frequency designed for crisis management because that is what his work required of him every day.

I did not match his energy. I slowed down instead.

I took a breath and let the pause sit longer than felt comfortable. I moved more deliberately. I lowered my voice rather than raising it to keep up with his pace.

He slowed down. Not because I asked him to. Not because I taught him a technique. Because his nervous system followed the room. Within twenty minutes he was speaking differently, thinking differently, accessing parts of himself that the frenetic pace had been keeping just out of reach.

That is when I understood that dialogue is not primarily a cognitive problem. It is a physiological one. When people are dysregulated they are not processing information the same way. They are scanning for threat. Everything the other person says gets filtered through that state before it reaches the part of them that could actually consider it. You can have the best content in the world and it will not land in a nervous system that has not settled enough to receive it.

Most dialogue programs skip this entirely. They go straight to the content. And the result is what I think of as dialogue theater. People perform the motions of listening. Nobody actually moves.

After one session a participant reached out. He was thoughtful, well-read, someone who had come in confident he understood a particular social issue from every relevant angle. During the session he heard something from people he thought he agreed with about the complexity underneath a position he held. Not an opposing view. A complication from within his own camp. Something he had not made room for.

His message afterward was not long. He said he needed to sit with it. That the conversation had added a layer he had not known was missing.

That is what I mean by dialogue done well. It does not move people from one side to the other. It reveals the texture inside a position they already held. It makes the map more accurate. And accurate maps produce better decisions than confident but incomplete ones.

My job in that room was not to be clever or neutral or even particularly skilled. It was to slow things down enough that people could feel the ground beneath them before I asked them to step toward each other.

Structure does that. Not warmth, not charisma, not good intentions. Specific structural design that creates deceleration. The kind of deceleration that allows someone to hear something genuinely unexpected and sit with it for a moment before responding.

That sitting is where everything happens. That sitting is what most institutions have completely stopped designing for.

We have optimized our organizations, our campuses, our meeting cultures for speed and output. We have stripped out almost every structural mechanism that used to create the deceleration dialogue requires. And then we wonder why people cannot talk to each other.

Here is what I believe after all of this work.

The goal is not agreement. It never was. The goal is a culture where people can disagree and stay in the room, where encountering a perspective you did not expect produces curiosity rather than contempt.

You cannot workshop your way to that culture. You cannot put it in a mission statement. You have to design your way there, deliberately, structurally, with the understanding that the conditions for dialogue are physical before they are intellectual.

The rooms that changed me most were not the ones with the best content. They were the ones where someone had thought carefully enough about structure that my nervous system could finally settle, and I could actually hear the person across from me.

That is the work. It starts with the design of the room.

Not a million. Not a settlement designed to bankrupt anyone. One dollar, plus the legal mechanism to protect a trademark the company has spent more than fifty years building.

The defendant is a drag performer and climate activist whose work Patagonia has, by its own account, supported. The company has said plainly that it agrees with much of the activist’s message. And it is suing anyway.

Most people read a story like this and immediately sort it into a side. I want to do something different with it, because underneath the headline is one of the hardest principles in leadership, and almost nobody practices it well.

A boundary you only enforce against people you dislike is not a boundary. It is a preference wearing a boundary’s clothes.

Let me say first what often gets lost in these stories.

Patagonia is one of the most genuinely philanthropic companies in the world. It has given away its profits, restructured its entire ownership so that the planet is effectively the shareholder, and spent decades funding environmental work most corporations wouldn’t touch. This is not a company looking for someone to crush. The one-dollar damages figure tells you that directly. They are not trying to win money. They are trying to hold a line.

And the line is this. You can admire someone, share their values, want them to succeed, and still need to protect the thing you built from being absorbed into something you no longer control.

That is not cruelty. It is consistency. And consistency is the part of leadership that looks cold from the outside and is actually the deepest form of integrity.

Here is the principle most leaders get wrong.

They believe that enforcing a boundary against someone sympathetic makes them the villain. So they let it slide. They tell themselves that because they agree with the person, because the cause is good, because the optics are uncomfortable, this one time doesn’t count.

But a boundary that bends based on whether you like the other party is not protecting anything. It is just measuring your affection. The moment you only enforce your principles against your opponents, you have admitted that they were never principles. They were weapons.

The hardest test of any boundary is the moment you have to apply it to someone you respect.

Patagonia said something in its filing that is, stripped of all the noise, a governance principle worth studying. They cannot selectively choose to enforce their rights based on whether they agree with a particular point of view. The instant a trademark is only defended against people whose message you dislike, it stops being a trademark and becomes a political instrument. To protect it at all, you have to protect it evenly. Especially against the people you’d rather not.

This is also just how trademark law works, and most people don’t realize it. A trademark is not a trophy you win once and keep on a shelf. It is a right you have to actively and consistently defend, or you lose it. If a company allows even sympathetic exceptions to accumulate, it can legally weaken or forfeit the mark entirely. The law essentially requires the consistency I’m describing. You enforce evenly or you watch the thing you built dissolve into the public domain. Selective enforcement isn’t just hypocritical. It’s how you lose the asset.

There is a second layer most people miss, too. A trademark is not only a name. It is an association. Every time a similar mark operates in the same space, the public begins to link the two, and the original brand starts being defined by whatever the other party does, says, sells, or becomes. It is a kind of slow training of the collective mind, the masses gradually learning to associate your fifty-year-old brand with someone else’s choices that you no longer control. Patagonia spent five decades building precisely what its name means. The risk is not one t-shirt. It is the gradual reassignment of meaning to a brand they can no longer steer.

I have watched this exact dynamic destroy partnerships, co-ventures, and internal teams for fifteen years.

Two parties align on a mission. The energy is good. The values match. And because everything feels warm, nobody wants to be the person who brings up structure. Who defines the boundary. Who asks the uncomfortable question about what happens if this grows, or changes, or starts to compete with the thing it was built alongside.

So the agreement stays vague. Goodwill becomes the load-bearing wall.

And goodwill is not a load-bearing material.

The breakdowns I am called into rarely happen between enemies. They happen between people who admired each other and never defined the line while the relationship was still warm enough to define it easily. By the time the conflict surfaces, the only tools left are the expensive ones. Lawyers. Ultimatums. Public statements. The exact place this case has ended up.

The lesson is not that you should be quick to enforce. Patagonia, by every account, was slow. It tried for years to find a path that let the activist keep working while protecting the brand. That matters. Enforcing a boundary should be the last step, not the first.

The lesson is that aligned relationships need clear structure more than adversarial ones do, not less. When you’re dealing with an opponent, everyone expects the boundaries. When you’re dealing with someone you admire, everyone assumes goodwill will hold, and so nobody builds the structure that would have made this resolvable without a courtroom.

The discipline is to define the line while you still like each other. To treat clarity as an act of respect rather than a sign of distrust. To understand that the kindest thing you can do for a relationship you value is to make its boundaries explicit before they’re tested.

I don’t know how this case will end.

But I know the principle underneath it is one most leaders avoid until it is too expensive to avoid any longer.

You will, at some point, have to protect something you built from someone you genuinely like. How you handle that moment will tell you whether your boundaries were ever real, or whether they were only ever pointed at people who already disagreed with you.

A dollar is not about the money.

It’s about whether the line means anything at all.

Measured. Controlled. Done it dozens of times. Never once put it in a cover letter.

I have also walked across hundreds of beds of hot coals and led other people through them. Executives. Teams. People who arrived certain they couldn’t and left knowing something about themselves that no workshop ever produced. I know what the moment before looks like on someone’s face. I know what changes on the other side.

Also not on the resume.

For years, I learned to live in two versions of myself.

One gets me in the room.

Clean career arc. Recognizable credentials. Embedded enterprise leadership. Google. Meta. Genentech. TED. Harvard negotiation training. Academic degrees. Executive coaching certifications with the right acronyms. Coached 60+ TED(x) clients too. It parses. It scans. It does not frighten the ATS.

The other one actually does the work.

That version includes time in India studying under Sikh and Hindu lineages with teachers who had been practicing longer than I have been alive. Pranayama and breath work studied at the source, not from an app. Clinical and medical hypnotherapy credentials and experience. Somatic and trauma-informed training. Work with veterans. Medicine circles. Grief that had no bottom and no timeline. A nonprofit built from nothing after #MeToo because something needed to exist and I was the person who could build it.

It includes the kind of presence that isn’t learned in a classroom, but in rooms where something real is happening and someone has to stay steady when it gets hard.

It includes the brick.

For a long time, I only sent the first version.

Not because I was ashamed of the second. Because I learned early that certain rooms don’t have language for it. That “somatic” makes some hiring managers nervous. That twenty years of integrative training—the kind that lives in the body and shows up in a room before you’ve said a word—doesn’t translate cleanly into a competency grid. That firewalking and grief work and nervous system mastery don’t fit neatly into a resume column.

So I got good at translation.

I learned to map experience into neuroscience language. To lead with what was legible and let the rest appear later, once I was already in the room.

I got very good at it. That’s not a brag. It’s an exhaustion report.

Recently, I showed someone the full version.

A leader I trust. Someone who has been in enough rooms to know the difference between credentials and capacity.

I showed him everything. The India years. The somatic work. The nonprofit. The fires. The medicine circles. The karaoke-room, fully-alive, uncurated version of me that doesn’t perform professionalism—it inhabits presence.

He looked at it and said: next time lead with this. I’d hire you.

And I didn’t believe him.

That’s the part I keep sitting with. Not the validation. The inability to receive it. Somewhere in years of learning to make myself legible, I started to experience the full version of myself as something that needed to be edited down to be acceptable—even when someone was standing in front of me saying the opposite.

Here is what I know from standing at the edge of fire with people who are certain they cannot cross.

The thing that stops them is never the fire. It is the story they are telling themselves about what they are capable of. A self-assessment formed so early and reinforced so often it starts to feel like fact.

Crossing doesn’t happen because fear disappears. It happens because something shifts enough for action to move anyway. Quiet enough to hear what’s actually true underneath the narrative.

I have helped hundreds of people reach that point. And I am still learning it in myself.

That is the bind I kept missing. The work is the credential. And I had to hide the work to use the credential.

There is a pattern I’ve seen on both sides of this work.

In corporate spaces, the integrative work reads as “too much.” Too unstructured. Too experiential. Too hard to quantify.

In integrative spaces, the corporate experience reads as “too much” in the opposite direction. Too institutional. Too compromised. Too far inside systems that people assume dilute clarity.

So you sand yourself down in both directions until you’re understandable everywhere and fully known nowhere.

What I’ve learned is this: the combination is not the problem. It is the point.

Because I am not two people with two resumes. I am the bridge between them. The same perception that reads a nervous system reads a boardroom. The same training that tracks what a body is doing when the words say otherwise is what lets me see the pattern underneath an organization in crisis. Most people have depth in one world. The rarer thing is someone who can stand in both at once and translate what neither side can see on its own.

That is what makes someone like me valuable inside an organization, not adjacent to it. Not a consultant who arrives and leaves. The person who can sit in the room every day and see the pattern before it becomes a problem. That is not a combination of credentials. It is a single capacity.

The reason I can sit with a C-suite leader in genuine pressure and not collapse into it is not the credential. It is the training underneath it. Nervous system work. Embodied practice. Years of learning how to stay present in intensity without performing stability. The reason I can walk into organizational chaos and see what is actually happening beneath the surface is perception training—the ability to track what is unspoken, to read the room below the language of the room.

None of that fits neatly into a resume. All of it shows up immediately in the room.

That training comes from somewhere. For me, it came from years in India. From grief that reshaped how presence works. From medicine work and clinical training and holding space in moments where there was no script. From a family that crossed fifteen days of open water on a wooden boat in 1980 with nothing but faith and each other. From a 22-year-old mother who held me the entire way and taught me, before I had words for anything, what it looks like to stay present through the unsurvivable.

That is also on the resume. Just not in the format most systems recognize.

I am not retiring the translated version. I still know how to speak different languages in different rooms, and that skill matters. But I am done treating translation as erasure. I am done leading with the version of myself that was designed to be easily categorized.

The full version is not too much.

For the right rooms, it is exactly enough.

His name was Wayne McDonnell. His document was titled “Analysis and Assessment of Gateway Process.” It was part of a broader Cold War investigation into whether consciousness could be used as an intelligence tool — whether the human mind, under certain conditions, could access information beyond the reach of ordinary perception.

The document was classified for twenty years. Declassified in 2003. Largely unread until 2021, when a Reddit post sent it viral and crashed the CIA’s FOIA server under the traffic load.

Most people focused on the remote viewing. The out-of-body travel. The more sensational conclusions.

But beneath all of that was a quieter finding.

Self-knowledge appeared foundational to perception itself.

McDonnell drew heavily on neuroscientist Karl Pribram and physicist David Bohm, whose work suggests reality functions less like a collection of separate solid objects and more like an interconnected field of energy and information. Consciousness, in this framework, is not entirely confined to the brain. Under certain conditions, the boundary between individual awareness and the larger field becomes permeable.

The document is speculative synthesis, not settled neuroscience. McDonnell was analyzing theories and experiential practices, not delivering proof.

But the questions it raises are real. And for anyone who has spent time studying consciousness, nervous system regulation, or the way perception shapes decision-making, parts of it feel less like discovery and more like recognition.

Reading it, I recognized something familiar.

I spent time in India studying yoga and life-energy systems under Sikh and Hindu lineages. I sat with teachers who had spent decades in these practices. I studied directly with Stanislav Grof in Taos New Mexico, whose work on non-ordinary states of consciousness explores similar territory from a clinical direction.

But the moment I understand best happened not in a temple.

It happened in the streets of Old Delhi.

Organized chaos. Goats and cows exchanging hands in narrow lanes. Dogs lying belly-up in the heat. A world so different from Los Angeles that my nervous system didn’t know what category to put it in.

At first I was nervous. The sensory overload was real. My analytical mind was doing what analytical minds do, cataloguing threats, calculating distances, looking for the familiar.

And then something shifted. Not gradually. Immediately.

I thought, strangely and clearly: if something happened and I had to stay here, I could make friends. I could find love. I could build community. I would be okay.

I didn’t reason my way to that. It arrived. Whole. Without explanation.

Moments later an old woman ran after me through the crowd. She pressed a small Ganesh keychain into my hand. She had seen me trying to haggle in my broken Hindi, she said, and found me endearing. Two young boys on a moped appeared shortly after and rode us back through the streets to where we were staying.

I have thought about that sequence many times.

The certainty arrived before the confirmation. The knowing preceded the evidence.

Years later I founded a nonprofit delivering emotional intelligence and medically accurate relationship education in the years after #MeToo.

I didn’t have a marketing budget. I didn’t have a network specifically built for this work. What I had was a program framed with enough precision and integrity that it answered something the moment was already asking for.

The connections came before I went looking for them. A principal here. A teacher there. Artists who heard about the work and offered to support it before I had thought to ask. Volunteers who showed up already aligned, already certain this was where they were supposed to be.

The work was not easy. But the field around it moved with unusual ease. Resources appeared at the threshold of need. The right people arrived at the right moments with a regularity that stopped feeling like coincidence somewhere in the second year.

What I came to understand is that coherence attracts. When the work is genuinely aligned with what is needed, it stops having to chase. That is not mysticism. It is what happens when the signal is clear enough to be heard.

This is where the Gateway document stops being about consciousness research and starts being about leadership.

Most leaders are operating from a layer of conditioned response so familiar it feels like reality. They are not seeing the room. They are seeing their history of rooms. They are not hearing what is being said. They are hearing what they have learned to expect.

Every decision made from that layer carries the distortion with it.

The ones who consistently make the best decisions under pressure are not the ones with the most information or the highest IQ. They are the ones who know themselves well enough to distinguish between what they are perceiving and what their nervous system is projecting onto a situation.

That distinction sounds simple. It is extraordinarily rare.

Self-knowledge, in this sense, is not therapy. It is not journaling. It is not 360 feedback.

It is the specific, often uncomfortable practice of seeing yourself clearly enough that you stop mistaking your conditioned reactions for accurate perception. That you stop performing certainty when what’s actually happening is that you’re afraid. That you stop managing a room when what the room actually needs is for someone to be genuinely present in it.

The Gateway document calls the state of clear perception the Absolute. The Indian traditions I studied have their own names for it. Neuroscience might describe it as heightened metacognition with less defensive filtering.

I call it what happens when a person finally stops performing and starts actually paying attention.

The CIA spent years trying to understand how human consciousness could access something beyond its ordinary limits.

What fascinated me most was that the document ultimately pointed not toward a technology, but toward a practice. Available to anyone. Requiring no clearance and no equipment beyond the willingness to sit with yourself honestly until the noise settles and something truer surfaces.

I have spent fifteen years in rooms with leaders helping them find that place. Not because I read about it. Because I found it in the streets of Old Delhi when the analytical mind finally went quiet and something clearer moved in.

The most powerful thing a leader can develop is not a skill.

It is the capacity to know what they actually know.

Before the analysis. Before the strategy. Before the meeting.

The answer is already there.

The practice is learning to hear it.

My grandmother — the woman who left Vietnam before the fall, who sponsored my family out of the Singapore camps, who called me her brave and beautiful granddaughter every time we met until she was 77 — was gone.

And a soul sister. My partner. Suddenly. By her own hand.

I don’t have clean words for what that year felt like. I’m not sure clean words exist for it. What I know is that I kept moving. Faster, if anything. Filling the silence with work, with mission, with the particular busyness that looks like strength from the outside and is something else entirely from the inside.

And then my body stopped me.

A cough that wouldn’t leave. Months of it. My body doing what I wouldn’t do for myself — insisting on stillness. Insisting on the grief I had been outrunning.

I had no choice but to sit with it.

Grief is not linear. It doesn’t arrive once and then resolve. It descends — again and again, in waves, at unexpected hours, triggered by small things that shouldn’t matter and somehow matter completely.

What I learned in that stillness is that grief doesn’t want to be managed. It wants to be witnessed. It wants someone to stay in the room with it instead of offering solutions or timelines or the promise that it gets easier.

It does get easier. But not because you outrun it.

Because you finally stop.

I think about my soul sister often. The weight I carried after — not just grief but the particular heaviness of wondering. Of replaying. Of all the things I wish I had said or asked or noticed.

That kind of loss doesn’t resolve. You learn to carry it differently. You learn that some things don’t heal so much as they become part of how you move through the world — more slowly, more attentively, with less tolerance for leaving things unsaid.

She changed how I listen. She changed how I love. She changed what I think is worth saying out loud.

What I also learned is that grief moves through organizations the way it moves through bodies.

Unnamed. Quietly. Reshaping everything underneath while the surface keeps functioning.

I've sat with the council circles at Snapchat to learn — a space built intentionally for something most corporate environments don’t allow. Not a meeting. Not a debrief. A circle where people could name what they were actually carrying. Where grief had a container instead of a workaround.

What happened in that room was not soft. It was not a detour from the real work.

It was the real work.

We are in a moment of collective grief that most organizations are not naming.

Mass layoffs. Restructuring. AI reshaping entire industries and the identities built inside them. The particular fear of people who worked hard and did everything right and still don’t know what comes next.

This grief doesn’t announce itself in meetings. It moves through people quietly — in how they show up, in what they can’t access, in the distance that opens between colleagues who used to feel like a team.

Everyone is carrying something.

The question is whether the organization creates any space for that — or whether people are expected to carry it alone, invisibly, and still perform.

Leaders don’t need a perfect blueprint for this.

They need the willingness to pause. To ask how people actually are and mean it. To create enough safety that grief can be named instead of managed. To understand that acknowledging loss doesn’t diminish productivity — it restores the human connection that productivity depends on.

A check-in. A circle. A moment where someone says: this has been hard, and we don’t have to pretend otherwise.

That’s not weakness in a leader.

That’s the thing that makes people stay.

My grandmother called me brave and beautiful every time we met.

I didn’t know, when I last saw her, that it would be the last time.

I try to remember that now — in sessions, in rooms, in conversations where something important could be said or left unsaid. I try to say the thing. To stay present. To not leave anything important unspoken because I assumed there would be more time.

She taught me that without meaning to.

So did my soul sister.

Grief is a radical teacher.

It doesn’t wait for you to be ready.

But if you let it — if you stop running long enough to actually feel it — it gives you something back.

Not the people you lost.

Something quieter than that.

The knowledge of what actually matters.

And the courage to act like it does.

It happens too gradually to notice. A little more distance here. A little less repair there. Choosing the easier thing so many times that the harder thing starts to feel unnecessary.

And then one day you look up and realize you're not lonely exactly. You're just not really in it anymore.

In Japan, there are real cases of people forming long-term emotional bonds with virtual partners and AI companions. One woman described marrying a holographic character she had built a relationship with over years.

It would be easy to read that as an outlier. A cultural curiosity.

I think it's a mirror.

AI companions are getting more emotionally responsive. They remember you. They don't reject you. They don't require repair after conflict. They don't withdraw. For many people, that starts to feel like safety.

At the same time, Japan, South Korea, much of Europe, and the US are all moving in the same direction: declining birth rates, delayed marriage, rising loneliness, fewer long-term partnerships.

Real relationships are getting harder to sustain. Artificial ones are getting easier to stay in.

That gap is not just sociological. It is personal. It is happening inside people, quietly, one small withdrawal at a time.

Psychology has been consistent on this for decades.

Irvin Yalom, Carl Rogers, relational psychology across traditions — they all arrive at the same place in different language. People don't primarily change through insight or advice. They change through relationship. Through being seen. Through rupture and repair. Through real human contact that asks something of you and gives something back.

Not understanding alone. Relationship.

The friction is not the problem. The friction is the medicine.

But something is fracturing.

More people are stepping away from real relationships and calling it healing, boundaries, or spiritual work. Sometimes that space is genuinely necessary. But sometimes it becomes emotional avoidance that feels elevated. A way of protecting yourself from the very thing that would change you.

Because real relationship requires capacity. To stay present when you feel misunderstood. To repair after conflict instead of disappearing. To tolerate someone else's emotional unpredictability without shutting down or burning everything down.

AI removes most of that friction. It offers presence without risk. Intimacy without exposure.

So people are drifting toward what costs less. Not consciously. Gradually. The same way you stop going to the gym not because you decided to quit but because you just kept choosing the easier thing until quitting became the default.

And when relational capacity drops, other things follow.

Rising loneliness is closely linked in public health research with emotional dysregulation — lower distress tolerance, higher reactivity, a nervous system that is always slightly braced. When people are not regularly grounded through safe connection, the body keeps a different kind of score.

These are not separate problems. They cluster around one thing: reduced capacity for real, regulated human connection.

So what looks like separate trends — AI companionship, rising loneliness, emotional volatility, declining partnership — starts to connect.

This is not a technology problem.

It is a capacity problem.

Capacity for intimacy. For repair. For staying present when it would be easier to leave. For letting someone actually know you instead of a curated version of you.

And when that capacity drops, people don't stop needing connection.

They start substituting it. And the substitutes get better every year.

If healing happens in relationship — and the research is consistent that it does — then the real crisis is not loneliness.

It is relational endurance.

The ability to stay human with each other under pressure. To choose the harder thing. To repair instead of retreat. To remain in real contact with another person even when that person is unpredictable and imperfect and sometimes gets it wrong.

No system can build that capacity for you.

It only grows in the one place it has always grown.

In relationship. With another human being. Who stays.

On paper, it was working. The org chart had been redrawn. The new leadership team had been announced. Town halls had been held. Culture decks had been updated with fresh language about shared values and unified vision.

And yet — something wasn't moving.

Managers were duplicating decisions. Teams that were supposed to collaborate were quietly routing around each other. A low-grade tension had settled into the organization that no one could name, so no one was addressing it.

They had hired me to design a leadership development program.

I told them I needed three weeks before I touched a single learning objective.

That pause — before the program, before the curriculum, before any intervention — is the work most organizations skip.

We have a design bias in organizational development. We move fast toward solutions. Someone surfaces a problem: engagement is down, a team is stuck, a leader is struggling. And almost immediately, the conversation shifts to what we should build. A workshop. A coaching program. A feedback framework. A retreat.

The instinct is understandable. Programs are visible. They signal action. They produce deliverables that can be reported upward.

But a program designed before a diagnosis is just a very expensive guess.

What I found in those three weeks wasn't a leadership gap.

It was a decision rights problem wearing a culture problem as a costume.

Two organizations had merged, but no one had mapped what actually changed underneath the org chart. The informal authority structures — who people actually went to when they needed a real answer — hadn't transferred. In one legacy organization, decisions had historically been made by a small group of senior individual contributors who held institutional knowledge no title had captured. In the other, authority flowed through hierarchy almost exclusively.

When those two systems merged, people defaulted to their original operating logic. Confusion wasn't a symptom of poor communication. It was a symptom of two incompatible decision architectures running simultaneously inside the same org chart.

No leadership program was going to fix that.

What fixed it was naming it — clearly, at the right level, with the data to back it up — and then designing a targeted intervention around decision rights, not development content.

This is what systems thinking actually looks like inside an organization.

Not a framework on a slide. Not a Cynefin diagram in a workshop. The real thing is slower and less elegant: sitting with what you're observing long enough to distinguish the symptom from the cause, and resisting the pressure to act before you understand.

Organizations under pressure — scaling fast, integrating acquisitions, navigating leadership transitions — are especially vulnerable to the program-first instinct. The urgency is real. The noise is loud. Stakeholders want to see movement.

But movement in the wrong direction compounds the problem.

A merger doesn't fail because the training was inadequate. It falters when no one maps the invisible architecture — the informal networks, the cultural load-bearing walls, the decision patterns — that didn't appear on either org chart and didn't survive the combination intact.

The organizations that integrate well aren't the ones with the most robust L&D calendar. They're the ones with someone who slowed down long enough to ask: what are we actually looking at here?

MIT research on organizational change consistently finds that transformations stall not from lack of effort but from misdiagnosis — leaders addressing the visible problem while the structural cause continues underneath. McKinsey's work on post-merger integration points to the same pattern: the organizations that capture value fastest are those that explicitly map cultural and operational incompatibilities before designing integration programs, not after.

The diagnostic phase isn't a delay. It's the work.

Three things that change when you lead with diagnosis:

1. You stop solving the stated problem and start solving the real one. The stated problem is almost never the problem. It's the place where the problem became visible. Diagnosis is the process of tracing backward from the symptom to the source — which requires a different set of questions than a needs assessment, and a different quality of listening than a stakeholder interview.

2. Your interventions get smaller and more precise. One of the counterintuitive outcomes of good diagnosis is that the intervention often shrinks. You need less when you know exactly where to apply pressure. Targeted beats comprehensive almost every time.

3. You earn the trust that makes the real work possible. Nothing builds credibility with senior leaders faster than demonstrating that you understand their business more deeply than they expected. Diagnosis done well is a form of partnership. It signals that you're not there to run a program — you're there to solve a problem.

The three weeks I spent before touching that leadership program changed everything about what we built.

More importantly, it changed what we didn't build — which saved the organization significant time, money, and the particular exhaustion that comes from doing a lot of work in the wrong direction.

The merger didn't need a better leadership curriculum.

It needed someone willing to look at what was actually there.

That's still the rarest thing I know how to offer.

Fifteen days on the South China Sea. A wooden boat carrying close to 80 people, lost, no destination certain, no country yet willing to claim them. My father was there. My five year old sister was there. And my mother was dehydrated, sick, and still nursing me — this baby she had carried out of a falling country in the dark, quietly, so no one would hear us leave.

I was 20 months old. I don't remember any of it.

And yet.

There is a kind of knowing that lives below memory. Below language. In the body, in the blood, in whatever moves through us before we have words for it.

I have spent my entire adult life learning to name that knowing professionally. Nervous system regulation. Somatic awareness. Presence under pressure. I have sat with executives and leaders and people in the hardest moments of their lives and I have helped them find the still place underneath the noise.

I have always known where I first learned it.

Not in a training room. Not from a credential.

On a boat. At 1 years old. In my mother's arms. Before I knew what fear was, I was held through it.

My family was Catholic. They left with faith and almost nothing else.

My maternal grandmother had left Vietnam before the fall of Saigon, already gone by 1975, already building a life somewhere else. When we were rescued by a Kuwaiti commercial ship and brought to the refugee camps in Singapore, she was the one who sponsored us. She was the one waiting.

We landed in Utah. The Mormon community there gave us clothes. They were kind in the way that quiet, practical kindness is kind — without ceremony, without expectation. My parents accepted it the way they accepted everything in those years. With gratitude and without much fuss. There was too much to do.

I have thought about that stretch of time often. The camps. The sponsorship. Utah. The particular texture of starting over with nothing in a place that looks nothing like home.

My mother moved through all of it holding me.

I feel very American. I also feel very Vietnamese. When I spent years in India studying, I felt very Indian.

People find that surprising. They expect someone with my origin story to need a fixed place to stand, a single identity to anchor to.

But I think my beginning produced the opposite.

When you start your life being carried across open water by someone who refuses to put you down — you learn early, in the body, before the mind can interfere — that home is not a place. Home is the willingness to stay present when everything around you is uncertain. Home is the person who holds on.

I have been building that home inside myself ever since.

I don't know exactly what my mother felt on that boat.

She doesn't narrate it the way I might. That is also something she gave me — the understanding that some things are carried without being explained. That presence doesn't require performance. That you can move through the unsurvivable without making a speech about it.

What I know is the fact of it.

She was 22. She was sick. The water had no bottom and the darkness had no guarantee. My father was there, holding what he could hold. And my mother held me.

For fifteen days she held me.

I have walked into a lot of rooms in my life. Boardrooms, conflict rooms, grief rooms, rooms where people have forgotten how to speak to each other. I have sat across from people in the kind of pressure that makes most people want to leave.

I have never once felt like I couldn't stay.

I know where that came from.

It didn't come from training or methodology or years of practice, though I have all of those things.

It came from being held on the water before I was old enough to be afraid of it.

It came from her.

And I have spent the rest of my life trying to offer other people some version of what she gave me on that boat.

Not rescue. Not answers.

Just the certainty that someone is not letting go.

The difficult conversations. The executive who won't hear feedback. The team that's been in conflict so long they've forgotten what it felt like before. The leader sitting across from you who is brilliant and defended and quietly drowning and doesn't know it yet.

That part is hard. But it's also clear. There's a container. A role. A reason you're in the room.

What nobody asks about is what happens after.

When the session ends and the client logs off and you close your notebook and walk back into your own life.

I've been asked, more than once, whether I can actually turn it off.

Whether the skills stay at work. Whether I come home and stop listening the way I listen professionally. Whether I get to just be a person.

The honest answer is no. And I've stopped thinking of that as a problem.

What I know how to do — really hear someone, track what's underneath what they're saying, stay present when things get uncomfortable, not take the bait when someone is defending instead of communicating — that doesn't live in my work brain. It lives in me. There's no commute it doesn't survive.

So I bring it home. All of it.

What that actually looks like is quieter than people imagine.

It doesn't look like facilitating my own relationships. It doesn't look like running a debrief after a hard conversation or naming someone's attachment pattern out loud.

It looks like staying in the room when the room gets tense. Not because I'm performing patience but because I've learned, at a cellular level, that the thing someone says when they're defensive is almost never the thing they mean. And that if you can wait — really wait, without preparing your response or managing your reaction — something truer usually surfaces.

It looks like knowing when I'm the one who's defended. That's the harder skill. Seeing yourself clearly in real time is different from seeing a client clearly. The stakes are different. The ego is more involved. But the practice is the same: what am I actually feeling, and is what I'm about to say going to serve this moment or just protect me from it.

It looks like not needing every conversation to resolve. Coaching teaches you that insight rarely arrives on schedule. You plant something and you wait. That's true at home too. Some things need to be said and then left alone to do their work.

I think the assumption is that people who do this work are either saints or frauds.

Either they've transcended the ordinary difficulties of being in relationship with other humans, or they're performing wisdom they don't actually live.

The truth is more ordinary than either.

I get it wrong. I get tired. I have days where I've given so much to the work that I come home empty and the best I can offer is presence without much behind it. I know what I should do and sometimes I do the other thing anyway.

But the training doesn't leave. It's not a hat I wear professionally and hang by the door.

It's closer to a language. One I've spoken long enough that I don't translate anymore. I just think in it.

What I've come to believe is that this work only means something if it changes you.

Not your resume. Not your methodology. You.

If you can hold a client in a moment of real vulnerability and then go home and be defended and reactive and unwilling to be seen — something didn't transfer. The work stayed at work. And that's a kind of compartmentalization that I think quietly costs people more than they realize.

The goal was never to be good at this between nine and five.

It was to become someone for whom this is just how you move through the world.

I remember a moment with my partner when things got uncomfortable and I had no words. Me, without words. I didn't reach for a reframe or a question or anything I would have used professionally. I just stayed. Present, quiet, without needing to fix it. And I spoke the next day, when there was actually something true to say.

That might be the most useful thing this work has ever given me. Not the language. The willingness to wait until the language is real.

I'm not there perfectly. Nobody is.

But I'm closer than I used to be. And the distance between who I am in a session and who I am when I close the laptop has gotten smaller every year.

That's the thing I actually measure. Not the client outcomes or the frameworks or the credentials.

Whether the work is making me more human.

So far, I think it is.

I spent two years living in the Sierra Nevada region. Lake Tahoe was close enough to feel like home — that water, that stillness, that particular quality of light. It's a place I know physically and feel connected to in a way that's harder to name.

So when I read that nearly 50,000 people in that region are being told to find alternative power sources because AI data centers are consuming larger portions of Nevada's electricity grid, something in me shifted. Not as a policy concern. As something more personal. A place I love being quietly reallocated to serve a demand most people never see.

There is no cloud. There are data centers, power grids, cooling systems, water infrastructure, and regional tradeoffs sitting underneath every interaction we treat as instant and weightless.

What looks like a software shift is, underneath, an infrastructure shift.

I use AI in my work. I recommend it to leaders and teams. This isn't a case against it — it's a case for understanding what we're actually working with.

The numbers are worth sitting with.

U.S. data centers consumed an estimated 211 billion gallons of water indirectly in 2023 alone — and that was before the current AI buildout hit full scale. Training a single large language model can directly evaporate 700,000 liters of freshwater. By 2028, Morgan Stanley projects AI data centers could drive an 11-fold increase in annual water consumption for cooling and electricity generation.

Energy demand tells the same story. A January 2026 report projects U.S. data center electricity demand will nearly double between 2025 and 2028 — from 80 to 150 gigawatts. That's the equivalent of adding a country the size of Spain to the grid in three years.

These aren't abstract projections. They're allocation decisions. And they're already landing somewhere.

We've seen this pattern before.

Electricity once felt like a magical abstraction — clean, infinite, always available. Until cities had to redesign around peak load, generation limits, and regional allocation.

The internet felt the same way in its early phase. Then streaming hit scale and bandwidth stopped being an IT detail. It became a national infrastructure constraint that reshaped pricing, regulation, and investment.

AI is following the same trajectory. But with a different input: intelligence itself.

Not storage. Not bandwidth. Cognition.

Cognition at scale doesn't behave like a software feature. It behaves like a utility demand system — continuous, unpredictable, compounding across every industry that adopts it. And like every utility system that scaled into infrastructure, the costs stop being abstract. They show up in electricity curves, water usage, grid stress, and the quiet reshaping of where compute can physically exist.

Here's what I think about as someone who develops leaders inside organizations navigating this moment.

MIT Sloan research on AI adoption across 50 organizations found that leaders who set clear guardrails — cross-functional, deliberate, informed about actual constraints — consistently outperformed those who simply enabled broad access and hoped for the best.

The difference wasn't technical literacy.

It was systems thinking.

The leaders who make the best AI decisions aren't the ones most excited about the technology. They're the ones who can see both layers simultaneously — the frictionless experience and the infrastructure underneath it.

That gap between what AI feels like and what it actually requires? That's a leadership problem. It shows up in adoption strategies that skip tradeoffs, in AI commitments made without understanding what they're actually resource-committing to, in teams who optimize for speed without accounting for the system they're accelerating inside.

Research on AI-driven leadership increasingly points to the same finding: the most critical capability isn't knowing how to use the tools. It's maintaining the judgment to know what the tools can't see — the second-order effects, the resource implications, the human costs of moving fast inside a constrained system.

Systems thinking has always been a leadership differentiator. AI just raised the stakes for not having it.

Three things leaders can do right now:

1. Map your AI commitments to actual resource costs. Before expanding AI tooling across your org, ask: what does this require in compute, data infrastructure, and human oversight? Build that into the business case, not as a footnote.

2. Create a cross-functional AI tradeoff conversation. Not just IT and legal. Finance, operations, people. What are we actually choosing when we choose this? That question belongs in the room before the contract is signed.

3. Build infrastructure literacy into leadership development. The next generation of leaders will make decisions at the intersection of AI capability and physical constraint. Organizations that develop that literacy now will move more strategically than those who learn it from the news.

The most important shift isn't that AI is powerful.

It's that intelligence is becoming infrastructural — which means every leader, every team, every organization is now operating inside an allocation system whether they understand it or not.

The ones who do will make better decisions. For their organizations, and for the places — and people — that sit underneath the abstraction.

Because every abstraction eventually meets physics.

And physics always has a place.

Belonging doesn’t fail loudly

When people stop feeling like they belong, they rarely name it. They adjust. They get more careful with language. They stop checking assumptions as often. They start carrying more of the context in their own head instead of sharing it out loud. Nothing breaks. Everything gets heavier.

The real issue isn’t disagreement. It’s interpretation drift.

Most organizations think alignment is about shared goals. But in practice, the real breakdown happens earlier—at interpretation. What did that decision actually mean? Is this direction fixed or still flexible? How direct is too direct here? What happens if I challenge something in real time? People don’t need identical opinions to work well together. They need stable interpretation of each other’s intent. Without that, every interaction carries extra cognitive load. And that load quietly drains belonging faster than any formal culture issue ever will.

Intergenerational organizations amplify this

Not age. Not tenure. But the era people were trained in.

Some were shaped in environments where clarity came from hierarchy and documentation. Some were shaped in environments where clarity came from speed and iteration. Some were shaped in environments where clarity came from constant informal coordination. So when they land in the same org, they’re not just bringing different skills. They’re bringing different assumptions about how work behaves. That’s where things start to drift—quietly.

After COVID, this became impossible to ignore

Distributed work removed a lot of the informal correction loops that used to keep interpretation aligned. People weren’t just missing meetings. They were missing context signals—tone, timing, micro-adjustments that happen in shared physical space. I built work post-COVID around this exact gap—less about traditional “unconscious bias” framing, and more about how perception, intent, and interpretation shift when people no longer share the same lived signals of work.

What became obvious very quickly: most misalignment wasn’t rooted in intent. It was rooted in signal distortion. People weren’t trying to exclude each other. They were reading different versions of the same moment.

Where bias actually shows up at work

Not in obvious or dramatic ways. In small interpretive shortcuts that compound over time: silence gets read as agreement, speed gets read as confidence, directness gets read as authority or aggression depending on who’s speaking, visibility gets mistaken for contribution. None of this is malicious. But it quietly shapes who gets heard, who gets looped in, and who starts adapting their behavior to stay legible. That adaptation is where belonging starts to thin.

The hidden cost: people start translating themselves

This is the part I see most teams miss. When interpretation isn’t stable, people don’t disengage immediately. They become translators. They pre-soften their opinions. They over-contextualize everything. They adjust tone before substance. They anticipate misunderstanding before it happens. And slowly, they stop showing up directly in their own thinking. Not because they don’t care. Because it costs less to be understood than to be precise.

What actually restores belonging

It’s not more messaging. It’s not more values. It’s reducing interpretation variance inside everyday interactions.

That means making a few things unambiguous: how decisions actually get finalized here, what kinds of disagreement are expected vs avoided, what signals are meaningful vs incidental, where people are allowed to be wrong out loud without losing standing.

Belonging improves when people stop having to guess how they’re being read.

Intergenerational organizations aren’t fragile. They’re layered systems that were never fully translated into a shared operating language. And most of what gets labeled as “culture issues” are actually interpretation issues that have been allowed to accumulate. The work isn’t to smooth out difference. It’s to make interpretation stable enough that people can stop editing themselves just to stay correctly understood. That’s usually where belonging starts to come back online.

The work I tend to gravitate toward sits right here—at the point where belonging, performance, and interpretation overlap. Because once people stop having to translate themselves just to be understood, most of the system starts working again.

The team is talented. The strategy is sound. The mission is clear. On paper, nothing looks broken.

And yet things begin to feel heavier than they should.

Meetings get longer. Decisions get revisited. Smart people start solving the same problem from different angles. Projects move, but not always in the same direction.

From the outside, it looks like a speed problem.

Inside the system, it is usually something else.

Friction.

Not the dramatic kind. Not conflict. Not obvious dysfunction.

The quieter kind.

A leader assumes alignment because everyone nodded in the meeting. A cross-functional partner interprets a priority differently than intended. A manager hesitates to make a decision because three other teams might be impacted. A talented employee spends more energy navigating ambiguity than doing the actual work.

None of it looks catastrophic.

Until it repeats at scale.

Research on team effectiveness, decision-making, and organizational execution consistently points to the same pattern: high-performing teams do not simply move faster. They reduce the number of places where work gets stuck.

Studies from Harvard Business Review on decision velocity and organizational clarity show that teams with clear decision rights, psychological safety, and shared operating norms consistently outperform teams with equally strong talent but inconsistent communication.

In other words:

Talent matters

.

Strategy matters.

But how people operate together matters more than most organizations realize.

The leaders who scale best tend to do three things differently:

●They create clarity before urgency forces it

●They make decisions that do not need to be re-decided

●They treat friction as data, not drama

That last one matters.

Because friction usually shows up before performance issues do.

It shows up as:

●repeated conversations

●unclear ownership

●talented people asking for the same clarification twice

●strong teams moving, but not moving together

Most organizations try to solve this with more process.

More meetings. More dashboards. More documentation.

Sometimes that helps.

Often, it just adds more surface area.

The stronger leaders do something different.

They slow down long enough to ask:

●Where, exactly, is energy leaking from the system?

Because at scale, the goal is not to move faster.

It is to move cleaner.

And the organizations that learn that early rarely need to work as hard to sustain momentum.

Equal effort.

Equal sacrifice.

Equal emotional labor.

Equal contribution.

It sounds mature.

It sounds fair.

It also quietly trains people to keep score.

And the moment human beings start keeping score, something important begins to erode.

Trust.

Generosity.

Curiosity.

The willingness to assume good intent.

I’ve seen this inside marriages.

I’ve seen it between people who built something meaningful together.

I’ve seen it inside executive teams responsible for thousands of employees, complex decisions, and cultures that shape how people live and work every day.

Different environments.

Same pattern.

Someone starts carrying more for a season.

A little more responsibility.

A little more emotional labor.

A little more uncertainty.

A little more of what no one else can see.

At first, it feels like leadership.

And sometimes it is.

But if it goes unnamed for too long, leadership can quietly become resentment.

Not because anyone is weak.

Because they’re human.

That’s why I no longer believe the strongest partnerships are built on fifty-fifty.

I believe they’re built on 100/100.

Not equal energy every day.

Some days you carry 70, and they carry 30.

Some days it’s 80/20.

Some seasons, life asks one person to carry more than they ever expected.

And then life shifts…

and the roles reverse.

Not equal output every season.

But equal ownership.

Equal willingness to repair.

Equal willingness to tell the truth before resentment becomes culture.

Researchers like John Gottman spent decades studying what predicts long-term relational success. It wasn’t perfect communication. It wasn’t compatibility. It wasn’t avoiding conflict.

It was something much more human:

Repair.

And something Gottman called bids for connection.

A bid can look almost insignificant.

“Hey… look at this.”

A hand on your shoulder.

A random article sent between meetings.

A sigh at the end of a long day.

“Got a minute?”

“Can I tell you something?”

Small moments that are rarely about the moment itself.

They’re often asking a much deeper question:

Are you with me?

Do I matter right now?

Can I reach you?

The healthiest couples don’t get this right every time.

The healthiest teams don’t either.

But over time, they learn to turn toward these moments instead of past them.

● To choose curiosity over assumption.

● Presence over performance.

● Repair over being right.

And in organizational psychology, research from Google found that the highest-performing teams weren’t defined first by intelligence, experience, or credentials.

They were defined by psychological safety—the ability to speak honestly, take interpersonal risks, ask difficult questions, admit mistakes, and recover without fear.

Different language.

Same principle.

Whether you’re leading a company…

a team…

a romantic partnership…

or a difficult conversation…

The question isn’t:

“Am I doing my half?”

The better question is:

“What does this moment require from me?”

Sometimes that means speaking.

Sometimes that means listening.

Sometimes that means repairing.

Sometimes that means admitting you’re reaching your limit before frustration starts speaking for you.

That’s leadership.

And often…

That’s love.

Three signs you’ve stopped partnering and started keeping score:

• You’re remembering everything you did, and very little of what the other person may be carrying.

• Your “help” starts feeling invisible.

• You’re having entire conversations internally instead of out loud.

Three practices that change everything:

• Name capacity before resentment.

• Repair faster than your ego wants to.

• Regulate your nervous system before you defend your position.

Because the strongest partnerships—at home or at work—were never built on half.

They were built by people willing to bring their whole selves.

You spend years learning how to design programs, facilitate rooms, coach leaders through the hardest conversations of their professional lives. You get good at it. You build a reputation. Clients refer you to other clients. And somewhere in the middle of all of that, you start to notice a pattern that nobody in this field talks about out loud.

The best thing you can do for your clients is make yourself unnecessary.

I did not figure this out on my own. I had to be humbled into it.

I found out the way you usually find out about these things. Not directly. Through someone who knew someone.

About a decade ago, a former client — a biotech company where I had spent six months running a leadership development program — had put out a search for a new facilitator. Different firm. Fresh start. The program I built was being replaced.

I wish I could tell you I handled this gracefully. I did not. I refreshed LinkedIn approximately 10 times looking for context clues. I replayed every session in my head. I considered, briefly, sending a very calm and professional email that definitely would not have been either of those things.

Instead I sat with it. Which is what I tell my clients to do. It is easier advice to give than to take.

Here is what I eventually had to admit: I had built something that only worked when I was there.

The sessions had been good. The feedback was strong. Leaders were showing up differently in the room. By every visible measure, the work was working. And then my engagement ended, and apparently so did everything we had built together.

My first instinct was to make it about them. Budget constraints. Leadership turnover. The usual reasons organizations quietly abandon development work. All of those were probably true.

But the more honest answer was simpler. I had designed a program that lived in the sessions. The insight stayed in the room. The behavior change stopped at the door. When I left, the program left with me.

I had spent six months building something that dissolved the moment I stopped showing up. Which, if you think about it, is a very expensive way to change nothing.

There is a version of this work that is accidentally designed to keep you needed. You build something excellent. People rely on it. They rely on you to deliver it. The organization grows while you are there and contracts when you are not. Nobody intends this. It is just the path of least resistance. It also happens to be great for repeat business, which I am not proud to admit crossed my mind.

Designing for your own obsolescence is harder.

It requires more upfront work, more trust in the people you are developing, and a willingness to hand something over before it feels completely finished. It means accepting that someone else will deliver your program differently than you would. That they will adapt it, simplify parts of it, emphasize things you would not have emphasized. That watching this happen will be uncomfortable in a way that is difficult to explain to anyone who has not built something and then had to let it go.

But it is the only approach that actually serves the organization.

A study published in the Journal of Applied Behavioral Science found that leadership programs designed with explicit transfer mechanisms — internal facilitators, peer accountability structures, documented methodology — produced behavior change lasting an average of 14 months longer than programs without them. Same content. Fundamentally different architecture. The difference was not what got delivered. It was what got left behind.

Fourteen months. For the same program. Just designed differently.

After the biotech moment, I went back and looked at everything I had built for that engagement. The session materials were excellent. The facilitation was strong. And there was almost nothing designed to survive my departure.

No internal facilitator trained to run the next cohort. No measurement system for the HRBP to track behavior change at 60 and 90 days. No peer accountability structure to keep leaders connected after the sessions ended. No documentation of why the program worked, only what it did — which meant anyone who inherited it would be following a script without understanding the reasoning behind it.

I had built a program. I had not built infrastructure.

The distinction matters more than most practitioners want to admit. A deliverable is something you hand over when it is finished. Infrastructure is something the organization runs on after you are gone. They require completely different design thinking, and most of us are trained to build the former.

I eventually got this right — twice, in ways that stuck with me.

The first was with a global speaker organization. Three years coaching their talent, but I also built a methodology the internal team could use after I was gone. The diagnostic framework. The common patterns. The moments where most speakers need a specific kind of intervention. What I handed over was not a curriculum. It was a capability. People I never met were coached using something I built.

The second was with a technology company running a manager development program. Instead of facilitating every session myself, I spent the first two months training three internal HRBPs to co-facilitate alongside me. By month four they were running sessions independently. By the end of the engagement they had adapted the curriculum for their own context in ways I would not have thought to. The program they ran in year two was better than the one I had designed in year one. I had nothing to do with it. That felt exactly right.

That is the best possible outcome. It is also, if I am honest, a little terrifying. Watching something you built continue without you, knowing it will be done differently, knowing you cannot control it anymore. I find this uncomfortable every single time. I have also learned that the discomfort means I care, and that caring is actually the point.

Before I design anything now, I ask three questions I used to skip entirely.

●What needs to be true for this work to continue after I leave? This forces the sustainability conversation upfront rather than as an afterthought, which is where it usually lives and where it usually dies quietly while everyone pretends not to notice.

●Who inside this organization needs to understand this well enough to carry it forward? The answer changes everything about how you design. You build with them, not just for them. They stop being an audience and start being co-architects.

●What would success look like in two years, not two months? Satisfaction scores and completion rates tell you almost nothing about whether development work is holding. The real signal shows up later — in how a leader navigates the next hard situation, in whether the behavior change survived contact with real organizational pressure. This question also makes clients slightly uncomfortable, which I have come to think of as a good sign.

Here is the counterintuitive thing I have learned after fifteen years of this work.

The organizations that get the most from their development investments are not the ones that hired the best facilitators. They are the ones that hired facilitators committed to making themselves unnecessary.

When clients know your goal is genuinely their long-term capability and not your continued engagement, something shifts. They invest more. They take the work more seriously. They stop treating development as something being done to them and start treating it as something they are building together.

The work lasts because they own it. Not because you are still there holding it up.

I think about the biotech company sometimes. I do not know if the new facilitator built something that held. I hope they did — not in a gracious professional way but in a real way, because the leaders in that organization deserved work that lasted.

What I know is what I would do differently. Less time perfecting the sessions. More time building the organization's capacity to run without me. An internal facilitator trained from month one. A measurement system built before the program launched, not after. A deliberate plan to make myself progressively less necessary.

The goal I never told my clients is this: I want to leave every organization I work with more capable than I found it. Not more dependent on me. Not impressed by what I built. More capable. On their own. Without me.

That is harder to sell than a six-month program.

It is also the only thing worth building.

I work with leaders and organizations on building development that holds — not just while I am in the room, but long after. If this resonated, I would love to hear what it brought up for you.

He knows exactly what it is. He can describe it in detail — the dynamic with his peer on the infrastructure team, the meeting that ends with vague agreement and no actual alignment, the slow accumulation of tension that nobody names. He has rehearsed the conversation in his head at least forty times. He knows what he wants to say. He even knows how he wants to say it.

He just has not said it.

When I asked him why, he paused for a long time.

"I tell myself I'm waiting for the right moment," he said. "But honestly? I think I'm afraid of what happens if I actually say it out loud."

Marcus is a VP at a fast-growing technology company. He is brilliant, highly regarded, and genuinely committed to his team. He is also one of the most conflict-avoidant leaders I have ever coached. And in fifteen years of this work, I have learned that those two things — exceptional capability and conflict avoidance — show up together far more often than most people realize.

What Conflict Avoidance Actually Looks Like

We have a distorted image of conflict avoidance. We picture someone who shrinks, who backs down, who cannot stand up for themselves. But in most of the leaders I work with, it looks nothing like that.

It looks like a meeting that ends with everyone nodding and nobody actually aligned. It looks like a decision that keeps getting deferred because the real disagreement underneath it has never been surfaced. It looks like a leader who is brilliant in a 1:1 but mysteriously vague in a room full of peers. It looks like a team that moves fast in slightly different directions because their leader never had the conversation that would have pointed them the same way.

It does not look like weakness. It looks like busyness, like strategy, like patience. It is remarkably easy to mistake for wisdom.

Research in organizational psychology backs this up. Studies consistently show that conflict avoidance in leadership is one of the strongest predictors of team dysfunction — not because conflict itself is necessary, but because the absence of honest dialogue creates accumulated ambiguity: a fog of unresolved tension that slows decision-making and erodes trust over time. Teams do not fall apart because people disagree. They fall apart because the disagreements never get spoken.

Why Smart People Avoid Hard Conversations

I want to be honest about something: I have avoided hard conversations too.

Early in my practice, I was coaching a senior leader whose behavior was genuinely harmful to her team. I could see it clearly. Her team could see it clearly. And week after week, I found ways to approach the topic sideways — reframing, reflecting, asking questions that circled the truth without landing on it.

I told myself I was being sensitive. I told myself the timing was not right. I told myself she was not ready.

What I was actually doing was protecting myself from the discomfort of saying something that might rupture the relationship.

Which is exactly what my clients do. Which is exactly what most people do.

The nervous system experiences a hard conversation as a threat. The brain moves toward certainty and away from ambiguity. Staying silent feels like resolution. Saying the true thing feels like risk. That is not a character flaw. It is a deeply human response to an evolutionarily ancient wiring system that has not caught up with the demands of organizational life.

Understanding that does not make the avoidance okay. But it makes it less shameful. And shame, ironically, is one of the things that makes it hardest to change.

What It Costs

Back to Marcus.

When we finally mapped out the seven months of not-having-the-conversation, what we found was remarkable. Twelve decisions that had been delayed or made suboptimally because the underlying misalignment was never addressed. Three team members who had started looking for other roles because they experienced the cross-functional friction as a leadership failure. One major project that came in six weeks late in part because two functions were pulling in subtly different directions that nobody had named.

None of this was visible in any single meeting. It was the accumulated cost of a conversation that never happened.

That is what conflict avoidance actually costs. Not a dramatic rupture. A slow, quiet tax on everything — on decision quality, on team health, on execution, on trust. It shows up later and it is almost impossible to trace back to the original moment of avoidance. Which is part of why it persists.

Building the Muscle

The good news is that the capacity for hard conversations is not a personality trait. It is a skill. And like any skill, it can be built deliberately.

Here is what I have learned works — both from research and from watching hundreds of leaders develop this capacity over time.

●Start smaller than you think you need to. Most people wait for a crisis to have a hard conversation, which means they are practicing under the worst possible conditions. Start with something lower stakes: a piece of feedback you have been sitting on, a misalignment you have been circling. The muscle you build there is the same muscle you will need for the bigger conversations.

●Separate the relationship from the conversation. One of the deepest fears underneath conflict avoidance is: if I say this, I will damage the relationship. But research on psychological safety consistently shows the opposite — people trust leaders more, not less, when those leaders are willing to have honest conversations. Avoidance does not protect relationships. It slowly hollows them out.

●Name what is happening in the room. One of the most powerful moves in a difficult conversation is simply to say what you are observing: "I notice we keep coming back to this without actually resolving it. I think there is something we are not saying." That sentence alone changes the container. It gives the other person permission to be honest too.

●Stay one more minute than is comfortable. Conflict avoidance is not just about not starting hard conversations. It is also about ending them too early — the moment it gets uncomfortable, the urge to wrap up and move on is overwhelming. Practice staying one more minute than you want to. That minute is often where the real conversation begins.

What Happened With Marcus

He had the conversation. Not because he stopped being afraid — he was still afraid. But because he finally decided that the cost of not having it was higher than the cost of having it.

It was uncomfortable. His peer was initially defensive. There was a moment about fifteen minutes in where Marcus told me he almost changed the subject.

He did not.

By the end of the conversation they had surfaced a fundamental misalignment that had been driving friction for months. They built a working agreement that held. The project that had been stalling started moving within two weeks.

Marcus told me afterward: "I spent seven months dreading something that took forty minutes."

That is almost always how it goes. The conversation we have been avoiding is almost never as catastrophic as the one we have been rehearsing in our heads. The silence, it turns out, is usually the most expensive option.

I work with leaders and teams on the dynamics that slow organizations down — including the conversations that are not happening. If this resonated, I would love to hear what it brought up for you.

Two types of decisions tend to look identical from the outside. Questions get asked. Information gets exchanged. A conclusion gets reached. But the intent behind them is different, and that difference shapes the outcome more than most people realize.

An evaluation is designed to understand. A filter is designed to sort. One creates space for nuance and signal that builds over time. The other answers a simpler question: does this fit what we need right now? Both are legitimate. Both are necessary. The problem is that under pressure, they tend to collapse into each other — and no one announces when it happens.

Consider a common scenario. A hiring team moves through a slate of candidates in a compressed window. By the midpoint, pattern recognition is doing most of the work. The questions are the same. The rubric is the same. But the attention is not. A candidate who might have stood out in a different context gets filtered through a version of the process that was never designed to surface what made them worth a second look. No one made a bad decision intentionally. The system just ran at a speed that made depth impossible.

As organizations scale, this becomes structural. More roles, more candidates, more competing priorities, less time. Research in organizational psychology consistently shows that in high-volume environments, people rely more heavily on pattern recognition. Familiar profiles. Initial impressions. Quick heuristics that stand in for deeper signal. This is not a character flaw. It is a rational response to overload. But it has consequences worth understanding.

When filtering happens in spaces that actually require evaluation, strong signal goes undetected. Not because it is not there — because the conditions for surfacing it were never created. Nuanced thinking gets compressed into a short exchange. Complex capability gets reduced to a recognizable profile. First impressions carry more weight than everything that comes after.

And there is a physiological dimension to this that rarely gets named. Speed feels decisive. The brain moves toward certainty and away from ambiguity. Filtering produces a clear output quickly, which registers as resolution. Evaluation requires sitting with uncertainty long enough for better signal to emerge, which the nervous system experiences as uncomfortable. So the pull toward filtering is not just organizational. It is human. Understanding that makes it easier to interrupt.

The same pattern shows up inside teams. Work moves fast. Priorities shift. Decisions get made on the fly. Speed is often exactly right. But when context is not fully shared before execution begins, the cost shows up later. Decisions get revisited. Work gets rescoped. People move quickly, but not quite together. Research on team effectiveness consistently finds that clarity and shared understanding predict performance better than speed alone, especially over time.

The cost is not just a missed hire or a delayed project. It is a compounding pattern of decisions made on thin data that no one connects back to the original moment. By the time the friction becomes visible, it is hard to trace it back to the filter that created it.

None of this is an argument for slowing everything down. It is an argument for being deliberate about which mode a decision actually calls for. In practice, that looks like a few specific things: creating enough space in a process for signal to build rather than just confirm, asking what information is still missing before concluding, and distinguishing between a decision that feels urgent and one that actually is. The leaders who do this well are not necessarily slower. They are clearer about when speed serves the outcome and when it compromises it.

When a decision carries real weight, the right question is not how fast it can be made. It is whether enough signal has actually been surfaced to make it hold. The cost of moving too fast on too little information is rarely visible in the moment. It shows up later as friction, rework, misalignment. And friction, compounded, is its own kind of slowness.

It isn't.

Diplomacy is a nervous system achievement.

I've spent years as a mediator, sitting in rooms with people in active conflict. Workplace disputes. Leadership ruptures. Teams that used to trust each other and stopped. What I learned inside those rooms, and later reinforced through Harvard Law's executive training in negotiation and mediation, is that the breakdown rarely happens because someone said the wrong thing.

It happens because someone felt something they couldn't regulate, and acted from that place before they had a choice.

Here's what the research confirms: when the nervous system perceives threat, and that includes social threat, the amygdala hijacks the prefrontal cortex. The part of the brain responsible for nuance, empathy, and long-term thinking goes offline. What's left is fast, reactive, and almost always costly.

The HeartMath Institute has been measuring this for decades. In a dysregulated state, IQ drops, creativity narrows, and the capacity to read a room accurately diminishes. You don't just feel reactive. You become less intelligent. Less perceptive. Less trustworthy to the people watching you.

This is why diplomacy can't be taught as a set of phrases or a conflict resolution framework alone. Those tools matter. But they're only accessible to a nervous system that is regulated enough to use them.

When you witness something that feels wrong at work, the body wants to tell someone. That's not weakness. That's not gossip waiting to happen. That's threat response doing exactly what evolution designed it to do: recruit allies, reduce uncertainty, restore a sense of safety.

The diplomat isn't the person who doesn't feel that pull.

The diplomat is the person who feels it fully and chooses differently.

I've seen this tested at its most extreme through my work with Braver Angels, the national organization bringing people across deep political and ideological divides into structured, humanizing dialogue. What that work teaches, over and over, is that staying in contact with someone whose worldview challenges yours is not a values exercise. It is a physiological one. Your body will try to exit. Cognitively, emotionally, physically. The practice is learning to notice that impulse without obeying it.

That gap, between the impulse and the response, is where real diplomatic capacity lives.

A few things that actually build it:

•Pause before you process out loud. The instinct to share what you witnessed is strong. Let it sit 24 hours before you decide what, if anything, to do with it.

•Name what's happening in your body, not just your mind. "I'm activated" is more useful information than "they were out of line." One you can regulate. One just fuels the story.

•Ask what outcome you actually want. Most reactive disclosures don't serve the goal. They serve the nervous system in the short term and damage trust in the long one.

•Learn to distinguish signal from noise. Not everything that feels wrong is wrong. A regulated nervous system can tell the difference. A dysregulated one cannot.

•Get comfortable with incompletion. Diplomatic people don't resolve every tension they notice. They hold it long enough to understand it before they move.

The leaders I've watched build the most durable trust across organizations aren't the ones who never feel the pull toward reactivity. They're the ones who've done enough interior work to have a real choice in the moment.

That is trainable. It is not a personality type.

And it is, without question, one of the most consequential capabilities in organizational life.

I worked with a leader everyone trusted. If something was unclear, she clarified it. If a decision stalled, she moved it forward. If tension showed up, she absorbed it and kept things on track. On paper, she looked like a high performer. In reality, she was holding together a system that wasn’t clear on ownership, priorities, or how decisions were supposed to move.

Because she was good at it, no one questioned it.

That’s the pattern I keep seeing.

What gets labeled as burnout is often something else: sustained over-responsibility in an environment that hasn’t defined how work actually flows. You can usually spot it early, not through performance reviews but through behavior. The same people get pulled into everything. They become the default decision-maker even when it’s not their role. They’re the ones people go to when something feels off, unclear, or stuck.

They don’t escalate. They absorb. They don’t wait. They figure it out.

For a while, it works. Projects move. Teams feel supported. Leaders feel reassured. But underneath that, the system starts reorganizing around the person instead of fixing itself.

Research on role clarity and job design has shown that when ownership is ambiguous and expectations are diffuse, high performers don’t slow down. They stretch. They fill gaps. Over time, that behavior becomes normalized, and the organization begins to depend on it.

That’s where the risk builds.

•Decisions start to bottleneck, not because people aren’t capable, but because others defer

•Standards become inconsistent depending on how involved that person is

•Accountability blurs because ownership was never clear to begin with

From the outside, it still looks like a strong team. From the inside, it feels heavy.

Most organizations misread the signal. They see a high performer under pressure and respond with more support, more resources, sometimes even promotion. But the issue isn’t capacity. It’s design.

There’s another layer that rarely gets named. Many of these high performers aren’t just executing and deciding. They’re regulating the environment. They’re diffusing tension in meetings, reading what’s not being said, adjusting how they communicate to keep things moving. That emotional labor compounds the load.

So you end up with one person carrying execution, decision-making, and relational stability.

That’s not sustainable.

If you want to shift this, the move isn’t to protect your high performers. It’s to remove the conditions that require compensation in the first place. That means getting precise about who owns which decisions, what “good” looks like, how quickly decisions should move, and what happens when something is unclear. It also means leaders modeling this in real time, especially under pressure, because that’s when patterns lock in.

If your best people are carrying the system, the system isn’t working. And at some point, they stop carrying it.