Emerging patterns in Designing for AI-first experiences

Work on designing AI-first assistant and agent experiences has been eye opening.

AI UX is both fundamentally the same and widely different, especially for vertical use cases.

There are clear and emerging patterns that will likely continue to scale:

  1. Comfort will start with proactive intelligence and hyper personalization. The biggest expectation customers have of AI is that it’s smart and it knows them based on their data. Personalization will become a key entry point where a recommendation kicks off a “thread” of inquiry. Personalization should only get better with “memory”. Imagine a pattern where an assistant or an agent notifies you of an anamoly, advice that’s specific to your business, or an area to dig deeper into relative to peers.
  2. There are two clear sets of UX patterns that will emerge: assistant-like experiences and transformative experiences. Assistant-like experiences will sound familiar by now. Agents will complete a task partially either based on input or automation and the user confirms their action. You see this today with experiences like deep search. Transformative experiences will often start by human request and will then become background experiences that are long running. Transformative experiences, in particular, will require associated patterns like audit trails, failure notifications, etc.
  3. We will start designing for agents as much as we design for humans. Modularity and building in smaller chunks becomes even more important. With architecture like MCP, the way you think of the world in smaller tools becomes a default. Understanding the human JTBD will remain core but you’ll end up building experiences in pieces to enable agents to pick and choose what parts to execute in what permutation of user asks.
  4. It’ll become even more important to design and document existing standard operating procedures. One way to think about this is a more enhanced more articulated version of a customer journey. You need to teach agents the way not just what you know. Service design will become an even more important field.
  5. There will be even less tolerance for complexity. Anything that feels like paperwork, extra clicks, or filler copy will be unacceptable; the new baseline is instant, crystal‑clear, outcome‑focused guidance. No experience, no input, no setting should start from zero.

Just to name a few.

The underlying piece is that this will all depend on the culture design teams, in particular, embrace as part of this transition.

What I often hear is that design teams are already leading the way in adoption of AI. The role of Design in a world where prototyping is far more rapid and tools evolve so quickly will become even more important. It’ll change in many ways (some of it is by going back to basics) but will remain super important nonetheless.

Most of the above will sound familiar on the surface but there’s so much that changes in the details of how we work.

Exciting times.

You can join the discussion here.

Join the discussion

You can join the discussion on this article here.

Learn more