This section presents icebergblue’s insights on UX. These insights have been gleaned from collaboration with a diverse group of designers, developers, stakeholders, and users, as well as participation in conferences and training seminars. The aim is to share valuable lessons and strategies that can help UX designers elevate their craft.
Not long ago, we collaborated with a new UX designer who was curious about creating user personas. To help understand the concept, we proposed two scenarios:
In some cases, identifying the user is straightforward. It’s the person using the product, who can be characterized by attributes such as age, gender, marital status, etc. This approach works well in the first scenario.
However, the second scenario is more complex as it may involve more than just the immediate user. Let’s delve deeper into this scenario: Can the user resolve the issue on their own? Have we designed the product in a way that allows the user to diagnose the problem with the car? Have we made it simple for them to fix the problem? For instance, if the issue is a dead battery, can they easily recharge it? Most of the time, this is a straightforward fix - they can connect the car to a charging station if it’s electric, or get a jump-start from another driver if it’s a gasoline model.
But what if the battery is dead and won’t recharge, despite the user’s attempts?
In such cases, as UX designers, we still have ways to identify the user.
Traditionally, we establish a persona for each use case we encounter, based on specific criteria that align with the user. This approach is effective when identifying the direct user.
Alternatively, we can utilize the ‘Jobs To Be Done’ (JTBD) framework. This approach concentrates on the tasks a user needs to complete a specific job. By shifting our focus to these tasks, we can create more flexible and adaptable personas, simplifying the process of matching any user. The JTBD framework’s scalability allows it to accommodate any new task, thereby broadening its applicability across various scenarios.
It’s important to note that JTBD doesn’t replace user personas, as identifying the user remains crucial. For instance, in the second scenario where the job to be done is to replace a dead battery, several potential users come into play. A car owner with knowledge of their vehicle might be able to swap out the dead battery for a new one. Alternatively, they might need to take it to a mechanic or a dealer, especially in cases where the battery panel of an electric car is completely dead.
In designing a user experience, we need to consider all potential users who will be affected by this issue and who will be involved in resolving it. This could include the car owner, a mechanic, or even roadside assistance services. By taking into account all potential users, we can design a more inclusive and effective user experience.
The recent block from the UK and EU of the Adobe and Figma merger has more affect on UX designers than just the design product. It means that decisions made by one governing jurisdiction can affect other jurisdictions and what decisions you will make.
When Adobe and Figma announced their merger in 2022, designers saw it as the beginning of a new Figma product that would integrate with Adobe's Creative Suite. This would give designers the ability to use Figma's design system tools, variables, developer tools, and their announced AI alongside Adobe's tools.
However, the UK and EU governing bodies saw the merger differently. They considered it a barrier to future innovations for both companies and a potential monopoly on other design tools entering the market. With Figma's dominance in the design space, it raised concerns about Adobe's less impressive XD design tool. Although both tools cater to the same market, Figma has gained a larger market share due to its superior design capabilities. In Fact, Invision has announced their closure recently. Possibly due to that dominance.
With the merger blocked, both companies will continue on separate paths. However, the key takeaway from this article is the impact of jurisdictional decisions. Designers must closely monitor decisions made in other jurisdictions that might affect their work.
This becomes evident with the increasing focus on accessibility, as many jurisdictions have implemented laws to enforce discrimintation against disability. For example, AODA (Accessibility for Ontarians with Disabilities Act) or EAA (European Union's Accessibilities Act) has required companies to make their websites accessible to everyone. Companies were given ample time to update their existing sites to be compatible with various assistive devices such as keyboards, screen readers, and captioning.
Designers and developers have to incorporate ARIA (Accessible Rich Internet Applications) into their code to ensure compliance. As designers, we need to consider accessibility in our designs. We have to ensure proper tabbing and keyboard actions for form submissions and provide appropriate responses that indicate server feedback to both sighted and visually impaired users. Additionally, we have to address the needs of colourblind users who may struggle to differentiate colours used for success, error, and other messages.
Designers now have to consider all these factors in their designs and maintain consistency throughout their websites. There are various ways to address these issues, such as bolding, icons, and strategic placement of messaging. Screen readers can also help mitigate these challenges through the use of specific ARIA tags. However, the overall design still rests in the hands of designers.
The EU’s cookie consent implementation is a prime example of jurisdictional impact. Websites commonly use cookies, but UX solutions vary by region. Language influences design, especially in multilingual countries. English wording is typically shorter than French, Spanish, or German, which must be considered for effective UX/UI design. Designs have to take greater care ensuring that the design does not impact the users' understanding of the page content. Buttons, links, and other design elements that work for English need to be adapted for other languages.
This doesn’t mean designers need to account for every language. However if you need to implement designs for a multilingual country, always factor language in your designs.
In our global economy, decisions made by any jurisdiction can significantly influence how we design and implement our websites. Designers need to stay informed about these decisions to create the best possible sites while ensuring compliance with relevant regulations.
