Avinash Vora

Integrity Scales Faster Than Intelligence

Thu, 23 Apr 2026 00:00:00 GMT

AI multiplies whatever you point it at.

Sound judgment gets amplified into good decisions at scale. Poor judgment gets amplified into bad decisions at scale. The multiplication is indifferent to which one you're feeding it.

I don't think we've fully absorbed what this means. Before AI, bad judgment was rate-limited by how fast one person could act. You could only make so many poor calls in a day. There was friction built into the system—meetings, approvals, the time it takes to draft an email, the pause between thinking something and doing something about it. That friction was also a buffer. It gave you time to reconsider, to notice when something felt off, to catch yourself.

That buffer is largely gone.

The Amplification Problem

Daniel Pink identifies integrity as one of six skills AI cannot replace. His argument is that AI can generate, analyze, and optimize, but it can't decide whether something should be done. That judgment remains human. I think he's right, and I think the implication is sharper than it first appears.

Integrity used to be primarily a character question. Are you honest? Do you keep your word? Do you act consistently when no one's watching? Those questions still matter. But AI adds a dimension: whatever your character produces, it now produces at speed and scale that weren't previously available. A person with sound judgment and a powerful model can make good decisions faster across more domains. A person with poor judgment and the same model can produce damage at a pace that wasn't possible before.

The tool doesn't care which one you are. It amplifies equally.

How Ethics Fade

Ann Tenbrunsel's research at Notre Dame describes a process she calls "ethical fading." It's the gradual disappearance of ethical considerations from a decision. Each individual step feels minor. The framing shifts slightly. What was once an ethical question becomes a business question, then an efficiency question, then just a question of execution. By the time you're acting, the ethical dimension has quietly dropped out of the frame.

This happens to good people. Tenbrunsel's point is that ethical fading doesn't require malice. It requires inattention. The small rationalizations accumulate beneath conscious awareness. You don't decide to cross a line. The line moves, imperceptibly, until you're on the wrong side of it without having noticed the crossing.

AI accelerates this. When the output arrives instantly—polished, confident, ready to deploy—there's even less friction to slow down and ask whether this particular application of the tool is something you'd stand behind if it were examined closely. The speed removes the pause. And the pause was where the judgment lived.

Rules vs. Values

Dov Seidman's argument in How: Why How We Do Anything Means Everything draws a distinction between rule-based compliance and values-based behavior. Organizations built on rules focus on what you can't do. Organizations built on values focus on who you are.

The difference matters because rules are finite and specific. Human ingenuity races along, generally complying with the rules while creating new behaviors that exist outside of them. Values operate differently. They're internalized principles that apply to novel situations, including situations no one anticipated when the rules were written.

AI generates novel situations constantly. Every new capability creates decisions that didn't exist before. Rule-based thinking can't keep up with that pace. Values-based thinking can, because it doesn't depend on someone having written the specific rule for the specific situation. It depends on the person asking: does this align with who I am and what I stand for?

The Front-page Test

Warren Buffett's observation applies here with more force than when he first made it: "It takes 20 years to build a reputation and five minutes to ruin it. If you think about that, you'll do things differently."

Five minutes was already fast. AI compresses it further. A single automated campaign, a single AI-generated analysis deployed without adequate review, a single decision made at machine speed with human-speed judgment—any of these can undo years of carefully built trust.

Pink mentions a version of the front-page test as part of his integrity framework. I think it's the most practical tool available for AI-era decision-making. Before deploying any AI-assisted decision or output at scale, ask: if this were attributed to me personally on the front page, would I stand behind it?

If the answer requires hesitation, that's the answer.

The test works because it collapses the distance between the decision and its consequences. AI creates distance. The output feels separate from you. It was generated, not written. Deployed, not decided. The front-page test closes that gap. It forces you to own the output as if you'd produced every word and made every judgment yourself. Because functionally, you did. You chose to use it. You chose to deploy it. Your name is on it.

Character as Infrastructure

