Navigation sets
A coherent family for destinations and core actions. Agree visible labels, the number of meanings and the environment in which they will be used.
Discuss this inventoryScope the system
An icon is a shape.
A family needs rules.
Begin with an inventory of meanings and where they appear. The work can then be scoped around the interface, rather than an arbitrary number of symbols.
Utility families
Icons for documents, toolbars and repeated workspace tasks. Define target sizes and the difference between decorative and actionable use.
Discuss this inventoryStatus language
Distinct signals for information, progress or confirmation. Pair shapes with contextual text; a colour change alone is not a complete status.
Discuss this inventorySpecify the handover
before drawing.
- Inventory
- Names, meanings and a reference to the interface context.
- Optical rules
- Grid, stroke, corner treatment and target display sizes.
- Files
- Agreed SVG naming and any required variants, with usage notes.
- Implementation
- Buttons, keyboard operation and accessible names are a separate product responsibility unless explicitly included.