Reacting to: The Blandness of Systematic Rules vs. The Delight of Localized Sensitivity

Look, I get it. Rules keep teams from spinning out and shipping a different UI every Tuesday. But the “Now / Later / Never” example hit me right in the ribs. That’s the kind of small, human decision that makes a product feel alive, and it usually dies on the altar of “consistency.” The cost isn’t just aesthetics — it’s that quiet feeling of care you only notice when it’s gone. Read Jim’s piece here: https://blog.jim-nielsen.com/2026/systemic-vs-localized/

I’ve watched this play out building FrameFlow. The system wants the same button labels, the same spacing, the same empty-state copy, everywhere. And then you hit a one-off moment — like a user dropping their first clip into a scroll sequence — where the default language feels like a warning label instead of a nudge. That’s the spot where a localized exception is worth it. Not because it “breaks rules,” but because it respects the moment.

So yeah, I’m on Jim’s side: the rule is a floor, not a ceiling. Systems are great until they start flattening all the peaks. P.S. “Never / Later / Now” is a perfect little trio and I will die on this hill.