M3.04.3uninterruptible playback feels like loss of controldesignresearch

Uninterruptible playback is felt as loss of control

Aliases: forced listen · locked TTS · cannot stop the prompt

What it is

If playback cannot be stopped, users feel out of control. The car starts reading a long text from a parent while the driver needs the next navigation turn and cannot take the floor; an IVR inserts a forty-five-second promo before the real menu and the only move is to listen. The feeling is not “this audio is long” — length is duration and fatigue — it is “I have no legal act.” A short locked prompt that arrives at the wrong moment is read the same way.

Why it happens

Control in a dialogue is the ability to seize the floor. When TTS is locked, the user is left with waiting. Waiting with no advertised end becomes unknown delay. A voice is heard as an agent; an agent that will not yield turns a tool into a dominant party. People look for control outside the channel: twist volume, mute, hang up, kill in-car dialogue. Those acts are what collapsed control looks like, not a preference about loudness. Even a short prompt, arriving when the user was about to speak, is stored as “it does not listen to me.” Barge-in restores agency; a lock spends trust in the whole voice channel, not only in that sentence.

Studying it

The same prompt: forced listen versus interruptible. Dependent measures: a perceived control scale (items such as “I could stop this”), abandonment, anger incidents, and whether people reach for the volume knob or hang up. Independent variables: prompt duration, whether a skip was announced.

Do not take raised voice after a failed interrupt as the main dependent measure; that is a different mechanism. Telling lab participants “this is the experiment, you cannot stop it” turns loss of control into procedure, and you are no longer measuring a product lock. In the field, look at unexplained promos and message-reading.

Where it stops holding

A once-per-call recording notice required by a regulator should still be skippable on repeat calls. Alarms and hazard phrases may have to finish; then say why, and keep them to a few seconds. A user who turned on “read messages in full” has authorised the lock; it is not the default. Hardware pause on a headset already returns control even when software barge-in is weak. An uninterruptible prompt with a large on-screen Skip is a lighter loss — control moved from mouth to hand, it did not go to zero.

Applying it

  • Promos, introductions, and messages are interruptible by default. Do not lock them.
  • What must finish should say why, stay short, and ship a mute or skip that is felt in about 300 ms.
  • In review, a prompt with barge-in off is a defect unless it has a written safety or legal reason.
  • How to check: how many people twist volume, hang up, or kill voice mid-prompt. That is the control signal. Add a post question: “could I have made it stop.”

Related

  • Same group: M3.04.1 Users must be able to barge in on playback at any time · M3.04.2 After barge-in, keep the playback position
  • Nearby: M3.09 Barge-in and interjection · M3.01 Naturalness and intelligibility of synthetic speech · M4.01 Social cost of using voice in public
  • Search terms: uninterruptible playback feels like loss of control · perceived control · forced listen

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/M3.04.3