Avinash Vora

Two Incompatible Things

Mon, 09 Mar 2026 00:00:00 GMT

The most useful definition of stress I've encountered is also the simplest: stress is the internal state of wanting two incompatible things at the same time.

Not pressure from outside. Not too much work. Not uncertainty. The structural experience of holding two desires that can't coexist—and refusing, or failing, to choose between them.

Want to build something new but also maintain everything you already have. Want more autonomy for the people around you but also want to stay closely involved in every decision. Want to say no to commitments but also want to be someone who shows up for everything. Each desire, on its own, is entirely reasonable. The stress doesn't come from either one. It comes from the contradiction.

Pressure vs. Contradiction

This distinction matters because the two types of stress require completely different responses. Pressure—too much work, a tight deadline, a high-stakes presentation—responds to the usual tools. Better planning, delegation, rest. You reduce the load and the stress reduces.

Contradiction doesn't respond to any of that. You can optimize your calendar, improve your systems, take a vacation, and come back to exactly the same tension, because the source isn't in your workload. It's in you. Two things you want that can't both be true, and no amount of efficiency will resolve that.

Kurt Lewin described this as approach-avoidance conflict: when you're drawn toward something that also carries a cost you want to avoid, the result isn't a decision. It's oscillation. The closer you get to choosing, the more the cost becomes visible, so you pull back. Then the desire reasserts itself, and you move forward again.

That oscillation is what "stuck" actually feels like. Not lacking options, but trapped between two options that each require giving up something real.

I see this constantly in the leadership teams I work with. The founder who wants the company to grow but also wants it to feel the way it did when it was twelve people, or the leader who wants honest feedback but also wants to be right. These aren't time management problems. They're structural contradictions, and they produce a kind of grinding, ambient stress that's disproportionate to the actual workload, because the source isn't the work.

Why Balance Doesn't Work

The instinct when facing a contradiction is to try to balance the competing desires. Have both, but in moderation.

Sometimes this works. There are genuine tensions that can be held productively—you can be both strategic and operational, both empathetic and direct. Not every conflict is binary.

But some are. And the ones that produce the most stress are usually the ones where balance is a fiction. You can't meaningfully build team autonomy while staying involved in every important decision. You can't genuinely protect your time while saying yes to everything that feels important. Those things are structurally opposed. "Balancing" them means doing both badly and feeling the friction constantly.

The honest question in these moments isn't, "how do I balance these?" It's, "which one am I going to choose, and what am I willing to lose?"

Nobody wants to answer that question. Because choosing means loss. You pick one thing and you give up the other—not hypothetically, but actually. The thing you give up was something you genuinely wanted. Neither answer is painless.

The Relief

What I've noticed, though, is that the stress drops almost immediately once the choice is made. Not because the situation gets easier, but because the structural contradiction resolves. You stop pulling in two directions at once.

The discomfort doesn't disappear entirely. Choosing to let go of something you wanted is uncomfortable, and it should be. But the specific kind of stress that comes from holding two incompatible things simultaneously—the grinding, ambient, disproportionate tension—that resolves. And in its place you get capacity back. The energy that was being consumed by the contradiction becomes available for the thing you actually chose.

The Unnamed Ones

Most of these contradictions are unnamed. They operate below the surface as a persistent tension that doesn't resolve. You feel stressed, but when you list the reasons, none of them fully explain the intensity.

The diagnostic is simple: when the stress feels disproportionate to the circumstances, ask whether you're trying to hold two things that can't coexist. It's a different question from "what's stressing me out?"—which produces a list of external pressures. The better question is: what are the two things I want that might be pulling in opposite directions?

The answer is usually immediate once you frame it that way. And the relief doesn't require solving anything. It starts with naming the contradiction.

Still Here

Mon, 02 Mar 2026 00:00:00 GMT

I've been listening to Beethoven's Ninth Symphony.

Beethoven went deaf a decade before he wrote it. The symphony opens in something close to chaos—fragmented, uncertain. I hear him searching for a key he can't quite find. It stays there for a long time. Three full movements of struggle and tension before the choral finale arrives with the Ode to Joy.

The reason that ending has moved people for two centuries is that it doesn't skip the darkness, it passes through it. The hope at the end is credible because the suffering was real.

I'm writing this from Dubai. It's been two days since the conflict started. My family is safe. We have power, water, internet, food—everything we had on Friday. The UAE's fantastic air defense has been intercepting all of the incoming missiles and drones, and the people running those systems kept millions of us safe.

I'm grateful for all of that in a way I couldn't have understood a week ago. The past two days have had a texture I don't have a reference for. Explosions, then silence. Shelter alerts on your phone in the middle of the night waking you up. Questions you don't have good answers to. You check the news and Reddit, then close it, then open it again. There's a hum of adrenaline underneath everything even when it's quiet outside.

