How to Create Icons that Make Sense

Here we present some rules of thumb for those who consider to request new icons.

Using Existing Icons

Don't Misuse Icons!

It confuses our users when the same icon is used for completely different purposes in different places in the system. It is sometimes a good idea to "recycle" an existing icon, but only if the new usage does not contradict the original meaning of the icon.

When/How Is a New Icon Sensible?

Space-Saving

Short, clear terms are better than icons whose meaning has to be learned.

In contrast, groups of terms and long terms can be better represented by an icon.

Easy to Locate

Icons make sense only when you do not have a lot of them scattered around the screen, all competing with each other, and when each icon can always be found in the same place (whenever possible).

Association

Good icons do not necessarily have to be self-evident, but they should make an impression and be easy to learn. This means the picture must be easily associated with its meaning.

Context and Consistency

Good icons clearly differ from their neighbors.

Develop your icons early on, in parallel to the overall design. Also be sure to consider any necessary related icons! Do conflicts exist with other icons/areas?

Internationality and Political Correctness

SAP icons must be comprehensible and acceptable in a wide range of language areas.

Color Legend

Red: Strong warning, stop, error, "Don't!", critical situation
Green: OK, allowed, not critical
Yellow: Advance warning, critical question
Gray: Inactive status

top