A Design System Cannot Fix a Broken Decision System

I have worked with design systems both before and after Figma made components, libraries and collaboration far easier.

I have seen what a good design system can do.

It can improve speed, reduce repeated effort and create familiarity across products. It can help a designer avoid rebuilding the same form, card or button every time a new journey begins. It can give technology and design a shared language.

But I have also seen teams create excellent component libraries and continue producing inconsistent experiences.

For a while, I believed the system simply needed more components, better documentation or stricter adoption.

The real problem was often somewhere else.

It was in the way decisions were being made.

One product owner wanted to follow the system. Another wanted their product to look different. One stakeholder prioritised conversion. Another prioritised the amount of information displayed. Design became involved early in one journey and two days before development in another.

Every decision made sense within its own small room.

Together, they created inconsistency.

We sometimes kept polishing the components while the real design problem was sitting inside the meeting.

A design system can tell us how a button should look. It cannot decide which action deserves priority.

It can define a form field. It cannot decide why the organisation is asking the customer for that information.

It can provide a modal component. It cannot prevent every stakeholder from placing their message inside one.

It can show the approved pattern. It cannot resolve who has the authority to approve an exception.

Those are decision-system problems.

I have seen designers blamed for inconsistency when they were responding to different stakeholders, different deadlines and different definitions of success. I have also seen teams bypass the system because they did not understand the reasoning behind it.

Governance is not simply telling people, “Please use the library.”

It means creating clarity around who owns the system, how changes are proposed, how exceptions are evaluated and how disagreements are resolved. It also means accepting that a design system is not a museum collection that must remain untouched.

Products evolve. Customer behaviour changes. Business priorities change. The system must be allowed to learn.

The important question is not whether a component was changed.

It is whether the change was intentional, evidence-based and returned to the system so the next team could benefit from it.

This is where design leadership becomes important.

The leader must connect individual product decisions to the larger experience. They must understand when consistency helps the customer and when a new problem genuinely needs a new solution.

Blind consistency can be as harmful as uncontrolled variation.

A familiar pattern should not be preserved simply because it already exists if evidence shows that it creates friction. At the same time, every new business requirement cannot become an excuse to invent another version of the interface.

That balance does not come from the design tool.

It comes from judgment.

The same issue will become even more important with AI. We can now generate screens, variations and content faster than ever. But speed does not automatically produce coherence.

If the underlying decision system is unclear, AI will help us create inconsistency at a much faster rate.

Before asking whether the design system contains enough components, I now ask different questions.

Do teams share the same experience principles?

Is ownership clear?

Are decisions being documented?

Does customer evidence have a consistent role?

Can someone challenge a senior stakeholder’s preference with reason and data?

Are exceptions fed back into the system, or do they quietly become permanent?

A healthy design system is not only a collection of reusable components.

It is the visible outcome of hundreds of shared decisions.

When those decisions are clear, the system creates speed and confidence.

When they are not, even the most beautiful library becomes another Figma file that everyone admires and nobody consistently follows.

Before fixing the design system, we may need to fix the way we decide.