In The Long Game of Character I wrote about how your behavior over time creates an ecosystem that either amplifies or undermines everything you're building. And in The Reputation You Have With Yourself, the internal track record that determines whether you trust your own judgment when it matters.

AI makes both of these more consequential. The ecosystem you've built around yourself now gets amplified by more powerful tools. The internal reputation you carry now applies to higher-stakes decisions made at faster speed.

Character is infrastructure. And like all infrastructure, you don't notice it until it fails.

Allocation As The New Leadership Skill

Fri, 10 Apr 2026 00:00:00 GMT

Daniel Pink recently identified six human skills that AI won't replace. One of them is allocation: the ability to direct intelligence resources effectively, deciding which tasks belong to humans and which to machines. It's a clean formulation. I've been turning it over because I think it's pointing at something larger than the AI conversation.

The allocation question has always been the leadership question. AI just makes it harder to ignore.

The Old Problem

Peter Drucker argued in The Effective Executive that what distinguishes great executives isn't intelligence, creativity, or work ethic. It's how they allocate their attention. Where they choose to spend their finite cognitive resources, and equally, what they choose not to spend them on.

His most quoted line captures it: "There is nothing so useless as doing efficiently that which should not be done at all."

This observation was published in 1967. AI has made it urgent. A machine can now do the wrong things far more efficiently than any human. If you haven't figured out what the right things are, the tool just accelerates the misallocation. Drucker's line remains the most precise diagnosis of how leader calendars go wrong. They are efficient. They are productive. They are working extremely hard on things that don't require their particular judgment, experience, or pattern recognition. They are, in Drucker's terms, doing the wrong things well.

The reason this persists is structural, not intellectual. The conceptual understanding is usually there: delegate more, protect their strategic thinking time, and spend fewer hours in the weeds. The problem is that the weeds are where they feel useful. The strategic work is ambiguous, slow to produce visible results, and psychologically uncomfortable in ways that tactical execution isn't. So the calendar fills with meetings they don't need to attend, decisions they don't need to make, and work they don't need to do. The wrong work just feels more like work.

Attention Has A Hard Budget

Kahneman established something in his research on attention that most people accept in theory but ignore in practice: attention is a finite resource with a hard capacity limit. You dispose of a limited budget that you can allocate to activities, and if you try to exceed that budget, you fail. Effortful activities interfere with each other. You cannot do several demanding things at once without degrading all of them.

This is a constraint, like physics. Every hour you spend in a meeting where your presence isn't actually required is an hour subtracted from work where it is. Every decision you make that someone on your team could make is a decision's worth of cognitive load consumed. The budget doesn't expand because the task felt important. It just gets spent. AI compresses this further: if a machine can draft the memo, summarize the data, and prep the analysis, the honest accounting of what genuinely requires your cognitive budget gets very short.

Allocation is the management skill. The quality of a leader's thinking depends directly on how much capacity is left after everything else has taken its share. And by the time you get to the work that actually requires your judgment, the budget is usually already spent on things that didn't.

The AI Extension

Pink's framing adds a new dimension to this old problem. When the only question was how to allocate work among humans, you could afford to be somewhat loose about it. If you kept doing work a team member could handle, the cost was your time and their development. Real costs, but manageable.

Now the question extends to machines. And the machines are getting better at a category of work that many leaders use to fill their days: summarizing, drafting, analyzing data, preparing presentations, processing information. If a significant portion of what you do each day can be done by AI, and another portion could be handled by someone on your team, then the honest accounting of what genuinely requires you gets very short.

This is where the two problems compound. If you can't let go of work that a human on your team could own, you're almost certainly not going to navigate the harder question of what to hand to a machine. The muscle is the same: assessing where your particular intelligence adds genuine value, and having the discipline to stop spending it everywhere else.

Drucker's line about doing efficiently what shouldn't be done at all becomes sharper in an AI context. The machine can do the wrong things far more efficiently than you can. If you haven't figured out what the right things are, the tool just accelerates the misallocation.

Why The Honest List Is Hard

Two columns.

