The interface is fine. I’m not! A case for emotionally aware modes.

I went online the other day to pay off my credit cards before the end of the month.

I was in a crappy mood for no particular reason. Nothing dramatic. Just one of those days when every small inconvenience feels slightly more personal than it should.

The banking site loaded exactly as it always does — clean. Consistent. On-brand.

But that day, the consistency did not reassure me. It felt cold.

The interface had arrived in the same emotional posture it brings to every interaction: calm, polished and professionally neutral. I had not.

That bothered me more than it probably should have.

Many of the digital spaces we visit most often remain strangely rigid about the state of the person using them. Responding to screen size, device, language, location, purchase history and browsing behaviour.

The design system is consistent.

The human is not.

I am not asking my bank to watch my face, analyse my typing speed or decide that I look financially vulnerable. That is not emotional awareness. That is emotional surveillance wearing a nicer outfit.

But what if the experience simply let me tell it what I needed?

The task would remain the same. The important information would remain visible. The bank would not need to diagnose my mood or build an emotional profile.

It would only need to let me choose the tone, pace and level of support that fit the moment.

We have spent years making interfaces responsive to devices.

Perhaps it is time to make them more responsive to people.

Consistency solved a real problem.

So, let’s take a moment to give conventional UX its due.

Consistency supports recognition, learning, accessibility, quality control and cross-channel coherence.

My whiny outburst is not proposing that banking navigation should rearrange itself because someone (A.K.A. me) had a bad morning.

The design system needs to remain consistent. Especially to help humans when we’re not.

So, what is it about not being understood that seems to make things worse?

Why emotional responsiveness matters to humans

Humans respond well to feeling understood.

Relationship researchers call this perceived responsiveness: the sense that another person recognizes what we need, takes our situation seriously and responds accordingly.

Your bank does not need to care about you in the way a person does. It does not need a personality, a sympathetic avatar or a chatbot that says, “I understand how you feel.”

But it could recognize that paying debt may be stressful. It could remove distractions, explain the consequences plainly, make recovery easy and avoid sliding a new credit offer into a vulnerable moment.

The interface does not need to pretend to be your friend.

So, how could an interface recognize or consider an emotional response in an app or web browser experience?

Start with a mode, not a diagnosis

From prior experience and research I’ve done to date, I’ll call out two ways that stand out to me.

1. Ask before diagnosing

Let users state what they need:

• I’m in a hurry = Give me the essentials

• I’m confused = Explain each step

• I’m overwhelmed = Reduce distractions

The wording should describe the experience/mode, not force users to disclose an emotion.

2. Adapt the interface, not the outcome

Do not change prices, rights, eligibility, recommendations or essential information.

Change pacing, density, hierarchy, guidance and interruption, and explain what changed. For example, a small message might say:

“Quick mode is showing only the steps needed to make this payment. You can return to the full view at any time.”

That protects the user’s mental model and makes the adaptation inspectable. The mode should also be easy to exit. It should not quietly become permanent or follow someone across unrelated services.

Pieces of this future already exist

Luckily, we are not starting from zero. Several familiar products already contain pieces of the idea.

Apple’s Focus feature allows users to create different interface conditions for different parts of their lives. Work, Personal and Sleep modes can change interruptions, visible screens and the information apps are allowed to surface.

Android’s Digital Wellbeing tools also recognize that context matters. Bedtime and Focus modes can reduce distractions, alter aspects of the display and help users manage when certain apps demand their attention.

The important idea underneath both examples is not emotion detection.

It is adaptation.

The experience changes because the person’s needs have changed.

What is surprising is how rarely that principle carries over into individual websites and digital services. Banking, insurance, healthcare, government services and other high-stakes experiences often present essentially the same interface regardless of whether someone arrives confident, distracted, overwhelmed or under pressure.

I think there is an opportunity to change that.

Not by teaching websites to diagnose our moods, but by giving people meaningful ways to tell an experience what they need from it.

So the design question becomes less:

How can an interface know how I feel?

And more:

How can an interface respond differently when I tell it what I need?