User-Experience-Designer Salesforce Certified User Experience Designer (SP25) Questions and Answers

The best place on the SLDS website for the designer to find accessible HTML and CSS used to create components along with implementation guidelines is the Component Blueprints 1 .  Component Blueprints are framework-agnostic, accessible HTML and CSS that provide the basic structure and style for Lightning components 1 . The designer can use the Component Blueprints to create custom Lightning Web Components that are consistent with the Lightning Design System.  Design Tokens (B) are not the best place to find HTML and CSS, as they are variables that store design attributes, such as colors, fonts, and spacing 2 .  Development Tools © are not the best place to find implementation guidelines, as they are tools and resources that help developers build and test Lightning components, such as VS Code extensions, LWC recipes, and Playground 3 .  References :

Component Blueprints | Salesforce Lightning Design System

Design Tokens | Salesforce Lightning Design System

Development Tools | Salesforce Lightning Design System

 The best way to apply branding to a Salesforce org using Lightning Experience is to create a custom theme in Themes and Branding. Themes and Branding is a feature that allows the administrator to customize the look and feel of Salesforce to match the branding of the organization. The administrator can add logos, default images, and colors to the theme. The administrator can also choose one of the built-in Salesforce themes, or create their own custom themes with just a few clicks. To create a custom theme, from Setup, enter Themes and Branding in the Quick Find box, then select Themes and Branding. Click New Theme and upload the logo, brand colors, and images that follow the company design guidelines.  The administrator can also preview and activate the theme for the entire org  1 .  References:  [Brand Your Org in Lightning Experience] (https://help.salesforce.com/s/articleView?id=sf.brand_your_org_in_lightning_experience.htm & language=en_US & type=5)

To customize the theme in the external customer support site to match the style guide requirements, the recommended next step is to configure the Experience Builder Theme panel. The Theme panel allows the designer to customize the look and feel of the site by setting the logo, colors, fonts, and other branding elements. The designer can also create custom themes and assign them to different pages or audiences. The Theme panel is the preferred way to apply consistent branding across the site without writing any code or overriding any styles.  References : : Theme Panel | Salesforce Help : UX Designer Certification Prep: Designing with Experience Builder | Trailhead

These are three of the four core principles of Web Content Accessibility Guidelines (WCAG), which provide a set of standards and best practices for making web content accessible to people with disabilities. The fourth principle is  Perceivable , which means that the information and user interface components must be presented in ways that users can perceive. The principles are further divided into 13 guidelines and three levels of conformance (A, AA, and AAA).  References :

[Web Content Accessibility Guidelines (WCAG) Overview]

[WCAG 2.1 at a Glance]

The designer should describe SLDS styling hooks as custom CSS properties that can easily style base and custom components. Styling hooks are placeholders in the SLDS style sheet that allow developers to customize the look and feel of their Lightning components by using the corresponding CSS custom properties. For example, the developer can change the background color of a button by setting the value of the --slds-c-button-brand-color-background custom property. Styling hooks are especially useful when working with web components and shadow DOM, as they enable component-level customizations without affecting the global styles. Styling hooks also provide consistency and performance benefits, as they leverage the SLDS design tokens and the native browser support for CSS custom properties.  References :

:  Styling Hooks - Lightning Design System

:  SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers

:  SLDS Styling hooks in Lightning web components - Forcetrails

The designer should describe the Salesforce Lightning Design System (SLDS) styling hooks as using standard CSS properties to easily style base and custom components. SLDS styling hooks allow developers to quickly and easily apply CSS classes to HTML elements, enabling consistent styling across both base and custom components. This allows developers to quickly and easily apply branding and styling to their Lightning Web Components, without needing to write custom CSS. For more information about SLDS styling hooks, please see the following Salesforce documentation: https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styles_hooks

 Voice and tone are two important aspects of UX writing that affect how users perceive and interact with a product. According to the Salesforce User Experience Designer Exam Guide, voice and tone are defined as follows:

Voice  reflects the personality of the brand or product. It is consistent and does not change depending on the context or situation. Voice conveys the values, mission, and identity of the brand or product through the choice of words, phrases, and style of communication.

Tone  reflects the way the voice speaks to the users. It is context-specific and can change depending on the user’s mood, goal, and situation. Tone conveys the attitude, emotion, and empathy of the voice through the use of punctuation, grammar, and formatting.

For example, Mailchimp is a brand that has a distinctive voice and tone. Their voice is friendly, humorous, and quirky. Their tone varies depending on the user’s experience, such as congratulating them for a successful campaign, or apologizing for an error. They use a tone map to guide their writers on how to adjust their tone for different scenarios.

Accordion elements are UI components that allow users to expand and collapse sections of content. They are useful for organizing information in a limited space, such as on mobile devices. However, they also have some usability challenges, such as discoverability, accessibil ity, and navigation. To improve the usability of accordion elements in a mobile environment, two possible ways are:

Include persistent headings. Persistent headings are the labels that indicate the content of each section and allow users to tap on them to expand or collapse the content. Persistent headings should be visible at all times, even when the content is expanded, so that users can easily see the context and switch between sections. Persistent headings should also be clear, concise, and descriptive, so that users can understand what each section contains and decide whether to explore it or not. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]

Only allow users to open one selection at a time. This means that when a user taps on a heading to expand a section, any other previously expanded section should automatically collapse. This prevents the content from becoming too long and overwhelming for the user, and also helps to maintain the focus and hierarchy of the information. It also reduces the need for scrolling and the risk of losing the position of the headings. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]

