Download Full Version User-Experience-Designer Salesforce Exam

Inclusive design is a design approach that aims to create products and services that are accessible and usable by as many people as possible, regardless of their abilities, preferences, or circumstances. Some of the benefits of inclusive design are :

• Extending access to more users: By considering the diverse needs and situations of users, inclusive design can expand the reach and impact of the product or service. For example, designing a website that is compatible with screen readers can benefit not only users who are blind or visually impaired, but also users who are in low-light environments or have low bandwidth.
• Reducing friction for users in achieving their goals: By removing unnecessary barriers and providing multiple ways of interaction, inclusive design can enhance the user experience and satisfaction. For example, designing a mobile app that supports voice input and output can benefit not only users who have difficulty typing or reading, but also users who are multitasking or have their hands busy. References: : [UX Designer Certification Prep: Designing for Accessibility and Inclusion | Trailhead] : [Inclusive Design | Salesforce Developer Guide]

Inclusive design is a practice of designing products, services, and experiences that are accessible and usable for as many people as possible, regardless of ability, age, gender, race, language, or culture. By incorporating inclusive design practices, you can extend access to more users and reduce friction for users in achieving their goals. Salesforce provides more information on the benefits of inclusive design here: https://www.salesforce.com/blog/2020/11/what-is-inclusive-design.html.

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

The discovery process is a crucial phase in any UX design project, as it helps to understand the user needs, business goals, and technical constraints of the problem1. The discovery process typically involves various research methods, such as interviews, surveys, observations, and analytics, to gather data and insights about the users and the context of use2. The outputs of the discovery process are artifacts that synthesize and communicate the findings and insights from the research. Some of the common outputs of the discovery process are:

• User personas: These are fictional representations of the target users, based on real data and insights, that describe their goals, motivations, pain points, behaviors, and preferences3. User personas help to empathize with the users and design solutions that meet their needs and expectations.
• Journey maps: These are visualizations of the user’s end-to-end experience with a product or service, from the initial trigger to the final outcome4. Journey maps help to identify the user’s actions, thoughts, emotions, pain points, and opportunities for improvement at each stage of the journey.
• High-level wireframes: These are low-fidelity sketches or diagrams that show the basic layout, structure, and functionality of the website or app. High-level wireframes help to define the information architecture, navigation, and content hierarchy of the solution, as well as test the usability and feasibility of the design concepts.

These three outputs are essential for planning out the website redesign using Experience Cloud, as they help to define the user requirements, the user flow, and the user interface of the solution. The other two options, interactive prototypes and high-fidelity mock-ups, are not outputs of the discovery process, but rather of the design and testing phases. Interactive prototypes are clickable simulations of the website or app that allow users to interact with the functionality and features of the solution. High-fidelity mock-ups are realistic and detailed representations of the website or app that show the final look and feel of the solution, including the colors, fonts, images, and icons. These two outputs are created after the discovery process, based on the feedback and validation from the user testing sessions.

References: UX Discovery Process: A Complete Guide, UX Research Methods: How to Uncover Valuable Insight about your Users, User Persona: What It Is and How to Create One, Journey Mapping101, [Wireframes: A Beginner’s Guide], [Prototyping 101: The Difference between Low-Fidelity and High-Fidelity Prototypes and When to Use Each], [What is a Mockup? The Final Layer of UI Design]

For the UX Designer at Cloud Kicks, thethree outputs of the discovery process that should be prepared are User Personas, Journey Maps, and High-Level Wireframes. User Personas are fictional characters that represent a target audience for the website, and are used to help guide the website design. Journey Maps are diagrams that illustrate the user's experience as they navigate the website, and provide insights into how the user interacts with the website. High-Level Wireframes are simple sketches of the website layout, and are used to organize the website's content and design elements. Interactive Prototypes and High-Fidelity Mock-ups are not necessary outputs of the discovery process, as they are more detailed representations of the design that come later in the design process. For more information, see the Salesforce Experience Cloud documentation (https://help.salesforce.com/articleView?id=experience_cloud_overview.htm &type=5).

The Path feature that should be used to add onboarding value for the sales representatives is the Key fields component. The Key fields component allows the admin to specify up to five fields that are important or required for each stage of the Path. The sales reps can see and edit these fields directly from the Path, without scrolling through the record page. This helps to guide the reps on what information they need to gather or update at each stage, and ensures data quality and completeness. The Key fields component can also be used to enforce validation rules or required fields, by preventing the reps from moving to the next stage until they fill out the necessary fields. References:

• : Set Up a Path
• : Considerations and Guidelines for Creating Paths
• : Optimize Sales Processes with Path in Salesforce