How far a hand can reach and how hard it can push both vary by percentile

What it is

Beyond static lengths and widths, anthropometric databases carry two further kinds of capability-limit data: the reach a given percentile of the population can achieve, and the maximum operating force (grip, push, pull) they can exert. This leaf is about how these two datasets get turned into design constraints — how far away a control can sit, and how much force it may require — not a re-explanation of why joint range of motion determines reach distance itself, which is a question of motor control mechanism.

Why it happens

These two kinds of data are discussed together because they constrain each other biomechanically: the closer a limb is to the edge of its reach range, the less force it can exert. As the arm approaches full extension, the joints sit at their most mechanically disadvantageous leverage, and the push or pull force available there is far below what the same arm can produce in a comfortable mid-range position. This means "how far away the control sits" and "how much force the control requires" are not two independent design decisions — placing a control that demands substantial force at the edge of the reach envelope effectively asks the user to perform a high-force action in precisely the posture where their force output is weakest, and that combination is itself a common source of design failure.

Studying it

Operating-force data comes from isometric testing with dynamometers and push-pull force gauges, building distribution tables of maximum voluntary force stratified by sex, age, and posture; these tests typically measure a brief peak exertion, not force output after repeated or sustained operation.

Where it stops holding

Standard force tables reflect a single, brief maximal exertion, and cannot be applied directly to scenarios requiring repeated or sustained operation — a control pressed hundreds of times in a shift should have a required force well below the value in a peak isometric table, or it invites cumulative fatigue and repetitive-strain risk. This is a fundamental difference between peak data and sustained-operation data, not something a simple discount on the same table can fix.

Applying it

• Check the control's usage frequency: an occasional, single-instance operation can reference peak force data for its ceiling; a control requiring repeated or sustained operation should instead use endurance/sustained-force data for the target population, set well below the peak table's value.
• Check whether the control's physical position sits near the edge of the user's reach envelope — if so, lower the required operating force further, or relocate the control closer to the body where force output is more favorable, rather than keeping the original force requirement unchanged.
• Verification: measure the actual force the target population exerts using a force gauge while performing the real task at the control's actual distance and posture, rather than applying a generic peak isometric table; for high-frequency controls, additionally measure how force output decays over repeated operation.

Related

• Same group: A11.06.1 Percentile selection and design coverage · A11.06.2 Hand length, finger width, and grip dimensions · A11.06.4 Static dimensions vs. dynamic working dimensions
• Adjacent: A8.25 Reach envelope and range of motion · A8.13 Finger independence and strength
• Search terms: isometric strength · force capability · reach envelope