Nesting an accordion inside of another is not a good way to improve the usability of accordion elements in a mobile environment, because it creates a complex and confusing structure that is hard to navigate and understand. It also increases the cognitive load and the number of taps required for the user to access the information. Using the ‘back’ browser button to collapse content is also not a good way to improve the usability of accordion elements in a mobile environment, because it breaks the user’s expectation and the consistency of the UI. The ‘back’ browser button should be used to go back to the previous page or screen, not to collapse the content within the same page or screen. It also makes it difficult for the user to return to the expanded content if they want to. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]   References:  [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Mobile Design]

 A prioritization matrix is a method that helps UX designers to inform user stories based on user value and development effort. A prioritization matrix is a table that compares different user stories or features based on two criteria: user value and development effort. User value is the benefit or satisfaction that the user will get from using the feature. Development effort is the time, cost, and complexity involved in building the feature. By plotting user stories or features on a prioritization matrix, UX designers can identify which ones are high-value and low-effort, which ones are high-value and high-effort, which ones are low-value and low-effort, and which ones are low-value and high-effort. This helps UX designers to prioritize the user stories or features that will deliver the most value to the user with the least amount of effort, and to deprioritize or eliminate the ones that will deliver the least value to the user with the most amount of effort. A prioritization matrix can also help UX designers to communicate and align with stakeholders and developers on the scope and feasibility of the project.  References :  Prioritize User Stories and Features Unit | Salesforce Trailhead ,  How to Prioritize User Stories (and Build the Right Features) ,  Salesforce User Experience (UX) Designer Certification Guide & Tips

Diversity, inclusion, and equality in design are values that aim to create products, services, and environments that are accessible, welcoming, and fair for all people, regardless of their age, gender, ethnicity, disability, sexual orientation, religion, or other characteristics.  Diversity, inclusion, and equality in design can also bring positive business outcomes, such as economic growth, greater market share, and less employee turnover 1 2 .

Economic growth is a business outcome that represents the increase in the value of goods and services produced by an organization or a country over time. Economic growth can be influenced by various factors, such as innovation, productivity, efficiency, and competitiveness.  Diversity, inclusion, and equality in design can contribute to economic growth by fostering creativity, innovation, and problem-solving, as well as by attracting and retaining diverse talent, customers, and partners 1 2 .

Greater market share is a business outcome that represents the percentage of sales or customers that an organization has in a particular market or industry. Greater market share can indicate the success and competitiveness of an organization, as well as its potential for growth and profitability.  Diversity, inclusion, and equality in design can help achieve greater market share by expanding the reach and appeal of products, services, and environments to diverse and underserved markets, as well as by enhancing customer satisfaction, loyalty, and advocacy 1 2 .

Less employee turnover is a business outcome that represents the rate at which employees leave an organization and are replaced by new ones. Less employee turnover can indicate the stability and quality of an organization, as well as its ability to retain and develop its human capital.  Diversity, inclusion, and equality in design can help reduce employee turnover by creating a positive and inclusive work culture, where employees feel valued, respected, and engaged, as well as by providing opportunities for learning, development, and career progression 1 2 .

A field-level error message is a message that appears next to a specific field when the user enters invalid data or omits required data. It helps the user to correct the error and proceed with the action. A field-level error message is more user-friendly than a validation rule, which displays a generic message at the top of the page and prevents the user from saving the record. A field-level error message can also provide guidance on the correct format and number of digits for the phone number field. Marking the field as required would not ensure that the user enters the phone number in the correct format and with the correct number of digits. Setting a prompt to display on the page using In-App Guidance would not prevent the user from entering invalid data or omitting required data.  References : [Field-Level Error Messages], [Validation Rules] , [In-App Guidance]

A usability study is a method of evaluating how easy and intuitive a product or service is to use by observing real users performing specific tasks. It can help identify usability issues, user needs, and user satisfaction. One of the first steps when planning a usability study is to define the goals of the study, which are the questions that the UX designer wants to answer or the hypotheses that they want to test. The goals of the study will guide the selection of the participants, the tasks, the metrics, and the methods of the study. For example, if the goal of the study is to find out how users navigate the Experience Cloud site, the UX designer might choose to use a task-based usability test with eye-tracking and think-aloud techniques.  References :

: User Experience Designer Certification Prep: Module 4: Analyze User Research Data

: User Experience Designer Certification Prep: Module 6: Validate User Interfaces

The Salesforce Lightning Design System (SLDS) provides component blueprints that will ensure consistency for Cloud Kicks’ functional components. Component blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. They follow the design guidelines, accessibility standards, and best practices of Lightning Experience. They also include variants, states, and modifiers to handle different use cases and scenarios. By using component blueprints, Cloud Kicks can create functional components that are consistent with the look and feel of Lightning Experience without writing custom code or CSS.  References :

Component Blueprints

Introduction to the Salesforce Lightning Design System

 To create a unique experience for each audience that includes colors, images, and typography, the recommended out-of-the-box design approach is to use branding sets and assign them to each audience using audience targeting. Branding sets are collections of branding attributes, such as logos, fonts, colors, and images, that can be applied to a site or a page to customize its look and feel. Audience targeting is a feature that allows the designer to deliver different content and experiences to different groups of users based on criteria such as profile, location, or behavior. By creating branding sets and assigning them to each audience using audience targeting, the designer can easily create a unique and consistent experience for each audience without creating separate sites or custom themes.  References : : Branding Sets | Salesforce Help : Audience Targeting | Salesforce Help : UX Designer Certification Prep: Designing with Experience Builder | Trailhead

The best approach for Cloud Kicks to create a unique look and feel for each audience is to create branding sets and assign them to each audience using audience targeting. With this approach, the same website can be used for both audiences, whilethe look and feel of each page can be tailored to each audience.

Branding sets allow you to create unique designs and apply them to specific audiences. You can create unique colors, images, and typography for each audience and then target them to the appropriate audiences using the audience targeting feature. This will ensure that each audience has a unique look and feel that meets their needs.

