У нас вы можете посмотреть бесплатно System messages that don’t explain what happened — UX Problems Guide Class 5.1 или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
In this episode of the Markswebb UX Problems Guide, we explore Class 5 — situations where users don’t understand what the service wants from them. Subclass 5.1 focuses on system notifications that fail to clearly explain what happened or whether any user action is required. System messages play a critical role in the feedback loop between users and digital services. Their purpose is to communicate system states, errors, or background processes in a way that is timely, clear, and actionable. When notifications are vague, generic, or poorly contextualized, users are left guessing — which increases stress and breaks trust. Based on Markswebb’s research, this issue frequently appears in account-related scenarios such as sign-up, login, verification, and plan changes. Generic error messages like “Something went wrong” provide no guidance on what caused the issue or how users should proceed. We illustrate this problem with an example from the Revolut app, where an unclear error message appears after SMS verification during registration. The message does not explain whether the issue is related to verification, timing, or the overall process, leaving users uncertain about their next step. In contrast, Open Talk demonstrates a best practice. When a payment fails, the app clearly explains what happened, what will happen next, and whether the user needs to take action. Visual cues, plain language, and support contacts help reduce anxiety and restore confidence. The video concludes with practical recommendations: making notifications contextual, using clear and unambiguous language, explicitly stating whether action is required, applying visual hierarchy to indicate severity, and testing messages in real user scenarios. Subscribe to stay updated on the next episodes and learn how to design products that truly support real user tasks. Take access to UX Problems Guide by Markswebb: https://uxproblems.markswebb.com/?utm... Learn more about Agency at the Main Website: https://markswebb.com/?utm_source=you... Follow us on LinkedIn: / markswebb Any questions are welcome in the comments.