They must be held, occupying both hands
Aliases: hands occupied · grip burden · controller occupancy
What it is
Someone needs to scratch a nose, lift a cup, or peel the headset off the bridge of the nose — and each hand is already wrapped around a block of plastic. Handheld controllers occupy both hands: pointing and buttons are available only while the grasp is maintained. Put them down and six-degree-of-freedom input vanishes with them; refuse to put them down and every real-world job that needs fingers has to wait.
Occupancy is not fatigue. Fatigue is the physiological bill for holding an arm up. Occupancy is the hand being seconded to a tool, so the same hand cannot also do another grasping job.
Why it happens
A controller stays alive only while it stays in the palm. A power grip locks thumb and fingers onto the shell so the keys remain reachable. Dual-wield is the default: one brick per hand, so each hand has six degrees of freedom. The hands stop being parts of the body and become stands for devices.
Every put-down and pick-up is a mode switch. Tracking drops, the origin may drift, the user has to find the keys again. That cost is high enough that people will keep holding the controllers while they hunt-and-peck a physical keyboard, steady a chair, or open a door. Even adjusting the headset — shifting the foam, wiping fog, tightening a strap — becomes a search for a place to park the hardware. The tool is not absorbed into the hand; the hand is absorbed into the tool.
Studying it
Do not stop at selection speed. Insert tasks that requisition the hands: sip water, type a few characters on a physical keyboard, reseat the headset, then return to the virtual task.
Independent variables: one controller versus two, presence of a wrist strap or a magnetic dock, whether the inserted task may free one hand. Dependent variables: time to finish the inserted task, drops and misplaces, error on the first action after return, a rating of “my hands were taken,” the rate at which people choose a one-handed mode.
Watch the seconds between put-down and pick-up. Whether the system hides the virtual hands, freezes them, or snaps them to the hip after tracking loss changes how willing people are to let go. A protocol in which both hands stay on the devices for the whole session will never surface occupancy.
Where it stops holding
A one-controller design occupies only one side; the free hand can still manage real objects, at the cost of unmatched six-DoF on that side. A wrist strap turns “cannot put down” into “putting down means fishing it back.” Conflict is sharpest at a desk where a keyboard and mouse already sit in reach; standing, with no real object that needs a hand, occupancy is almost invisible. Users who already operate one-handed are excluded by a dual-wield default, not given an extra channel. Children’s hands fill the shell; once the palm is occupied, no spare finger remains for a second job.
Applying it
- Ship a one-handed path through the core loop; do not write every action as requiring two controllers.
- Give the controller a put-down location that has a tracking meaning: a magnet, a hip dock, a desk rest. On release, the virtual pointer should enter an explicit idle, not drift.
- Do not schedule don/doff, lens wipes, or drinking inside a passage that demands continuous dual grip.
- Prefer speech or a nearby physical keyboard for text, rather than forcing people to peck virtual keycaps while still holding the devices.
- How to check: insert three real jobs into a complete task — a sip of water, reseating the headset, typing one’s name on a physical keyboard. Count how often a controller is stuffed under an arm, held in the teeth, or dropped. Each incident is occupancy the design failed to absorb.