Scenario 1
"In Lingual, users earn badges that they display on their user profiles. The user earned the Word Wizard badge for adding their first 500 words to their word bank. This is shown after the user completes a lesson."
Delivery method and rationale
New Screen— Since this is a big achievement and we’re at the end of a flow by ending a lesson, it’s appropriate to pause with a final celebratory screen before being guided into the next lesson.
Explaining my copy choices
- The headline was meant to be playful, positive, and magic-themed. Exclamation point, justified.
- A quick, Midjourney assisted badge logo. Inspired by Gandolf.
- The copy under the badge was meant to explain what it means, how it was earned, where to view with a link.
- Next line of copy was to encourage learner to continue. Brand voice included with the magic reference. Using "journey" as a subtle LOTR reference.
- Copy on the CTA meant to clearly set expectations for what is next.
- The text link copy meant to clearly state what happens if that action is taken.
Scenario 2
"The user tries to exit in the middle of a learning session. All session data will be lost if they exit."
Note— I'd question why this would be the case because it seems like not having auto save would be a huge competitive disadvantage. I’d highly encourage the product team to add that ASAP.
Delivery method and rationale
Confirmation Pop-up— Appropriate to interrupt the flow with a pop-up in order to block and confirm a destructive action.
Explaining my copy choices
- I chose to put a text label on the close action in the dialog for accessibility. "Close" the dialog.
- Using a clear headline in the form of question.
- Paragraph copy plainly states what happens if you leave without saving.
- The primary CTA should be to save. We want to encourage them to do so. Answering the headline question in the CTA gives continuity.
- The secondary CTA is to leave without saving, therefore losing progress.
Scenario 3
"The user chose to unfollow a fellow learner."
Delivery method and rationale
Toast— Informational. No need to interrupt the current screen
Explaining copy choices
- Simple, clear language. Going with “You’ve” vs. “You”. I think either would work but “You’ve” sounds better to me.
- Not necessary, but could add a subtext line of “Farewell” or “Safe travels”. A touch of lightheartedness. It’s not that serious.
Scenario 4
"Next lesson can’t load because the user lost internet connection."
Delivery method and rationale
Error Notification— I would call this an alert or error notification that can be dismissed but doesn’t time out on its own. If it’s cleared, the user sees it regenerated if the error happens again and they know that it’s current and not from the previous attempt. The page has a skeletal loading state.
Explaining my copy choices
- The user is blocked. Plainly worded error message stating what’s going on and what they can do.
Scenario 5
"Users have daily word bank goals based on their daily target of new words. For example, a user can set their goal as adding 10 new words per day to their word bank. During a lesson, a user has just met their daily word bank goal and earned a reward: 10 Ling-gems, for use at the Ling-shop. (It’s up to you to decide where in the flow to present this information and how. During the lesson? After a lesson is complete? Only when the user visits their profile? Explain where you chose to put this message and why.)"
Delivery method and rationale
Toast— A temporary message in context is right for this, making a toast a good choice. It’s like a high-five after a three-pointer. An enthusiastic acknowledgement but not high priority at the moment. We don’t need to stop the game. I’m assuming the Ling-gems will also be in an end of lesson summary and in the user’s profile.
Explaining my copy choices
- Using a magic wand emoji to keep the magic theme. Copy is simple, clear, and celebratory. I considered subtext acting as a guide on where to view the gems (in your profile), but decided to leave out, going with the assumption that they would know this from onboarding, and it would get redundant every time.
