I am stuck on a usable empty state. I need to design an empty state that explains value and gives one obvious next action, but my current attempt is getting vague and too big. What would you check first?
The checklist I use for a usable empty state
Sharing the wording because it gave me something I could check instead of a confident wall of text.
First, shrink the decision. Do not solve the whole subject at once.
- Name the user decision first.
- Check the keyboard path.
- Remove one competing action.
Write down the result you need by the end of this session. Then choose one input you trust and make a first pass that can be checked. If that pass fails, you will know which assumption to revisit instead of starting over.
The smaller decision was the missing piece. I was asking for the whole system at once.
4 comments
Sign in to join the conversation.