Overview
Buttons, fields, and tables are useful foundations, but scientific software is defined by the meaning carried through its states. A record may be pending, invalid, quarantined, superseded, reviewed, or unavailable, and each state changes what a user can safely do next.
When those meanings are rebuilt separately in every feature, the product becomes difficult to learn and difficult to trust. The same word can describe different behavior, while important exceptions disappear into styling or one-off messages.
The problem
Most design systems begin with visual consistency and only later encounter scientific complexity. A shared component may look identical across workflows while representing different permissions, provenance, or review requirements.
The result is a system that is consistent at the surface but inconsistent in use. Users have to remember local rules instead of recognizing a reliable pattern.
The approach
The system should define each meaningful state, its visible explanation, the actions it permits, and the data or permission rule behind it. Components are then connected to those rules rather than treated as decorative wrappers.
Examples should cover laboratory, clinical, and operational contexts, including incomplete data, failed controls, corrections, and records that have been replaced but must remain discoverable.
The decision
Not every difference needs a new component. The useful distinction is between a visual variation and a change in meaning. Variants are reserved for behavior that users must understand, while content and state rules stay explicit.
Evidence package
The evidence includes state inventories, component behavior, content rules, accessibility checks, permission examples, and tests across normal and exceptional workflows. Teams should be able to trace a visible state back to the rule that produced it.
What the case shows
A scientific design system becomes valuable when its components carry consistent meaning through change and exception. The goal is not to make every screen look identical; it is to make important behavior recognizable.