top of page
Product design team comparing design system components with AI decision patterns for transparency, human review, and accountability

From Design Systems to Decision Systems

7 days ago
7 min read

As software becomes more intelligent, consistency needs to extend beyond how products look and behave to how they make decisions, communicate uncertainty, and involve people.

I've been thinking about how our design systems need to evolve as AI becomes a bigger part of the products we're building.

Over the years, we've invested a lot of effort in creating consistency across digital experiences.

We establish patterns for navigation, interactions, forms, notifications, and the countless other elements people encounter when using software.

We create shared components and guidelines so teams don't have to solve the same problems over and over again.

And when design systems work well, they do more than make products look consistent.

They help teams move faster, reduce unnecessary complexity, and create experiences that feel familiar to the people using them.

But AI is introducing a different kind of design challenge.

What happens when two parts of the same product make recommendations differently?

Or when one AI capability explains why it suggested something, while another simply presents an answer?

What happens when people can question or override an automated decision in one workflow but not another?

Those experiences might use exactly the same components and still feel fundamentally inconsistent.

And I think that's something we need to start paying more attention to.

Consistency Has Always Been About More Than Appearance

One thing I've learned from working on complex enterprise products is that consistency matters most when people are trying to get something done.

Someone managing facilities, equipment, maintenance, or operations doesn't want to relearn how the software works every time they move between tasks.

They need to understand where they are, what information matters, and what they can do next.

A good design system helps create that familiarity.

But the real value isn't that every button looks the same.

It's that people can develop a reliable understanding of how the product works.

They know what to expect.

They can build confidence through repeated use.

And they can focus more of their attention on the work they're responsible for rather than figuring out the software.

AI complicates that relationship because we're introducing capabilities that don't always behave in entirely predictable ways.

A system might recommend an action, generate a summary, identify an anomaly, or complete part of a workflow.

The interaction may be beautifully designed.

But the questions people have about that experience are different.

Why did the system recommend this?

How much should I trust it?

What information did it consider?

What happens if I disagree?

And who is responsible if the recommendation turns out to be wrong?

Those aren't questions a component library can answer on its own.

When Every Team Solves AI Differently

Imagine several product teams introducing AI capabilities across an enterprise platform.

One team builds an assistant that recommends maintenance priorities.

Another helps people investigate asset performance.

A third uses AI to summarize inspections or identify potential compliance issues.

Each team has a legitimate customer problem to solve.

Each team is experimenting, learning, and trying to deliver value.

And each team may make reasonable design decisions based on its particular use case.

But without shared guidance, those decisions can add up to a fragmented experience.

One assistant might present its recommendations with a detailed explanation.

Another might provide a simple confidence indicator.

A third might offer no explanation at all.

One workflow requires a person to approve an action. Another makes a similar decision automatically.

One allows people to correct the information used by the system. Another doesn't provide that option.

Individually, each experience might make sense.

Together, they can create confusion about what the product is capable of and how people are expected to work with it.

This feels familiar to me.

We've seen similar challenges when different teams independently design navigation, forms, and workflows.

It's one of the reasons we invest in design systems in the first place.

The difference is that inconsistent AI behavior can have consequences beyond usability.

It can affect people's decisions, their understanding of responsibility, and ultimately their trust in the product.

What Would a Decision System Look Like?

I've started thinking about this as an opportunity to expand our design systems into something that also addresses how intelligent capabilities behave.

Not a replacement for the components, patterns, and guidelines we already have.

An additional layer.

A shared set of principles and experience patterns that help teams make consistent decisions about how AI interacts with people.

For example, we might establish common guidance for how a product:

- Communicates uncertainty when information is incomplete. - Explains recommendations in ways that are meaningful to the person making the decision. - Distinguishes between suggesting an action and taking one. - Determines when human review or approval is appropriate. - Allows people to question, correct, or override a recommendation. - Makes automated actions understandable and traceable. - Helps people recover when something goes wrong.

These aren't necessarily individual UI components.

Some might become reusable interaction patterns. Others might be guidelines, decision frameworks, or shared expectations that teams use during discovery and validation.

And they shouldn't all produce identical experiences.

A recommendation about organizing a work queue doesn't need the same level of explanation or oversight as a decision that could affect safety or regulatory compliance.

The goal isn't to force every AI capability into the same interaction.

It's to create consistency in how we think about the decisions behind those interactions.

Shared Principles, Contextual Decisions

I think there's an important balance here.

Design systems are valuable because they reduce unnecessary variation.

But sometimes variation is necessary.

Different users have different responsibilities. Different workflows carry different consequences. And different industries have requirements that can't always be addressed with one universal pattern.

