Design system reviews on a fixed cadence, not waiting for complaints
In system operation, if system review still waits for someone to complain before changing it, small deviations often accumulate into another way of working.
In icon design, if icons still pursue a beautiful symbol set, the result is often beautiful but requiring added text to understand, or each interpreted as something different. The safer approach is every icon must be explainable in one sentence, saying only this one thing, with a meaning statement that locks this choice in place.

Icons written into files are not the same as icons actually being designed. The first step of translation is every icon must be explainable in one sentence, saying only this one thing.
If translation only shortens the pursuit of a beautiful symbol set, teams still encounter: beautiful but requiring added text to understand, or each interpreted as something different.
Every icon must be explainable in one sentence, saying only this one thing. Fail this, and icons remain in pursuit of a beautiful symbol set.
Icons most often shift form when tasks are divided. Departments each take away an easy-to-say phrase but neglect to take the corresponding refusal.
So externally the pursuit of a beautiful symbol set remains visible, while internally it cannot be explained: beautiful but requiring added text to understand, or each interpreted as something different.
The minimum unit of an icon is not an entire handbook but a judgment usable on the spot. The meaning statement should be that unit.
When teams receive an icon, they need not guess what the brand department might think.
Before entering the library, sample one instance on-site to see if the meaning statement has reverted to pursuing a beautiful symbol set.
Revision is not necessarily bad. Bad is revision with no one acknowledging the icon has changed.
Judgment must stay with the people using it. The design lead must also give the site the authority to refuse based on the meaning statement.
At training's end, test one question only: do different people articulate the same meaning?
From what cannot be delegated to tools available on-site, each layer answers one question only, avoiding the risk of rewriting icons as the pursuit of a beautiful symbol set.
This layer documents what in the icon cannot be delegated.
This layer reduces the icon to checkable conditions.
This layer specifies what the icon can vary in different contexts.
This layer assigns the icon to the people using it, and documents exceptions.
Note: This diagram is a conceptual framework. It explains a way of thinking and is not statistical data. Source: Qingmei Future Insights.
In icon design, mark the moment when the icon is actually invoked—not when it looks like a beautiful symbol set.
Replace lengthy explanations with a meaning statement, retaining only what supports 'every icon must be explainable in one sentence, saying only this one thing.'
Before entering the library, ask only: do different people articulate the same meaning? If you can't answer, it's not yet a decision.
Design lead. Icons without a maintainer will be quietly altered in conflicts.
In system operation, if system review still waits for someone to complain before changing it, small deviations often accumulate into another way of working.
In brand visual review, if the identification system still means finishing the system and putting it in the handbook, the result is often a complete handbook with daily materials still made separately.
In material review, if logo application is still adjusted by what looks good to individuals, the result is often the same logo losing its task across different materials.