The best way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce is to group similar fields using sections. Sections are UI components that allow you to organize fields into logical groups and provide headings and descriptions for each group. Sections help to improve the readability, scannability, and usability of the page layout by reducing the visual clutter and providing a clear structure and hierarchy for the information. Sections also help to align the page layout with the user’s mental model and expectations, as well as the business processes and workflows. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Including all potentially useful fields is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create a crowded and overwhelming interface that is hard to navigate and understand. It can also increase the cognitive load and the scrolling effort for the user, as well as the maintenance cost for the designer. It is better to include only the essential and relevant fields that the user needs to perform their tasks and goals, and use other methods such as related lists, tabs, or modals to display additional information. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Making field labels and API names identical is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create confusion and inconsistency for the user and the developer. Field labels are the text that appear on the user interface to identify the fields, while API names are the unique identifiers that are used by the system and the code to reference the fields. Field labels and API names should be different, because they have different purposes and audiences. Field labels should be clear, concise, and descriptive, using natural language and proper capitalization, punctuation, and spacing. API names should be concise, unique, and consistent, using underscores and camel case to separate words. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

Marking all fields as required is not a good way to ensure the end-user experience when designing a new page layout for a custom object in Salesforce, because it can create frustration and annoyance for the user, as well as increase the error rate and the abandonment rate. Required fields are fields that the user must fill in before they can save or submit the record. Required fields should be used sparingly and only for the fields that are absolutely necessary for the system or the business logic. Marking all fields as required can make the user feel pressured and constrained, and force them to enter irrelevant or inaccurate data. It can also make the user miss the truly important fields, or give up on completing the record altogether. [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]   References:  [UX Designer Certification Prep: User Interface Design Principles], [UX Designer Certification Prep: Salesforce Design System]

 The best option for improving the user experience of looking for and viewing commonly used reports is to update the Home page with access to commonly used reports. This way, the user can quickly access the reports they need without having to use the global search bar every time. This also follows the principle of designing for the user’s goals and tasks, which is one of the learning objectives for the Salesforce User Experience Designer certification.  References : [Design for the User’s Goals and Tasks], [Change or Add Report Chart and Dashboard Components to Home Page]

https://trailhead.salesforce.com/en/content/learn/modules/ux-designer-certification-prep/design-for-the-users-goals-and-tasks :  1

The Web Content Accessibility Guidelines (WCAG) are a set of standards that aim to make web content more accessible to people with disabilities. The WCAG are organized by four principles, which state that content must be:

Perceivable: Users must be able to perceive the information and user interface components in ways they can sense, such as through sight, hearing, or touch.

Operable: Users must be able to interact with the user interface components and navigate the content using various input methods, such as keyboard, mouse, voice, or gesture.

Understandable: Users must be able to comprehend the information and the operation of the user interface, which means that the content must be clear, consistent, and predictable.

Robust: Users must be able to access the content using a wide range of technologies, including different browsers, devices, and assistive tools, which means that the content must be compatible with current and future web standards.  References :  WCAG 2 Overview ,  Understanding the Web Content Accessibility Guidelines

The best place for the team to explore Lightning component code, documentation, and specifications is the Components Library on developer.salesforce.com 1 .  The Components Library is the Lightning components developer reference, where the team can find code samples, SDKs, tools, metadata coverage information, and a developer guide for Lightning Web Components 1 .  The team can also use the live code environment to code their first Lightning web component and see the results in real time 2 . Salesforce Extensions for VS Code (A) is a powerful tool for developing Lightning components, but it is not a source of code, documentation, and specifications. Design Tokens on SLDS website (B) are a way to store and maintain consistent design attributes across different platforms, but they are not specific to Lightning Web Components.  References :

Components Library on developer.salesforce.com

Get Started Coding | Lightning Web Components Developer Guide

 Styling hooks are CSS custom properties that allow developers to customize the appearance of base and custom components in a consistent and supported way. They work with web components and shadow DOM, which provide encapsulation and modularity for LWC. Styling hooks use the  --slds  namespace and follow a naming convention that reflects the component, category, property, attribute, and state of the element being styled. For example,  --slds-c-button-brand-color-background-hover  is a styling hook for the button component, brand category, color background property, and hover state. Styling hooks can be declared in the CSS file of the LWC or in a global CSS file that affects all components on the page. Styling hooks are not standard CSS properties, but custom ones that are defined by SLDS and applied to the components using the  var()  function.  References :

Styling Hooks - Lightning Design System

SLDS Styling Hooks | Lightning Web Components Developer Guide | Salesforce Developers

–dxp Styling Hooks | LWR Sites for Experience Cloud | Salesforce Developers

The Salesforce Lightning Design System (SLDS) styling hooks use standard CSS properties to easily style base and custom components. Salesforce documentation states that “SLDS styling hooks are CSS classes that give you access to the same styling used in the Salesforce Lightning Design System. They make it easy to style base and custom components with the same look and feel” [1] .

[1] https://developer.salesforce.com/docs/component-library/documentation/lwc/lwc.use_slds_styling_hooks

The three standard Salesforce objects that should be used in this experience are:

Lead : A lead is a person who has shown interest in the company’s products or services, but has not yet been qualified as a potential customer. Leads can be captured from various sources, such as web forms, referrals, events, or marketing campaigns. Leads can store information such as name, email, phone, company, and status. Leads can be converted into accounts, contacts, and opportunities when they are ready to buy.

Contact : A contact is a person who is associated with an account and has a role in a sales process. Contacts can store information such as name, email, phone, title, and address. Contacts can be related to multiple accounts, opportunities, cases, activities, and other ob jects. Contacts can be used to track the communication and interaction history with the customers.

Opportunity : An opportunity is a sales deal that is in progress or has been closed. Opportunities can store information such as name, amount, stage, probability, close date, and owner. Opportunities can be linked to accounts, contacts, products, price books, quotes, contracts, and other objects. Opportunities can be used to forecast revenue, manage sales pipeline, and track sales performance.

