--- title: "Not Disturbing Someone Is Not Automatically Considerate" author: "Shawn Jiang" lang: en date: 2026-09-17 canonical: https://tplog.dev/en/essay/not-disturbing-is-not-automatically-care/ translations: ja: https://tplog.dev/ja/essay/not-disturbing-is-not-automatically-care/ zh: https://tplog.dev/zh/essay/not-disturbing-is-not-automatically-care/ --- # Not Disturbing Someone Is Not Automatically Considerate Japan Airlines has an advertisement called [*Art of J*](https://www.youtube.com/watch?v=q80BDbXgu7Q) that runs for about three and a half minutes. It is divided into three chapters. The second is titled “Privacy,” with the Chinese subtitle 「私密空間」. In business class, a man sits with his head lowered, folding small squares of paper that range from yellow to red. One by one, they become cranes, then a forest, then a maple tree. The passenger beside him is reading. A flight attendant pours wine without interrupting him. The words on the screen read: “Let nothing disturb you. 不讓任何事情干擾你.” The advertisement presents freedom from interruption as the highest form of intimacy. A person can disappear into something very small, and no one calls him back. Here, privacy feels less like solitude than protected attention. You do not have to perform constant availability. Choosing not to enter that space can be an act of care. Someone is doing something that requires sustained attention. At that moment, even asking “Is there anything else you need?” is itself an interruption. He has to put down the paper, look up, give an answer, and then find his place in the fold again. Staying out of his attention gives him room. Not every intermediate moment is worth calling someone back from. But this is not automatically care. Not disturbing someone is one way to care for them, not the highest principle. We cannot see whether the man folding paper ever wants to speak. An advertisement will not show the other side: when no one asks, reminds, or interrupts, who bears the cost of voicing a need? Taken too far, restraint becomes indifference. The person being served may even feel that speaking up would spoil the refinement of the experience. Silence is not the same as consideration. When service is hidden from view, the labor behind it disappears too. The same fork appears in sentences, products, and Agents. The question is not whether everything has been said, but whether to enter the attention someone else is already using. When I write, I sometimes remove a qualifying sentence. All it did was say where a judgment applied. Without it, the article is cleaner, and the reader does not have to be pulled along by the author. But if what is missing is exactly the boundary the reader needs in order to take the next step, they can only read what remains as a stronger conclusion. The sentence does not interrupt them, but it leaves them to complete the meaning. Sometimes writing has to press a point. Sometimes it has to make the reader uncomfortable. That intrusion is not discourteous. It takes the burden back from the reader. When I build products, I also tend to treat notifications as noise and remove them. One less pop-up makes for a cleaner interface. Some people simply want to finish what they are doing without being asked for confirmation again and again. But suppose their permission has expired and the action never actually took place, while the interface remains quiet. The user thinks it is still in progress. Ten minutes later, they check and discover that nothing happened. The product did not disturb them. They saw fewer pop-ups, but paid for it by having to investigate on their own. When I work with an Agent, I may hand it a long-running task and hope it will not call me back for every small question. What I want is a stretch of attention that remains unbroken. One common outcome is that the Agent gets halfway through and reaches a point only I can decide: whether to change a public API, for example, or whether to delete a file that people still use. It does not ask. It works around the issue or stops there. When I return hours later, I find that the work is no longer on its original path. The Agent did not disturb me. But discovering the blockage, reentering the context, and supplying the missing decision are still my responsibility. Too many notifications and people turn them off. No notifications at all, and the one decision that only a person can make may sink to the bottom. From the outside, not disturbing someone and neglecting one's responsibility can look much the same. Once the business-class cabin, the paper cranes, and the maple leaves are stripped away, there is still one question to ask: does staying out of someone's attention actually reduce their burden? If it only looks more restrained and more polished, it is merely atmosphere. Sometimes a product must put that one decision in front of a person. Sometimes an Agent must interrupt you. The standard is not whether it resembles refined restraint, but whether the other person's situation is better as a result. Protecting someone's attention and shifting the cost of speaking up onto them both look like noninterference from the outside. Each time we decide whether to enter someone else's attention, perhaps all we can ask is this: by staying out this time, are we reducing their burden, or leaving them to discover alone that they are already stuck?