There are many instances of “add functionality” across the product. It is effectively a call to action; as such it should be clear and consistent in describing the item to be added.
[Plus icon] + Add + [what is being added]
In other words, it abides by the same style as any CTA:
[Verb] + [Noun]
[Try] + [Free]
|
✅ Do Keep it specific and short.
[+] Add segment |
🛑 Don't Be vague or general – specify exactly what’s being added.
[+] Add value |
|
✅ Do The engineering directors made several important decisions at the meeting. It’s ok to use more than two words if common sense demands it, ie. release group.
[+] Add release group |
🛑 Don't Avoid adding the word “new”. By definition, adding something for the first time makes it new.
[+] Add new value |
|
|
🛑 Don't Be unnecessarily verbose.
[+] Add new task field here |
|
|
🛑 Don't |
Exceptions
There are a few instances where we don’t abide by this rule.
1) Companies (RH navigation of the Features board): here there are two possible legitimate actions, and so we cannot combine them into one descriptor.
|
✅ Do |
|
2) Where there is limited space in the UI, and text would impede clarity, we may use a tooltip or placeholder field.