Lies, Damned Lies, and Performance Evaluations

You do their performance evaluations. Their survival in the company depends on your decision and your criteria. So when you say “I get along fine with the people who report to me because I always get good evaluations from them,” do you really think that’s evidence?

This doesn’t mean they lack courage or are being strategic. They might be entirely sincere. The asymmetry simply means you cannot know. When you hold power over someone’s professional life, that structural inequality is present in every interaction whether anyone responds to it or not. Their positive evaluation might reflect their genuine experience of working with you. Or it might not. The asymmetry makes the meaning of their feedback fundamentally indeterminate.

And while the surveys are anonymous, there are just too many managers who’ve told me they can recognize who wrote the comments by the way it was written and the words they used. So even the structural protection of anonymity often dissolves in practice. And if comments are too risky and you take them off, then you’re left with numbers. And as Disraeli said, there are lies, damned lies, and statistics.

You might deserve the praise. But their positive evaluation, given the context, cannot tell you whether you do.

The same dynamic appears when executives cite employee engagement surveys as proof their culture is healthy. The survey measures what employees are willing to say about a culture that determines whether they remain employed. What you’re measuring isn’t engagement. It’s what people are willing to have measured.

==

photo by Jon Tyson

Trust Doesn’t Work Like That

I keep seeing versions of the same claim: that trust is the natural result of psychological safety. Or that it can be engineered through a formula.

That’s tidy. It’s appealing and it’s convenient.

It’s also not true.

Psychological safety may create the conditions where trust could grow. But that’s all they are: conditions. Trust is never automatic, and never unilateral. It’s not a reward for checking the right boxes.

Trust is a decision. It’s someone else’s decision.

And that changes everything.

Trust works like foreign currency. It’s never strong in general, only strong against something else. The dollar is not stronger overall; it is stronger than the euro, the yen, whatever you’re measuring it against. Trust operates the same way: relational, contextual, and maddeningly specific. You might be someone’s anchor while remaining someone else’s question mark.

Here’s the thing: you can create the perfect conditions (open communication, demonstrated competence, unwavering reliability) and still manufacture nothing. You can create the environment where trust might grow, but the seed belongs to someone else entirely.

The other person chooses to trust. It doesn’t happen automatically. Their history, their scars, their appetite for vulnerability are all variables you’ll never control, no matter how trustworthy you become.

Which leaves you with a paradox in human connection: you can perfect your trustworthiness but never guarantee their trust. You can tend the garden but not force the bloom.

So create the conditions and then wait.

You can knock. But the door has to be opened from the other side.

The idea that trust is relational, chosen, and not guaranteed lies at the heart of my approach to leadership practice. It invites us to hold both our responsibility for trustworthiness and our humility about what trust ultimately requires.

==

Every orchestra needs a conductor. Really?

The Orpheus Chamber Orchestra has operated without a conductor since 1972. Representatives from each section meet to discuss how they’ll approach a piece. Leadership rotates. Decisions emerge from dialogue among those who will execute them.

They’re a Grammy Award-winning ensemble.

Each musician must listen more intently and communicate more directly. Take greater ownership of the whole. Lead when their expertise matters most. Follow when others’ does. This distribution of authority changes what becomes possible.

Your organization employs people who create knowledge, apply expertise, and solve novel problems. The work can’t be fully specified in advance. Solutions emerge through collaboration. Value comes from synthesis and innovation.

Management is coordination. Things need to be done, sometimes in certain ways, at certain times, by certain deadlines. The question is where the capacity for coordination resides.

Orpheus demonstrates that coordination can live in a system rather than in a person. This requires structure: the section representatives, the meeting protocols, and the rotation of leadership within sections. It requires discipline, deep engagement, clear communication, and shared responsibility.

It doesn’t require a conductor.

The musicians need a framework for deciding together how to play. They need engagement with each other and the work. They need conditions in which shared vision can emerge.

Remove the conductor and different questions surface. What does leadership look like when genuinely distributed? What does a manager do when the team coordinates itself? What changes about authority when those doing the work hold it?

Orpheus is smaller than a full symphony. They select members carefully. They’ve built practices over decades. Their approach takes more time and generates more conflict. It demands more from each musician. It’s not universal.

But it exists. And it produces excellence.

The conductor stands separate from the orchestra, interpreting the score and imposing coherence. Orpheus embeds interpretation and coherence within the ensemble itself. One model centralizes the capacity for coordination. The other distributes it.

Which model matches how knowledge actually gets created in your organization? Not the theory. Not the org chart. The reality of how problems get solved when the work goes well.

The conductor metaphor has shaped management thinking for decades. It suggests that coordination requires a central authority who stands apart from the work, sees the whole, and directs the parts.

Orpheus suggests something different. Coordination is a capacity that can be built into how people work together. Authority can reside in those doing the work. The manager’s role might be something other than conducting.

What if it never was?

==

photo by Luisa Wachsmuth

Quiet Giving

In the early 2000s, a group approached me with a simple but unusual question. They were earning more than they needed and wanted to give back. But their question wasn’t the usual “how do I give?” or “where do I give?” Instead, they asked something different: “How can we give without it being about us?” These weren’t people seeking tax advantages or recognition. They wanted to give in ways that left no fingerprints.

The Search

