Conversational Experience Is the New Responsive

Jul 12, 2025 · 3 min read

In 2015 and 2016 I worked at Accenture, alongside their design team at Fjord, and they were already playing with conversational UX back when none of the pieces to actually build it existed yet. There were no large language models, no real infrastructure, and most people could not begin to imagine replacing a button with a handful of words, so the whole thing read like a research curiosity. I saw it differently. To me it was never a curiosity at all, it was the endgame, because interfaces had always been a workaround for machines that could not hold a conversation with you.

That was nearly a decade ago. I have been following that same thread ever since, and here we are, landed almost exactly where it was always heading.

From Screens to Conversations

Responsive design was all about screen sizes, and this new shift is about something deeper, the very way we interact in the first place.

In a normal UI you click your way through a set of predefined paths, the buttons and forms and filters and menus that somebody laid out for you ahead of time. With a language model in the mix that whole thing flips around, because now you simply say or type what you want, and the system answers you, asks you to confirm, and then goes and does it. It is a lot less clicking, and a lot less friction between you and the thing you actually came to do.

None of this means UI is going away, of course, but its job quietly changes. Instead of being the main event, the interface starts to play a supporting role to the conversation, giving you clarity, feedback, and a reason to trust what just happened.

What Conversation Demands

Responsive design made all of us rethink layout, and conversational design asks for something harder, it asks us to rethink the flow itself.

We are not really designing screens anymore, we are writing exchanges, and every product flow starts to feel more like a dialogue, full of prompts and replies and little checks and choices along the way. The user is the one steering, and the system responds, or gently nudges, or steps in when it is actually needed.

And just like responsive design had its grids and its breakpoints to lean on, conversational design is going to need tools and patterns of its own. The good news is that we already have a working model sitting right in front of us: the humble call center.

What Call Centers Got Right

Call centers have been running structured conversations for decades now, and their scripts are anything but random, they are tuned within an inch of their life for speed, clarity, and repeatability. Whether the person on the line wants to change a password or close their account for good, there is already a tested path waiting to walk them through it.

That same mindset carries over almost perfectly. When you sit down to build a conversational feature, it helps enormously to think the way a call center agent would:

• What's the user trying to do?
• What's the clearest path to get them there?
• Where should we confirm, clarify, or redirect?
• How do we show the result in a way that builds trust?

A Quick Example

Say someone wants to update a product's price inside an e-commerce admin. In a traditional interface that turns into a little journey:

• Open the catalog
• Find the product
• Click through to edit
• Change the price
• Hit save

In a conversational flow, that same task looks a lot more like this:

• User: "I want to update pricing for product X to $49.99."
• System: "Just to confirm, you want to update the price for Product X with SKU ABC132 to $49.99?"
• User: "Yes please."
• System: Pulls current data (MCP magic), creates a draft change, shows it back to the user. "Ok, I've gathered the information and here's how Product X looks with the requested changes. Do you confirm the update?"
• User: "Yes, looks good."
• System: Applies the update (more MCP magic), confirms success, and provides links or instructions to verify the changes were made correctly. "Ok, the changes were applied and now Product X has a price of $49.99. Here's the link to the product details so you can review everything is correct."

Fewer clicks, a lot less screen to wade through, and honestly a good deal more clarity about what just happened.

Designing for Conversations

Now, not everything should be conversational, and not every user is going to want it that way, and that is completely fine. In the same way responsive design never actually killed off desktop-first thinking, this is not here to replace the visual UI we already know, it simply adds one more option to the table.

But as these conversational interfaces keep spreading, pretending they are not happening stops being a realistic plan. Which means those of us in UX and product have a pile of genuinely new work waiting for us:

• Define reusable patterns for conversation, just like we do for UI components.
• Map out flows with clear entry points, confirmations, and exits.
• On chat interfaces, combine language and visuals carefully: use data representations when they add value, not by default.
• On the web, use tools like assistant-ui or prompt-kit to build chat apps that let you control output and data representation for the right scenarios.

One Last Thing

Responsive design once made us rethink fixed layouts, and conversational design is now quietly making us rethink fixed interfaces altogether. In the end it all comes down to intent, to clarity, and to trust, to meeting people wherever they happen to be, whether that is on a screen, inside a chat, or just talking out loud.

Conversation, I am convinced, is the new responsive. And the teams who really understand that early are the ones who will get to shape whatever comes next.