Field note · 11 May 2026
Why calendar reminders go quiet after the second week
People turn reminders on during setup, live with the noise for a few days, then bury the feature without ever calling it a failure.
Amina Rahman
In three studies of calendar apps used by office staff in Petaling Jaya and Shah Alam, the reminder toggle was switched on during the first sitting more often than any other extra. By day twelve, most of those same people had either muted the channel or moved the noisy events into a calendar they never opened at work.
The pattern is easy to miss if you only count “reminder created.” Creation happens in a burst, usually while someone is copying a recurring meeting from an old tool. The person is not deciding that they want to be tapped on the shoulder for the rest of the year. They are finishing a chore.
What happens next is almost always social, not technical. A reminder fires during a stand-up, or in a Grab on the way to Batu Caves, and the person feels rude. They do not open settings to write a better rule. They silence the lot. When we asked later whether the feature had “failed,” several people looked confused. They had not filed a complaint. They had protected the room they were sitting in.
A useful adoption question, then, is not “did they enable reminders?” It is “what did they do the third time a reminder arrived in front of someone else?” That third time is where the feature either earns a quieter place or gets buried. Product groups who only look at enablement rates will keep polishing a switch that already did its job — and miss the week-two silence that actually decides whether the capability stays in daily use.
If you are preparing a Feature Adoption Study around reminders, bring the list of events people consider private, the channels the app can use (banner, email, lock screen), and one week of anonymised fire-times if you have them. We will not need a funnel chart. We will need to sit with the person at the hour the reminder usually lands.