We held a few workshops exploring their question. And then they started experimenting. What if you gave in ways that created no relationship at all? What if resources flowed so cleanly that they left no trace of the giver? They noticed immediately what got in the way. Foundations. Named donations. Tax breaks. The entire apparatus that had grown up around giving.

Through frank conversations, patterns emerged. They realized something fundamental: if they wanted to improve circumstances for specific persons – with first names and last names – they had to understand who those people were and what their situations were. Not categories. Not demographics. Actual people in actual situations. Two questions became essential: What does this specific person actually need? And what is the broader context of that need?

But they learned to be careful with language. They weren’t “solving problems” – they were improving circumstances or enabling initiatives. This precision mattered. A scholarship might provide access to college, but if the student isn’t eating a nutritious meal today, the scholarship doesn’t improve the circumstances in which they’re trying to learn. The group learned to ask: What is this person already trying to do? What would actually improve the circumstances in which they’re acting?

They agreed to name conditions precisely. Not the sanitized language of nonprofit reports, but actual circumstances. Not “food insecurity” – not eating a nutritious meal today. Not “housing instability” – no place to sleep tonight. Vague language lets you avoid seeing what’s actually happening. Precise language forces you to see the person. Quiet giving wasn’t just about anonymity. It was about accuracy – seeing someone clearly enough that resources could move without distortion.

Cash worked better than checks. Paying someone’s overdue bill without telling them who paid it. Adding time to an expiring parking meter. Funding what someone actually needed after understanding their specific circumstances. Over time they discovered ways to give more substantially while remaining discreet. The methods were surprisingly simple: give without announcement, act without signature, build without claiming. Know the person, not the category. Name the circumstances precisely. Enable their initiatives rather than solving their problems. They were amazed at how value moves most freely when nothing echoes back.

The Reveal

Little did they know, someone had already answered their question. Not through philosophy, but through practice.

In 1939, a young man named Nicholas Winton sat at a small desk filling out papers long into the night. No medals. No spotlight. Just a typewriter and the desperate hope of saving as many children as he could before the borders closed. One by one, he found trains. Found families. Found a way. 669 children escaped because one ordinary man chose extraordinary compassion. He never spoke about it. The papers went into a dusty box in his attic.

Fifty years later, his daughter found them while cleaning. Had she not been curious that day, Winton would have taken the story to his grave. 669 lives saved, zero credit received, zero credit sought.

Shortly after the discovery, Winton sat in a TV studio, unaware of what was coming. The host asked the audience: “If you were saved by Nicholas Winton, please stand up.” Row by row, people rose. Mothers. Fathers. Grandparents. Lives that existed only because he cared. Winton turned, eyes wide. A lifetime of quiet love suddenly visible.

This is what the group had been searching for. Not the drama of the discovery, but the fifty years of silence. The genuine indifference to credit. The dusty box that might never have been opened. Resources flowing freely, leaving no trace, requiring no acknowledgment. Winton hadn’t strategized anonymity. He simply hadn’t thought to mention it.

The Tension

Ken Barrett runs laundromats. For years, he kept his WiFi password posted publicly. Nothing special. Just access. One day, a mother approached him in tears: “If it wasn’t for your free WiFi, my daughter and her friends may not have graduated.” Her family couldn’t afford internet. After the library closed, the kids walked to Ken’s laundromat to finish homework. Ken added benches and tables. Made it comfortable. Created study spaces in four of his five locations.

He didn’t announce this. Someone else noticed and shared his story. Now thousands know his name. Ken gave without signature. Recognition came anyway, as a side effect of genuine impact.

The question: Can giving be “quiet” if it becomes visible?

The group wrestled with this. Was Ken’s story evidence that they’d failed, or evidence that they’d succeeded? They landed somewhere unexpected: Don’t avoid visibility. Avoid seeking it. The goal is perfect indifference to credit. The quieter your intention, the louder the impact can afford to be.

Other Examples

They started finding more examples. Not people following a philosophy, but people who’d simply practiced this way of being.

Paul Newman walked into a Manhattan shelter on Christmas Eve in 1983 carrying two wooden crates from his farm. “Where’s the kitchen?” he asked, already rolling up his sleeves. For hours, he cooked. Garlic sizzled, bread rose, soup bubbled. He moved between the stove and the tables, serving over two hundred people. When the last guest left, he stayed to sweep the floor and stack chairs. Before slipping out into the snow, he said softly to a volunteer: “Food matters. But being here with them matters more.” The next morning, no newspapers called. Newman had told no one. One of the most recognizable faces in America, uninterested in leveraging it.

Bob Marley wrote “No Woman, No Cry” but gave the songwriting credit to his friend Vincent Ford, who ran a soup kitchen in Trenchtown. The royalties from that song flowed directly to keep the kitchen running for years. No foundation. No administrative costs. No naming rights. Just a steady stream of resources flowing exactly where they were needed. Ford’s name appeared on the credits. The motivation stayed hidden for years.

Ken created access through infrastructure. Newman created connection through presence. Marley created sustainability through redirection. Same principle: remove yourself from the equation and let resources flow where they’re needed. None of them had strategized it. Like Winton, they simply hadn’t thought it remarkable enough to mention.

Who Benefits?

The group started asking a different kind of question. If giving could be this simple and effective, why had charity become so complicated? What were all the other systems actually for?