Column one: tasks where your judgment, relationships, or pattern recognition are genuinely irreplaceable. Where you see things nobody else on the team can see. Where your specific experience makes a qualitative difference in the outcome.

Column two: everything else. Tasks that feel important. Tasks you're good at. Tasks that produce the satisfying feeling of getting things done. But tasks where a capable team member, given clear context, could produce 80% of what you produce. Or where a machine, given the right prompt, could do it faster.

The honest version of this list is uncomfortable, because column one is almost always shorter than leaders expect. The gap between "I'm the best person to do this" and "I'm the only person who can do this" is wide. Most of what fills a leader's day lives in that gap: work where they add value, but where the value doesn't justify the cost of their attention.

The reason the list is hard to make honestly is that column two often contains the work that built your career. The deal you could close better than anyone. The product decision you'd make differently. The operational detail you'd catch that others miss. These are real skills. They produce real results. And the role has moved past them. The work that only you can do now is probably the work you find hardest to point at: reading patterns across the business, seeing what's missing, asking questions nobody else is positioned to ask, making the calls that require integrating information from every function simultaneously.

The Same Principle, Extended

Pink's framing of allocation as a human skill in the AI age is useful because it makes visible something that was always true but easier to avoid. The question was never about working harder or being more disciplined with your calendar. The question was always about what deserves your attention and what doesn't.

The AI era just makes the accounting more precise. When a machine can draft the memo, analyze the data, and summarize the meeting, the thing that's left is the thing that was always the real job: deciding what matters, reading people and situations, exercising judgment in conditions of uncertainty, and asking the questions that reframe the problem.

These are allocation decisions. They always were. The only difference now is that the cost of getting them wrong is more visible.

Make the two lists. Be honest about how short the first column is. That gap between what you do and what only you can do is where your attention is leaking. And attention, once spent, doesn't come back.

What's Left When The Machine Finishes

Tue, 07 Apr 2026 00:00:00 GMT

There's a moment in leadership meetings that keeps recurring. The data is on the table. The reports have been distributed. The dashboards are current. Everyone in the room has access to the same information, and most of them have reviewed it.

Then there's a pause. The information is present, but it doesn't point anywhere on its own. Numbers on a screen don't contain a direction. They contain possibilities, and someone has to turn those possibilities into a decision.

The person who breaks the pause is almost never the one who adds more data. It's the one who composes something from what's already there. Who takes the revenue numbers, the customer feedback, the competitive landscape, and the team capacity constraints and assembles them into a narrative that says: here's what I think this means, and here's what we should do about it.

That's composition. Analysis takes things apart. Composition puts them together into something that didn't exist before.

Ingredients And Meals

Daniel Pink describes this as one of the essential human skills in an AI world. He calls it "composition." The metaphor he uses is cooking: AI delivers ingredients, humans serve meals. The machine can give you every relevant data point, summarize every report, generate every possible analysis. What it can't do is look at all of that and say: this is what it means for us, right now, given who we are and where we're trying to go.

The reason it can't do this is that composition requires judgment that lives outside the data. It requires knowing which facts matter more than others in this specific context, which trade-offs are acceptable given this team's capabilities, which risks are worth taking given this company's stage. The data doesn't contain those answers. The person interpreting it does.

This has always been true, but AI is making it visible in a way it wasn't before. When generating information was expensive and time-consuming, the people who could gather and organize it had real value. That value is collapsing. What remains is the value of knowing what to do with it.

Integrative Thinking

Roger Martin spent years studying how the most effective leaders make decisions. His finding, detailed in The Opposable Mind, was that the best leaders don't choose between the options presented to them. They hold opposing ideas in constructive tension and generate a new option, one that contains elements of both but is superior to each.

Martin calls this integrative thinking. It's the ability to face a genuine either/or dilemma and refuse to accept it as binary. Instead of choosing A or B, the integrative thinker asks: what would a solution look like that captures the best of both?

This is composition applied to decisions. The raw material is a set of conflicting possibilities. The output is something new, a synthesis that wasn't on the table before someone assembled it from the parts.

