Pass the Salesforce Designers User-Experience-Designer Questions and answers with ValidTests

 The best way for the designer to help mitigate pushback from developers is to work together on setting up UX Indicators. UX Indicators are a set of metrics that measure the user experience of a product or feature, such as usability, satisfaction, engagement, and adoption1. By working together on setting up UX Indicators, the designer and the developers can align on the goals and expectations of the design changes, and use data and evidence to evaluate their impact. This can help to reduce the subjective opinions and assumptions that might cause pushback, and foster a collaborative and user-centered culture. Sharing research notes from previous projects with them (A) might not be very helpful, as the research might not be relevant or applicable to the current project, and the developers might not trust or understand the research methods or findings. Getting buy-in from the development lead first and let them persuade others (B) might not be very effective, as it might create a top-down or hierarchical approach that does not involve the developers in the design process, and might make them feel excluded or ignored. References:

UX Designer Certification Prep: UX Indicators

 The human-centered design approach is a problem-solving technique that puts real people at the center of the development process, enabling designers to create products and services that resonate and are tailored to the audience’s needs. The human-centered design approach typically involves four stages: clarify, ideate, develop, and implement1. The first stage, clarify, is dedicated to collecting data and observing the users to clarify the problem and how to solve it. Rather than developing products based on assumptions, designers conduct user research and assess user needs to determine what the users want. The clarify stage requires empathy—the capability of understanding another person’s experiences and emotions. Designers need to consider the users’ perspectives and ask questions to determine what products they’re currently using, why and how they’re using them, and the challenges they’re trying to solve2.

Therefore, the activity that should come first in the human-centered design process is observing the medical staff while they use their existing portal. This activity will help the UX designer to understand the context, the goals, the pain points, and the preferences of the medical staff, as well as to identify the opportunities for improvement and innovation. The other activities, such as estimating the cost, writing technical requirements, and designing a mockup, belong to the later stages of the human-centered design process, after the problem and the user needs have been clearly defined.

References: What is Human-Centered Design? — updated 2023 | IxDF and What Is Human-Centered Design? | HBS Online

The first activity inthe process when using a human-centered design approach to redesign a portal that medical staff use to report on patient demographics should be observing the medical staff while they use their existing portal. This is a critical step in the process, as ithelps to identify user needs, preferences, and behaviors so that the design of the new portal can be tailored to meet their specific needs.

Observing the medical staff while they use the portal will help to identify any existing problems and highlightareas where the portal can be improved. This can include issues with usability, functionality, and accessibility. Additionally, observing how the medical staff interact with the portal can help to identify any potential areas of improvement and uncover anyhidden requirements or user needs.

References: [1] https://www.salesforce.com/blog/2019/02/human-centered-design.html [2]  https://uxplanet.org/human-centered-design-process-3d3d3f9a50db [3] https://uxdesign.cc/human-centered-design-for-ux-designers-d4f0e741b9a9

A lookup relationship is a type of relationship that links two objects together, but the relationship is not required. This means that the child object can exist independently of the parent object. A lookup relationship can be either one-to-many or many-to-one, depending on the cardinality of the objects involved. For example, a contact can have a lookup relationship to an account, which means that a contact can belong to one account, but an account can have many contacts. Alternatively, a custom object can have a lookup relationship to a user, which means that a custom object can belong to many users, but a user can have only one custom object record. References: Trailhead: Data Modeling, Trailhead: Salesforce User Experience Designer Certification Prep, Salesforce Help: Define Lookup Relationships