But I don't want to write a post about how we're fine. A lot of people aren't. People lost their lives here, and many more across the region. Families are living through something I can't begin to understand. People in have been under threat for decades. Hundreds of thousands of travelers are stranded, cut off from the people they were trying to get home to. There are people in this city who have family in places where the phones have stopped working. "We're okay" is true for my household. I'm aware of how much that leaves out, and I hold all of them heavily in my heart and thoughts.

Over the past 48 hours, people I haven't talked to in years have reached out. Old colleagues, clients, vendors, family and friends. From India, the US, the UK, Singapore, Germany, Australia, Canada, and of course all across the region. Not with anything particular to say—just to ask if we were okay.

Nobody's message was polished. Nobody was performing concern. They just asked: are you safe? Is your family okay? Do you need anything? When things get real, people stop curating. They just reach out. The fact that people I'd lost touch with thought of us and paused whatever was going on in their own lives to send a message—that's the thing I'll carry from this.

I have enough normalcy right now to open a laptop and write this. A week ago I wouldn't have noticed that as something to be grateful for.

I don't have analysis to offer about what's happening. I won't pretend that my understanding of the geopolitics or where this goes is important. What I see is what's in front of me: a city still functioning because people built defense systems that work and operated them under real pressure, while fasting, with their loved ones in danger. I have experienced a fragment of what an innocent civilian living in a warn-torn country lives through every day.

Beethoven wrote the Ninth while Europe was coming apart—revolutions, wars, authoritarian crackdowns. His own life was falling apart too. He was isolated, in pain, losing the one sense his life depended on. And from inside all of that, he wrote music that insists human connection and joy are still worth reaching for—not by pretending the darkness isn't there, but by moving straight through it.

I don't know what the next days or weeks look like. But people I hadn't spoken to in years thought of my family. The systems held. My family is safe. And across this region, people are doing what people always do when things get hard—they reach for each other.

If you've reached out over the past two days—thank you. Whether I was able to express my gratitude appropriately or not, it really mattered and meant something to me.

If you're somewhere going through something harder than what I'm describing—I'm thinking of you. If I can help, please reach out.

The Long Game of Character

Tue, 24 Feb 2026 00:00:00 GMT

Character isn't a moral ideal. It's a filter. And over enough time, it's the most powerful one you have.

Your behavior—not your stated values, your actual behavior—sends a signal. Every kept commitment, every uncomfortable truth, every admitted mistake becomes part of that signal. So does every shortcut, every hedged truth, every moment where self-protection wins over transparency. The people around you read this signal, mostly unconsciously, and adjust accordingly.

Over years, the signal acts as a filter. People who match it stay and deepen the relationship. People who don't match it, gradually drift away. The result is an ecosystem—a team, a network, a set of relationships—that reflects the character you've demonstrated, which isn't always the character you believe you have.

Cooperation and its Opposite

Robert Axelrod's research on cooperation makes this concrete. He ran tournaments where different strategies competed in repeated interactions—computer programs playing the prisoner's dilemma thousands of times. The strategy that won over the long term wasn't the cleverest or the most aggressive. It was among the simplest: cooperate by default, reciprocate what you receive, forgive occasional defection, be transparent about what you're doing.

The sophisticated strategies—the ones that tried to exploit, deceive, or game the system—won individual rounds. But over many interactions, they created environments where everyone was playing defense. Trust collapsed. Every interaction became a calculation. The cooperators, meanwhile, found each other and built something that compounded.

This maps cleanly onto what I observe in organizations. The environments where problems surface early, where people push back on each other's ideas without it becoming personal, where the real conversation happens in the room rather than after it—these aren't the result of a culture initiative or a set of values on a wall. They're the accumulated effect of a leader who has been direct, honest, and transparent, consistently, including when it cost them something. The people who stayed were the ones who matched that signal.

The environments full of politics and impression management, where the meetings are smooth but the real conversations happen in the hallway? Same mechanism, different signal.

The Time Horizon Problem

The difficulty with character-as-strategy is that it operates on a time horizon most people don't plan for.

Cutting a corner feels costless in the moment. Managing a narrative feels smart. Hedging instead of telling the truth feels prudent. And in any single interaction, it often is. The cost isn't in the moment. It's in what the pattern creates over years.

This is the same challenge as any compounding system. Small inputs produce invisible effects in the short term and dramatic ones over time. The person who exercises consistently for a decade doesn't see results on any given day. But the long-term outcome is unmistakable.

Character compounds the same way. Keeping commitments, telling uncomfortable truths, and admitting mistakes doesn't produce visible benefit in any given interaction. Over years, it builds something—a reputation, a team, a set of relationships—that couldn't have been constructed any other way. And the inverse compounds just as reliably.

The Diagnostic

There's an uncomfortable diagnostic embedded in this. Look at the people around you: your team, your close relationships, the partnerships that have lasted. What pattern do you see?

If you're surrounded by people who surface problems early, tell you what you need to hear, and operate with transparency—that's the ecosystem your signal created. If you're surrounded by people who tell you what you want to hear, manage impressions carefully, and keep the real conversations off the record—that's a different signal. It came from somewhere.

The question isn't whether you have good values. Most people do. The question is whether your behavior, in the small moments when no one is checking, matches the signal you think you're sending.