The leaders Martin studied, people like A.G. Lafley at Procter & Gamble and Nandan Nilekani at Infosys, didn't succeed because they had better information than their competitors. They succeeded because they were better at composing meaning from the information everyone had. They saw connections and possibilities that others, looking at the same data, missed.

The Widening Gap

This distinction is becoming sharper every quarter. AI tools are making certain kinds of contribution almost free. You need a market summary? Done in minutes. Competitive analysis? Generated from public data. Financial projections under different scenarios? Built while you wait.

The question that follows is the one that matters: so what? What does this mean for us? What should we do?

The people who can answer that question are becoming more valuable. The people whose primary contribution was generating the material that precedes the question are finding their role compressed. This is already happening in real meetings, in real companies.

Linus Pauling reportedly said the best way to have a good idea is to have lots of ideas. AI gives us the "lots of ideas" part for nearly free. The human skill is recognizing which ideas matter and composing them into something that works.

The Skill That Matters

The practical implication is worth paying attention to. Next time you're in a meeting where the data is abundant, notice two things. Notice who adds more information to the pile. And notice who takes what's already there and assembles it into a direction.

These are both valuable contributions. But they're becoming asymmetric. The first one is getting cheaper every month. The second one isn't. The ability to compose, to synthesize, to look at a set of parts and see what they could become together, is the skill that's left when the machine finishes its work.

It's worth asking whether you're developing that skill or spending your time on the parts that are becoming free.

Taste Is A Leadership Skill

Wed, 01 Apr 2026 00:00:00 GMT

Daniel Pink recently identified taste as one of six human skills that become more valuable as AI advances. His argument: AI is excellent at generation. It can produce endless options, drafts, strategies, designs. But generation without discrimination is just volume. Someone has to look at the output and know what's good. That's taste. And it's a capacity AI doesn't have.

This matters for leadership more than most discussions about AI acknowledge.

What Taste Looks Like in Practice

Analysis can narrow five strategic options to three. It can model scenarios, weight risks, and rank expected outcomes. What analysis cannot do is tell you which option fits this team, this competitive position, this stage of growth. That final act of recognition draws on something harder to articulate: a sense of fit built from years of watching strategies succeed and fail, noticing which conditions produce which outcomes, developing an internal model for what "right" looks like in context.

That sense of fit is taste. It matters precisely because it can't be reduced to a framework or a checklist.

The Science of Expert Recognition

Herbert Simon spent decades studying how experts think. Through extensive research on chess masters and professional decision-makers, he found that experts store tens of thousands of meaningful patterns in long-term memory. When they encounter a new situation, they don't analyze it from scratch. They recognize it as an instance of a pattern they've seen before, and that recognition triggers stored knowledge about what works.

Simon put it plainly: "The situation has provided a cue; this cue has given the expert access to information stored in memory, and the information provides the answer." Intuition, in his framing, is nothing more and nothing less than recognition.

Gary Klein's research on naturalistic decision making confirmed this from the field. He studied firefighters, critical care nurses, military commanders, and other experts making high-stakes decisions under time pressure. What he found challenged the conventional model of decision-making, which assumes people generate options and then compare them. Experts under pressure don't do this. They recognize the situation as a type, the type suggests a course of action, and they mentally simulate that action to see if it will work. If it will, they go. If it won't, they adapt.

Klein called this recognition-primed decision making. Experts aren't choosing between alternatives. They're recognizing what fits. The first option they consider is usually viable, because their recognition is drawing on a deep library of patterns built through experience.

Taste as Applied Pattern Recognition

Simon and Klein's research maps directly onto what Pink describes. Taste is pattern recognition applied to quality and fit. The same mechanism Klein observed in firefighters operates when a leader reads a strategy deck and feels something is off before they can say why. The pattern doesn't match their internal library, and the mismatch registers as felt sense before articulated critique. AI pattern-matches statistically across training data. Human experts pattern-match against lived context. The difference matters most when the question is "does this fit us, here, now?"

