Emotional features: what users feel is part of the product

When an app asks for a verification code, iOS can surface the code from the incoming SMS above the keyboard. One tap and I am done, without opening Messages or risking a wrong copy.

I like this feature because it understands the exact tension of that moment. The SMS might take a while, or I might copy the wrong number. When the code appears on its own, that small chain of risks disappears.

In product work, we usually map the task and document possible errors. The user's emotional state stays implicit. I started to think we should record it with the same care. Someone may arrive at a screen in a hurry, feeling unsure, tired, or afraid of losing what they just did. The interface can make that state worse or help resolve it.

I use “emotional features” as shorthand for decisions that change that feeling. The term is a little grand for something that may fit in a single line of interface. Still, it reminds me to ask a simple question during discovery: what is this person feeling right now?

The feeling that it worked

We associate mouthwash's freshness with a clean mouth. When we wash dishes, the foam helps us see where the detergent has already passed. Those sensations do not measure how well the products work on their own. They still shape our experience of them.

Interfaces provide signals too. The code suggested above the keyboard tells us that the system understood the SMS. A progress bar makes waiting predictable.

A cue earns its place when it answers a real question the user has. An animation added to the end of every task usually becomes decoration. Worse, some products use color and counters to manufacture anxiety. Emotion can support a thoughtful experience or a dark pattern. The user's intention should determine which one the product creates.

The question that changed Zenklub's clinical record experience

When I worked at Zenklub, we wanted to increase adoption of the digital clinical record. The feature mattered to professionals' daily work, but usage was still below where we expected it to be.

During an interview, I asked a professional how they felt after completing a record. They described relief and a sense of having done what needed to be done. The same idea came up in other conversations, along with the feeling of being productive when records were up to date.

Until then, we had been looking at the record as a form that needed to be completed. The interviews showed us a task that remained open after the appointment. While the record was incomplete, part of that visit's work stayed with the professional.

We created an adaptive widget on the professional's home page with the records that were still pending. It worked like a task list tied to appointments. When records were overdue, the component called attention to them. When the professional finished everything, the interface changed state and acknowledged completion with an animation.

Other changes were part of the redesign, so I do not attribute the entire result to the widget. The emotional insight set the direction for the work. In three months, adoption of the clinical record went from 38% to more than 90%.

How I use this lens today

Since then, I have tried to understand the state users arrive in and how they would like to leave. I also look for the moment when the tension shifts. It might be the confirmation that a file was saved or the ability to undo an action.

The conversation becomes more useful when it is grounded in a real task. “How do you feel when you do this?” often surfaces details that “Do you like this feature?” never reaches. We still need to observe behavior and measure outcomes afterward. An emotional response gives us a hypothesis. It does not give us permission to fill the screen with celebrations.

Maybe “emotional feature” is not the best name. I keep using it because it makes me look beyond the task described in the requirement. Every flow happens with someone who brings an expectation into it.