Forgive Yourself For Not Knowing

Wed, 18 Feb 2026 00:00:00 GMT

We evaluate our past decisions under conditions that would be thrown out of any fair court.

The evidence: everything that happened after the decision. The hire didn't work out. The strategy was wrong. The conversation you avoided festered. In retrospect, the warning signs were clear. The right move is obvious.

But the evidence was generated by the consequences of the decision itself—consequences that, by definition, your past self didn't have access to when they acted. You hired the wrong person? You know that now because you saw what happened. The version of you that made the hire was working with incomplete information, which is what every hire actually is. You spent a year on the wrong strategy? You know it was wrong because you ran the experiment. The version of you that chose it didn't have the data yet.

The defendant is your past self. The judge is your current self, armed with all the information the defendant never had. It's a rigged trial, and we run it on ourselves constantly.

Drag, Not Wisdom

Most people carry a portfolio of these. Past decisions that look obvious in hindsight, generating a persistent guilt that masquerades as conscientiousness.

The problem is that this weight doesn't function the way we think it does. We imagine it makes us wiser—more careful, more attuned, better at pattern recognition. Sometimes that's true. But more often, what I observe is something that looks like learning but functions as drag.

Making a bad call on a hire makes you overly cautious in all hiring, not just analogous situations. Trusting the wrong person makes you slower to trust anyone. Making a bold move that didn't work makes you allergic to boldness itself, even when boldness is exactly what's called for.

The guilt doesn't sharpen judgment. It blunts it. It introduces hesitation into decisions that don't deserve it—not because the current situation warrants doubt, but because a past situation taught you that your own judgment can't be fully trusted.

That's not wisdom. That's an old wound leaking into the present.

What Self-forgiveness Actually Is

Kristin Neff's research on self-compassion reframes this usefully. Self-compassion isn't self-indulgence. Neff defines it through three components: self-kindness rather than self-judgment, recognition of common humanity rather than isolation, and mindfulness rather than over-identification with painful thoughts.

The research is consistent and counterintuitive. People with higher self-compassion don't have lower standards. They tend to have higher personal standards and greater motivation to improve. What they have less of is rumination. They spend less cognitive energy replaying their failures and more energy learning from them and moving forward.

This maps onto something I notice in practice. The people who've found a way to forgive their past decisions aren't the ones with lower standards. They're the ones with more available capacity. They're not spending energy relitigating old calls, so they have more to invest in current ones.

Self-forgiveness isn't softness. It's the removal of a structural impediment.

Lessons vs. Weight

The practice is distinguishing between the two.

The lessons—what to watch for next time, what patterns to recognize earlier, what instincts to trust—those stay. Those are the return on the painful experience. They earned their place.

The weight—the guilt, the replaying, the "I should have known"—that's what can be set down. Not because it doesn't matter, but because it has stopped producing anything useful. It's taking up space you need for the decisions in front of you.

Forgive yourself for not knowing what only time could teach you. Embedded in every regret is the belief that you should have known better. Sometimes that's true—sometimes you ignored clear evidence, and honest accountability for those moments matters. But more often, the knowledge that would have changed the decision simply wasn't available yet. You hadn't lived through the experience that would generate it. You were an earlier version of yourself, operating with an earlier version of your understanding.

Expecting that person to have made a better call is expecting them to have been someone they weren't yet.

Borrowing Knowledge

Wed, 11 Feb 2026 00:00:00 GMT

I noticed something recently that's been bothering me. I was trying to explain a concept I use all the time—something I'd reference fluently in conversation without a second thought—and when I stripped out the jargon, I couldn't quite get there. I could use the word, I could deploy it in a sentence that sounded right. But when I tried to describe the actual mechanism underneath—what causes what, how it works, why it matters—the explanation fell apart.

The vocabulary was smooth but the understanding was full of holes I hadn't noticed.

The Name and the Thing

Richard Feynman—the physicist, not exactly a business guru—made a distinction I keep coming back to. He argued that knowing the name of something and understanding it are entirely different acts. You can learn the word "gravity" without having any real sense of what gravity does. You can be fluent in a vocabulary without grasping a single mechanism underneath it.

His test was characteristically simple: try to explain the thing to a child. Not dumbed-down—translated and concrete. If you can describe what's actually happening—what causes what, what changes when conditions shift, why it matters—in language a twelve-year-old could follow, you probably understand it. If you can't get there without reaching for the technical term, that's not a vocabulary problem, it's a comprehension problem.

There's an image from the Feynman method that stuck with me: we tend to think our knowledge is a smooth, paved highway—a continuous understanding with no breaks. But usually it's more like a series of islands with rickety little bridges between them. Each piece of jargon is a sign posted on an island. It doesn't tell you whether there's a solid bridge to the next concept or just open water you've been stepping over without noticing.

The place where the explanation breaks down—where you reach for the technical term because you can't say it plainly—is the rickety bridge and where the understanding hasn't been built yet.

Borrowed Versus Owned

