A button pressed often cannot sit somewhere that forces the arm above shoulder height

What it is

If an interaction gets triggered repeatedly within a single session — a frequently-used button at the top of a nav bar, a floating gesture that needs to be summoned often — that high-frequency action cannot be placed somewhere that requires raising the arm above shoulder height to reach it. This is the design redline that everything about arm-raise fatigue ultimately converges on, and it's distinct from an occasional, one-off overhead action.

Why it happens

A single overhead action, even one long enough to produce noticeable fatigue, carries limited cost if it isn't repeated — the muscle has ample time to recover. High-frequency repetition compresses the recovery time between actions, so the load hasn't fully dissipated before the next static or near-static hover begins; what the body actually bears is a stacked load, not an isolated one-off. Overhead posture is also the heaviest-load angle range to begin with, so combining high frequency with a high-load angle is the fastest route to discomfort or outright rejection of the interaction.

Studying it

This boundary is supported by exposure-response research in occupational health on overhead work: associations between long-term jobs requiring frequent overhead reaching (certain assembly or stock-picking tasks) and the incidence of shoulder injuries (rotator-cuff-related problems, for instance) have been observed repeatedly. That evidence supports treating "overhead plus high frequency" as a combination to be proactively avoided, rather than something to fix only after users complain.

Where it stops holding

This redline targets high-frequency, repeated actions. If a given function is triggered only rarely — a one-time setting, an infrequent emergency action — the accumulated load stays limited even if it sits above shoulder height, and it falls outside what this rule is meant to constrain. Banning every overhead position outright would over-restrict layout freedom.

Applying it

• Measure the actual trigger frequency of each interaction target in the interface, and constrain the highest-frequency ones to at or below shoulder height, reserving above-shoulder space for low-frequency actions only.
• For existing high-frequency overhead actions, provide an equivalent lower alternative (voice, a mirrored trigger zone lower down) rather than relying on telling users to "use it less."
• Verification: from real usage logs, tabulate each interaction target's average daily trigger count against its height, and plot frequency against height. Any target landing in the "high-frequency plus overhead" quadrant goes on the must-relocate list; work through it item by item and re-check the resulting distribution.

Related

• Same group: A8.19.1 unsupported arm-raise fatigue sets in within tens of seconds · A8.19.2 fatigue accelerates jointly with elevation angle and duration · A8.19.3 perceived fatigue lags physiological fatigue · A8.19.4 short usability tests miss this problem
• Nearby: A8.25 reach envelope and range of motion · A8.22 repetitive strain injury
• Search terms: overhead reach · repetitive overhead work · shoulder injury risk