I'm confident that many UX teams started from a team of one, and progressed through a similar growth process to become larger and more mature UX organizations. I hope that sharing my experience might help others in similar shoes to make their work, and UX maturity progress more efficient.
This is Volume 2 of Examples of Bad UX, a collection of confusing product interfaces, features, and web applications that each of us encounters, unfortunately, too often.
There is no question of how important security and data protection is. The point of my discovery is that even in the most secured application with many layers of protection, there is always a point when a user interacts with the app. And if security-focused requirements affect User Experience in a negative way, making it confusing, unintuitive, or annoying – then users will try to simplify their tasks to avoid the complexity and confusion and will act in the way that will make the security of their data, and the security of the application itself weaker.
We encounter bad UX every day; it could be a tool we use, or confusing feature, application, website… Bad UX slows us down, prevents us from completing the task, or makes us feel frustrated.
Slang, trivia, cultural references, abbreviations, antiquated words, measurement systems - all of that, and more, could be confusing for non-native speakers. Using common and easy to understand rules and references, planning your design with respect to other cultures will help us to create a better, an inclusive User Experience, online and offline.
Do you work in an organization that doesn't have an established UX discipline, a clear owner of UX in the upper management and any shared design practices? If you do - you may have an excellent opportunity to advocate for Users and their needs and start the conversation about the User-centered design process. Bringing the UX process into a project is the first step in that direction.