Work That Isn't Named

Hi readers,

As I continue to refine how I write about Lasting Work, I do know that I want to examine how systems and organizational structures reflect the current culture or are embedded in it.

This leads me to the male loneliness crisis that we’re seeing in headlines everywhere (podcasts, op-eds, think pieces). And, I keep wondering: what does this look like at work? Who’s affected, and who’s doing something about it?

Instead, I reached a different question:

How is relational and socialization labor distributed in organizations, and what are the structural conditions under which this labor remains invisible or uncompensated?

It’s a pattern I recognized from my own experience and observations. The loneliness conversation points to something real. But I think it’s missing a piece: the labor that creates connection in the first place. Who does it? Where does it live? And why doesn’t it show up anywhere official?

This essay is about that labor. The work that isn’t named.

Enjoy,

Kristina

Most organizations say they value collaboration, ownership, and professionalism. That language appears everywhere — in values decks, performance reviews, onboarding documents, and all-hands on meetings. It sets expectations for how work should feel and how people should show up.1

At the same time, many people inside those organizations feel worn down in ways that are hard to explain. They aren’t necessarily disengaged or unmotivated. They’re doing their jobs, often well. And yet the work requires more effort than it seems to.

Organizations usually frame the tension as a personal problem. Maybe people need to communicate better. Maybe they need to be more proactive. Maybe they need stronger boundaries or better time management. These explanations are familiar because they’re convenient. They offer a way to address discomfort without questioning the structure of the work itself.

But there’s another explanation that’s easier to miss, precisely because it doesn’t point to any one person at all. A great deal of modern work functions only because someone is quietly compensating for systems that were never fully designed, which is essential for organizational stability and continuity.2

Once you start noticing this pattern, it shows up everywhere.

Projects move forward because someone remembers that and never wrote it down. Meetings stay productive because someone reframes a poorly worded comment before it escalates. Decisions land because someone anticipates how they’ll be received and adjusts the message in advance. Confusion doesn’t spiral out of control because someone intervenes early, informally, and without recognition.

What’s striking is not that this work exists, but how quickly it becomes expected. Over time, people learn that competence at work isn’t just about completing tasks. It’s about translating expectations, smoothing rough edges, and absorbing ambiguity so others don’t have to.

None of this is accidental. It’s learned behavior that sustains organizational stability, and while it rarely appears in job descriptions or performance metrics, it’s essential for maintaining continuity.

Because this labor is largely invisible, organizations tend to misdiagnose the problems it’s quietly solving. When friction surfaces, people often frame the response in terms of individual improvement: better communication, stronger ownership, more initiative.

These responses sound reasonable. In many cases, they’re even well-intentioned. But they share a common effect: they shift responsibility away from the structure of the work and onto the people navigating it.

Instead of asking why expectations are consistently unclear3, the question becomes: why didn’t someone ask the right clarifying questions? Instead of examining how decisions are made and communicated, the focus shifts to how well someone received those decisions. Rather than redesign processes, leaders ask people to adapt more skillfully to those already in place.

Over time, this work changes from something you choose to do into something others expect from you. Not formally assigned, but quietly relied upon. And because it’s never named, it’s never fully supported.

This dynamic remains so persistent in part because most organizational systems fail to register this kind of labor. Performance metrics track outputs, not judgment. Documentation captures steps, not interpretation. Org charts show authority, not influence or dependency.

As a result, the system looks stable from the outside. From the inside, it’s being held together by effort that doesn’t show up anywhere official. When people carrying this load burn out, disengage, or leave, leadership often describes it as unexpected. For the people doing the work, it rarely is.

What’s missing isn’t just visibility but also a sense of validation. When this labor is visible, it can be distributed, supported, or designed out. When it isn’t, it simply accumulates.

Designing work differently starts with making invisible labor visible.

Where does ambiguity show up again and again? Who absorbs it?

Which decisions require translation every time?

What work is essential but unofficial?

These questions don’t lead to quick fixes but push organizations to confront how much of this work has been quietly outsourced to individuals and mislabeled as professionalism or resilience, prompting structural change.

When organizations take this work seriously, something changes. Clarity replaces heroics. Ownership becomes explicit instead of assumed. Invisible labor is either shared, supported, or designed out altogether.

There is real tension here, and it’s work naming. The moment you try to formalize this kind of work, you risk flattening it. Turning it into a checklist loses nuance. Turning it into a role risks undervaluing it. Leave it informal, and it disappears again.

There is no perfect solution. But refusing to acknowledge the problem guarantees the worst outcome: sustained effort without recognition, authority, or relief.

Workers often experience this as loneliness, but the feeling should be attributed to the individual. It’s structural. It comes from carrying responsibility without power, from being relied on without being resourced, from knowing how the system actually works while pretending it works as documented.4

That distance doesn’t just separate people from leadership. Over time, it separates them from the work itself.

Work ends up like this, not because people are careless, but because systems evolve faster than they’re redesigned. Informal fixes harden into expectations. Adaptation becomes a substitute for intention.

Eventually, everyone pays for it.

Lasting work doesn’t rely on quiet heroics or unspoken effort. It doesn’t depend on a few people holding everything together behind the scenes. It is designed to make responsibility visible, to reduce the need for constant translation, and to acknowledge the full shape of what it takes to function.

When work only “works” because someone is absorbing the system’s failures, that isn’t resilience.

It’s deferred design. Organizations overlook the hidden work that sustains them, risking long-term instability and inefficiency if left unaddressed.

And deferred design always comes due.