Follow the infrastructure that has grown up around modern philanthropic giving: Professional fundraisers charge steep fees. Nonprofit executives earn six-figure salaries. A whole industry profits from monitoring and evaluating philanthropy. Corporate donors receive tax deductions and marketing value that often exceed their actual giving. Wealthy philanthropists gain social influence, naming rights, and legacy control. Grant-making foundations accumulate power while their assets often grow faster than they’re distributed. The people who need resources often receive less than half of what was originally given.

The financial incentives run deeper. Nonprofit organizations don’t pay taxes on property, income, or investments. Massive public subsidy. Meanwhile, donors deduct their contributions. Both benefits come at public expense. Decisions about deployment remain entirely private. Taxpayers subsidize private charitable choices twice over.

The Transaction

Walk through any hospital, university, or cultural institution. Notice how many surfaces bear donors’ names. Buildings, wings, rooms, benches, bricks. All for sale in exchange for recognition that outlives the donor.

Much of modern philanthropy purchases immortality. The institution becomes a monument to the donor. The hospital wing heals people, yes. It also ensures the donor’s name outlives them. Naming rights expose the transaction perfectly: the “gift” is contingent on perpetual recognition. The recipient becomes billboard provider. You’re purchasing something in return.

The System

Professionalization makes social problems more profitable to manage than to solve. Nonprofit organizations depend on the continued existence of the problems they address. Complete success would eliminate their reason for existing.

This creates an ecosystem whose livelihood depends on the perpetuation of need. The incentive structure rewards growth, visibility, and fundraising capacity rather than actual problem-solving. Grant-making processes favor organizations that can write compelling proposals over those that might be most effective at direct service. The apparatus privileges presentation over impact.

Much of what we call charitable giving has become a sophisticated system for extracting value from the human desire to improve others’ circumstances. Professional fundraisers need donors who need tax advantages who need recognition who need causes that need management who need oversight that needs funding. Everyone in the chain benefits. Except the people the charity claims to serve.

Ancient Wisdom

The group had thought they were pioneering something. But near the end of our workshops, someone brought in a passage: “When you give to the needy, do not let your left hand know what your right hand is doing.”

The wisdom was explicit: invisibility, ego-removal, the danger of making charity about the giver. Modern philanthropy has built an entire industry around making sure everyone knows. Elaborate systems for the left hand to track, publicize, and celebrate what the right hand is doing.

Winton had lived this differently. For fifty years, he forgot to mention it. The papers sat in a box. The children grew into parents and grandparents while he went about his ordinary days, not thinking of himself as remarkable. The group hadn’t discovered something new. They’d rediscovered something old, something that the complexity of modern philanthropy had buried.

What This Reveals

A small group of people developed effective ways to improve others’ circumstances that required no infrastructure, generated no overhead, created no tax complications, and left no traces. What is all the complexity of modern philanthropy actually for?

Modern philanthropy channels genuine human compassion into a system that socializes the costs through tax subsidies while privatizing the benefits: recognition, influence, tax savings. It transforms the simple impulse to improve others’ circumstances into a complex industry that serves everyone except those who need resources. By making charity complicated, expensive, and institutional, the system convinces us that improving others’ circumstances requires expertise, infrastructure, and mediation. The group discovered the opposite. Removing all those barriers made resources flow more freely.

The best giving leaves no trace. Impact flows most freely when nothing echoes back. Removing yourself from the equation is a stance.

The End

The group held their final workshop session on a Tuesday afternoon. They had found what they were looking for. A practice so simple it required nothing but commitment to its principle.

They understood what Winton had embodied, what Barrett and Newman and Marley had practiced in their different ways: that the best giving leaves no trace, that impact flows most freely when nothing echoes back, that removing yourself from the equation is a stance.

We closed the session. People gathered their things. A few conversations in the parking lot, then silence. I’ve never organized a reunion. Never sent a follow-up survey. Never asked what became of their practice. Because if they’re true to what they discovered, they’re somewhere right now improving the circumstances of someone with a first name and a last name. And I will never hear from them again.

==

 

photo by Kayra Siddik

What You Lose Every Time You Get Promoted

Organizations rarely name what actually happens when you get promoted: each transition destroys your identity. The capabilities and ways of working that made you successful at one level become obsolete at the next. Every promotion is not an expansion of capability. It is the death of one professional identity and the birth of another. And that destruction follows a recursive pattern that compounds with every promotion.

The recursive pattern

When you move from individual contributor to manager, you lose the satisfaction of creating tangible output and must find meaning in developing others. When you move from manager to manager of managers, you lose direct contact with individual development and must find meaning in shaping systems. When you move to organizational leadership, you lose decisive ownership of your domain and must find meaning in collaborative deliberation with peers.

Each transition asks you to surrender the identity and capabilities that made you successful at the previous level. The engineering manager who writes code at night isn’t integrating her technical skills. She’s trying to keep a dead identity on life support.

And each time, the new identity is more abstract:

  • IC identity: “I wrote this code. I designed this system.” You can point to the thing you made today.
  • Manager identity: “My team shipped this feature.” You can still see the output, even if your hands didn’t create it.
  • Manager of Managers identity: “The organization delivered these results.” The causal chain is longer.
  • Organizational Leader identity: “We navigated this tension productively and made a better collective decision.” Your contribution is the quality of the deliberative process itself, almost entirely invisible.

