============================================================ nat.io // BLOG POST ============================================================ TITLE: The Loneliness of Responsibility DATE: July 27, 2026 AUTHOR: Nat Currier TAGS: Leadership, Responsibility, Engineering, Personal ------------------------------------------------------------ Late-night incidents have a particular kind of intimacy. Voices arrive from bedrooms, kitchens, hotel rooms, and dark offices. Nobody looks entirely like the role they perform during the day. The system is failing, information is incomplete, and a small group of people must become coherent before the situation does. I know what people need from me in those moments. They need a voice that does not accelerate the fear. They need the decision framed clearly enough to act. They need someone to separate what is known from what is assumed, protect the people doing the work from unnecessary interruption, and accept that a decision made with partial information may still become the decision for which someone is accountable. I can do that. I have done it through outages, escalations, hiring crises, difficult feedback, high-value technology decisions, and organizational moments where uncertainty could not be postponed until everyone felt ready. Eventually, the incident ends. The status stabilizes. People disconnect one by one, relieved and exhausted. The room becomes quiet. My mind does not always leave with them. It reviews the decision, searches for what we missed, anticipates the questions that will arrive in the morning, and calculates how much uncertainty should be shared with whom. The calm that helped the group function was real. So was everything the calm had contained. The strangest part is that a night like this can leave a person surrounded by gratitude and completely alone. > **Thesis:** Being the strongest person in the room can become surprisingly lonely because competence teaches people to depend on you at the same time it teaches them to stop asking whether you are all right. > **Why now:** Organizations are asking fewer leaders to absorb more uncertainty, while reliability still makes its own human cost easy to overlook. > **Who should care:** Founders, CTOs, senior engineers, managers, parents, partners, and anyone who has become the person everyone calls when something difficult happens. > **Bottom line:** Responsibility becomes more durable when leaders create appropriate places for their own uncertainty and build enough judgment around them that consequence can be carried together. [ Competence changes what people ask of you ] ------------------------------------------------------------ The transition happens slowly. At first, people ask whether you can solve a problem. Then they ask you to solve more important problems. Eventually, they stop asking whether you can and begin arranging the organization around the assumption that you will. This is how trust is built. It is also how a role can harden around a person. When you repeatedly remain calm, people experience you as calm. When you make difficult decisions, they experience you as decisive. When you absorb an escalation without spreading panic, they experience you as stable. The visible behavior becomes the whole available model. Nobody is necessarily being careless. They may respect you, appreciate you, and care about you deeply. But competence changes the direction of attention. People bring you what they cannot carry. They ask what should happen, whether the risk is acceptable, how to respond, and what you need them to do. They ask fewer questions about what happens inside you while you answer. Leaders help create this pattern. I certainly have. I learned early that visible uncertainty could amplify uncertainty in everyone else. In some situations, that is simply true. If a leader reacts chaotically during an outage, the team has to manage the system and the leader. If an executive speaks carelessly about a threat, people may spend days interpreting fear instead of solving the problem. So I became good at metabolizing. Concern entered. A decision left. Ambiguity entered. A plan left. Criticism entered. Context and direction left. This ability is useful. It can be generous. It can create the room in which other people do their best work. It can also teach everyone, including the leader, that the process has no cost. [ The absorber still holds the pressure ] ------------------------------------------------------------ By the absorber, I mean the person expected to take in uncertainty, criticism, and fear, then return decisions that other people can use. Every organization has versions of this role. Sometimes it belongs to a manager. Sometimes it belongs to the senior engineer who can make an incident legible. Sometimes it belongs to the founder who translates an unstable market into a coherent week of work. In families, it may belong to the person who remembers the appointments, notices the change in mood, anticipates the practical risk, and stays functional when someone else cannot. The absorber often looks strongest at the exact moment they have the least room to process. During layoffs, people deserve clarity, dignity, and as little additional chaos as leadership can manage. The person delivering the message may also be grieving, angry, ashamed, uncertain, or afraid. Those feelings cannot be made the responsibility of the person losing a job. During difficult feedback, a manager may care about the person and still need to say something that will hurt. The manager's discomfort cannot be used to soften the truth until it becomes useless, nor can it be handed to the recipient as a request for reassurance. During an incident, fear may be reasonable. The team still needs prioritization more than a live broadcast of every scenario running through the leader's mind. This is part of leadership. The problem is not that the absorber contains pressure for a time. The problem is having nowhere legitimate for that pressure to go.
Conceptual illustration of a finned copper radiator still glowing in an empty thermal hall after the surrounding ceramic masses have cooled.
I have carried decisions home after the organization had moved on to execution. I have remained mentally inside a conversation long after everyone else had reasonably returned to the rest of their lives. I have scanned for the next problem because being surprised felt like a failure of responsibility. This resembles the pattern I wrote about in [I Mistook Anxiety for Personality](/blog/i-mistook-anxiety-for-personality), but it is not the same argument. That essay examines the internal engine that can turn curiosity, preparation, and care into continuous vigilance. This one is about what happens socially when reliability becomes a role. Even a person with no unusual anxiety can become isolated when a system depends on their ability to receive what other people cannot yet hold. The loneliness is not the absence of people. It is the absence of reciprocal space. You can spend the entire day in conversations, be central to every important decision, and have no conversation in which you are allowed to arrive before the answer has been formed. [ Shielding can quietly become concealment ] ------------------------------------------------------------ Leaders should protect teams from some things. Not every rumor deserves circulation. Not every executive disagreement belongs in the room where engineers are trying to finish a release. Not every possible risk should interrupt people before it becomes probable enough to change their work. Filtering is part of responsible attention. But shielding has a dangerous success condition. When it works, other people experience less chaos. They become more focused and effective. The leader receives positive evidence that absorbing more is helpful. So the boundary expands. The team is protected from uncertainty that it actually needs in order to make good decisions. Senior people are spared the consequence that would help their judgment mature. The leader answers questions before others can feel the weight of deciding. A temporary buffer becomes a permanent design. The organization looks calm because one person is concealing the amount of force required to keep it calm. This is not only a well-being problem. It is an operational weakness. If uncertainty can be processed only by one leader, that leader is a single point of failure. If difficult decisions require one person's emotional stability, the organization's resilience is partly theatrical. If nobody else sees the full shape of risk, nobody else can develop the judgment needed to carry it. I have sometimes called this protection when it was also control. Carrying the burden myself reduced the chance that someone else would mishandle it. It also reduced the chance that they would learn to handle it at all. I remained useful, and the system remained dependent. The hardest leadership lesson in that sentence is that indispensability can feel responsible. It can also feel good. Being needed provides identity, access, and evidence of value. The person everyone calls rarely has to wonder whether they matter. It is possible to resent the weight and protect the arrangement that keeps delivering it. I have had to become more honest about both sides. [ Privilege and cost can be true together ] ------------------------------------------------------------ Leadership has given me extraordinary opportunities. I have been trusted with consequential decisions. I have worked with talented people across countries and cultures. I have had the authority to hire, promote, change systems, allocate resources, and shape environments in which people spent a meaningful part of their lives. I chose these roles. Even when circumstances were difficult, I had forms of agency, compensation, access, and influence that many people did not. Any honest account of leadership's emotional cost has to retain that asymmetry. Responsibility is not something that merely happened to me. I pursued it, accepted it, and often enjoyed it. I would choose much of it again. Naming cost does not turn choice into victimhood. We understand this easily in technical systems. A component can provide enormous value and still require maintenance. A design can be appropriate and still create operational risk. Refusing to observe the risk because the system is useful would not be gratitude. It would be negligence. Human systems deserve the same honesty. A leader can be privileged and tired. Grateful and lonely. Capable and in need of support. Proud of carrying responsibility and aware that the current way of carrying it cannot continue indefinitely. The denial is not noble. It makes the system less observable. I used to believe that acknowledging the personal cost of responsibility weakened the meaning of service. Now I believe the opposite. If I cannot describe what a role requires from a person, I cannot design that role responsibly. If the only acceptable leader is one who has no needs, then we are selecting for concealment rather than strength. The limited research on leader loneliness does not prove that responsibility causes isolation. One [three-wave study of 200 mid-level managers](https://journals.aom.org/doi/10.5465/AMBPP.2019.10232abstract) found that sharing sensitive information upward, with people who held greater organizational power, predicted lower leader loneliness. The same conference paper reported associations between leader loneliness and emotional exhaustion, depletion, and sleep problems. A [2024 study on leadership emergence](https://journals.aom.org/doi/10.5465/AMPROC.2024.21509abstract) found associations among loneliness, lower leadership self-efficacy, and lower willingness to lead. These are conference papers with specific samples and bounded findings. They do not establish that every leader is lonely, that power inevitably isolates, or that disclosure to direct reports is a cure. They do support a distinction I have learned through experience: a person can be highly connected by role and poorly supported as a person. The direction of disclosure matters. Power matters. The existence of an appropriate relationship matters. The absorber needs somewhere to arrive without first converting the pressure into an answer. [ Responsibility follows you across the door ] ------------------------------------------------------------ Professional leadership is only one place this pattern appears. In family life, responsibility can become even less visible because it is braided into love. Partners and parents anticipate. We remember what might be forgotten. We notice a change in tone, prepare for a difficult week, absorb a child's fear, or stay steady when someone we love cannot. The work is ordinary and profound. It does not obey office hours. I have spent parts of my adult life moving from a day in which an organization depended on my judgment into an evening in which people I loved needed patience, attention, and steadiness. They were not asking too much. They were asking for what relationships ask of us. But the body does not maintain separate ledgers. Responsibility accumulates even when every individual claim is legitimate. A difficult decision at work does not cancel a child's need. A family concern does not pause an incident. Love does not make capacity infinite. People who appear capable are often offered less care because care is allocated toward whoever is visibly struggling. This can be reasonable in the moment. The child in distress needs the parent. The engineer facing an unfamiliar failure needs the senior person. The partner having the harder day may need more of the available attention. The problem emerges when the moment becomes the permanent relationship. If one person is always the stable one, instability has nowhere honest to appear. They may begin hiding ordinary needs because expressing them seems like a breach of role. Other people may stop offering support, not from indifference, but because the relationship has taught them that support flows in one direction. Being loved is not always the same as being looked after. That is one of the quietest forms of loneliness I know. [ Vulnerability needs a boundary ] ------------------------------------------------------------ The popular correction to stoic leadership is vulnerability. The word is useful and dangerously underspecified. A leader announcing every fear can create the same problem as a leader denying all fear. In both cases, the team must organize around the leader's emotional state. One produces silence. The other produces instability. Hierarchy does not disappear because the person with more power speaks candidly. If I tell someone whose pay, promotion, project, or job I influence that I am overwhelmed by an organizational decision, they may feel obligated to reassure me. They may suppress their own concern to protect mine. What looks like openness from my side may feel like an assignment from theirs. Bounded vulnerability is different. It means saying what is true at the level another person needs in order to understand reality and exercise judgment. It means admitting uncertainty without exporting responsibility for it. It means naming a mistake without making the injured person comfort the person who caused it. A leader can say that a decision is difficult, that important information remains missing, or that a previous conclusion was wrong. That honesty can increase trust because it makes the actual decision surface visible. It also gives others permission to bring evidence, disagreement, and concern into the room. The deeper processing may belong somewhere else. Peers can understand the asymmetry of responsibility without depending on the same hierarchy. A trusted adviser can challenge the story a leader tells about being indispensable. A partner or friend can care about the person rather than the role, provided the relationship remains reciprocal. Professional support can offer a place where the leader does not need to protect the listener from the material being processed. The answer is not disclosure everywhere. It is no longer requiring one person to contain everything nowhere. [ Delegation is not the same as shared responsibility ] ------------------------------------------------------------- I have delegated many tasks while keeping the responsibility that made the tasks consequential. Someone else prepared the analysis. Someone else led the project. Someone else ran the meeting. But the assumptions, decision rights, risk threshold, and final judgment remained with me. From the outside, work had moved. Inside the system, very little responsibility had. Shared responsibility requires more. People need context, not only instructions. They need authority proportionate to the outcome they are expected to own. They need room to make a decision differently from the way the senior person would make it. They need to experience consequence without being abandoned inside it. This is uncomfortable for the leader because developing judgment includes allowing decisions that are sound and unfamiliar. The leader may see a risk the other person has not weighted correctly. Sometimes intervention is necessary. Sometimes the discomfort is simply the sensation of no longer controlling every path to a result. I am still learning to distinguish those moments. Useful questions help. What decision is actually mine? What information do I have that the other person lacks? Have I transferred the authority required to own the result? Am I intervening because the risk exceeds an agreed boundary, or because another person's method makes me uneasy? These questions do not remove final accountability. In many roles, failure still stops with the leader. They change what happens before failure arrives. When several people understand the risk, can challenge the model, and have real authority to act, calm no longer depends on one person's ability to conceal pressure. The organization can be honest earlier. The leader can be uncertain without making the uncertainty contagious. Other people become strong enough to support the structure rather than merely shelter beneath it.
Conceptual illustration of several bridge towers and cables sharing the weight of one illuminated span across dark water.
[ No one should carry the whole structure alone ] ------------------------------------------------------------ I still expect leaders to be steady. There are moments when someone has to make the call, receive the criticism, protect the team, or hold a line while better information arrives. Responsibility cannot always be distributed evenly, and pretending otherwise abandons the people who trusted someone to lead. But steadiness is not the absence of an inner life. The late-night incident call eventually comes again. The voices are tired. The system is unclear. People look toward the person they expect to create order. What I want now is not to escape that responsibility. I want a different room. I want senior people who can name what they know and what they do not know. I want ownership that has been developed before the crisis, not improvised during it. I want someone else able to challenge my framing, another person able to carry the decision, and a system in which calm is produced by shared capacity rather than private concealment. After the call, I want relationships in which I do not have to arrive as the answer. This requires me to release parts of the identity that responsibility built. I have to let other people be strong in ways that make me less central. I have to admit uncertainty before it has been converted into something impressive. I have to accept support without turning the receipt of it into another task I perform well. That is harder than carrying more. It is also more responsible. Being the strongest person in the room should never mean becoming the only load-bearing person in it. Strength is not measured by how much weight one person can absorb, but by whether that person builds enough strength around them that no one has to carry the whole structure alone.