There's a useful distinction here between knowledge that's borrowed and knowledge that's owned. Borrowed knowledge is language you can deploy without a mental model behind it. You can use the word in a sentence, you can nod along when someone else uses it. But if someone pressed you on the mechanism, you'd stall. Owned knowledge is different—you've built it from the ground up. You can explain it, apply it in new situations, and recognize when it doesn't hold.

Most of us are operating on more borrowed knowledge than we realize. The frameworks we've absorbed, the terminology we've picked up, the concepts we reference because we've heard them referenced—these give us fluency. Fluency is genuinely useful. But fluency isn't understanding, and the gap between the two is easy to miss because the fluency feels so much like comprehension.

I've caught this in myself, sometimes. It happens with concepts I've used for years—confidently, in conversations where no one pushed back—that I couldn't explain from first principles if someone asked me to slow down and walk through the actual mechanism. The labels were doing the work. My understanding was thinner than my vocabulary suggested.

Feynman put it bluntly: you cannot fake simplicity. Complexity is a place to hide, but simplicity is naked.

Why the Gaps Hide

The part of this I find most interesting is why these gaps persist—sometimes for years—without being noticed.

Most environments reward fluency over understanding. The person who speaks confidently in the right vocabulary sounds competent. The person who pauses and says "I'm not sure I actually understand how this works" sounds like they're behind. So the incentive is to perform understanding—to sound like you know—rather than risk the vulnerability of admitting you don't.

In a business context, Edmondson's research on psychological safety is relevant here, though in a slightly different way than it's usually applied. The safety question isn't just whether a team can disagree openly. It's whether people can admit, to themselves and to each other, that they don't fully understand something they've been talking about fluently. That's a different kind of vulnerability. It's not "I disagree with you." It's "I've been nodding along, but I don't actually get this."

Feynman warned that the first principle is not to fool yourself, and that you're the easiest person to fool. When you add the social dynamics of a team or a professional environment—where fluency is rewarded and confusion is stigmatized—the fooling compounds. Everyone uses the same words. Everyone assumes everyone else understands. The shared vocabulary becomes a shared blind spot.

The Blank Page

Feynman's method for breaking through this is almost absurdly simple. Take a blank page. Write one concept at the top—something specific, not an entire field. Then try to explain it in plain language, as if to a sixth grader. No technical terms, no jargon; just: what's actually happening here? What causes what? Why?

Wherever the explanation breaks down—wherever you feel the pull to reach for the technical term because you can't say it simply—mark that spot. That's the gap, and that's where you thought you understood but didn't.

Then go back to the source material with those specific gaps as questions. Not rereading everything from the beginning—hunting for the missing piece. Fill the gap, return to the explanation, and try again until the whole thing flows as a plain-language narrative that a kid could follow.

It sounds almost too basic to be useful. But the power is in the honesty it forces. You can't fake the plain-language explanation. Either you can describe the mechanism concretely or you can't. The jargon has nowhere to hide.

What You Actually Know

I've been running this on myself. Picking concepts I use regularly and putting them through the blank-page test. The results have been humbling. Some things I thought I understood well, I did. But others—things I've been fluent in for a long time—turned out to have significant gaps I'd been stepping over without realizing.

The honest version of what happened is that the labels were giving me a sense of completion that the understanding hadn't earned. The word was there, so my brain marked it as known. The blank-page test forced me to look behind the word, and behind it was less than I expected.

I think this matters beyond the personal level too. When a team shares vocabulary without shared understanding, they can talk past each other for a long time without noticing. The language creates the appearance of alignment. The gaps only surface under pressure—when a decision comes along that doesn't fit the familiar vocabulary, and each person fills in the mechanism differently.

But the starting point is individual. It's sitting with the uncomfortable question: of all the concepts I use fluently, how many could I actually explain—simply, concretely, from the ground up—without the jargon doing the work for me?

The Focus You Fear

Tue, 03 Feb 2026 00:00:00 GMT

I've had a running list for most of the past year—things I want to get better at, projects I want to finish, skills I want to develop. At various points there have been four or five items on it, all getting some portion of my week. I'd rotate between them, make a little progress on each, and feel like I was being productive.

But when I look back honestly at what actually moved substantially during that time, the answer is: not much. Everything inched forward. Nothing transformed. I was busy with all of it and I couldn't point to any one thing where I'd gone deep enough for the work to become genuinely good.

Then I think about the stretches where I did produce something I was proud of, and they all have the same shape. I'd gotten slightly obsessed with one thing. Not in a dramatic way—I just stopped splitting my attention. That one thing became what I thought about when I wasn't working on it. I'd notice relevant ideas in unrelated places. Connections started forming on their own. The work got richer in a way that doesn't happen when you're context-switching between four different goals.

What Depth Actually Feels Like

There's a difference between working on something and being in something, and I think the difference is time. It's not necessarily clock time, it's accumulated attention. When you've been sitting with one problem or one craft for weeks and months, your mind builds a kind of internal world around it. You hold more of it in your head at once. You start seeing patterns that aren't visible in the first few sessions.