Each level is harder to inhabit, harder to feel competent in, provides less immediate satisfaction. The grief compounds because just when you’ve finally learned to derive meaning from the abstraction, just when you’ve built a new professional identity and found your footing, you get promoted. You spend two years discovering that your value comes from developing your team rather than doing the work yourself. You finally feel the satisfaction when someone you coached has a breakthrough. And then we promote you. That direct development work you just learned to love? Not your job anymore.

The refuge of power

Leaders retreat to what they know, seeking refuge in an identity they know how to inhabit. Where they can still feel competent. Where their expertise still matters in ways they can directly experience. Where they have control over variables that produce tangible outcomes.

When you can no longer derive identity from what you produce, you grab for identity through what you can control. Power becomes the refuge from abstraction and loss. You reach for certainty because deciding means you don’t have to sit in ambiguity. You seek visibility because when people do what you say, you can see your impact. You tighten control because determining outcomes means you’re not dependent on others. You validate your expertise by ensuring people defer to you, proving you still matter.

The CEO who micromanages is seeking the feeling of competence through control because they never successfully grieved the loss of hands-on creation. The executive who dominates meetings is grasping for the certainty of “being right” because the ambiguity of collaborative deliberation provides no ground to stand on.

Organizations full of individually capable leaders become toxic political environments because they promoted people into identity-destroying transitions without support. But this isn’t only psychological failure. It’s structural design. Organizations reward executives who “take charge” and “drive results,” language that encodes a bias toward unilateral control over collaborative deliberation. The very behaviors that indicate unprocessed grief are the ones that get celebrated and compensated.

Power is what you reach for when you’re drowning in abstraction and loss. The organizational debt of eroded trust, broken relationships, alliance-building instead of collaboration isn’t a failure of process or skills. It’s unprocessed grief manifesting as destructive behavior.

What I observe in those who navigate this well

The people who make it through these transitions share something I find interesting: they work as if they’re managing one team, the people who report directly to them. Not the team below them. Not peer domains. Not work that now belongs to their reports. Just their team.

This pattern holds at every level. The manager focuses on their direct reports (the ICs). The manager of managers focuses on their direct reports (the managers). The functional leader focuses on their direct reports (the senior managers). The organizational leader focuses on their direct reports and their peers as their working team.

When leaders violate that boundary, managing past their directs or trying to control peer domains, they seem to be using positional power to avoid grief. Staying in an old identity by force. What they’re missing is operational clarity about where their actual leverage is. A manager trying to manage two levels down is working on variables they don’t actually control. Their direct report sits between them and that team. Any attempt to go around them either undermines authority or wastes energy on influence they don’t have.

The leaders who navigate transitions well appear clearer about the actual nature of their work. They identify where their leverage is and stay focused there. But holding that boundary seems to require staying with discomfort when every instinct tells you to reach for the familiar.

What I notice in those who make it through is something that might be called the discipline of non-interference. The capacity to not act when action would provide comfort but undermine others’ development. Leadership as restraint practiced at scale. The hardest transition isn’t learning new skills. It’s learning when not to use the skills that made you successful. Tolerating the space where you’re not the hero, not the expert, not the decider. They hold the boundary as a commitment that seems to force them to discover what contribution means at this level.

What enables someone to stay there long enough to discover new sources of meaning? Those who make it through begin to notice impact in forms they didn’t previously recognize as contribution. They start to see that the abstract work (the quality of a deliberation, the strength of a system, the capability of their team) actually does produce something real, even if their hands never touch it. The question becomes: can you stay in the not-knowing long enough to discover what satisfaction feels like at this level of abstraction?

The expanding scope

What changes at each level isn’t the principle of “manage your team.” What changes is the scope of what you must consider. But here’s the paradox: your scope expands while your leverage contracts.

  • Manager: your team’s work, how it fits into the broader function, coordination with adjacent teams
  • Manager of Managers: the entire functional domain, resource allocation, functional strategy
  • Functional Leader: your function’s role in organizational strategy, dependencies with other functions, how your decisions affect the whole company
  • Organizational Leader: the entire enterprise (market dynamics, competitive landscape, cross-functional tradeoffs, long-term viability)

Yet at every level, you still only directly manage one team. The challenge becomes: How do I make good decisions that account for this massive scope of consideration, when my direct control is limited to developing this small group of people who report to me?

The organization works because everyone is applying the same principle at their level. Each person managing their team, considering their scope, with that same discipline recursing down through every layer.

The reframe

At every level, the people who report to you are contributors. They’re just contributing different things:

  • ICs contribute technical output, functional execution, tangible deliverables
  • Managers contribute team capability, people development, coordinated execution
  • Managers of Managers contribute organizational systems, functional strategy, leadership capacity
  • Functional Leaders contribute cross-functional integration, organizational outcomes, strategic direction

You’re always managing contributors. The nature of their contribution changes, but your job remains the same: enable your contributors to contribute at their level.

And you yourself are a contributor to the level you report to. The manager contributes team capability to the manager of managers. The functional leader contributes cross-functional integration to the organizational leadership team. Everyone is simultaneously managing contributors below them and contributing to the level above them.

You don’t stop being a contributor when you become a manager. You become a different kind of contributor. You don’t stop managing contributors. You manage contributors whose contribution is enabling other contributors. The grief isn’t “I’m no longer a contributor.” It’s “my form of contribution has changed.”

What we’re really asking

