Design systems fail in two directions. Too loose and nothing is consistent. Too tight and every real product need becomes an exception, until the team quietly stops using the system at all.
rules, defaults and escape hatches
The healthiest systems separate the three. A small number of real rules that must hold. A larger set of good defaults that cover most cases. And an honest escape hatch for the rest, with a route back into the system when the pattern proves itself.
the system is a product
It has users, a backlog and a support cost. Treating it as a one-off deliverable is why so many systems are abandoned a year after the launch deck.
If people are working around the system, the system is giving you feedback.
Leave room. Document the reasoning, not only the result, so the next person can tell the difference between a rule and a habit.