To view the history of cases that a specific customer has submitted, the representative should go through the following hierarchy of information: All Accounts > Account Detail > Contact Detail > Case Related List. This is because cases are related to contacts, and contacts are related to accounts. By navigating from the account level to the contact level, the representative can see all the contacts associated with a specific account. Then, by selecting a contact, the representative can see the case related list, which shows all the cases that the contact has submitted or been involved in. This way, the representative can view the history of cases for a specific customer in a logical and efficient manner.  References : : UX Designer Certification Prep: Designing with Service Cloud | Trailhead : Service Cloud Basics | Salesforce Help

Two resources that can help a UX Designer to explore sample code for Lightning components and see how changing the code affects the visual appearance in real time, without deploying any code to a Salesforce org, are:

Lightning Design System Website. The Lightning Design System website is a resource that provides design guidelines, UI components, and code samples for building Lightning applications. The website also features a live code editor that allows the designer to edit and preview the code for Lightning web components and Aura components, and see the changes reflected in the browser instantly. The live code editor also provides syntax highlighting, auto-completion, and error checking features. The designer can use the Lightning Design System website to experiment with different code snippets and learn how to apply the design principles and best practices for Lightning components.  Lightning Design System Website , [UX Designer Certification Prep: Salesforce Design System]

Local Development Server. The Local Development Server is a resource that allows the designer to build, run, and test Lightning web components without deploying them to a Salesforce org. The Local Development Server is a CLI plug-in that creates a local web server that serves the Lightning web components from the local file system. The designer can use the Local Development Server to edit the code for Lightning web components in their preferred code editor, such as Visual Studio Code, and see the changes updated in the browser automatically. The Local Development Server also supports hot reloading, which preserves the component state and the browser session during code changes. The designer can use the Local Development Server to speed up the development and testing process and to debug the code for Lightning web components.  Local Development Server , [UX Designer Certification Prep: User Testing and Evaluation]

The Lightning Web Component Recipes App and the Developer Center’s Lightning Component Library are not resources that can help a UX Designer to explore sample code for Lightning components and see how changing the code affects the visual appearance in real time, without deploying any code to a Salesforce org. The Lightning Web Component Recipes App is a sample application that showcases the functionality and best practices for Lightning web components. The Developer Center’s Lightning Component Library is a reference guide that provides documentation and examples for Lightning web components and Aura components. However, neither of these resources allow the designer to edit and preview the code in real time, as they require the code to be deployed to a Salesforce org or a scratch org first.  Lightning Web Component Recipes App ,  Developer Center’s Lightning Component Library , [UX Designer Certification Prep: User Testing and Evaluation]  References:   Lightning Design System Website ,  Local Development Server ,  Lightning Web Component Recipes App ,  Developer Center’s Lightning Component Library , [UX Designer Certification Prep: Salesforce Design System], [UX Designer Certification Prep: User Testing and Evaluation]

 The best way to present Knowledge articles to different audiences is to use page layouts or permissions to display only the fields needed for each audience. This way, the same article can be reused for both internal and external users, but with different levels of detail and visibility. Page layouts can control which fields are shown on the article detail page, and permissions can control which fields are searchable and editable. This is more efficient and consistent than writing separate articles for each audience, which would require more maintenance and duplication. Topics and data categories are different ways of organizing articles, but they do not affect the fields that are displayed. Topics are used for external sites, such as communities or portals, and data categories are used for internal sites, such as the Salesforce app. They can be mapped to each other, but they do not have to be organized the same way.  References :

5 Best Practices for Salesforce Knowledge

The Ultimate Guide to Salesforce Knowledge

How to Write a Good Knowledge Base Article

Prepare Your Salesforce Knowledge Base

According to the Salesforce Lightning Design System, the minimum touch screen target size for interactive elements on mobile devices is 44 pixels wide x 44 pixels tall. This size ensures that users can easily tap the elements without accidentally hitting the wrong ones or missing them entirely. The touch target size also takes into account the average finger size and the device resolution. Smaller touch targets may cause frustration and errors for users, especially those with low vision, motor impairments, or large fingers.  References : : Salesforce Lightning Design System - Sizing : Salesforce Lightning Design System - Accessibility

Dynamic Actions are a feature that allows the UX Designer to customize the actions that appear on the Highlights panel of a Lightning record page based on criteria such as record status, user profile, or field value. This way, the UX Designer can declutter the Highlights panel and show only the relevant actions for each record. Dynamic Actions can be configured in the Lightning App Builder instead of the page layout editor, which gives more flexibility and control to the UX Designer.  References :

Salesforce Dynamic Actions – Overview & Deep Dive Tutorial

Create Dynamic Actions in Lightning App Builder - Salesforce

Add Visibility Rules for Dynamic Pages - Trailhead

 User interface planning is an essential part of the Einstein Bot implementation process, as it involves designing the bot’s appearance, behavior, and interactions with the customers. User interface planning can affect the bot’s effectiveness and customer satisfaction, as it can influence the clarity, efficiency, consistency, and beauty of the bot’s experience.  User interface planning includes 1 :

Choosing a bot avatar and name that match the brand and tone of the company

Configuring the bot greeting and fallback messages that set the expectations and boundaries of the bot’s capabilities

Designing the bot dialogues and menus that guide the customers through the conversation and provide relevant options and information

Testing and iterating the bot user interface based on user feedback and analytics  References :  Einstein Bots Project Planning | Salesforce Trailhead

Customer interviews are a qualitative research method that allows the UX Designer to understand the needs, goals, pain points, and behaviors of the target users. To conduct effective customer interviews, the UX Designer should follow some best practices, such as:

Engage in a friendly and informal way: The UX Designer should try to establish rapport and trust with the interviewee, and make them feel comfortable and relaxed. This can help elicit honest and candid responses, and encourage the interviewee to share more details and stories.  The UX Designer should use a conversational tone, smile, and show interest and empathy 1 2

Ask open-ended questions: The UX Designer should avoid asking yes/no questions, or questions that lead or suggest a specific answer. Instead, the UX Designer should ask open-ended questions that allow the interviewee to express their thoughts and feelings in their own words.  The UX Designer should also probe deeper by asking follow-up questions, such as “why?”, “how?”, or “can you tell me more about that?”  1 2

Listen actively and attentively: The UX Designer should focus on listening to the interviewee, and avoid interrupting, judging, or correcting them. The UX Designer should also use verbal and non-verbal cues, such as nodding, eye contact, and paraphrasing, to show that they are paying attention and understanding the interviewee.  The UX Designer should also take notes or record the interview, with the interviewee’s permission, for later analysis 1 2

Ignore vague or general answers: This is not a best practice, because vague or general answers can indicate that the interviewee is not comfortable, engaged, or clear about the question.  The UX Designer should try to clarify the question, or ask more specific or concrete questions, to elicit more meaningful and relevant responses 1 2

Analyze findings in the moment: This is not a best practice, because analyzing findings in the moment can distract the UX Designer from listening to the interviewee, and bias their interpretation of the data.  The UX Designer should wait until the interview is over, and review the notes or recordings, before analyzing the findings and identifying patterns, insights, and opportunities 1 2

 Confirmation bias is the tendency to seek out and prefer information that supports our preexisting beliefs, while ignoring or rejecting information that contradicts them. Confirmation bias can affect the validity and reliability of user feedback, as it can lead to biased questions, selective interpretation, and skewed results. To avoid confirmation bias in user feedback, Cloud Kicks can follow these two strategies:

Interview users about the intended use of the product to support the questionnaire creation. This can help Cloud Kicks to understand the user needs, expectations, and goals, and to design questions that are relevant, clear, and unbiased.  By interviewing users, Cloud Kicks can also avoid making assumptions about the user behavior, preferences, and pain points, and instead base their questions on real user data and insights  1 .

Diversify feedback by ensuring it features as many unique perspectives as possible. This can help Cloud Kicks to reduce the risk of sampling bias, which occurs when the feedback is collected from a group of users that is not representative of the target population.  By diversifying feedback, Cloud Kicks can capture a wider range of user opinions, experiences, and feedback, and avoid overlooking or dismissing important user segments or viewpoints  2 .

A heuristic evaluation is a method of inspecting the usability of an interface by comparing it to a set of general principles or heuristics. It can help identify potential problems and areas for improvement in the design. A heuristic evaluation is usually done before creating any prototypes, as it can provide insights and guidance for the design process. A low-fidelity prototype is a rough sketch or mockup of an interface that can be used to test and validate design ideas with users. It is usually created after conducting some research and analysis of the user needs and goals. A design template is a pre-made layout or structure that can be used to create an interface. It can help save time and ensure consistency in the design, but it may not suit the specific needs and preferences of the users or the business. A design template is usually applied after defining the content and functionality of the interface.  References :

[Heuristic Evaluation]: This is a Trailhead module that explains what a heuristic evaluation is, how to conduct one, and how to use the results to improve the design of an interface.

[Low-Fidelity Prototyping]: This is a Trailhead module that covers the benefits and best practices of creating and testing low-fidelity prototypes with users.

[Design Templates]: This is a Trailhead module that introduces the concept of design templates and how to use them in Experience Cloud.

 Screen flow is a Salesforce functionality that allows the UX Designer to create interactive workflows for the users with just a few clicks. With screen flow, the UX Designer can create step-by-step workflows that include screens for data entry, decision points based on user input, and automated actions based on their responses. Screen flow can make the user experience more engaging by presenting the users with what they need, when they need it, and using their input to guide them and automate their tasks.  Screen flow can also be customized and embedded in various ways, such as on a Lightning page, a button, a utility bar, or an Experience Cloud page 1 2 3

Lightning Survey is a Salesforce functionality that allows the UX Designer to create and distribute surveys to collect feedback from customers, employees, or partners.  Lightning Survey is not suitable for creating complex processes or workflows, but rather for measuring satisfaction, loyalty, or engagement 4

Process Builder is a Salesforce functionality that allows the UX Designer to create and automate business processes without code. Process Builder can perform actions based on criteria, such as updating records, sending emails, or invoking flows.  Process Builder is not suitable for creating interactive workflows with screens, but rather for automating background tasks 5

 A diary study is a research methodology that involves asking participants to record their thoughts, feelings, behaviors, and activities over a period of time, usually in response to prompts or questions from the researcher 1 . A diary study is suitable for Cloud Kicks (CK) to conduct discovery phase research to understand more about the customers’ purchasing habits, as it will allow them to remotely observe customers’ buying patterns over the course of a 2-month period.  A diary study will also provide rich and contextual data on the customers’ needs, preferences, motivations, and pain points, as well as the factors that influence their purchasing decisions 1 .  References :  Salesforce User Experience Designer Exam Guide ,  Diary Studies: How to Conduct from Start-to-Finish

Consequence Scanning is a workshop method that helps teams to identify and mitigate the potential positive and negative impacts of their products or services on users, society, and the environment. When conducting a Consequence Scanning workshop, two important considerations are:

Consider design ramifications to prevent misuse and protect communities : This means that teams should think beyond the intended use cases and benefits of their products or services, and also consider the possible unintended or harmful consequences that may arise from their design choices. For example, teams should ask themselves how their products or services could be misused, abused, or exploited by malicious actors, or how they could affect vulnerable or marginalized groups, or how they could contribute to environmental or social issues. By considering these design ramifications, teams can proactively address and mitigate the ethical risks and challenges that may emerge from their products or services, and protect the well-being and interests of their users and communities.