Becoming an organizational leader means surrendering decisive control and unilateral authority (the very capabilities that defined functional leadership excellence) and finding meaning in something maximally abstract: the quality of collective deliberation itself. You must derive satisfaction from outcomes you don’t fully control. You must feel competent at work that produces no tangible artifacts. You must find meaning in the deliberative process rather than in decisive action. Your contribution is the quality of your engagement with peers, an identity that only exists in relationship and can’t be fully controlled by any individual.

That’s grief work. Until we name it as such, we’ll keep promoting people into identity-destroying transitions without support, creating the organizational debt of broken relationships and toxic politics, then wondering why smart, capable leaders keep struggling with cross-functional collaboration.

Navigating these transitions requires yet another surrender of what made you successful, yet another grief process for what you’ve lost, and yet another discovery of meaning in increasing abstraction. All while everyone pretends it’s just learning new collaboration skills.

==

 

photo by CHUTTERSNAP

The Columbo Advantage: How cultural narratives create negotiation blind spots

When a culture invests heavily in a particular image of power, the blind spots become predictable. Americans consume Superman mythology daily: Iron Man, Captain America, the archetype where speed, polish, and overt competence signal strength. This creates a perceptual framework. Power looks like this.

In negotiation, this framework becomes a vulnerability.

Superman

Cultural narratives shape how people allocate attention, what cues they privilege, and where they expect power to reside. The Superman narrative teaches what strength looks like. More importantly, it teaches what doesn’t count as strength. That negative space becomes structural vulnerability.

When someone scans for Superman, they’re matching against a template: crisp strategy, decisive posture, visible capability. If you don’t fit, you slide beneath conscious attention. You’re not the negotiator. You’re just there.

The evaluation occurs pre-consciously, in seconds. If you don’t fit the schema, you’re filed as non-threat. That classification is remarkably difficult to revise.

Columbo

Go slow. Talk slow. Speak circuitously. Look unthreatening, and they won’t see you coming. By the time they recognize you’re negotiating, you’re already behind them.

Lieutenant Columbo: rumpled raincoat, apologetic tone, meandering questions. Suspects underestimated him because he violated every cultural marker of competence. By the time they realized what was happening, he’d already mapped their story and found the contradictions.

When you violate the template, you create a classification problem. They can’t place you. While they’re trying to understand what you’re doing, you’re already structuring the game.

Speed, polish, and visible efficiency can be tactical liabilities. When you present as Superman, you confirm expectations. You’re legible, predictable, and easy to respond to.

Someone who understands the narrative their counterpart has internalized gains leverage before any tactic is deployed.


Negotiation begins with the cultural stories that shape what people can see. Walking into a negotiation with Superman narratives running in the background isn’t a personal failing. It’s predictable cultural training.

Predictable patterns create predictable openings.

Notice the perceptual system you’re operating inside. Notice the one your counterpart is operating inside. By the time they see you, you’re already standing exactly where you need to be.

==

Stories from the Room: Use your words, Morgan

Dear Morgan,

There was a moment today that stayed with me. You were speaking with such passion that we all leaned closer to listen. When your words faltered, you paused and said to yourself, “Use your words, Morgan. Use your words.” We heard you speak to yourself, and everyone smiled.

We all recognized that voice: the one we use with our children and the one we sometimes need ourselves when our thoughts are clear but won’t come out right.

You made it simple: you stumbled, you smiled, and you started again. The whole room understood. We waited.

You might have felt embarrassed, yet instead, you showed us how to smile at ourselves. While we often try to sound clever, you sounded true.

Thank you for that moment.

Warm regards,
Richard

==

 

photo by Brett Jordan

Not All Conversations Are Transactions

We treat most workplace communication as if it were transactional: I send a message, you receive it. I deliver information, you process it. Success is measured by whether the exchange occurred.

But some conversations aren’t transactions at all. They’re acts of creation.

When two people genuinely work together toward shared understanding, when they practice what I’ve called “co-responding,” something emerges between them that belongs to neither person individually. This isn’t metaphor. It’s a describable phenomenon you can learn to recognize.

What emerges

Consider what happens when you and another person truly co-respond: you’re not just expressing yourself clearly and listening carefully. You’re asking “Is this what you meant?” You’re offering “Let me see if I understand…” You’re working together, iteratively, to create mutual comprehension.

Two things accumulate in this process:

  1. The effort itself. This is genuinely shared labor. The questions asked, the clarifications offered, the patience extended. This work exists in the space between us; and
  2. The understanding that results. When we successfully co-respond, the comprehension we create isn’t just two identical thoughts in two separate minds. It’s a jointly constructed meaning. You understand what I meant, I understand what you meant, and we both know that we’ve understood each other. This knowing-together exists between us.

These two elements, the accumulated effort and the achieved understanding, form something that persists.

How precedent accumulates

This precedent-setting isn’t abstract. It has tangible effects.

Each genuine exchange establishes conditions for the next. The relational space between you becomes more capable. Communication becomes easier, faster, more nuanced. Not because either of you individually got better at communicating, but because of what you’ve established together through prior exchanges.

You see this when a brief exchange conveys what would have taken paragraphs with someone else. “The Q3 situation” means something specific between you and this colleague because you’ve established that understanding through repeated co-responding. With someone new, you’d need twenty minutes of context.

You can feel the difference. With some people, conversation flows. You pick up threads months later as if no time has passed. Complex ideas require fewer words. You’ve established precedents through genuine co-responding that make this possible.

