Adaptive hearing protection that reacts to your environment.
We found that people don't like to wear hearing protection when the volume can change often—like in construction sites or factories—because they need to communicate, and constantly removing hearing protection is inefficient.
Chameleon is hearing protection that responds to the volume of the environment: When it's quiet, you can hear as if you're not wearing hearing protection. When it gets loud, it reacts in an instant to protect your hearing until it's safe again.
We surveyed and interviewed people who work in construction, manufacturing, and live music production1 about their hearing protection use. A vast majority answered that while they know they should wear, protection they often don't. When asked why, they said they often needed to talk at work, and it's tedious to constantly remove hearing protection and put it back on.
Based on our research insights, we came up with a number of areas our device should excel in. We then turned them into engineering functional requirements and metrics.
Attenuation: Must protect the wearer from potentially damaging sound.
Communication: Should allow communication when there is no damaging sound.
Comfort: Should be comfortable to wear for a full work day.
Cost: Should be reasonably priced relative to other products in the space.
Durability: Should withstand daily use in a rugged environment, and consume minimal power.
Measurement: Should accurately measure the noise level, and conform to ANSI standards.
I started to draw up flows and storyboards for the ideal use of the device. Storyboards helped identify different use scenarios (who's talking? who's making the noise?), and functions we had initially overlooked (like override buttons to preemptively close the device), but a user flow was not very helpful, since the primary goal is to not interfere with the wearer's work. Any user flow was a straight line from the beginning off the day to the end.
We found that the user story: "As a worker, I want to protect my hearing and still be able to communicate when working" helped us focus in during development.
Full Prototype Mk. 1
Over the next couple months we worked on the electrical and software systems, as well as testing different ways to dynamically attenuate. Our first system prototype was a retrofit on an existing ear-cup, and was used to test the measurement, control logic and mechanical components of the system.
Though a good proof-of-concept, this prototype was too slow, and too noisy for what we needed to do with it. We also noticed when testing it that long hair tended to get caught in the disk—definitely not ideal.
Full Prototype Mk. 2
I spent the next 4 months working on all aspects of the design: electronics, embedded code, mechanical and acoustics.
After a few dozen smaller scale prototypes to test each part of the system independently, we finally had a working full-system prototype.
Pitch and Demo
We showcased our prototype at the Systems Design Engineering Symposium where we won People's Choice award. We also won the Norman Esch Entrepreneurship Award for our pitch and product demo!
Live music workers means, for example: stagehands, producers, and directors, not performers themselves ↩