
On Head
Detection
Bose QC Ultra Headphones

On Head
Detection
Bose QC Ultra Headphones
Case
PROBLEM
Leveraging an accelerometer, a capacitive proximity sensor, and additional orientation cues to help users get the best wear-based automatic power, connectivity, and playback experiences.
ROLE
UX Lead Designer: Created the state-to-state logic for On Head Detection (OHD) and conceptualized & lead the invention of orientation based auto-disconnection.
TIMELINE
2024-2025
RELEVANT PRODUCTS
Bose QC Ultra Headphones 1st & 2nd generation
Design
Automatically disconnect Bluetooth™ when doffed to a flat cup position
Pause content when the product is removed from the user's head
Enter low power state after product isn't used for a while
Start up from low power state upon donning
Design
Automatically disconnect Bluetooth™ when doffed to a flat cup position
Pause content when the product is removed from the user's head
Enter low power state after product isn't used for a while
Start up from low power state upon donning
Considerations
Solid Data
Automatic UX depends on crucial data coming together to indicate a product’s realtime state.
Accuracy
Inaccuracy is costly.
False positives erode trust. False negatives can break continuity in sessions.
Adaptability
The system must work across personal characteristics, motion patterns, and environments.
Constraints
Sensor Array
A limited set of sensors is available to infer wear state, orientation, and thermal data.
Latency Sensitivity
Signals must be read consistently and accurately in order to reliably indicate new position and appropriately enter the associated product state.
Interaction Variance
A single experience must account for usage variability to a high level of individuality beyond simple physiognomy.
Edge Cases
Ambiguous positions and interactions create edge cases. These must be tied to a most probable product state.
Determinations
Favor Active Usage
Skewing sensors toward sensitivity for in-use states is favorable.
Sensor calibration works on a spectrum from a “worn” to an “off” state. Interruption is more painful to the user than a product that doesn’t power off systematically.
Keep the Button
Offer a manual power option.
The product needs to fail gracefully and allow room for correction. An undetected positional change requires a quick and intuitive manual fallback. When full capability isn’t possible, clarity remains.
Quickly Communicate
Indicate the product is on before full boot up is complete.
Communication is key. Users benefit from knowing the system is working as intended, even if the product hasn't fully transitioned to its end state.
Final Flow
Hover over the information tiles to learn more about how the system is designed.
Due to the nature of my NDA and respect for my employer, I cannot further expand on developmental processes or use internal language and terminology. This is all in an effort to protect IP.
For more details on the design process for this project, please view the full case study on a desktop or tablet.
