Alarm usability

Freshness Warning
This blog post is over 19 years old. It's possible that the information you read below isn't current and the links no longer work.

I have a new alarm clock. The old one was fine, but a little ugly, so we bought a sleek black clock radio. Yesterday I turned the volume of the radio down to a whisper and didn’t turn it back up before going to bed that night. This morning I awoke to a faint beeping sound and realized that I’d overslept. After a moment of wondering how I slept through the alarm and what that quiet little beeping was, I realized the beeping was the alarm.

The volume knob not only controls the radio’s volume, but the alarm’s volume as well. I’d turned the alarm down so low I could barely hear it. That’s not something I’d expect, and it’s not how the alarms I’ve used in the past have worked. This is probably the result of some engineer or manager deciding that the alarm volume should be configurable and that the existing UI should be used to configure it.

When you are creating a UI, stop looking for things to add to it. Don’t try and find more things to let the user configure. Every single configurable option is a choice the user has to make. It’s something that can be misconfigured and cause user confusion.

Often the option you are letting the user configure has a setting that is clearly best. Other times there is little difference at all to the settings. In those cases, pick an option and hard code it. Reduce the number of choices your users must make and your application will be better for it.

Kevan
July 17, 2003 10:18 PM

Our old alarm worked very well - the TV. Even if the volume was all the way down, the noise of the tube warming up and the raised brightness level in the room woke us. Now, of course, we have a different alarm system entirely - a baby. Oh how I long for some configuration options...

Torgny Bjers
July 19, 2003 3:45 PM

Aiee, Adam, I've never known a different alarm clock than those that have the radio and alarm volumes synchronized. I'm so used to it, and besides, I never use the radio in it anyway... :)

Matt Montag
June 8, 2006 2:25 PM

Your alarm clock issues seem arbitrary after reading Torgny's comment: he has illustrated you were merely trained by an alarm clock that worked the opposite way!

David Boland
November 8, 2006 10:11 AM

This was an old post but my wife recently went through a few alarm clocks. One that she liked at first (a Philips) was nice and sleek too, and had features such as wake to CD, and slow ramp up alarm volume. But all the buttons were identical looking, you had to use the reflection off the inprinted plastic words on the buttons to read them and they were all next to each other all around the CD lid. That clock was a nightmare! "Did I just hit snooze or alarm 24hr reset?" I offered to program her an alarm clock on for the notebook computer. I could reprogram features and functions infinitely as she had whims, sync to yahoo calendar or her Palm, automatic M-F, etc. I would've thought the notebook to be ideal but she didn't like that idea, she wanted a physical clock to push or hit in the morning. (Strangely her wish list included ability to play MP3's, change colors, change brightness, etc...). Anyway about the volume feature, I've always wondered why clocks that have the sleep function volume tied to the waking alarm volume? Doesn't make sense to me. The sleep volume should have quiet volumes as you lull off to slumber and the alarm volume should be fairly loud. The Philips (overly complex, hidden button) clock did have two volumes, one for sleep, one for alarm. I guess that was it's only good feature, but not enough to keep it around.

This discussion has been closed.

Recently Written

The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2023 Adam Kalsey.