I'd compare it to the difference between visiting a city for a weekend and living there for a year. The weekend gives you landmarks and a rough sense of the place. The year gives you the backstreets, the rhythms, the things you'd never notice passing through. You can't shortcut that. It takes sustained presence.

Research on deliberate practice points at something similar—concentrated hours in a single domain predict expert performance more reliably than raw talent or total hours spread across many domains. The depth itself is doing the work. It's not just a nicer way of learning. It's a different kind of learning.

When I split ninety days across four goals, I get about twenty days of depth on each. That's enough to feel like progress but not enough for the interesting part to start. I stay in the shallows of every goal, where the effort-to-insight ratio is worst.

Busyness as its Own Kind of Avoidance

The part I've been slower to admit is that staying spread thin can itself be a way of hiding.

It doesn't feel like hiding. My schedule is full. I'm making progress. I have things to show for my time. But if the net effect is that I never go deep enough on the thing that actually matters—the one I care about most, the one where real failure would sting—then all that productivity is serving a protective function. I'm staying busy enough to avoid the discomfort of committing.

Because that's what real commitment costs. Choosing one thing means letting the others sit. It means I can't tell the story of being someone who's "working on everything." And the scariest part: it means that if the one thing doesn't work, I don't get to blame the lack of time or the competing priorities. I gave it my attention and it wasn't enough, or I wasn't good enough. That's a much harder thing to sit with than a crowded to-do list.

I think this is what's actually going on when people procrastinate, most of the time. It's not laziness—it's the fear of what it would mean to really try. Keeping many things alive keeps the question of "am I good enough at this one thing" safely in the realm of theory. You never have to answer it because you never created the conditions where you could.

Starting is Mechanical, Not Motivational

When I catch myself in this pattern, the thing that actually helps isn't thinking about it differently. It's doing something absurdly small.

I ask myself what matters most right now—just one thing—and then I ask what the very next physical action is. Not "work on the project." That's too abstract to actually start. The physical action: open the file. Write a single bad sentence. Send the one email I've been putting off. Something so trivially small that it would be embarrassing to not do it.

Most of the friction I experience isn't about not knowing what matters. It's the gap between knowing and doing. Shrinking that gap to one tiny concrete step is usually enough to get me moving. And once I'm moving on one thing—actually in it, not just thinking about it—the pull toward the other things quiets down.

The Trade-off Nobody Wants to Make

The part of this that's genuinely hard is the trade-off. Going deep on one thing for three to six months means other things stagnate. Not forever, but noticeably. You don't get to maintain the appearance of balanced progress across every area of your life. Something has to give, and it has to be visible.

That feels like loss. And it is loss, in a sense. But the alternative has its own cost that's easier to ignore: you never reach the depth where breakthroughs live. You stay at the surface of every goal, working hard and wondering why nothing feels like it's really moving.

The people I've watched do work I genuinely admire tend to cycle through this. A few months of intense focus on one thing, then a shift. Not balance as most people think of it—more like a rotation of deliberate imbalance. Each cycle goes deep enough for the compounding to actually work, and then they move on to the next thing that deserves that kind of attention.

I'm trying to get better at this. It's harder than it sounds, because the pull toward spreading thin is constant and it always feels reasonable. But I keep coming back to the same uncomfortable question: what would happen if I actually stopped hedging and gave one thing everything I had for six months?

The honest answer is that I'd find out whether I'm good enough. And I think that's exactly why it's so hard to do.

The Engine That Runs You

Tue, 27 Jan 2026 00:00:00 GMT

A client told me last month that she'd hit every target her board set for the year. Revenue up, team retention strong, product roadmap on track. By any external measure, it was her best year. She described it as the most exhausting, hollow twelve months of her career.

"I spent the whole year performing," she said. "Not leading. Performing. Every board meeting was about proving I belonged. Every decision was filtered through how it would look. I hit the numbers, but I have no idea what I actually think about where this company should go."

She wasn't burned out from the work. She was burned out from the engine she was running it on.

The Fuel Matters More Than the Speed

I've started paying closer attention to this—not whether someone is motivated, but what they're motivated by. The distinction changes everything.

Fear works. If you're afraid of getting fired, you'll work hard. If you're afraid of looking incompetent, you'll prepare thoroughly. But fear-driven work is expensive. It raises cortisol, narrows thinking, and makes you defensive in exactly the moments that require openness. You can sprint on fear, but you can't build on it.

Rewards work too. Bonuses, promotions, recognition—these produce effort. But there's a well-documented pattern: once you start doing something for a reward, the reward becomes the reason. Remove it, and the motivation collapses. Worse, research on contingent rewards shows they can actually erode interest in work people previously found intrinsically meaningful. The reward replaces the reason.

Then there's approval. This one is subtle because it often looks like high performance. The leader who's always prepared, always responsive, always exceeding expectations—sometimes that's excellence. Sometimes it's someone who's outsourced their sense of worth to their audience. From the outside, it looks like success. From the inside, it feels like anxiety.