Bring together a cross-function group with varied experiences : This means that teams should involve diverse and relevant stakeholders in the Consequence Scanning workshop, such as product managers, designers, developers, researchers, testers, marketers, legal experts, ethicists, users, or representatives from affected communities. By bringing together a cross-function group with varied experiences, perspectives, and backgrounds, teams can gain a more holistic and comprehensive understanding of the potential impacts of their products or services, and avoid blind spots, biases, or assumptions that may limit their vision or judgment. A cross-function group can also foster more creative and collaborative problem-solving, and generate more inclusive and responsible solutions.

Card sorting is a UX research method used to discover how people understand and categorize information. In a card sort, participants group ideas or information written on cards into different categories in a way that makes sense to them. The designer can use virtual cards, pieces of paper, or an online card sorting tool. Card sorting can help the designer to:

Assess the information architecture (IA) of a website or homepage

Learn how people understand different concepts or ideas, and how they feel about them

Understand where users expect certain content to be found

Get inspiration for labeling and grouping content or ideas

In this case, the designer wants to understand the structure and layout of the navigation menu for the Experience Cloud site. The designer can use card sorting to learn how users would group and label the pages or features of the site, and what categories or subcategories they would expect to see in the navigation menu. This can help the designer to create a user-friendly and intuitive IA that matches the users’ mental models and expectations.

To conduct a card sorting activity, the designer should:

Define the goal and scope of the card sort

Choose the type of card sort (open, closed, or hybrid)

Choose the format of the card sort (moderated or unmoderated)

Select the cards and categories to use

Recruit and screen the participants

Run the card sort sessions

Analyze and interpret the results

Apply the findings to the design

The correct answer is B, have users sort the cards based on similar categories or groups. This is the main task of a card sorting activity, where users are asked to group the cards (representing the pages or features of the site) into categories or groups that make sense to them. The designer can then analyze the results to see how users organize and label the information, and use that to inform the design of the navigation menu.

CK can assign learning content to employees using In-App Learning functionality in the following two ways:

Trailmixes : Trailmixes are custom learning paths that can include modules, projects, trails, and even external links. CK can create and assign trailmixes to learners based on their roles, goals, or interests. Learners can access trailmixes from the Learning Home or the Guidance Center in Salesforce.

Modules/Badges : Modules are units of instruction that cover specific topics and skills. Badges are earned by completing modules or projects. CK can assign modules or badges to learners to help them learn specific features or functionalities in Salesforce. Learners can access modules or badges from the Learning Home or the Guidance Center in Salesforce.  References :

:  In-App Guidance in Lightning Experience

:  Learn MOAR in Spring ' 21 with In-App Learning

:  Enable Users to Learn in the Flow of Work

 A service-blueprinting workshop is a process that involves mapping out the flow of a service, identifying the touchpoints, actors, processes, and systems that are involved, and highlighting the pain points and opportunities for improvement. A service-blueprinting workshop is a collaborative and creative way to redesign services with stakeholders, as it allows them to see the big picture, empathize with the users, and co-create solutions. A service-blueprinting workshop is suitable for Cloud Kicks (CK) after they have finished conducting research and synthesizing the findings, as it will help them address the issues uncovered in the study and design better service experiences for their customers.  References :  Service Design Service Blueprints ,  How to create a service blueprinting facilitation guide ,  Workshop exercise: Service Blueprint

 The next phase after discovery, research analysis, and ideation is prototyping, which is the process of creating low-fidelity or high-fidelity representations of the design solution that can be tested and validated with users and stakeholders. To prepare for this phase, the UX designer should determine what to prototype, which means deciding on the scope, the level of detail, the format, and the tools for creating the prototype. The UX designer should consider the following factors when determining what to prototype:

The goals and objectives of the prototype: What is the purpose of the prototype? What questions or hypotheses does it aim to answer or test? What feedback or data does it seek to collect?

The target users and audience of the prototype: Who are the users and stakeholders that will interact with or evaluate the prototype? What are their needs, expectations, and preferences? How will they access and use the prototype?

The features and functionality of the prototype: What are the key features and functionality that the prototype should include or exclude? How will they support the user goals and tasks? How will they demonstrate the value proposition and the design principles of the solution?

The fidelity and interactivity of the prototype: How realistic and detailed should the prototype be? How interactive and responsive should the prototype be? How will the prototype convey the look and feel, the content, and the behavior of the solution?

The tools and methods of the prototype: What tools and methods will be used to create and present the prototype? How will they affect the time, cost, and quality of the prototype? How will they facilitate the testing and validation of the prototype?

Updating the homepage with access to commonly used reports is the best way to make sure the user can quickly accessthe reports they need. This could include making the global search bar bigger on every page, adding the daily task component to the homepage, or creating a mind board to communicate the visual style of the UI. Additionally, Salesforce has some great resources on designing for search, such as their Search Design Guide [1] and their Search Best Practices [2] .

[1] https://www.salesforce.com/content/dam/web/en_us/www/documents/salesforce-search-design-guide.pdf [2]  https://developer.salesforce.com/docs/atlas.en-us.salesforce_search_best_practices.meta/salesforce_search_best_practices/search_best_practices_intro.htm

 The Salesforce Lightning Design System (SLDS) is a collection of resources that help you create user interfaces that are consistent with the Salesforce Lightning principles, design language, and best practices. The SLDS resources that could be used to make custom applications look, act, and sound like Salesforce are:

Blueprints and tokens: Blueprints are ready-to-use HTML and CSS UI elements that provide the foundation for Salesforce experience development. Tokens are visual design values and attributes that ensure branding and UI consistency at scale. By using blueprints and tokens, you can create custom components that follow the SLDS design standards and patterns.

