Does the Desire to Be Missed Make Teams Fragile?

A short summary of Hattori, K. (2026) “The Desire to Be Missed: Irreplaceability and Leadership in Teams”.

Background

People often want to be the person an organization would struggle without. Managers and mentors encourage members with exactly this message: you are indispensable to this team. And it is true that feeling one’s work matters draws out effort. What this paper shows is that the same feeling may also leave the team fragile.

Organizations normally try to reduce their reliance on particular individuals, that is, to reduce key-person risk. They document procedures, share information, develop successors, and build systems so that work continues when someone is away. Yet employees do not always want to become replaceable. The wish to be missed is also a wish to leave a large void behind. Documentation and handover fill that void in advance.

What the paper does

Consider a team that produces one shared outcome. Each member chooses productive effort and a costly replaceability investment that allows the work to continue in her absence: documentation, information sharing, cross-training, succession preparation.

When a member is absent, the team loses not only the output attached to her but also the coordination that ran through her. Part of that loss can be recovered if she has prepared in advance. What is not recovered is how much she is missed, the void her absence leaves.

Here is the tradeoff. Preparing protects team output when she is away. But it also shrinks the void she would leave and therefore reduces how much she is missed. A member consequently provides enough backup only while her probability of being absent outweighs her desire to be missed.

What it finds

First, the desire to be missed has two faces. On the effort margin it is largely productive: the more a member can contribute, the larger the void her absence would leave, so she works harder. On the backup margin the sign flips. The more she prepares, the less the team depends on her, and the less she is missed. Motivation rises while the team’s capacity to absorb an absence falls.

Whether the motive helps or harms the team depends on how tightly the work is linked. Where an absence mainly removes the absent member’s own output, the gain in effort can outweigh the loss of backup. But in a team where one member’s absence halts the work of several others, the backup she withholds is exactly what the team needs most. As a team grows and dependence spreads, a culture of being indispensable that once served it can start to put it at risk.

The mechanism is sharpest for leaders. A leader is a coordination hub connected to many colleagues, so her absence leaves the largest void. While the desire to be missed is weak, this makes her back herself up most heavily, and the most central member is also the best insured. But if the motive grows strong enough, backup collapses, and the member who would leave the largest void remains at the center with nothing behind her. A leader can be the team’s greatest strength and its largest single point of failure at once.

Furthermore, because abler members leave larger voids, they carry more of both the effort and the backup. They end up doubly burdened, and the less able member can be better off. The moment of departure is especially dangerous: someone taking leave still enjoys the team’s output after returning, but someone leaving for good no longer has that material stake, while the wish to be missed remains. It also follows that members who are rarely absent have the weakest material reason to make themselves replaceable, so their backup is the first to go.

Why it matters

Organizations work hard to make people feel that their work matters and that they are indispensable. This is an effective way to draw out effort. But if people are judged too much by how badly they would be missed, the incentive to make oneself replaceable is blunted. Output and engagement can look healthy while the team quietly loses its ability to absorb an absence, and the bill arrives only when someone is gone. This is not ordinary free-riding: material self-interest alone would leave backup thin but positive, whereas the desire to be missed can drive it to zero. Monitoring and output-based pay therefore do not reach it.

The order of operations matters. Standardize roles first, proceduralize handovers, and make dependence run through systems rather than through particular people. Then tell people their work matters. The foundation comes first and the culture second.

It is also necessary to reward more than effort. Documentation, cross-training, named backups, and the quality of a handover can all be verified, and they can be paid for directly. The reward should be concentrated on the most central roles, where an absence costs the most. A blanket instruction that everyone document their work can leave the most fragile places as thin as before. Departures need their own instruments as well, such as a paid transition period or a bonus tied to a completed handover.

In closing

Nothing in this story requires anyone to behave badly. A team can become fragile simply because its members want to be missed. “We really can’t manage without her” is at once evidence of her importance and a defect in the team’s design. The wish to be missed is not something to be blamed. But it is precisely because people have it that organizations must prepare in advance.

This research was supported by JSPS KAKENHI Grant Number 24K04912.