Consider an AI recommendation to postpone a maintenance activity.

In one context, that might be a relatively routine scheduling decision.

In another, it could involve equipment with inspection requirements, contractual obligations, or safety implications.

We wouldn't necessarily want those experiences to be identical.

But we would want teams to ask a consistent set of questions.

What is the consequence of getting this wrong?

What does the person need to understand before acting?

What information could be missing?

When should the system ask for confirmation?

What needs to be recorded?

And how can someone correct the decision if circumstances change?

Shared principles can help teams answer those questions without dictating every detail of the solution.

To me, that's a more useful kind of consistency.

This Isn't Something Design Can Own Alone

There's another aspect of this that I think is particularly important for design leaders.

It's tempting to frame these challenges as a new set of UX standards that designers should create and enforce.

But the decisions involved reach well beyond design.

Product teams need to understand the customer problem and the value of automation.

Engineering teams need to understand what the technology can reliably do, where it may fail, and how its behavior can be monitored.

Security and compliance teams bring essential expertise about controls, obligations, and consequences.

Domain experts understand the operational realities that may never be fully represented in the data.

Design and research bring an understanding of how people interpret information, exercise judgment, and respond when technology doesn't behave as expected.

None of those perspectives is sufficient on its own.

And I don't think the solution is to create another layer of governance that slows every team down.

The opportunity is to establish enough shared understanding that teams can make better decisions earlier.

When do we need an explanation?

When does someone need to approve an action?

How do we distinguish a recommendation from an automated decision?

What should happen when someone disagrees with the system?

If we can establish some common expectations, teams can spend less time debating the basics and more time solving the specific problems their customers face.

That's the same benefit we've always hoped to get from a good design system.

Research Has an Important Role to Play

I also think this creates an interesting opportunity for research.

We can't assume that an experience is trustworthy simply because people say they trust it.

And we can't assume that an AI capability is successful simply because people accept its recommendations.

Someone might accept a recommendation because it looks convincing.

They might ignore a useful recommendation because they don't understand how it was generated.

Or they might repeatedly approve automated actions without really reviewing them.

Those are very different behaviors, even if our analytics show similar interaction patterns.

We need to understand whether people can recognize when a recommendation is questionable.

Whether the explanation helps them make a better decision.

Whether they know when to intervene.

And whether they can recover when the system makes a mistake.

That kind of learning can inform patterns that extend beyond a single feature or product.

Instead of every team independently discovering how people respond to uncertainty, we can build a shared understanding and continue refining it over time.

I think that's where research and design systems can become especially powerful together.

Starting Small

I don't think we need to build an entirely new framework before teams can start doing this work.

In fact, I'd be hesitant to do that.

AI capabilities are evolving quickly, and we're still learning how people want and need to work with them.

A comprehensive set of standards developed too early could become outdated before it's widely adopted.

I'd rather start with a few real experiences.

Look at where AI is already being introduced.

Identify the decisions those capabilities are asking people to make.

Compare how the experiences communicate recommendations, handle uncertainty, and involve human judgment.

Find the patterns that should be shared.

Test them with customers.

And evolve the guidance as we learn.

That feels more practical to me than trying to anticipate every possible use case.

It's also consistent with how good design systems tend to grow.

We learn from real product needs, identify what's reusable, and create shared approaches that make the next problem easier to solve.

The Next Layer of Design Maturity

I don't believe the arrival of AI makes our existing design systems less valuable.

If anything, consistent navigation, clear interactions, accessibility, and well-designed components become even more important as products grow more complex.

But I do think we need to broaden our definition of consistency.

It's no longer enough for intelligent capabilities to look like they belong to the same product.

People also need to develop a reliable understanding of how those capabilities behave.

When the system is making a suggestion.

When it's acting on their behalf.

When they should question it.

And what they can do when something doesn't seem right.

That's not simply a visual design challenge.

It's a product experience challenge that requires shared thinking across disciplines.

For me, the opportunity isn't to move away from design systems.

It's to build on what we've learned about creating consistent interactions and apply that same intentionality to how our products make decisions.

Because as software becomes more intelligent, people shouldn't have to guess how much control they have, what the system knows, or when they should trust it.

And helping create that clarity feels like an important next step for human-centered design.

Comments


Let’s Connect

Good things often start with a conversation.

​

Whether you’re interested in product and creative leadership, collaboration, photography and art—or simply want to exchange ideas—I’d love to hear from you.

Susan Ripley Logo

© 2026 by Susan Ripley

  • X
  • White LinkedIn Icon
bottom of page