With others, every exchange feels laborious. You’re explaining the same things the same way for the fifth time. Nothing has accumulated between you. You’ve been talking at each other, and those precedents, of not seeking confirmation, of not offering clarification, yield only transactional results.

You see erosion in real time: someone asks “So what you’re saying is…?” and you cut them off with “No, just do what I asked.” That moment establishes what’s possible next time. And the time after that.

What precedent you’re setting

Here’s what unsettles me: most of us don’t recognize that every exchange sets precedent.

Each conversation establishes what’s possible in the next one. What you do—the questions you ask, the clarifications you seek, the patience you extend—becomes part of what exists between you. What you don’t do—the questions not asked, the assumptions left unexamined, the shortcuts taken—becomes part of what exists between you too.

These precedents accumulate. They don’t reset. The world doesn’t start over each time you have a conversation. You’ve had exchanges before. You either left things well-tended or you left an impression. If you’ve had several of those, they add up to something.

We measure communication by immediate outcomes. Did they understand? Did they agree? Did they comply? These questions treat each exchange as discrete, complete, forgettable.

But if every exchange sets precedent, then there are no neutral transactions. You’re either establishing conditions that make future understanding more possible, or you’re not. The care you take matters. Not because you’re “investing” for some future return, but because what happens now shapes what’s possible next.

Most of what we call “communication” in organizational life creates no precedent worth having. It’s transactional by design. Send the email. Deliver the message. Check the box. Move on.

The irony is that the transactional approach is less efficient. Without accumulated understanding between persons, every exchange starts from zero. You’re perpetually re-establishing context, re-explaining, re-confirming.

Whereas genuine co-responding creates precedent that compounds. The tenth conversation is easier than the first. Not because either of you got better at communicating, but because of what you’ve established together.

What this asks of you

If every exchange sets precedent, then communication isn’t about your eloquence or your message or your persuasiveness.

It’s about what precedents you’re willing to establish with another person.

Which requires time you might not want to spend. Patience you might not feel you have. Genuine curiosity about what the other person means, which is impossible if you already know what they’re going to say.

It requires treating understanding as something constructed together rather than transmitted from one person to another.

Most of all, it requires recognizing that the question isn’t “Did they get my message?” but “What are we establishing together?”

Not all conversations are transactions. Some are acts of creation.

The question is: which are you practicing?

And what becomes possible, or impossible, because of it?

==

 

photo by Tatiana P

Intellectual loneliness

Part I

Intellectual loneliness isn’t about wanting deep talks. It’s about noticing how few people can stay with complexity.

You start to see that most conversations aren’t about understanding. They’re about securing a feeling of being right. You watch people build entire worldviews from headlines, vibes, and whatever their algorithm served that morning. You hear the silence that follows when you say something that doesn’t fit neatly into their script.

It’s not arrogance. It’s fatigue, from constantly translating your real thoughts into something safer, smaller, more palatable. From knowing that nuance ends more conversations than it begins.

No one tells you this part: once your mind stretches, it never contracts. The old forms of talk (habitual, performative, eager for certainty) stop feeling like connection. They start feeling like exile with company.

You stop looking for the clever, the informed, the impressive. You start looking for those still capable of wonder. People who haven’t traded curiosity for coherence. Minds that don’t flinch when a thought refuses to resolve.

Here’s what makes it worse: even when you name intellectual loneliness, people try to understand it for you instead of with you. They explain your experience back, as if you need help understanding what you just said. They analyze your framing. Compliment your articulation. Offer adjacent thoughts.

“What you’re really saying is…”

“This reminds me of…”

Each move translates your thought into their vocabulary, making it legible instead of letting it stay strange.

And then they solve it. They treat the loneliness as a bug to fix rather than a symptom of the shallowness that created it. They offer strategies for “dealing with” intellectual isolation instead of presence inside complexity.

Both moves erase you while pretending to engage. They perform comprehension while missing the point. And now you’re lonelier than before because they think the conversation happened, but it didn’t. You were translated, managed, solved. Not met.

The fatigue compounds. You name something true and difficult; they explain it back and offer solutions, as if you’d asked to be fixed. And now you’re lonelier still.

In the end, intellectual loneliness isn’t about being too smart for others. It’s about wanting to stay human in a culture that rewards the opposite. It’s wanting to think with someone instead of being understood by them. It’s the exhaustion of watching even that desire get turned into another problem to solve.

Part II – What Was Left in the Inkwell

I thought I was done with intellectual loneliness. But it wasn’t done with me. I kept noticing the small violences of translation, the daily courage it takes to stay complex, the hunger for a different kind of belonging. There was more left in the inkwell.

The Cost of Translation

Intellectual loneliness doesn’t begin in the absence of others. It begins in you, in the moment you start editing your thoughts before they reach your mouth.

You learn quickly what lands and what doesn’t. Which ideas get nods and which get silence. And slowly, without deciding to, you become fluent in a second language: the one where your actual thinking gets compressed into something safer.

This isn’t code-switching. It’s thought-switching.

And it’s expensive.

Translation isn’t neutral. Each time you simplify a thought to make it palatable, you start thinking in pre-translated forms. You start having thoughts already shaped for other people’s comfort. Eventually, you stop having certain thoughts altogether. The translation cost is too high, so the thought never forms.

The loneliness becomes internal before it’s interpersonal.

