Offering voice options does not cancel the default
Aliases: TTS choice architecture · default stickiness · voice menu
What it is
A settings menu with male, neutral, and celebrity voices does not cancel what the factory female voice is already doing. Options are a capability on a menu. The default is what is actually heard when no one chooses. In choice architecture, the default carries most people. What culture repeats is also the unaltered voice — unboxing, ads, the speaker in someone else’s kitchen. Shipping options can be written up as “we have already gone neutral.” What they do not cancel is the default’s effect. This card is about choice architecture, not how a default female voice binds role to gender (that is the binding), and not how to answer abuse.
Why it happens
Defaults stick: they are read as a recommendation, and changing them requires discovery, comparison, and the risk that “it will work worse from now on.” Voice gender is also a setting most people never treat as a task — lights and Wi-Fi force people into settings; voice gender does not. The distribution of what is heard in the field therefore hugs the factory value; menu length barely enters that distribution. Ads and packaging keep demonstrating the default, so people who do not even own the device still learn “who the assistant is.” Options can even backfire: a longer menu looks like the problem is solved, and review of the default gets skipped. Only a forced choice (pick one at unboxing, nothing pre-ticked) pulls the distribution off the factory value. A skippable “pick a voice?” still dumps most people onto the pre-ticked one.
Studying it
Compare three unboxings: female pre-ticked, changeable; nothing pre-ticked, must pick; rotate by day until pinned. Dependent measures: gender distribution of the voice still in use after a week, and reach rate to the setting. Do not report “how many voices we offer” as the result — that is menu length, not the heard distribution.
In the field, sample new devices without steering people into settings, and record the timbre that actually speaks in week one. A lab that walks everyone to the settings page will overstate option use. Content analysis checks whether ads and retail demos still use the factory line.
Where it stops holding
Accessibility users who depend on one familiar timbre should have that choice override the default, and the override must stick across version updates rather than snap back to factory female. When only one high-quality timbre exists, the menu is empty and the problem returns to default binding, not to choice architecture. Households that pin different voices for different members need the device to remember the mapping; it must not fall back to factory on every wake. Writing “there is a male option” as having handled gender hides the stickiness this card is for inside a menu.
Applying it
- Do not pre-tick at unboxing. Force one choice, or rotate until pinned. Skip must not equal female.
- Do not put female first on the options page as “recommended.” Sorting and labels must not imply that waiting to serve fits one social gender better.
- Ads, packaging, and retail demos should show the choice, in line with the field default — not only the factory line.
- How to check: new users, no prompt to open settings, one full week, then the timbre distribution that actually spoke. If it still piles on factory female, options have not started work. Also count how many people never opened the voice page — that slice lives only in the default.
Related
- Same group: M4.11.1 A default female voice binds the assistant role to gender · M4.11.2 How the system answers abuse encodes a stance
- Nearby: O1.04 Privacy by Default · M2.05 Persona · M3.01 Naturalness and Intelligibility of Synthetic Speech
- Search terms:
default effect·choice architecture·TTS voice options