Guidelines for voice and tone: Voice and tone guidelines help you write clear, concise, and consistent content that reflects the Salesforce brand personality and values. By using voice and tone guidelines, you can create custom applications that communicate effectively and respectfully with your users.

The SLDS resources that are not relevant to make custom applications look, act, and sound like Salesforce are:

Full functional components: Full functional components are pre-built Lightning components that provide out-of-the-box functionality and interactivity. They are not part of the SLDS, but rather part of the Lightning Component Library. You can use full functional components to speed up your development process, but they are not necessary to make custom applications look, act, and sound like Salesforce.

In-App Guidance: In-App Guidance is a feature that allows you to create and deliver contextual help and training to your users within your application. It is not part of the SLDS, but rather part of the Salesforce Platform. You can use In-App Guidance to enhance your user experience and adoption, but it is not essential to make custom applications look, act, and sound like Salesforce.

Quantitative research methodology should be used to measure the success and usability of a feature on Experience Cloud. Quantitative research involves collecting and analyzing numerical data that can be measured, compared, or statistically tested. Quantitative research can help answer questions such as:

How many users are using the feature?

How often are they using it?

How long does it take them to complete a task with the feature?

How satisfied are they with the feature?

How does the feature affect key performance indicators, such as conversion rates, retention rates, or revenue?

Quantitative research methods can include surveys, analytics, A/B testing, usability testing, and benchmarking. These methods can provide objective and reliable data that can be used to evaluate the impact and effectiveness of a feature on Experience Cloud.

Qualitative research methodology, on the other hand, involves collecting and analyzing non-numerical data that can reveal users’ attitudes, behaviors, motivations, and preferences. Qualitative research can help answer questions such as:

Why are users using or not using the feature?

What are their pain points, needs, and goals with the feature?

How do they feel about the feature?

What are their expectations and feedback for the feature?

How does the feature fit into their context and workflow?

Qualitative research methods can include interviews, focus groups, observations, diary studies, and card sorting. These methods can provide rich and detailed insights that can be used to understand the user experience and identify opportunities for improvement.

Both quantitative and qualitative research methods are valuable for UX design, but they serve different purposes and answer different types of questions. In this case, the UX designer wants to know if the feature was successful and track usability over time, which are questions that can be best answered by quantitative research methods.

 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 implement 1 . 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 solve 2 .

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.

A UX Designer should take the following steps to create and deliver responsible and transparent AI technology 1 2 :

C. Document model cards to clarify intended context and use cases.  Model cards are standardized documents that provide essential information about a machine learning model, such as its purpose, performance, limitations, and ethical considerations 3 .  Model cards can help UX Designers to communicate the design choices and trade-offs of their AI systems, and to ensure that they are aligned with the user needs and expectations 4 .

D. Provide clear explanations of AI predictions or recommendations.  Explanations are user-facing descriptions of how and why an AI system produces a certain output, such as a prediction, a rec ommendation, or a decision 5 .  Explanations can help UX Designers to increase the transparency and trustworthiness of their AI systems, and to empower users to understand, control, and evaluate the AI outcomes 6 .

A Salesforce Console application is designed to optimize the user experience for service representatives who work on multiple records and tasks at the same time. The console navigation features allow the user to access multiple records and related information in a single screen, without switching back and forth between tabs or windows. The features that are relevant to the designer recommendation are:

More than one detail item can be open at a time. This allows the user to work on multiple records simultaneously and switch between them easily.

Multiple subtabs can be beneath a single parent record. This allows the user to view and access related information, such as activities, emails, notes, and attachments, without leaving the parent record.

A split list of records and individual record detail can be seen on the same screen. This allows the user to browse through a list of records, such as a queue or a report, and see the details of the selected record on the same screen.

The feature that is not relevant to the designer recommendation is:

Service representatives with lower resolution monitors will have a better user experience. This is not true, because a Salesforce Console application requires a minimum screen resolution of 1024 x 768 pixels to display properly. Users with lower resolution monitors may experience scrolling issues or truncated information.

Changing the role hierarchy and reassigning account owners can have a significant impact on the data visibility and performance of Salesforce. An architect should consider the following points in this situation:

Changing complex role hierarchy can cause a high level of sharing recalculation.  Depending on the sharing settings, roles can control the level of visibility that users have into the Salesforce data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless the sharing model for an object specifies otherwise. When the role hierarchy is changed, Salesforce must recalculate the sharing rules and group membership for all the affected users and records, which can take a long time and consume a lot of system resources.  Therefore, changing a complex role hierarchy should be done carefully and preferably during off-peak hours 1 .

Replacing account records ownerships massively can cause data skew.  Data skew occurs when more than 10,000 child records are related to the same parent record, or more than 10,000 records of any object are owned by a single user. This can cause performance issues, such as locking, timeouts, and failures, when updating or sharing those records. When account owners are reassigned massively, it can create or worsen data skew, especially if the accounts have many child records, such as contacts and opportunities.  Therefore, replacing account records ownerships massively should be avoided or minimized 2 3 .

Relationship Design is a creative practice that drives social and business value by building strong relationships. It is based on four mindsets: compassion, intention, courage, and reciprocity. Cloud Kicks can incorporate Relationship Design principles into its business model and customer offerings by adopting these mindsets and applying them to its products, services, and interactions. Some examples of how Cloud Kicks can do this are:

Prioritizing innovation over copying the competition. This shows that Cloud Kicks is courageous and intentional in creating unique and valuable solutions that meet the needs and expectations of its customers and communities.  Cloud Kicks can use design thinking methods, such as empathy mapping, ideation, and prototyping, to generate and test new ideas that solve real problems and create positive impact  1 .