What makes this insidious is how invisible it is. The calibration happens automatically, a micro-adjustment between what’s true and what’s survivable in conversation. You soften a critique. You add a disclaimer. You frame your uncertainty as humility rather than as the actual state of rigorous thinking.

And everyone congratulates you for being reasonable.

But reasonable is often just another word for pre-digested. For thoughts that have already been made safe, stripped of their strangeness, their edges, their capacity to disrupt. What passes for clarity is often just compliance. And the cost of that compliance is that you become unintelligible to yourself.

You forget what you actually think. The gap between your private complexity and your public simplicity widens. And the loneliness deepens because now you’re not just isolated from others, you’re exiled from your own thinking.

This is what intellectual loneliness really is. Not the lack of smart people around you, but the slow disappearance of your own mind under the weight of making it tolerable to others.

The Courage to Stop

At some point, you have to decide: Do I keep translating, or do I stay here?

Staying sounds simple. It’s not.

Staying means letting your thoughts remain unresolved when every instinct says to wrap them up neatly. It means saying “I don’t know yet” in cultures that mistake certainty for competence. It means refusing to collapse complexity into the binary, the branded, the actionable, even when that refusal is read as weakness, confusion, or worse: a lack of conviction.

Nuance isn’t a personality trait. It’s a practice. And it requires courage because the world punishes you for it.

You’re called indecisive when you’re actually being thorough. You’re accused of “bothsidesism” when you’re trying to hold contradiction without resolving it prematurely. You’re told you’re overthinking when you’re just thinking. The pressure to land, to have a take, to be useful: relentless.

Staying in nuance becomes an act of resistance.

Not the performative kind. The quiet kind. The kind where you simply refuse to simplify what shouldn’t be simplified. Where you let a question remain a question. Where you allow your thinking to move through ambiguity and discomfort without rushing to the exit.

Nuance has no social reward. Certainty gets retweeted. Clarity gets applause. Nuance gets you labeled as evasive, academic, detached. People stop inviting you to weigh in because they know you won’t give them the clean answer they want.

What they don’t see is that staying in complexity isn’t neutrality. It’s not fence-sitting or moral cowardice. It’s the refusal to let truth be crowded out by the need for comfort. It’s choosing accuracy over applause. And it costs.

It costs relationships with people who need you to be simpler than you are. It costs opportunities in spaces that reward hot takes over hard thinking. It costs the easy belonging that comes from agreeing quickly and loudly.

But here’s what you gain: you get to keep your mind.

You get to think thoughts that don’t yet have names. You get to follow an idea into uncomfortable territory without apologizing for the journey. You get to be wrong in interesting ways instead of right in boring ones.

And every so often, you meet someone else who’s also refused to collapse. Someone who can stay in the mess with you. Someone who doesn’t flinch when a thought refuses to resolve. Someone who understands that thinking with someone means staying present to difficulty instead of managing it away.

Courage isn’t intellect or patience. It’s refusing to abandon yourself for someone else’s comfort.

Belonging, Redefined

What’s left isn’t loneliness. It’s something else.

The old model of belonging was built on sameness. Shared beliefs. Aligned values. Common conclusions. You belonged because you agreed, because you fit, because your thoughts didn’t ask too much of anyone else.

But that kind of belonging was always conditional. It required you to stay small, stay legible, stay safe. And the moment your thinking stretched beyond the agreed-upon boundaries, you were out.

What becomes possible when you refuse that contract is a different kind of kinship, based on the willingness to stay in the uncertainty together.

This is what it means to think with someone instead of being understood by them.

Being understood is passive. It’s someone receiving your thought, processing it, nodding. It might feel good, but it’s not generative. It doesn’t create anything new. It’s recognition, not collaboration.

Thinking with someone is active. It’s two minds staying present to a question neither of them can answer yet. It’s the willingness to be changed by the conversation, to let the thought move in directions you didn’t anticipate, to sit in the productive discomfort of not knowing where you’ll land.

You need those who can think beside you, without needing to resolve the tension.

This kind of belonging is rare because it asks more of people. It requires presence instead of performance. Patience instead of productivity. The ability to sit with someone in their unfinished thinking without trying to finish it for them.

But when you find it, even once, the loneliness shifts.

Not because it disappears. But because you realize the loneliness was never about being alone. It was about being met with management instead of presence. With solutions instead of companionship. With explanations instead of exploration.

The people who can stay don’t make the loneliness go away. They make it bearable. For a few hours, or a few minutes, you get to stop translating. You get to let your thoughts stay strange, unwieldy, unresolved. And instead of shrinking under the weight of someone else’s need for clarity, you feel your mind stretch in the presence of someone who isn’t afraid of the stretch.

That’s the belonging that matters, built on mutual willingness to stay open to complexity. To not foreclose on difficulty too quickly. To honor the slowness that real thinking requires.


 

The loneliness isn’t a problem to solve. It’s a signal. It tells you when you’ve wandered too far into translation, when you’ve made yourself too small, when you’ve traded your complexity for the comfort of being easily understood.

The path out isn’t about finding more people or better conversations. It’s about stopping. Refusing to compress what shouldn’t be compressed. Having the courage to stay unresolved when resolution would be dishonest.

Belonging is the shared commitment to remain in difficulty together. To think with instead of at or for. To let the questions stay open and the thinking stay alive.

The loneliness doesn’t disappear when you do this. But it changes shape.