This is what I explored in Borrowing Knowledge: owned knowledge versus borrowed knowledge. Taste can't be borrowed by reading a strategy book or attending a workshop. It's built through direct experience. Making decisions, watching outcomes, updating the internal model. The cycle has to be lived.

And as I wrote in The Focus You Fear, depth over breadth is how this kind of knowledge accumulates. Fifteen years in one industry builds a richer pattern library than three years in five industries. The depth itself is doing the work.

Why AI Can't Replicate This

AI generates by statistical pattern matching across its training data. In a narrow sense, this resembles recognition. But it's missing the experiential foundation that gives human taste its power.

When a leader recognizes that a strategy "fits," they're drawing on embodied knowledge: the memory of watching a similar strategy fail at a previous company, the felt experience of a team that was ready for a particular kind of challenge versus one that wasn't, the accumulated sense of what this specific market rewards. This knowledge is contextual, situated, and personal. It can't be abstracted into training data because much of it was never written down.

Ira Glass described a version of this in creative work: "All of us who do creative work, we get into it because we have good taste. But there is this gap. For the first couple years you make stuff, it's just not that good. But your taste, the thing that got you into the game, is still killer." The gap he describes is the distance between recognizing quality and being able to produce it. The taste comes first. The skill catches up through volume of practice.

In leadership, the equivalent gap is between recognizing the right strategic direction and being able to articulate why. The recognition often arrives before the reasoning. And that's fine. The reasoning can be reconstructed. The recognition can't be manufactured.

Developing Taste Deliberately

If taste is pattern recognition, and pattern recognition develops through experience, then the question becomes how to accumulate the right kind of experience.

Kahneman and Klein's joint paper on the conditions for developing genuine intuitive expertise identifies two requirements: an environment with enough regularity that patterns exist to be learned, and sufficient practice with feedback to learn those patterns. Both conditions matter. Practice without feedback doesn't build accurate recognition. And feedback without sufficient repetition doesn't build speed.

For leaders, this means that taste develops through a specific cycle: make a decision, observe what happens, connect the outcome back to the conditions that existed when you decided. The connecting step is where most people lose the thread. Decisions happen. Outcomes arrive. But the explicit linking of "I chose this because I saw that pattern, and here's what actually happened" is the deliberate part of deliberate practice.

Few leaders do this deliberately. Decisions pile up. Outcomes blend together. The pattern library grows slowly and somewhat randomly instead of being actively curated. Meanwhile, AI is getting better at everything around taste—the analysis, the option generation, the data synthesis. The gap between what AI handles and what only you can judge is widening. The taste that fills that gap is either sharpening or it isn't.

Something to Try

After your next significant strategic decision, write down what made you choose. Not the post-hoc rational justification. The actual moment of recognition. What did you see? What pattern triggered the response? What felt right, and why?

You might struggle with this. The recognition often happens below the level of conscious articulation. That struggle is useful. It forces you to surface the mental models you're actually operating from, which is the first step toward refining them.

Taste is earned. And developing it deliberately, by paying attention to your own recognition patterns, builds a capacity that no amount of AI-generated analysis can substitute for.

The Skill That Can't Be Automated

Fri, 27 Mar 2026 00:00:00 GMT

Daniel Pink recently laid out six human skills that become more valuable as AI advances. The first one on his list: asking better questions. His argument is straightforward. AI is extraordinarily good at generating answers. It can produce a hundred plausible responses to any prompt in seconds. The cost of answers is collapsing. Which means the scarce resource was never the answer. It was knowing which question to ask.

The idea has stayed with me because it names something that happens in every leadership meeting where I've facilitated a decision.

The Wrong Problem, Solved Beautifully

Leadership teams fail more often from misdirected effort than from poor execution. A room full of smart, experienced people solving the wrong problem with impressive efficiency.

It looks like productivity. The conversation is energetic. People are engaged, contributing, building on each other's ideas. Solutions emerge. Decisions get made. And then weeks later, the real issue surfaces anyway, because nobody paused long enough to ask whether the question they were answering was the right one.