Reframing products in terms of user value over features and functions. This shows that Cloud Kicks is compassionate and reciprocal in understanding and communicating the benefits and outcomes that its products and services can deliver to its customers and stakeholders.  Cloud Kicks can use value proposition design tools, such as the value proposition canvas, to identify and articulate the jobs, pains, and gains of its customers, and how its products and services can address them  2 .

Uncovering customer needs over broadcasting product benefits. This shows that Cloud Kicks is intentional and reciprocal in listening and learning from its customers and co-creating solutions with them.  Cloud Kicks can use user research methods, such as interviews, surveys, and observations, to discover and validate the needs, preferences, and behaviors of its customers, and to involve them in the design process  3 .

These two design considerations should be made when planning for a customer support site in experience builder that will be internationalized across 12 different countries. They are related to the principles of internationalization and localization, which are the processes of designing and adapting a product or service to meet the needs and preferences of users in different cultures, languages, and regions. By taking these considerations into account, a UX designer can create a site that is consistent, usable, and appealing for a global audience.

Country may read text in a different direction (right to left) vs (left to right) and layouts will need to be adjusted: This consideration is related to the principle of bidirectionality, which is the ability of a product or service to support both left-to-right (LTR) and right-to-left (RTL) languages, such as Arabic, Hebrew, Persian, and Urdu. These languages have different writing systems, text alignment, and reading order than LTR languages, such as English, French, Spanish, and German. Therefore, a UX designer needs to adjust the layouts of the site to accommodate both LTR and RTL languages, such as by using flexible grids, mirroring elements, and avoiding fixed positions. This way, the site can provide a natural and intuitive reading experience for users in different countries.

Colors may have different cultural meanings in different countries, changing the intent of UI elements: This consideration is related to the principle of cultural sensitivity, which is the awareness and respect of the cultural differences and preferences of users in different countries. Colors are one of the most important aspects of visual design, as they can convey emotions, moods, messages, and actions. However, colors can also have different cultural meanings and associations in different countries, which can affect how users perceive and interact with the site. For example, red can mean danger, passion, or luck, depending on the country. Therefore, a UX designer needs to choose colors that are appropriate and consistent with the intended meaning and purpose of the UI elements, such as buttons, icons, labels, and alerts. This way, the site can avoid confusion, misunderstanding, or offense for users in different countries.

Einstein Bots and Automated Invitations are two Salesforce features that can boost engagement on Cloud Kicks’ website. Einstein Bots are chatbots that can provide automated and personalized responses to customers’ questions and requests on the website. They can also escalate complex cases to human agents, collect feedback, and provide recommendations.  Einstein Bots can help Cloud Kicks to improve customer satisfaction, reduce wait times, and increase conversions  1 . Automated Invitations are pop-up messages that invite website visitors to start a chat or video call with a service agent. They can be triggered by various criteria, such as time spent on the website, page visited, or customer profile.  Automated Invitations can help Cloud Kicks to proactively engage with potential customers, offer assistance, and generate leads  2 .  References:  [Einstein Bots Basics] (https://ascendix.com/blog/salesforce-sales-engagement/), [Set Up Automated Chat Invitations] (https://bing.com/search?q=Salesforce+features+to+boost+engagement)

To let its users know when a new feature is enabled or available with a short video explaining the new feature, the recommended solution is to use a docked prompt using In-App Guidance. In-App Guidance is a feature that allows the designer to create prompts and walkthroughs that guide users through new or complex tasks in Salesforce. A docked prompt is a type of prompt that appears at the bottom of the screen and can contain text, images, or videos. A docked prompt can be used to announce a new feature and provide a short video tutorial on how to use it. The designer can also set the conditions for when and how often the prompt should appear, and track the user engagement with the prompt.  References : : In-App Guidance | Salesforce Help : UX Designer Certification Prep: Designing with In-App Guidance | Trailhead

 When the organization-wide default for Accounts is private, users can only access the accounts they own or are explicitly shared with them.  However, when the organization-wide default for Opportunities is private, users can access the opportunities they own, are explicitly shared with them, or are associated with accounts they can access 1 . Therefore, when ownership-based sharing rules are created for each team to grant access to opportunities owned by their team members, the sales reps on the same team will also have Read access to the accounts for those opportunities.  This is because the sharing rules for opportunities automatically grant access to the parent accounts 2 .  However, the sales reps will not have Edit access to the accounts, unless the sharing rules specify Full Access for the opportunities 3 . The sales reps will also not have access to all accounts or all opportunities, only those that are owned by their team members or themselves.  References :  Sharing Records Owned by High-Volume Portal Users | Salesforce Security Guide ,  Sharing Rules | Salesforce Security Guide ,  Create Owner-Based Sharing Rules | Salesforce Security Guide

The Salesforce Lightning Design System (SLDS) is a collection of design guidelines, components, and resources that enable developers and designers to build consistent, high-quality, and responsive user interfaces across the Salesforce platform. The SLDS provides UI kits and plugins for popular design and prototyping tools, such as Sketch, Adobe XD, and Figma, that allow designers to quickly create mockups and wireframes using the SLDS components and styles. By leveraging the SLDS, the designer can accelerate the visual design process and ensure alignment with the Salesforce brand and best practices.  References :

[Salesforce Lightning Design System]

[UI Kits and Plugins]

[UX Designer Certification Prep: Visual Design]

When restyling a <</b> lightning-modal / > Lightning Web Component (LWC) to meet brand guidelines, it ' s important to know that styling customization options may be limited. Specifically, only the main Lightning Modal component can be styled using styling hooks. This limitation means that while you can apply brand-specific styles to the overall modal component using styling hooks, the finer control over the modal ' s internal sections (like the body, footer, and header) might not be directly accessible through these hooks. This constraint necessitates a strategic approach to styling, focusing on the aspects of the modal that can be customized to align with brand guidelines while understanding the inherent limitations.