It stops feeling like exile and starts feeling like discernment. You’re not isolated because you’re broken or too difficult or incapable of connection. You’re lonely because you’ve refused to abandon your own mind. And that refusal, costly as it is, is also what makes real contact possible.

Because the people who can meet you there (the ones who don’t flinch at complexity, who don’t rush to resolution, who can sit with you in the unfinished thinking) are looking for you too.

Not to fix your loneliness. Not to explain it back to you. But to think with you. To stay with you. To build something together that doesn’t yet have a name.

They’re out there, waiting for someone who won’t make them translate.

And that’s enough.

==

 

Tools Are Never Just Tools. That Includes AI.

The tech industry isn’t just providing solutions in search of problems. It’s reshaping our understanding of what a problem is—and what it means to solve one—in ways that fit the tools it can profitably offer.

We often stop at the surface: the belief that every human challenge has a technological fix. But that belief is only the entry point.

First, there’s the quiet assumption that Silicon Valley not only has the means to solve problems, but the right to define them for the rest of us. Whose definition of “problem” are we working with?

Then, deeper still, there’s the logic of the market: the need to create new problems in order to justify new tools. Innovation, under this view, is less about discovery and more about manufacturing demand.

And at the heart of it all: the reshaping of human experience itself. A world where our ways of thinking, working, and relating must adjust to the logic of the tools—rather than the other way around.

This isn’t new.

Echoes from the Past

Fifty years ago, well-meaning American volunteers traveled to rural Mexico to “help.”

They brought ideas, energy, and middle-class assumptions. They believed they were modernizing communities, solving problems. But they imposed values that didn’t fit, created dependencies they didn’t see, and failed to listen to the people they came to serve.

The parallels now:

  • Tech workers building AI systems they believe will help humanity.
  • Imposing Silicon Valley values—efficiency, scale, optimization—on complex human problems.
  • Creating new dependencies in the name of progress.
  • Operating at a distance from the people most affected by their tools.

The logic hasn’t changed. Just the scale, the speed, and the rhetoric.

No Tool Is Neutral

You hear it often: “But they’re just tools.”

A casual shrug. As if that settles the matter.

But tools are never just tools.

Every tool carries assumptions—about the world, about what matters, about what needs fixing. A hammer assumes something needs hitting. A spreadsheet assumes life can be modeled in rows and columns. An AI system assumes something should be predicted, optimized, or automated.

These aren’t neutral starting points. They’re embedded ways of seeing.

Tools reflect choices—often invisible—about what counts as intelligence, which outcomes are desirable, whose data is worth collecting, whose voice gets heard.

And once introduced, tools don’t just sit there waiting to be used. They reshape the environment they enter.

Workflows bend to fit the tool. Expectations shift. Entire job roles get redefined. Soon, the way things could be is forgotten—because the tool has made a particular way of working feel inevitable.

Think of the smartphone. Not because the phone itself was some flawless leap forward—but because the world reorganized itself around its presence.

The pattern:
A tool arrives.
We adjust.
The adjustment creates new expectations.
Those expectations drive the need for more tools.
The room for real choice shrinks.

McLuhan, Revisited

Marshall McLuhan: “We shape our tools, and thereafter our tools shape us.”

But it’s not just a one-time shaping. It’s recursive:

  1. We build tools that reflect our worldview.
  2. These tools reshape how we behave, work, and relate.
  3. Our new behaviors lead us to build more tools.
  4. Which shape us further.

Each loop tightens the fit. Each cycle reduces friction—until the tool feels natural and the world it creates feels inevitable.

What changes everything now is speed. McLuhan observed cultural shifts over generations. Today, our behaviors are reshaped in months. Ecosystems, industries, even our attention—redesigned in real time.

The Pattern

When power wears the face of help, when solutions are offered without asking the right questions, when tools redefine what it means to be human—that’s when we need to pause.

Not to reject the tool outright.

But to ask: What values does this tool assume? What kind of person does it reward? What ways of being does it make harder?

Tools shape us. But we get to notice. We still have that responsibility.

Even—especially—when the tool says it’s here to help.

AI as the Latest Iteration

If this pattern has played out before, AI may be its most potent form yet. Not because it’s evil, but because it’s persuasive. And fast. And everywhere.

AI isn’t one thing. Large language models train us to think in particular linguistic patterns. Recommendation algorithms shape what we see and therefore what we think about. Computer vision systems define what counts as recognizable. Predictive systems encode assumptions about risk and value into consequential decisions.

Each operates differently, each shapes us differently. But they share something crucial: they all arrive with embedded assumptions about what matters, how intelligence works, and what constitutes progress.

AI doesn’t just offer answers. It frames the questions. It encodes definitions of intelligence, appropriateness, value, truth. And then it trains us—subtly, constantly—to match those definitions.

It’s easy to mistake AI for a neutral force. But AI systems are trained on data that reflect specific histories, specific cultures, specific blind spots. They’re designed to optimize, predict, and automate—as if those are self-evidently desirable things.

They aren’t.

And like the missionaries of progress before them, AI tools arrive not just with solutions, but with assumptions about what needs solving, how it should be solved, and who gets to decide.

The risk isn’t just bad code. It’s that we begin to see ourselves—our choices, our relationships, even our thinking—through the lens of what the system can recognize. And in doing so, we shrink ourselves to fit.

==

photo by Doug Vos