In Spanish (Spain), "encantada" is said when you meet someone. It literally translates to "enchanted". A small spell, cast in one word. And in Brazilian Portuguese, when you thank someone, they often answer "imagina." Imagine. As in, please, do not even carry the weight of the favor.
Some words do not translate cleanly because they are not carrying information, they are carrying a posture. "Encantada" and "imagina" both say you matter to me more than this exchange does. The same sentence can be technically polite and still land as either warm or empty, depending on what is underneath it.
I think about this when I look at how products treat the people using them, and how studios treat the people they work for. There is a version of service that checks the box. Got it. Done. You're welcome. It is correct, it answers the question that was asked. And there is another version that does something harder to name, where the person walks away feeling like someone actually understood what they needed, not just what they typed.
Most software lives in the first register. Most studios do too. Someone asks for a screen, they get a screen. Someone asks for a feature by Friday, they get a feature by Friday. The work matches the request exactly, and that is the problem, because the request is almost never the same thing as the need.
It is not about more words
The warm version is not always longer, and it is not more decorated. The difference is that it knows what the moment is for. A confirmation is not there to announce that something happened, the person just watched it happen. It is there to answer the quiet question underneath: am I done here, or is there still something I need to do? Translated, not localized. Functional, not enchanted.
Getting that right is not a writing trick. It is paying attention. It means asking what a person is actually feeling at that exact point, and answering that, instead of restating the screen back to them. The flat line answers the interface. The warm one answers the person.
The words were never the hard part. Understanding the context and going a little bit further is.
Why this is getting rarer
It has never been easier to produce the technically correct version of almost anything. A line of copy, a screen, a passable component. The tools we have available now are amazing and fast. What they are good at is the literal request. What they cannot do is feel what a moment is actually for, and answer to that.
So the flat register is becoming the default. The correct-but-empty version costs close to nothing now, which means it is what most things ship with. The work that will stand out is the work that still does the slow, human part: noticing what each small moment is really asking for. That attention is the whole job. It was always the whole job. It is just more visible now that the easy part has been automated away.
The part worth protecting
The test we keep coming back to is small and a little unscientific: does this carry a posture, or only information? Most of the time the difference is not a feature you can point to. It is a hundred small decisions not to stop at the obvious answer.
That is the part worth protecting, especially now. The obvious answer is free. The version that makes someone feel taken care of still takes a person who decided to go further.
If you're building or redesigning a product and want a partner who'll push past the brief to the actual problem, we're happy to take a look.
Start a conversation with MUXA