5 exercises — Practice writing helpful, action-driving empty states for first-time zero states, search results, setup flows, social feeds, and billing pages.
0 / 10 completed
1 / 10
A team collaboration tool shows this empty state when a user has no projects: "No projects." What should the empty state include?
Empty states should turn the blank void into an invitation — with context, value framing, and a single CTA.
The empty state's three jobs:
1. Explain the context — what is a project? Why would they want one?
2. Set the zero-state expectation — this is normal, everyone starts here
3. Provide one clear CTA — the exact next step to fill the empty state
Option A — motivational quotes are a UX anti-pattern; they don't help users accomplish anything
Option B — deflecting to admin is only appropriate for enterprise tools with strict provisioning models
Option D — explains via navigation instruction; verbose; no clear CTA
Option C ✓ — contextualizes + invites action in a visually engaging way
Empty state principles:
• If it's a first-time state, explain the value before asking for action
• If it's a search/filter result empty state, offer to reset filters or broaden search
• If it's a loading/error state, distinguish clearly from empty data
Key vocabulary:
• Empty state — the UI state shown when a section has no content yet
• Zero-state design — designing specifically for first-time users who have no data
• Activation CTA — the CTA that triggers the first meaningful user action
• Value framing — explaining the benefit of a feature before asking users to set it up
2 / 10
A user uses the search feature and gets no results for "onboarding checklist template". Which empty state copy is best?
Search empty states should echo the query, suggest recovery actions, and offer an alternative path.
Three elements of an effective search empty state:
1. Echo the query — "No results for '...' " confirms the system processed their input
2. Suggest a recovery — "Try a shorter search" provides a concrete fix
3. Offer an alternative path — "Browse all templates" prevents a dead end
Option A — doesn't confirm what was searched; doesn't help them recover
Option B — better (echoes query) but offers no path forward
Option D — too long; "not indexed correctly" is system-language that shifts blame onto the user or the system
Option C ✓ — all three elements present in one sentence
Key vocabulary:
• Search empty state — the result when a search returns no matches
• Query echo — including the user's search term in the empty state message to confirm it was received
• Recovery suggestion — advice to modify the search that led to no results
• Alternative path — a link or CTA that offers a different way to find what the user needs
3 / 10
A data analytics dashboard shows an empty state because the user hasn't connected a data source yet. Which empty state best drives setup completion?
Setup empty states should create anticipation of the value users will see, not just state the prerequisite.
The difference between B and C:
• B ("Connect a data source to see analytics") — transactional, flat; frames the empty state as a problem
• C ✓ — "your dashboard is ready" (it's prepared for them, not broken); "come alive" creates anticipation; CTA is direct
The framing "your [thing] is ready" is a powerful setup empty state pattern — it tells users:
• This is a normal, intentional starting point
• Something good is about to happen
• You're one step from value
Option D — navigation instruction in copy is a deep anti-pattern; if connecting requires 3 menu clicks, the CTA should take them there directly.
Key vocabulary:
• Setup empty state — an empty state that requires user action (configuration, connection) to resolve
• Anticipation framing — using aspirational language to make users excited about completing setup
• Direct CTA — a link or button that takes users to the setup page in one click
• Navigation antipattern — describing a navigation path in text instead of providing a direct link
4 / 10
An activity feed on a social coding platform is empty for a new user. Which empty state copy best encourages engagement?
Social empty states should acknowledge the quiet moment without negativity, then invite the action that fills it.
Analysis:
• Option A — "No activity yet" — no context, no path forward
• Option B — passive future tense ("will show") — no CTA
• Option C — good: action-oriented CTA; specific about content types; but slightly instruction-heavy
• Option D ✓ — "quiet" is a soft, non-alarming way to describe the empty state; the CTA is prominent; content types are listed to motivate
"Your [thing] is quiet right now" is a popular and effective empty state pattern that:
• Normalizes the state (quiet, not broken)
• Doesn't imply the user has done something wrong
• Creates room for the CTA to feel like an invitation, not an obligation
Key vocabulary:
• Social empty state — empty state on social/community features that depend on user connections
• Soft empty state language — non-alarming framing like "quiet" or "empty" vs. "no data" or "no activity"
• Content type enumeration — listing specific types of content that will appear to motivate setup
• Network effect empty state — an empty state caused by not having enough connections yet
5 / 10
A billing history page is empty because the user is on a free plan and hasn't made any purchases. Which empty state is best?
Billing empty states on free plans are a conversion opportunity — but the tone must be informative, not pushy.
This empty state sits at the intersection of utility and business goal:
• Utility: explain why the page is empty (free plan = no invoices)
• Business goal: surface the reason to upgrade without being aggressive
Option B — accurate but ends in a dead end; no path to explore or upgrade
Option C — frames "no billing history" as a problem to solve; feels pushy
Option D ✓ — explains the state; offers two non-aggressive CTAs: "see what's included" (low commitment) and "upgrade anytime" (higher commitment, low pressure)
The "anytime" in "upgrade anytime" is a subtle pressure-reducer — it communicates "there's no urgency, do it when you're ready."
Key vocabulary:
• Billing empty state — the page state shown before first purchase or on a free plan
• Conversion opportunity — an empty state that can surface an upgrade CTA without being intrusive
• Low-commitment CTA — a CTA that requires minimal decision ("see what's included") before a higher-stakes action
• Pressure-reducing language — copy that removes urgency ("anytime", "whenever you're ready")
6 / 10
Alex (Lead Developer) just left a comment on your code review: 'This feature isn't showing any data. The empty state needs to guide the user towards checking the API endpoint configuration.' Which of the following copy options would be most effective in this situation?
The key here is to directly address Alex's concern – the missing data. Option 1 clearly directs the user to check the configuration, which aligns with his comment. Options 2 & 3 are too technical and potentially intimidating, while option 4 offers generic troubleshooting advice without focusing on the immediate problem.
7 / 10
You're designing the empty state for a new user onboarding flow within our internal developer portal. The portal currently has no features enabled and you want to encourage them to start using it. Which of these options is most suitable?
The core goal is to encourage initial action. Option 1 provides a simple and direct call to action, while options 2 highlights the potential of the platform without being overwhelming. Options 3 is negative and demotivating, and option 4 offers support when it's not necessarily needed at this stage.
8 / 10
You're writing the description for a Slack message displayed in a channel when a new user has just created a project. The project is empty and contains no tasks. What's the best approach to the copy?
The goal is to provide context and a gentle nudge. Option 2 clearly states the action that needs to be taken. Options 1 & 3 are too celebratory or overly descriptive, while option 4 uses a literal code ID which isn't helpful for a new user.
9 / 10
A backend service returns the following JSON response when no data is available in an API endpoint: {"status": "empty", "message": "No results found."} You're designing the empty state for this scenario. What copy would be most appropriate to display?
Given the JSON response, 'No results' is the most direct and concise translation. Options 2 & 3 are overly verbose, while option 4 suggests a technical issue that isn't necessarily the case.
10 / 10
You're building an empty state for a new feature: 'Automated Code Reviews'. A developer hasn't configured any rules yet. What copy best encourages them to set up these reviews?
Option 1 clearly states the current state and offers a positive call-to-action. Options 2 & 3 are slightly more direct but still encouraging. Option 4 is passive and doesn't motivate the user to take action.
This exercise, "Empty State Copy", tests your understanding of ux writing vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this UX Writing exercise for?
It's designed for IT professionals and learners who want to sound natural discussing ux writing topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more UX Writing exercises?
Browse the full UX Writing exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.