Make the next action easy to understand.
Describe the action
Use labels that explain what will happen. A button called “Save changes” communicates more than an isolated arrow. Keep the wording consistent across forms, navigation and confirmation messages.
Design the other states
Consider loading, empty results, invalid input and success before treating a component as finished. Error messages should identify the problem and help someone recover without erasing their work.
Test the sequence
- Can a new visitor tell where they are?
- Can the action be completed with a keyboard?
- Does the result explain what changed?
Explore the journal for new notes as they are published.