The urgency to solve overtakes the discipline to define. This is human. We're wired for it. An open question creates discomfort, and solutions relieve that discomfort. So we rush toward resolution, and the quality of the question goes unexamined. AI accelerates this. When you can generate and execute answers faster than ever, the cost of the wrong question compounds at machine speed.

The Research on Question Formulation

Hal Gregersen at MIT has spent years studying how the world's most innovative leaders think. He interviewed over 200 of them, and found that they exhibit a disproportionately high question-to-answer ratio. In transcribed interviews, they ask significantly more questions relative to the answers they give. They spend more time on formulation than most people spend on solutions.

This resonates with the question-behavior effect I've written about before. Asking someone a question activates a fundamentally different cognitive process than giving them an answer. The question creates internal reasoning. The answer creates evaluation. These produce different qualities of thought and different levels of commitment to whatever follows.

Gregersen calls the best questions "catalytic." They dissolve barriers to thinking and redirect the search into pathways nobody was considering. His question burst methodology works on this principle: instead of brainstorming answers, a group spends a concentrated period generating only questions about a challenge. No answers allowed. The result is consistently a reframing of the problem that opens up solutions the group hadn't considered.

The question shapes the search space. Get the question wrong and every answer, no matter how sophisticated, is irrelevant. Get the question right and the answers often become obvious. AI can generate those answers instantly. It cannot generate the question. Framing requires contextual judgment that no model has.

Why This Was Always the Bottleneck

There's a quote attributed to Einstein: if he had an hour to solve a problem, he'd spend 55 minutes defining the problem and 5 minutes solving it. Whether he actually said it is debatable. That it rings true to anyone who's worked on hard problems is not.

The ability to frame a problem well has always been the highest-leverage skill in any room. The person who can look at a messy situation and articulate the actual question underneath the noise creates more value than the person who generates the fastest answer to whatever question happens to be on the table.

This was true before AI. But AI made it visible by removing the other constraint. When generating competent answers required significant time and expertise, both skills mattered. Now that answers are nearly free, the asymmetry is exposed. The question is the bottleneck. It always was. We just couldn't see it clearly because answers were expensive enough to seem like the scarce resource.

What This Means for Leadership

The leaders who consistently produce the best outcomes are the ones who slow the room down long enough to get the question right.

This is harder than it sounds. The pressure in any meeting is toward resolution. People want to solve, decide, move forward. The person who says "wait, are we asking the right question?" risks looking like they're slowing things down. And they are slowing things down. That's the point. The ten minutes spent interrogating the question saves the three weeks spent executing the wrong answer. In an AI-accelerated environment, those three weeks compress into three days, and the wrong answer gets implemented with more confidence and less friction. The cost of a bad question is higher than it's ever been.

The discipline is specific: resist the pull toward solutions long enough to examine the problem. Ask what's actually going on. Ask what would have to be true for the proposed solution to fail. Ask what question you'd be asking if you weren't anchored to the one already on the table.

Something to Try

Before your next meeting where a decision needs to be made, spend the first ten minutes only asking questions. No solutions, no proposals, no evaluations. Just questions about the problem. Anyone can contribute a question. Nobody is allowed to answer one.

It will feel unnatural. The room will want to solve. That pull toward resolution is exactly the thing worth examining. Notice what happens to the quality of the conversation once the room has been forced to think about the problem before jumping to solutions.

The skill that can't be automated is knowing what to ask.

The Conceptual Age Hit Leadership Teams First

Mon, 23 Mar 2026 00:00:00 GMT

Daniel Pink's A Whole New Mind argued that three forces—material abundance, automation, and global outsourcing—were rendering pure left-brain analytical work insufficient. The economy was shifting from the Information Age to what he called the Conceptual Age, where right-brain abilities would become the primary source of value. He identified six "senses" for this new era: Design, Story, Symphony, Empathy, Play, and Meaning.

The book was published in 2005. Twenty years later, the thesis has held up remarkably well. But I think Pink was describing something that had already been true in leadership teams for a long time before it became true for the broader economy.

