Without synced visual or haptic confirmation, people cannot tell which force level they have reached

What it is

With no mechanical notch, the pad does not feel “just crossed into band two.” If the system also fails to mark that crossing with a matching vibration or visible change, people guess. Synced confirmation of force level means a band boundary must be marked in the frame it is crossed, on the hand or in front of the eyes—not as a result after release. Discoverability is whether people know they can push harder here. This is whether, already pushing, they know which band they are in.

Why it happens

Effort sense is coarse and laggy; crossing a software threshold does not mint a mechanical event by itself. Confirmation has to be added: layered haptics (a pulse per band), surface yield, or a visible state of the object (a preview layer). The point is sync: a pulse late of the threshold, and people release before they feel it, or feel it after they have already run into the next band. Visual confirm in another corner of the screen, while the eyes are on a primary task, is no confirm. One identical chassis buzz can say “a force event happened,” not “which band.” Without confirmation people compensate by bottoming, staring at numerals, or giving up on bands—the force channel in name only.

Studying it

Same thresholds, compare no confirm, vision only, haptics only, both, and deliberately shift confirm before or after the threshold.

Independent variables: confirm channel, delay relative to threshold, whether per-band confirms are distinct, whether a primary task occupies vision. Dependent measures: correct stops in the target band, overshoot, early release, whether people can name the current band aloud.

When vision is occupied, vision-only highlight should get clearly worse; that is why confirm belongs on the hand. Making every band the same buzz measures “event or not,” not “which band.”

Where it stops holding

A mechanical second stage of travel is synced confirmation; stacking a motor makes two events. Users with hearing loss miss an audible motor click; confirm must be able to ride skin or vision. When power-saving mutes haptics, force banding should degrade to a single threshold or off, not continue silently. In sun, on-screen confirm dies; in a car, confirm belongs even more on the hand. A safety-critical band that rides only a hint do-not-disturb can clear is no confirmation.

Applying it

• Mark every band boundary with a confirm aligned to the threshold and distinct across bands; default to the hand, vision as supplement.
• Budget delay against a release action; a late confirm is not a receipt.
• When haptics are off, degrade the banding with them.
• Verify: no numerals, vision occupied by a primary task, people stop in a named band. If vision-only is clearly worse, ship layered pulses on the hand. Delay the pulse tens of milliseconds and watch early release and overshoot rise. Mute haptics and confirm that banding is disabled or merged.

Related

• Same group: C10.12.1 A pressure sensor must separate a user’s resting-force baseline from an intentional extra push · C10.12.2 Holding a pressure level continuously fatigues the hand more than holding a position · C10.12.3 How many force levels can be reliably told apart is limited by sensor precision and the stability of human force
• Adjacent: C10.04 Pressure Input · C10.08 Key Travel, Tactile Detent, and Confirmation
• Search: force-band feedback · level confirmation · haptic click