Body Doubling
If a task that was immovable alone becomes startable the moment someone else is in the room, even someone doing nothing at all, this is the pattern that explains why.
The other person does not help. They do not check the work, set deadlines, or supervise. They might be reading on the couch or sitting on mute in a video call, and yet the cleaning happens, the filing happens, the document finally moves. The community named this body doubling, and it is one of the most widely used and least understood tools in the neurodivergent toolkit. The story usually attached to it is guilt: needing a babysitter to do basic adult tasks. This cluster replaces that guilt with a mechanism. Unlike most patterns on this site, it is not a failure map. It is a working scaffold: an accurate read of your own activation architecture, plus deliberate environment design.
Where it starts for you
The useful question is which channel is live for you. For some it is presence itself: a sister reading on the couch saying nothing, and the kitchen that waited three weeks gets done in ninety minutes. For some it is the witness: announcing three goals in the co-working thread and posting the finished draft at noon, because seen work is what registers as real. For some both channels exist but the costs run high, so doubling with a best friend is two hours of effortless focus and the same format with coworkers is exhausting by minute forty. That is not proof the tool fails, it is the net equation coming out with opposite signs, and the fix is format, not willpower.
And for some, presence does nothing at all. A partner sits with you for the tax return, warm and patient, and nothing happens. That is not a failed attempt at the pattern, it is a different architecture: some starting systems open on interest, not on company, and this was never your tool. One more surprise: body doubling is not only for low-drive tasks. A double's presence can also ease you out of deeply absorbing work, which is part of why the practice is so widespread.
It's not that the filing got interesting. It's that the room stopped being empty.
the reaction we design for
Traits in this cluster
Starting runs on fuel, and this is a machine with parts. Knowing which parts are live for you decides whether the tool works and which format it works in.
The gate: every start has a threshold to cross, and it opens on accumulated signal, not on how much you care. The whole question is what pays the toll.
The inner fuel: interest, novelty, meaning. It is domain-specific by design: it fires for some content and simply does not fire for other content, and valuing a task does not convert into signal for it.
Presence fuel: for some architectures, another person in the room is itself rewarding. Presence alone changes the motivational economics of the task, no help required.
Witness fuel: a separate channel: being seen makes effort register as real, rewarded work. Goal announcements and camera-on focus rooms run on this one.
The net equation: presence pays, but it also charges: decoding, regulating, masking. A session works only while the fuel gained exceeds the cost, which is why the classic format is quiet parallel work with a familiar person.
The limits: the scaffold is availability-contingent. When the person leaves, the task goes back to being hard, not because you failed, but because the fuel left with them. That is a design constraint, not a flaw.
These are the three traits this cluster is built from. Two supply the fuel, and one defines when you need it. Open any card to read it.
The domains it spans
Two domains, one hand-off: the fuel comes from Connection and gets spent in Drive and Energy. That crossing is the entire trick.