Visual Consistency Does Not Mean Identical Pages
An article and a billing screen can look different while sharing a coherent design language. Consistency is most useful when it preserves meaning.

Make the same signal mean the same thing
A billing screen needs dense comparisons and clear amounts. An editorial page needs a comfortable reading rhythm. Giving both an identical layout would ignore their different jobs; sharing typography, interaction conventions, and semantic color choices can still make them feel part of one product.
Problems arise when a signal changes meaning unexpectedly. If an accent treatment marks the primary action on one page, a selected filter on another, and an error elsewhere, a visitor must repeatedly reinterpret it. Review the meaning, not just the color value.
Compare like with like
Place equivalent controls side by side in the same state and at the same width. A disabled button should not be judged against an enabled one, and a compact table action need not have the same dimensions as a prominent page-level action.
For each difference, ask whether it follows a rule. “Compact actions are used inside data rows” is a rule. “This screen looked better with a smaller button” is a local preference that becomes hard to maintain as the product grows.
Look for the source of repeated variation
Imagine twelve cards with inconsistent spacing. Ten come from a shared component; two were built locally. Editing twelve pages would hide the structural distinction. Review the shared card’s spacing and the reason the two exceptions exist before choosing the scope of a change.
Design tokens make recurring choices explicit, but a token name alone does not explain when to use it. Pair the shared value with a short usage rule and an example of a legitimate exception. This keeps the system useful without turning every new composition into a policy dispute.
Review more than the ideal example
Use a long heading, a missing image, an empty result, and a dense body of text. These states expose whether a component has a coherent layout rule or merely accommodates the sample content used to design it.
Record the rule you want to preserve: equal emphasis for comparable choices, clear separation between content groups, or a stable location for the next action. That gives a later contributor something more durable than an instruction to match one screenshot.