I recently fixed a small problem on my mother's scooter. It wasn't the engine, the brakes, or anything mechanically significant.

A tiny ₹40 buzzer had stopped working.

The buzzer wasn't even part of the original scooter. It had been added later while installing accessories, and its only purpose was to emit a soft beep... beep... beep... whenever the turn indicator was on.

When it stopped working, my mother immediately noticed.

"I keep forgetting that the indicator is on."

At first, it sounded like a trivial inconvenience. After all, every scooter already has a blinking arrow on the instrument cluster. The information was still there. Nothing was technically broken except the sound.

But that's exactly what made the problem interesting.

As designers, we often think of products as collections of physical components. A buzzer is just another inexpensive electronic part connected to a wire. Yet the moment it disappeared, it became obvious that it wasn't merely producing sound.

It was performing cognitive work.

The dashboard already communicated the state of the indicator visually. The buzzer communicated the exact same information through sound. It didn't add new information; it simply introduced another sensory channel.

This is called multimodal feedback. The value wasn't redundancy. The value was that the rider no longer had to repeatedly look down at the dashboard to know whether the indicator was still on.

That led me to think about cognitive load.

Every task competes for a limited amount of mental bandwidth. Riding a scooter isn't just about steering. A rider is constantly balancing, controlling the throttle, watching traffic, anticipating other vehicles, navigating unfamiliar roads, and reacting to unexpected situations.

For experienced riders, much of this becomes automatic. Remembering to cancel an indicator barely registers as another task.

But not everyone rides that way.

My mother, like many occasional or less confident riders, devotes most of her attention simply to riding safely. Her mind is occupied by the primary task of controlling the scooter. Under those conditions, remembering to cancel an indicator becomes a secondary task.

It isn't forgotten because it's unimportant.

It's forgotten because the brain naturally prioritizes what feels most critical.

The buzzer doesn't improve memory.

It removes the need for memory altogether.

Instead of asking the rider to periodically think, "Did I turn the indicator off?", the scooter answers that question on their behalf every second the indicator remains active.

The product quietly externalizes a tiny piece of cognition. It carries a small mental responsibility so the rider doesn't have to.

This is one of the most beautiful things great products do. They don't simply add functionality.

They reduce the amount of thinking required to use them.

They replace recall with recognition. Rather than expecting people to remember, they allow people to perceive.

Good design isn't about making users smarter.

It's about asking users to think less.

What fascinated me even more was that this buzzer wasn't part of the original design.

Someone had felt the need to add it later.

That raises a far more interesting design question.

Why did someone feel the need to add it in the first place?

When users repeatedly modify products in similar ways, they're often revealing a gap between the designer's assumptions and real-world usage. The scooter assumed that a blinking dashboard light was sufficient feedback.

For many riders, it probably is.

For others, especially riders operating under a higher mental workload, it isn't.

This is an edge case.

Not every rider needs an indicator buzzer. Many experienced riders instinctively cancel their indicators or notice the dashboard light without conscious effort.

Designing around every edge case would quickly make products unnecessarily complex.

But edge cases deserve attention when three things are true.

• The consequence is meaningful.
• The solution is inexpensive.
• The change doesn't negatively impact everyone else.

This tiny ₹40 buzzer satisfies all three.

Forgetting an indicator can confuse surrounding traffic and increase the likelihood of unsafe situations. The solution costs almost nothing, requires almost no maintenance, and doesn't fundamentally change how the scooter behaves.

Yet for riders with a higher cognitive load, it quietly removes one more thing they need to think about.

That isn't designing for the average rider.

It's designing for moments when people are mentally stretched to their limits.

Every product asks something of its user.

Sometimes it's physical effort.

Sometimes it's time.

More often than we realize, it's attention.

Great products don't just reduce physical effort.

They reduce mental effort.

The ₹40 buzzer didn't make the scooter faster. It didn't improve fuel efficiency. It didn't add horsepower. It didn't even tell the rider something they couldn't already know.

What it removed was the need to constantly remember.

Perhaps that's what thoughtful design really is.

Finding small opportunities to let the product think, so the person doesn't have to.