These engines all produce motion. But they share a structural problem: the source of fuel is external. Someone else controls the supply. When the threat recedes, the reward disappears, or the audience changes their mind, the engine stalls.

The Shift That Sustains

The leaders I work with who sustain through difficulty—real difficulty, not the performative kind—have a different relationship with their work. They've made a shift I find hard to describe precisely, but it looks something like this:

They stopped optimizing for outcomes and started paying attention to the process. Not as a "journey before destination" platitude—more structurally. They found the zone where the work itself is challenging enough to be engaging, and they oriented around getting better at it.

I described it to a COO I work with as the difference between "winning the quarter" and "becoming the kind of operator who can navigate anything." Same work, different orientation. One is fragile—you win or you don't, and the satisfaction is brief either way. The other compounds.

The ones who go further connect the work to something beyond themselves. They can name who benefits. Not in a mission-statement way, but in a specific, concrete way. "My team has four people in their first management role. If I do this well, they'll be better leaders for the rest of their careers." "The customers who use this product are small business owners who can't afford the enterprise alternative."

That kind of clarity doesn't make the work easier. It makes it more durable. Research on purpose and persistence consistently shows that people who connect their work to a contribution beyond themselves sustain effort longer, procrastinate less, and report higher well-being and even reduced mortality—even when the work is hard.

The Diagnostic

There's a question I've started using with clients that sounds simple but tends to land hard:

What's actually driving you right now?

Not the answer you'd give in a performance review. The real one. Sit with it for a moment.

Are you avoiding a consequence? (Fear)
Are you chasing a reward or a milestone? (Incentive)
Are you performing for someone's approval or validation? (Audience)
Are you trying to win, prove something, or reach a finish line? (Achievement)
Are you engaged in getting better at something that matters to you? (Growth)
Do you know who benefits from your work, and does that sustain you? (Purpose)

Most people, when they're honest, find they're running on a mix. That's normal. The question isn't whether you ever operate from fear or approval—everyone does. The question is which engine is primary. Which one do you default to when things get hard?

The default engine determines the experience. Two people can do identical work, produce identical results, and have completely different internal lives based on what's driving them. One is anxious and brittle. The other is challenged but grounded. Same output. Different fuel.

Moving the Default

The useful insight, I think, is that this isn't fixed. You can shift what drives you—not all at once, but incrementally.

If you're running primarily on fear, the move isn't to eliminate fear. It's to find one thing about the work that you're genuinely curious about or interested in. Add a small intrinsic element alongside the external pressure. Give yourself something to move toward, not just away from.

If you're running on approval, the shift is noticing when you're filtering decisions through "how will this look?" and asking instead "what do I actually think is right here?" Not always. Just sometimes. Enough to start rebuilding an internal standard that doesn't depend on the audience.

If you're running on achievement—hitting targets, winning, proving—the reframe is from "did I win?" to "did I grow?" Measuring success by what you learned and how you improved, not just whether you got the result.

These are small moves. But they shift the engine. And the engine determines everything downstream—how you handle failure, how you treat people when you're under pressure, whether the work feels sustainable or slowly corrosive.

The Real Question

My client who hit all her targets? She's rethinking what she's optimizing for this year. Not the goals themselves—those are still ambitious. But the relationship she has with the work. She wants to lead from something more durable than the need to prove she belongs.

That's not a soft ambition. It's one of the hardest shifts a leader can make. Moving from an engine that's worked—that's produced real results—to one that might sustain her for the next decade without the brittleness.

The question I'd leave you with is the same one I keep asking myself: what are you actually running on? And is that engine taking you somewhere you want to go, or just somewhere fast?

The Reputation You Have With Yourself

Mon, 19 Jan 2026 00:00:00 GMT

A CEO I work with second-guessed himself in front of his leadership team last month.

He'd made a call about resource allocation. Reasonable decision, defensible logic. Then, ten minutes later—with no new information—he started walking it back. "Actually, let me think about this more." The team exchanged glances. Then, sensing the instability he'd created, he overcorrected. Restated the original decision with a certainty that rang false. Convinced no one.

The team felt both versions as instability.

What struck me wasn't the wrong call. CEOs make wrong calls constantly—that's not what erodes trust. It was where the wobble came from. Not the complexity of the decision. Something underneath.

The Internal Reputation

I've started thinking about self-esteem differently in that it is the reputation you have with yourself. Not confidence as a personality trait or positive self-talk, but something more structural.

Every decision you make is a data point your future self observes. Did you keep the commitment you made this morning? Did you tell the truth when it was easier to hedge? Did you follow through on what you said you'd do?

When your actions align with your own code, you build self-trust. When they don't, you erode it—even if no one else sees.

The leaders I work with who hold a room well, who sit with disagreement without becoming defensive, who make decisions cleanly—they're not necessarily smarter. They've built an internal track record they can trust. When they say, "I think we should do this," they believe themselves.

The ones who wobble? Often it's not that they lack information or skill. It's that they've accumulated enough small violations—broken commitments, avoided truths, unfollowed-through intentions—that they don't fully trust their own judgment anymore.