The Shift That Already Happened

The functional expertise that got people into the leadership room—the financial acumen, the operational precision, the technical depth—is necessary but not sufficient once they're there. The work of a leadership team is fundamentally different from the work that qualified each member to join it.

A CFO who only runs numbers is less valuable than one who tells a story with them. The numbers are the same. But the CFO who can frame quarterly results as a narrative about where the company has been and where it's heading produces a different quality of alignment than the one who presents a spreadsheet. That's Pink's Story sense in action.

A COO who optimizes individual processes is less valuable than one who sees how all the pieces connect—how a change in the sales process ripples through fulfillment, capacity planning, and customer experience simultaneously. That's Symphony: the ability to see relationships between disparate things and combine them into something coherent.

A CEO who is analytically brilliant but can't read a room builds teams that perform on paper and underperform in practice. The analytics are correct. The team dynamics are off. People are compliant rather than committed. The meetings run efficiently but the real conversations happen afterward. That's the absence of Empathy—the inability to perceive what others are feeling and respond accordingly.

In a leadership team, these are the real work. And none of them can be automated.

What The Research Shows

The intuition that right-brain abilities matter for team performance has strong empirical backing. Woolley et al.'s 2010 study at MIT, published in Science, found something that surprised even the researchers: a group's collective intelligence—its ability to perform well across a wide variety of tasks—was not strongly correlated with the average or maximum IQ of its members.

