Outside of the timezone-agnostic advantages, .beats are about what I'd expect single notable tasks to resolve to and seem to be a great notation for that purpose. Retrieving an item I know the rough location of might take 1 .beat, disinfecting a kitchen countertop might take 2 .beats, resolving a P1 service outage I know the cause of might take 4 .beats to correct, verify and push into production. That ease is what makes it a viable replacement for me.

So after widespread adoption it could be used effectively as second nature and improve communication without the wasted thought cycles it takes to consider seconds/minutes, just to end up supplying poor ETAs. For example, from, "just a second," really meaning anywhere between 5 and 300 seconds, to a moment being hopefully less than 15 minutes, instead we hear, "need to grab something from the garage, back in... 2 beats," to mean around 3 minutes and parallelise our own movements appropriately.

With that edge, I'm optimistic that .beats wouldn't become arbitrary language after a few decades, that its use would be more thoughtful, but I'm ignorant to the psychology.

If decimal time of any description were to catch on, all systems should be updated, right down to the instruments requiring microsecond accuracy. Similarly, while we propose reformed timekeeping, can we decimalise the calendar year? https://en.wikipedia.org/wiki/Calendar_reform