The override I almost regretted removing

Early on, FounderFlow let you dismiss an alert with one tap and move on, no explanation needed. I almost removed that in a redesign, because I wanted every override to come with a reason (too noisy, not relevant, already knew, etc.), figuring the extra data would help it learn faster.

I tested the "reason required" version on myself for two weeks before shipping it. What I noticed was that on my busiest days, I started ignoring alerts instead of dismissing them, because typing a reason felt like one more task, and ignoring something takes zero effort. That's worse than a clean dismiss, an ignored alert looks identical to one nobody has looked at yet, so it pollutes the "unreviewed" queue instead of clearing it.

So the one-tap override stayed. I added an optional reason field instead of a required one, most people skip it on obvious dismissals and only fill it in when something's actually worth flagging as mistuned. Turns out friction in the wrong place doesn't produce better data, it just produces avoidance.

Curious if others have had a "more rigorous" feature idea backfire once real usage patterns showed up. What did you end up simplifying back down?