And that distrust leaks.

What It Looks Like

Leaders with eroded internal reputation show specific patterns:

Public second-guessing. Not the healthy "let me reconsider"—but anxious revisiting that signals the leader doesn't trust their own thinking.
Overcorrection into false certainty. When they sense they've created instability, they swing to performed confidence. Teams aren't fooled.
Avoiding difficult conversations. Not because they lack skill, but because they don't trust themselves to handle what might surface.
Excessive validation-seeking. Checking with too many people before acting. This isn't thoroughness—it's outsourcing confidence.

Research on leader behavioral integrity shows that alignment between words and actions is foundational to how teams trust leaders. But it has an internal precursor: whether the leader trusts themselves. Teams feel the difference between a leader who is genuinely open to being wrong and one who doesn't trust their own thinking.

How It's Built

The fix isn't affirmations or confidence workshops. It's keeping small commitments to yourself. The workout you said you'd do, the conversation you've been avoiding, or just simply the thing you promised yourself last week.

Small acts of integrity compound into a self you can trust. Small violations—the workout skipped, the conversation pushed, the intention abandoned—erode that foundation in ways that don't announce themselves until you need to draw on it.

The compounding works in both directions.

This isn't about perfectionism. Perfectionism is a defense mechanism—it delays action because you don't trust yourself to recover from a wrong move. This is simpler: noticing the commitments you make to yourself and whether you keep them.

The Foundation

The confidence you're looking for—the kind that lets you hold a room, make decisions cleanly, sit with disagreement—isn't something to acquire from outside. It's something you've been building or eroding all along, in the small moments no one else sees.

What would change in how you show up if you spent six months keeping every commitment you make to yourself? Even the ones no one witnesses?

That's the foundation. Leadership presence is built on top of it.

Present In The Room

Tue, 13 Jan 2026 00:00:00 GMT

There's a line of thinking I keep coming back to: the idea that time isn't wasted by what you're doing, but by whether you're actually there for it.

You can spend an hour doing something meaningful—important work, a real conversation, time with someone you love—and still have wasted that hour. Not because the activity was wrong, but because you weren't present for it. Your body was there, but your mind was elsewhere. The hour passed, and you weren't really in it.

This is different from the obvious ways we waste time: scrolling, procrastinating, or avoiding hard things. Those are visible, and we beat ourselves up about them. But there's a subtler drain that's harder to see which is all the hours we're technically present but actually absent. We're at dinner, but mentally replaying a conversation from earlier. Or in a meeting, but three meetings ahead in our minds. With our kids, but composing an email we'll send later.

The moment appears, it passes. We weren't there for it.

The Disappearing Frame

Imagine life as a series of frames, each appearing and vanishing instantly.

If your attention is on the current frame—if you're actually there for it—then you experienced that moment. You were alive to it. But if your mind was elsewhere—stuck on a past frame, anxious about a future one, running some internal simulation—then you missed it. The frame passed and you weren't watching.

This isn't about productivity or optimization. It's closer to a question about being alive. How many of the moments you're given do you actually experience? How many pass while you're mentally somewhere else?

I catch myself doing this. In conversations, I've not listened—I'm preparing my response. In meetings, I've not been present—I'm thinking about the next thing, or the last thing, or something unrelated entirely. I'm attending my own life without being present for it.

The math is uncomfortable. If I spend even half my waking hours with my mind somewhere other than where my body is, I'm not living half my life. I'm just persisting through it, surviving the moments rather than experiencing them.

Why This Is Hard

The mind's default mode is absence. Left to itself, it drifts to the past (regret, rumination, replaying) or the future (anxiety, planning, rehearsing). It runs simulations. It composes responses. It worries. It rarely just stays here, now.

I wouldn't say this is a flaw, exactly. The ability to mentally time-travel is part of what makes us human. We can learn from the past and prepare for the future in ways other animals can't. But the cost is that we're rarely where we actually are. The present moment—the only one that's real—becomes just a waystation between mental destinations.

I notice this most in contexts that should demand presence. Moments that matter, passing while I'm elsewhere. There's research on this. Studies on mind-wandering find that people's minds are not on what they're doing about 47% of the time. And the finding that keeps surfacing: mind-wandering correlates with unhappiness. Not because daydreaming is bad, but because not being where you are has a cost.

Attendance Versus Presence

Attendance is showing up. Being in the room, having the meeting on your calendar and your body in the chair. Presence is actually being there for it, with your attention on what's happening. Mind and body in the same place.

Most of life, I think, is attended rather than experienced. We show up for the hours we're given without really being there for them. The moment happens, we're somewhere else, it's gone.

This shows up in my facilitation work with leadership teams. I'll see or hear about meetings where everyone is technically present but attention is fragmented, or people waiting for their agenda item, mentally running their own department, rehearsing what they'll say when it's their turn. The conversation becomes a series of parallel monologues. People talk past each other because no one is actually listening—they're just waiting to speak.

