More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Ux writing in action
- 2. UX writing in action Tips and tricks to improve microcopy Anja Wedberg & Pieterjan Benoit
- 3. Agenda • Introduction Online shopping gone wrong • Vida.pl homepage • Examples: Video game Contact form 404 page Site navigation page Website icons Request demo form pawelorzech.pl • Takeaways Anja Wedberg & Pieterjan Benoit
- 4. Introduction • Show you UX writing in practice • Highlight a few common issues • Suggest alternative solutions The goal of this workshop is to: The workshop is *not* about: • Pointing fingers • Making anyone feel bad
- 5. Online shopping gone wrong
- 6. Online shopping gone wrong
- 7. Online shopping gone wrong
- 8. Online shopping gone wrong
- 9. Online shopping gone wrong
- 10. Possible improvements 1. Inform user of delivery restrictions straight away 2. Provide newsletter sign-up option to be notified 3. Explain error during check-out flow 10
- 11. Vida.pl – Home page 11
- 12. Vida.pl – Home page 12
- 13. Vida.pl – Home page 13
- 14. Vida.pl 14
- 15. 15
- 17. Vida.pl – Free consultation 17
- 18. Possible improvements • Start with a clear message about the company’s activities • Adjust the text on the ‘Ask about a product’ button to something more general: • Get in touch • Contact us • Move the testimonials further down on the home page • Minimise legal copy by using links • Move the ‘request for free consultation’ further up the page for better visibility • Improve both design and copy of the error messages of the contact form 18
- 19. Game pop-up 19 • ‘Coming soon’ instead of ‘Announcement’ • Text a bit more engaging, e.g. • ‘This game is getting an update! Soon you’ll be able to:’ • The user loses their game process: source of stress. • ‘Unfortunately the update will reset your current game progress. We’ll compensate for that with some in-game goods after the update.’
- 20. Game pop-up 20 • ‘Update’ or ‘Game update’ • Mention the loss of current game progress again: • No unpleasant surprises
- 21. Contact us 21
- 22. Contact form 22
- 23. Contact form – error messages 23
- 24. 404 page 24
- 26. Icons 26
- 27. Request form 27
- 28. Request form 28
- 29. Request form 29
- 30. Possible improvements • Text that explains the error • Translate Polish error text • Explain what email/phone will be used for • Option to give email only • Option to indicate contact preference • Explain benefits of the newsletter • Confirm how often newsletters are sent out • Change Submit to something more specific • Indicate when to expect a reply 30
- 32. Takeaways • Every word matters • Write clear, concise and useful copy • Conversational writing (according to voice & tone) • Anticipate user concerns and frustrations • Consistency throughout the interface • Design and content should work together: • Fonts • Colours • Page layout • Icons • Connected with different business units 32
- 33. Tack så mycket! Thanks a mill! Tusen takk! Dziękuję Ci bardzo!
Editor's Notes
- Mention that our approach is to see every website and digital product as a work in progress – things are changing fast in the industry and it’s good to constantly review, test and improve existing content. Also mention that today’s examples are based on our *assumptions* - this is not recommended practice as in a real-life situation, we would make use of style guides, UX research, company goals etc.
- Always at the bottom of the page. Should be more up
- No consistency in the error messages: Please … This field is required ‘Accept…’ - imperative
- Clients page: icons are only used here, aren’t used throughout the website