Making a single action simpler is not a win if it means doing it more often

What it is

When optimizing interaction efficiency, if the chosen approach achieves a simpler single action, a lower learning cost, or a cleaner interface by increasing the number of times an action must be repeated, that optimization is not a genuine efficiency gain in terms of repetitive strain injury — it merely shifts a cognitive or interface-level cost into a bodily cumulative-load cost. This conclusion requires bringing repetition count itself into the definition of "efficiency," rather than judging only by how easy or fast a single action is.

Why it happens

Many common efficiency techniques — breaking a complex action into several simpler steps, replacing one large-amplitude movement with several small repeated gestures, letting users reach a setting through repeated small adjustments instead of one direct input — do genuinely lower the cognitive or motor difficulty of a single action, but they often achieve this by increasing how many times the action must be repeated. If the interaction gets used frequently, that increased repetition directly raises the exposure-frequency risk factor. Even though each individual action looks simpler and takes less time, the cumulative bodily load over the long run can end up higher than the pre-optimization design — it's just that this cost never shows up in a conventional efficiency metric like task completion time.

Studying it

When comparing a design before and after a change, count the number of action repetitions required to accomplish the same goal in addition to the usual task completion time and error rate, and look at both together. If a design completes the task faster but with a noticeably higher repetition count, factor in the operation's actual usage frequency to determine whether the total cumulative repetitions over the long run are also increasing.

Where it stops holding

This conclusion mainly applies to core operations that will be used frequently and repeatedly over the long term. For low-frequency or one-off operations, even if an optimization increases the repetition count of a single instance, the accumulated total exposure stays small and doesn't constitute meaningful risk — there's no need to sacrifice the simplicity of a single action for these.

Applying it

• Add "number of action repetitions needed to complete a unit task" as an evaluation metric for efficiency alongside task completion time and error rate — don't judge a design's merit using only the latter two.
• For high-frequency core operations, prioritize designs that reduce both single-action difficulty and total repetition count at the same time (batch processing, remembering frequently used settings), rather than simply splitting one action into several simpler ones.
• Verification: compare the average daily or weekly total action count between the old and new designs under the same real usage scenario — not just the action count within a single task. If the new design's total repetition count is noticeably higher, re-evaluate whether this "optimization" is worthwhile, or add design measures that reduce the repetition load.

Related

• Same group: A8.22.1 high-frequency small-amplitude movement causes cumulative injury · A8.22.2 frequency, force, posture, and recovery time jointly determine risk · A8.22.3 injury is delayed, and short-term absence of symptoms doesn't mean safety
• Nearby: A8.09 speed-accuracy trade-off
• Search terms: repetition count · efficiency trade-off · cumulative exposure