Google's research on team effectiveness found that the highest-performing teams had roughly equal conversational turn-taking. MIT's work on collective intelligence found similar patterns—high-performing groups were distinguished by social sensitivity and responsiveness. But both of these require actual presence. Listening that's real listening, not just silence while you load your response.

The leadership team context matters to me professionally. But I don't think this is fundamentally a work problem. It's a human problem. The gap between attendance and presence runs through everything.

No Clean Answer

I don't have a fix for this.

I've tried various things. Meditation helps, sometimes. So does the simple act of noticing—catching myself when my mind has drifted and gently bringing it back. There's a question I ask at the start of important sessions: "What would need to be true for you to be fully here for the next few hours?" Sometimes just naming the distractions creates a little more space. Morning pages have probably been the most recent addition to the toolbox that have made a significant difference here.

But mostly, I just keep losing presence and finding it again. It's not a skill I've mastered. It's more like a practice I keep failing at, noticing the failure, and returning to. I think there is value in even noticing this: I can say for certain that I spent years wandering through work and life not realizing this. How many important moments or conversations were you a part of where the memories are fleeting?

What I'm more confident about is that this matters. Not in a productivity sense—though there are productivity implications—but in a deeper sense. The question of whether you're actually present for the life you're living feels like one of the important questions.

Each moment appears and vanishes. If you're not there for it, you missed it. Not metaphorically—literally. That moment is gone and you weren't in it.

How much of your life do you want to actually be there for?

I keep asking myself that, because the question itself seems to help. It pulls me back, sometimes, from wherever my mind has wandered to. Back to here, back to now, back to the only moment that's actually happening.

The Operator's Guide to Morning Pages

Mon, 05 Jan 2026 00:00:00 GMT

It's the first full week of January. The holidays are over. You're probably trying to shift into execution mode—looking at quarterly priorities, scanning your calendar, feeling the pressure to produce.

But there might be a resistance. Not laziness exactly—more like fog. A difficulty getting traction that manifests as "I'll just clear my inbox first" or "Let me review this one more time before I start."

I've been recommending something to the leaders I coach that sounds almost too simple to be useful: twenty minutes of longhand writing, first thing in the morning.

Three pages. Stream of consciousness. No topic, no structure, no purpose beyond getting whatever's in your head onto paper.

This practice comes from Julia Cameron's book The Artist's Way, where she frames it as a tool for creative recovery. I've adapted it for a different context. I think of it as operational hygiene—a way to clear the cognitive channel before the actual work begins.

The River Metaphor

Here's the mental model that makes this click for me: your capacity for strategic thinking, problem-solving, complex decision-making—think of it as a river. It doesn't run dry. It gets blocked.

Over time, fear, perfectionism, low-grade anxiety, and the accumulated weight of everything you're carrying build up like sediment on the riverbed. The channel narrows. Flow restricts. You sit down to do important work and find yourself fighting through resistance that has nothing to do with the work itself.

Morning pages is dredging. You're putting the petty, anxious, boring, repetitive thoughts onto paper so they stop circulating in your working memory. You're not solving anything. You're clearing space so solving becomes possible.

The Smoke Alarm Problem

We all have an inner voice that evaluates our work, flags risks, identifies problems. In a business context, it's easy to mistake this voice for good judgment. Often it isn't.

Cameron describes the inner critic as a faulty smoke alarm—one that responds to burnt toast with the same urgency as a house fire. It doesn't distinguish between a typo in an email and a genuine strategic threat. It just fires.

When you write morning pages, you externalize that voice. You put it on paper: "I'm worried this project will fail." "I think they're going to figure out I don't know what I'm doing." "What if Q1 is a disaster?"

Seen in ink on a page, these thoughts become observable rather than ambient. You can examine them as data instead of experiencing them as background noise. They lose some of their power.

Why Handwriting Matters

I'm insistent about this with clients, even when they push back: morning pages must be handwritten. No typing. The objection is always the same: "I type faster." That's precisely the problem.

Typing is optimized for output velocity. It allows you to stay ahead of your thoughts, which means you can gloss over them. You're transcribing, not processing.

Handwriting is slower. The friction is the point. It forces you to sit with the thought long enough to actually metabolize it. There's research on this—handwriting engages the reticular activating system differently than typing—but honestly, the felt experience is evidence enough. Try both and notice the difference.

The Practice

If you want to try this:

Wake up twenty minutes earlier than usual. Get a cheap notebook—nothing precious, nothing you'll feel protective about. Write three pages of whatever comes. If nothing comes, write "I don't know what to write" until something else surfaces.

This isn't journaling. It's not necessarily meant to produce insight. It's meant to clear the channel. Don't write it for an audience. Be vulnerable, be true to your thoughts and feelings, and most importantly, don't worry about doing it the right way. The way you do it is the right way for you.

I've been doing this for a while now. The surprising thing isn't the writing itself—it's how different the first hour of real work feels afterward. There's less friction. Less fog. The river flows a little easier.

Might be worth twenty minutes to find out if it works for you.