What predicted team performance was social sensitivity (measured by the ability to read emotions in others' eyes), the equality of conversational turn-taking, and the proportion of members with high social perceptiveness. Teams where a few people dominated the conversation had lower collective intelligence than teams where participation was distributed. No AI tool replicates any of this. Social sensitivity, turn-taking, and perceptiveness are embodied human capacities.

Google's Project Aristotle reached a similar conclusion from a different direction. After studying over 180 teams internally, they found that who was on the team mattered less than how the team worked together. Psychological safety—whether people felt safe to take risks and be vulnerable—was the single strongest predictor of team effectiveness. Not talent, not experience, not seniority. The relational dynamics.

Roger Martin's work on integrative thinking adds another layer. He studied exceptional leaders and found that their distinguishing capability wasn't analytical horsepower. It was the ability to hold two opposing ideas in tension and produce a creative resolution that contained elements of both. That's a right-brain operation. It requires comfort with ambiguity, the capacity to see systems rather than components, and the willingness to sit in uncertainty long enough for a synthesis to emerge.

Why This Accelerates Now

If the Conceptual Age was already playing out in leadership teams before Pink named it, AI accelerates the transition for everyone else. Every analytical task that can be clearly specified is now automatable. Financial modeling, data analysis, process optimization, report generation—the left-brain work that constituted much of a knowledge worker's value is increasingly handled by tools.

What remains is what Pink identified twenty years ago. The ability to design experiences, not just products. To tell stories, not just present data. To see how disparate elements fit together into a whole. To understand what other people are feeling and respond to it. To approach problems with playfulness rather than pure procedure. To connect work to something meaningful beyond the immediate deliverable.

These were always the skills that separated effective leadership teams from stagnant ones. The difference now is that they're becoming the skills that separate valuable contributors from automatable ones, at every level.

The Practical Question

Pink's six senses map onto specific, observable behaviors in a leadership team meeting. Each one represents a capacity that AI makes more valuable precisely because AI handles everything around it.

Design is the difference between a functional but lifeless quarterly review and one where the presentation itself communicates clearly, where information architecture serves understanding rather than just data transfer.

Story is the difference between "revenue grew 12%" and a narrative about what drove that growth, what it means for the company's trajectory, and what it demands next.

Symphony is the difference between each function reporting in isolation and someone connecting the dots—noticing that the customer churn pattern, the hiring bottleneck, and the product delay are all expressions of the same underlying problem.

Empathy is the difference between a technically correct decision and one that accounts for how the people affected by it will actually experience it.

Play is the difference between a meeting where every minute is optimized for output and one where ten minutes of unstructured exploration produces the insight that the structured portion never would have.

Meaning is the difference between a team executing tasks and a team that can articulate why those tasks matter.

Pick one of these that your leadership team is weakest on. In your next meeting, deliberately introduce it. If it's Story, ask someone to frame the data as a narrative rather than a report. If it's Empathy, ask each person to articulate what the person to their left is most worried about right now. If it's Play, carve out ten minutes with no agenda and see what surfaces.

The analytical capabilities are the foundation, not the structure. The structure is built from the things Pink identified twenty years ago, and which AI is making more valuable every day. The smartest team is the one where the room itself gets smarter.

The Question That Changes The Room

Mon, 16 Mar 2026 00:00:00 GMT

When a leader states a position, the room evaluates it. People listen, assess whether it seems reasonable, and—if the person has authority—mostly agree. This isn't dishonesty. Disagreeing with the person who controls your career requires a higher threshold of conviction than agreeing does. So the default is agreement. The agreement is real, but it's thin. It starts fragmenting the moment everyone leaves the room, because nodding isn't the same as believing.

When a leader asks a genuine question, the room does something different. People stop evaluating someone else's argument and start generating their own. The thinking shifts from "is this reasonable?" to "what do I actually think?" That shift changes everything that follows.

Why Questions Work Differently

The mechanism is self-persuasion. Research on the question-behavior effect shows that asking people about their intentions changes their subsequent behavior—not because the question contains information, but because generating an answer activates internal reasoning. People asked "will you vote tomorrow?" are significantly more likely to vote than people told "you should vote tomorrow."

When you generate your own argument for something, that argument carries more weight than one handed to you from outside. You built it. The reasoning came from your own head. You're more invested in it. This is why alignment built through genuine discussion holds, while alignment built through compelling presentations fragments.

The implications for anyone who leads meetings or makes decisions in a group are significant. Every time you open with a statement, you're asking the room to evaluate. Every time you open with a question, you're asking the room to think. The first produces compliance. The second produces conviction.

Genuine vs. Performed

The critical distinction is between genuine questions and directives in question form.

"Don't you think we should focus on the enterprise market?" is not a question. It's a statement of preference with a question mark. The room recognizes this instantly. The expected answer is "yes," and most people give it—not because they agree, but because contradicting a directive-as-question has high social cost and low benefit.

Genuine questions sound different. "What's the strongest argument against this approach?" forces critical thinking rather than affirmation. "If we execute this perfectly and it still fails, what's the most likely reason?" gives people permission to voice concerns without framing them as disagreement. "What are we not talking about that we should be?" creates space for things too uncomfortable to raise without an invitation.

These aren't soft questions. They're demanding—they require real thought. But they produce a different quality of conversation than any amount of compelling presentation.

The Hard Part

This only works when the curiosity is real. People have extraordinarily sensitive radar for performed curiosity. Someone who asks "what do you think?" while visibly waiting for the room to confirm their predetermined answer is conducting a ritual, and everyone knows it.

Genuine curiosity requires holding your own opinion lightly enough that you could be changed by what you hear. Not that you always will be. But the possibility has to be real. And if you ask a genuine question and then ignore the answers, the message is clear: the question was theater. People stop answering honestly very quickly.

Edmondson's work on psychological safety describes the conditions under which people feel safe enough to speak honestly. But safety is only half of it. The other half is whether speaking honestly produces anything. Safety without follow-through is a more comfortable form of being ignored.

The people I've watched who are best at this can hold a strong opinion and genuine curiosity simultaneously. They believe they're right, strongly, with good reasons, and they're still authentically interested in what the room thinks—because they've learned that a group's collective intelligence, when actually accessed, regularly produces insights they wouldn't have reached alone.

The Sequence

The insight isn't that leaders should stop having opinions or making decisions. It's about sequence. Question first, then direction. Let the room contribute to the thinking before the conclusion is drawn, rather than asking people to ratify a conclusion already reached.

The difference seems small. In practice, it changes what's possible.

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.